In your case it is almost unnoticeable. In mine, it is quite noticeable:
I've also realized that the stutter occurs even when the planet is not in view:
You can hear the moment of the 1st impact when the freeze occurs in the 2nd video.
Stuttering, FPS drops, etc
- Thread starter Andromeda456
- Start date
-
- Tags
- fps performance stutter
In your case it is almost unnoticeable. In mine, it is quite noticeable:
I've also realized that the stutter occurs even when the planet is not in view:
You can hear the moment of the 1st impact when the freeze occurs in the 2nd video.
Yes thats it. I didnt know how to say that in English.
I'm not entirely sure what "FOV-pop" is.
Any way you could catch this on video?
Is this with standard vsync at 60Hz?
Vsync within game is set to off. Refresh Rate and frame rate limit (again withing game options) are set to 60Hz.
Vsync from the NVIDIAs settings for the elitedangerous64.exe is set to fast. It was exhibiting the same behavior even before I used your suggestion to set it to fast.
I remember setting Vsync from within the game to on (a few years back iirc..) and fps dropped from 60 to 30. At least now I don't have the screen tearing..
I am also running a few side apps in the background - maybe one or more of these have an impact I don't know. Namely these are EDDI,
ED Discovery, EDMC, OBS (recording constantly replay buffer (2GB RAM space reserved)) and browser (Firefox latest version) with Inara and EDDB sites loged in my account(s). All apps are all up-to-date to their latest versions. RAM usage as reported by Task Manager is ~50%-55%, VRAM usage as reported by GPU-Z is also around ~50-55%. CPU is ~ 15-20% with occasional spikes to ~25%-30%.
Last edited:
I think this is the problem.
I get the least stutters when I set in game Vsync and frame rate limit OFF, using Nvidia adaptive Vsync (adaptive because my setup isn't powerful enough for 60 FPS everywhere, anytime).
PS: EDDI is definitely a major contributing factor.
Last edited:
"Fast" works best with an uncapped frame rate.
Not particularly surprising, given what it's doing.
The reason I am using a frame rate cap is because I read somewhere in the past (and not exclusively to E: D), that putting a fr cap is freeing up resources for the GPU and this results in a smoother less jaggy / stuttery game exoerience as the GPU has more time to allocate to different tasks. That was a long time back though. I've also noticed (and that is in relation with the above) that the GPU usage is not at ~100% all or most of the time, and consequently running a bit cooler, when there is a fr cap. And because I am in a difficult financial situation I am doing this with the hope that my GPU will last longer and not break until I have the means for an equivalent replacement (rtx 2080ti cough cough ahhm..).
Anyway at least now I found a major suspect.
Capping the frame rate will indeed reduce load, power consumption, and make the card easier to cool. However, it will generally not result in a smoother experience vs. uncapped and fast sync relies on frame rate running higher than refresh rate.
I wouldn't worry too much about longevity. You aren't going to kill it by running it within spec, at any load, unless it's a bad sample.
I've got two 580s sitting in their boxes and RIP. Never overclocked them, only used them in SLI back in ~2014 early 2015 to drive my 3 display setup in NVIDIA surround (2D, not 3D) configuraiotn. After a couple of months a bad smell started coming out from the back and PC froze. Cards died. Another 780 ASUS Stryx edition 6gb is also in its box, still functional but with issues after ~ 2&1/2 years of service. It started with random PC freezing. Substituted with a friends similar one and all OK. Send back to eshop which I bought it from. They supposedly tested it and claimed it didn't produce an issue on them and send it back. Got a temporary 960 in the interim until I had enough cash to afford my current 1080ti. Can't afford to loose it now. Frame rate cap will remain. I've also deliberately thermal throttled it through its utility to drop its power consumption & frequency once temp reaches 75C as well as its fan running at full speed once temp reaches ~67C. In my country we have a saying: If you get burned many times you blow the yogurt.
Last edited:
Failure rates tend to follow a bathtub curve, where a significant minority of samples make it through QA with defects, and thus tend to fail early on. Failure rates then fall dramatically as those samples are weeded out, rising again years later as parts finally start to wear out.
I recommend testing any new part extensively to make sure it's not a defective sample. Most shops allow easier returns within the first month or thereabouts, so for the first several weeks I have something I'm hitting it with cycles the harshest tests I can find, pushing them to their limits and thermal cycling them hundreds of times. I've killed many dozens of video cards, but if they last that first month in my hands, the odds of them failing in the next five years are quite slim. Indeed, I can count on one hand the number of video cards I've had die after I moved them out of my test boxes into active service.
If the quality of the part is still in question and you can't afford to lose it, there isn't much you can do now. However, in the future, I'd recommend making sure you aren't stuck with a defective sample, so you don't have to fear losing something if you actually use it to it's full potential.
A faulty or PSU can damage components connected to it, and loads in excess of what the PSU can deliver can cause problems, but these almost never present as performance issues. Stuff tends to shut off (over/under current/voltage protection on either end), or suffer excess wear until it become blatantly unreliable. Far more likely to see restarts or crashes than stuttering or other application performance problems, if the PSU is or has been the issue.
PSU in my case was and still is a 1200Watt Corsair (~250-270€ / ~300$). I don't think it was the issue in my case. My PC case is also a thermaltake armor+ full tower with ample space and equiped with 6 Noctua fans. Not counting the CPU cooler's 2 additional fans. So the GPUs didn't have an excuse to fail. They were bad samples and I was just unlucky to get them.
About stress testing in the 1st month of purchase, yes I do it also but not so excessively as you describe. I run a few benchmarks but I don't stress them continuously for the whole night or many hours. Generally it is more likely for a component to fail if you stress - idle - stress - idle - stress - idle and so on. That's what a modern demanding gaming environment does. During gameplay the GPU is not constantly under 100% load - it fluctuates. That puts a lot of stress in it. So I run a benchmark then wait a couple of mins then run another one. That's why I chose to reduce its max boost frequency to Nvidias factory default values - cause every GPU manufacturer default OCs its cards a small %. I don't like that. And also I manually thermal throttle it to my liking. Yes I may loose a few fps but better loose a few fps than the GPU
.
About stress testing in the 1st month of purchase, yes I do it also but not so excessively as you describe. I run a few benchmarks but I don't stress them continuously for the whole night or many hours. Generally it is more likely for a component to fail if you stress - idle - stress - idle - stress - idle and so on. That's what a modern demanding gaming environment does. During gameplay the GPU is not constantly under 100% load - it fluctuates. That puts a lot of stress in it. So I run a benchmark then wait a couple of mins then run another one. That's why I chose to reduce its max boost frequency to Nvidias factory default values - cause every GPU manufacturer default OCs its cards a small %. I don't like that. And also I manually thermal throttle it to my liking. Yes I may loose a few fps but better loose a few fps than the GPU
.I wonder if I change processor affinity for the suspicious application (EDDI) through task manger it may help.
Another app completely unrelated with ED was momentarily freezing when taking screenshot with its internal screenshot capture key. The developer of this app moved the screenshot process to a different cpu thread and stuttering was gone. Of course this was internal re-coding of the same app - here we have 2 different apps. Just thinking aloud here.. probably I am saying nonsense..
PS: OK I am running crazy: Today there is no stutter/ lag whatsoever. I am running all my usual background apps (namely EDDI, EDMC, ED Discovery & OBS recording 2GB replay buffer, Firefox on, no stutter at all.. BUT I noticed that there is no sound upon probe impact on planet surface. What th is going on??
Last edited:
Eventually yes. The momentary freezing upon 1st probe impact has returned. I've also noticed similar momentary freezes upon approaching planets with geo, bio and generally surface POI. Planets that I have already mapped in inhabited systems. The momentary freeze is followed by EDDIs voice initiation. At least most of the times. Anyway I think I am chasing the dragon here. Other people have more serious issues like the OP for eg. I can live with this.
Hello folks,
I'm getting this stuttering and FPS lowering problem too. It happens to me in a RES while shooting pirates. I had my settings on ultra and lowered them to medium and it got a lot worse.
I have tried restarting the game and it seems to help for at least a little while.
It also seems to be worse after I installed the latest graphics drivers.
I was hoping to play the game with the steam VR device but the stuttering would drive me nuts. It stutters a lot worse when I turn the ship fast.
AMD Threadripper 16-core CPU (1950X)
AMD RX 5700
It's an interesting problem. Hopefully they will fix it someday.
I'm getting this stuttering and FPS lowering problem too. It happens to me in a RES while shooting pirates. I had my settings on ultra and lowered them to medium and it got a lot worse.
I have tried restarting the game and it seems to help for at least a little while.
It also seems to be worse after I installed the latest graphics drivers.
I was hoping to play the game with the steam VR device but the stuttering would drive me nuts. It stutters a lot worse when I turn the ship fast.
AMD Threadripper 16-core CPU (1950X)
AMD RX 5700
It's an interesting problem. Hopefully they will fix it someday.
So I guess I solved this problem of mine. The unoptimised model draw distance is to blame. I suggest settings a fps cap to 60 since that's what a 9400f is capable of. 1070 is a powerful GPU and at res sites it pushes the fps to above 60 and causes the microshuttering problem as the cpu can't keep up. U should try capping the fps and if that doesn't work just reduce the model draw distance