Very odd ship-specific low-fps issue

Scoob

Scoob
Hey all,

Wasn't going to share this, but it's still on my mind.

FPS is generally really good for me, not dipping below the 60hz limit I've set. I don't really do on-foot stuff, my actions are largely limited to things I could do in Horizons, but I do use the Odyssey client.

Anyway, I went back to my carrier the other night and, looking through my available ships decided to jump into my Cutter. The instant I switch to the cutter - and bear in mind I've literally just selected it from my available ships - my FPS absolutely tanks to like 10 - 12 fps and stays there. Everything works, but even navigating menus is horrible. I switch to another ship and all is well again.

What about my Cutter could possible cause such an fps drop before I've even taken it out of the Carrier? I didn't go back to the Cutter again that evening, out of time, but it did puzzle me. When I get the chance (hopefully some time this week) I will try this again, and see if fps dips once more. I didn't take the Cutter out of the hangar as the game would have been totally unplayable, and that low an fps gives me almost immediate eye strain, soon followed by nausea as I'm particularly sensitive to such things.

Not really expecting a definitive answer here, more wondering if anyone else has ever experienced odd ship-specific fps issues like this.
 

Rat Catcher

Rat Catcher
That's strange, @Scoob

I'll take a peek with one of mine.

Nope: Not for me...
Screenshot_0002.jpg


Screenshot_0003.jpg

The FPS was going between 230-240 (1440) so pretty much identical.
 
Last edited:

Scoob

Scoob
Thanks for checking @Rat Catcher.

I'm using the midnight black paint job on this particular Cutter - not that I can see the said paint job when sat in the cockpit while in a menu. I did go to the outfitting screen, so the fps drop was there also, but fps dropped the moment I switched to the ship, then went back to normal the moment I switched away. Weird.
 

Rat Catcher

Rat Catcher
Scoob said:
Thanks for checking @Rat Catcher.

I'm using the midnight black paint job on this particular Cutter - not that I can see the said paint job when sat in the cockpit while in a menu. I did go to the outfitting screen, so the fps drop was there also, but fps dropped the moment I switched to the ship, then went back to normal the moment I switched away. Weird.
Click to expand...
I've the midnight black on my Cutter too...
I'll nip back in and replicate going to outfitting in a few minutes, will keep you posted!
 

Scoob

Scoob
Just heading back to my Carrier to test this out again...fps currently just fine.

Edit: Well, everything is perfectly fine now. Must have been a random coincidence that switching to this ship previously impacted fps as it did...then switching back (to an Anaconda) saw things normal again. Weird.

I don't recall ever having to clear any Caches before, exactly where are they located?
 
Last edited:

dannysquid

dannysquid
Is it possible something like this might be caused by it struggling to deal with a particularly large texture that needs to be loaded in?
 

Scoob

Scoob
dannysquid said:
Is it possible something like this might be caused by it struggling to deal with a particularly large texture that needs to be loaded in?
Click to expand...

Could be, I really don't know. Performance is generally good for me, and I've never seen such a severe fps drop before, certainly nothing that seems to be linked by changing ships. Still, who know what other stuff is going on in the background with Windows. I have noticed for a while now that Windows can be very slow at purging Standby memory when RAM is full and it's needed for other things. I use a small tool to manually do this at times, and it can really help - didn't appear to be the culprit this time though.
 

SSMYT

SSMYT
Scoob said:
Just heading back to my Carrier to test this out again...fps currently just fine.

Edit: Well, everything is perfectly fine now. Must have been a random coincidence that switching to this ship previously impacted fps as it did...then switching back (to an Anaconda) saw things normal again. Weird.

I don't recall ever having to clear any Caches before, exactly where are they located?
Click to expand...
C:\Users\******\AppData\Local\Frontier Developments\Elite Dangerous and C:\Users\******\AppData\Local\NVIDIA\DXCache
If you have AMD, i dont know
 

Scoob

Scoob
SSMYT said:
C:\Users\******\AppData\Local\Frontier Developments\Elite Dangerous and C:\Users\******\AppData\Local\NVIDIA\DXCache
If you have AMD, i dont know
Click to expand...

Thank you, I do have an NV card, yes.

So, is this one of those folders you clear down if you experience a specific issue, or one you clear down regularly as a matter of course to avoid potential issues? I don't recall ever touching this folder nor its contents previously.
 

SSMYT

SSMYT
Scoob said:
Thank you, I do have an NV card, yes.

So, is this one of those folders you clear down if you experience a specific issue, or one you clear down regularly as a matter of course to avoid potential issues? I don't recall ever touching this folder nor its contents previously.
Click to expand...
normally it is a folder that must be cleaned in each driver update, since elite generates the shaders again, also in each elite update since they can be corrupted and it is recommended, "that happened to me with 1.10", also yes you have extra space on the Windows Disk I recommend you go to the nvidia panel and set the shader cache to 10 GB, so that the GPU does not delete the cache that you are going to use and has to regenerate it, since normally the cache does not exceed 4 GB but if you play games in DX12, vulkan or games like elite that despite being DX11 use cache, this limit is exceeded and starts deleting old caches that you may need and must regenerate them since another game deleted them to occupy their space, In addition to the fact that in each new driver the way of generating cache changes, the shader cache is different for all PCs even if you have the same gpu, since it generates it thinking about your CPU, ram etc and when you update, the code is updated , for this reason it regenerates it, deleting it forces to generate them in a clean way and not to use obsolete ones, also the shader cache is used by windows and browsers, remember that since a browser or windows itself can overload the cache, that's why the limit 10gb
 

Scoob

Scoob
I have my shader cache set to 10GB - a tip a while ago from the SC community - seemed to make a slight improvement. Game runs like carp again since the 3.17.x updates though lol. I did actually change my GPU recently (1070 to 3070) so I should double-check nothing's been reset. I'll give a folder a quick purge regardless.
 

SSMYT

SSMYT
Scoob said:
I have my shader cache set to 10GB - a tip a while ago from the SC community - seemed to make a slight improvement. Game runs like carp again since the 3.17.x updates though lol. I did actually change my GPU recently (1070 to 3070) so I should double-check nothing's been reset. I'll give a folder a quick purge regardless.
Click to expand...
if you change GPU, nvidia automatic change cache shader, and, I also put that limit for SC and everyone was better for me
 

Cmdr64

C
Scoob said:
Hey all,

Wasn't going to share this, but it's still on my mind.

FPS is generally really good for me, not dipping below the 60hz limit I've set. I don't really do on-foot stuff, my actions are largely limited to things I could do in Horizons, but I do use the Odyssey client.

Anyway, I went back to my carrier the other night and, looking through my available ships decided to jump into my Cutter. The instant I switch to the cutter - and bear in mind I've literally just selected it from my available ships - my FPS absolutely tanks to like 10 - 12 fps and stays there. Everything works, but even navigating menus is horrible. I switch to another ship and all is well again.

What about my Cutter could possible cause such an fps drop before I've even taken it out of the Carrier? I didn't go back to the Cutter again that evening, out of time, but it did puzzle me. When I get the chance (hopefully some time this week) I will try this again, and see if fps dips once more. I didn't take the Cutter out of the hangar as the game would have been totally unplayable, and that low an fps gives me almost immediate eye strain, soon followed by nausea as I'm particularly sensitive to such things.

Not really expecting a definitive answer here, more wondering if anyone else has ever experienced odd ship-specific fps issues like this.
Click to expand...
For the hell of it. Reset your bios to defaults. This fixed all my issues. No clue why. Not all games had problems either.
 
You must log in or register to reply here.
Back
Top Bottom