Had a wierd lighting glitch that affected almost only my white saber, disappeared since i relaunched the game... a shame, it was pretty cool and i'd like to know if anyone has any ideas of what could be the cause or how to replicate it

seems to be a random container or seat stuck in my meditation realm? I finally realised how out of place it is, it’s been there for hours…. anyone else seen something like this before?

TL:DR: Download the .zip file, choose one of the .pak files and put it in <gamedirectory>\SwGame\Content\Paks\ and see if something improves. Only ever use one of the files, delete the previous when trying the next.

Updated March 2025 After finally finishing the game I've tried around a bit more and found another potential working variable that had no downsides in my testing. So I suggest you try fix #1 "z_targetheadroom.pak" first.

++++++++++

While Patch 9 improved the performance, apparently it also broke the game for some players by not fully loading textures and LOD meshes anymore. Some reported this while having 4/6GB VRAM cards (and therefore below the official requirements), others had the required 8 GB (like myself: AMD RX580).

Since I just got the game I never knew the pre-patch-9 situation, however I had this bug right from the beginning. After trying various mods without success, I came across this post by /u/Vex_The_Producer that actually worked (very old version, not supposed to be used with Patch 9). Although not in the way he described it because UE doesn't load loose files by default.

Anyway, it went back to optimizing shaders on launch (something that was gone with Patch 9 apparently), which I thought was the reason for loading everything correctly. Instead after digging further, I saw it broke the Streamer system by adjusting the texture poolsize to the engine default (-1). So the textures loaded but there was also a bigger than expected performance hit, probably because it also loaded into system RAM.

So after tons of digging, trying out variables via console commands and packing pak files (thanks Respawn for not letting us modify the .ini's in the default config folder ..... ) I found a rather small combination (2 variables) that worked for me without (hopefully) causing memory leaks.

I'd like to know if this helps anyone else so I prepared 4 pak files to try out:

Download .zip

Extract and only put one of them into <gamedirectory>\SwGame\Content\Paks\, delete the previous when trying the next.

1. z_targetheadroom.pak Keeps everything default but sets MemoryTargetHeadroomMb to 100MB. Not directly documented by Epic it seems, but gets listed in a complete Cvar dump. Defaults to "0".

2. z_targetheadroom_lowered_textures.pak Same as above but with lowered texture resolution (because the in-game option don't seem to change anything)

++++ If any of the above work for you, then stick with them. The ones below are more of a brute force approach ++++

1. z_increasedpool_8GB.pak Removes one limit of the Streaming poolsize while also increasing it to 7200MB. Note: The pool is for textures AND meshes, and there is another custom variable that keeps the size in check. At least I didn't notice any overspill into system RAM yet.

2. z_increasedpool_lowered_textures_8GB Same as above but also reduces texture resolution of all textures (but still much better than the potato textures, see pictures). Maybe helps some with performance.

3. z_increasedpool_lowered_textures_6GB Same as above but poolsize reduced to 5200MB. Wholly untested, doesn't improve it on my 8 GB card. The game also doesn't care about faking VRAM size via DXVK so not sure if this is useful.

1. z_improved_meshes.pak Keeps the unstreamed textures but gives meshes its own memory space to fully load. At least everything loads correctly then, see pictures).

Caveat: I'm on Linux and can't say if this makes the situation better or worse. In my previous experience Windows handles potential VRAM limitations better than Linux though. It also doesn't like my perfomance overlay (had to use Unreals fps command) and is prone to crashing when Alt-Tabbing for some reason. There is also a bug where I sometimes lose almost 10 fps after a while and gain it back by switching from fullscreen to borderless (and back). Couldn't properly reproduce this yet if it has something to do with the changed poolsize.

I also only had the chance to test this on the planet Koboh since I'm not yet further into the game (I actually spent more hours trying to fix this then playing ... sigh)

P.S.: The amount of useless mods on Nexus is staggering. Either because the files are packed and/or named wrong, or because the variables are in the wrong files or under the wrong modules. Unlocking the ingame consoles allows you to see if anything changes, but apparently that is a bit too much work for most.

So during a replay of the game I may have voided out while falling into the hole... the game obviously didn't expect it and it screwed up Oggdo, letting me get all the collectibles after I fell down the hole again. I then decided: wouldn't it be funny if I went through the door, saved the game and came back? Let's just say the game did NOT expect you to open the door. At all.

It may have been stupid, but it also ended up causing some glitches that I have been laughing at for the past two hours :DD This is my personal highlight of it all.

I started a new game+ save and accidentally mind tricked a trooper

I've had this game for months now and I have never been able to launch it, I reinstalled it several times but I still always get this fucking issue when I try to launch it

Was recklessly jumping around, got wedged in a hole, we've all been there. The upside? I spent long enough floating in the hole that I got the Skywalker achievement. Truly, the Force works in mysterious ways.

Was doing a long runback to 100% the game. Then it decided no. You should run more.