Outerra forum
Anteworld - Outerra Game => Tech demo, support, updates => Topic started by: HiFlyer on September 18, 2014, 06:21:29 am
-
An issue I've been having for a long time, and reported in this thread earlier is something I've started thinking of as the "pulse of Outerra"
There is a regular very steady (but slight) hitch that occurs in Outerra at almost exactly one second intervals.
It only disappears when you start Outerra at absolutely default settings. As soon as you change anything at all, the pulse starts. Systematically changing features one by one to see if there is something in particular causing it shows nothing. Anything other than absolute default starts the pulse.
Removing the overclock on my machine and returning it to default settings gets the exact same result.
Pulling or rearranging ram-sticks has no effect.
Nvidia settings all at default has no effect.
Killing all other killable processes, including shutting down the firewall has no effect.
Pulses are not synchronous with HD access.
Power supply shows steady voltage.
Lower resolutions have no effect.
I'm out of ideas!
Log is below
https://www.dropbox.com/s/v5pvmaknjghqdf1/english.log?dl=0 (https://www.dropbox.com/s/v5pvmaknjghqdf1/english.log?dl=0)
-
Does it happen with vertical refresh locked too?
-
Does it happen with vertical refresh locked too?
On my machine, Outerra hates Vertical refresh. Locking it at either 30 or 60 introduces pretty bad shudders. I'm thinking of re-installing, but suspect it wont help.
-
But I noticed in the eng.log that swap_interval=1 (locked to 60). Are you setting the v-sync in control panel?
-
But I noticed in the eng.log (http://goo.gl/Pj6bvt) that swap_interval=1 (locked to 60). Are you setting the v-sync in control panel?
No I was just confirming (again) that V-sync is a bad idea on my system. I test multiple times before reporting anything. :)
-
Ah ok, so can you upload eng.log and time.log from a session where the problem shows?
-
I'm sending you another log.......
But after several restarts of Outerra, the problem for now, is no longer evident. :-\
Strangely enough, my eng.log (http://goo.gl/Pj6bvt)s which were formerly huge 400kb and more (too large to be attached here, which is why I sent it through dropbox, are abruptly more normal sized again, but still too large to be attached. :o :-\
Should it re-occur (with my luck, in about an hour) I will append another log.
https://www.dropbox.com/s/v5pvmaknjghqdf1/english.log?dl=0 (https://www.dropbox.com/s/v5pvmaknjghqdf1/english.log?dl=0)
-
Hmm ... log writer dumps the accumulated logs about every second ::)
-
Hmm ... log writer dumps the accumulated logs about every second ::)
Ya' know, I am more and more sure that Outerra would be much happier on an SSD..........
-
Well, everything would be happier on an SSD :)
But disk transfers are not large (except for video), so it definitely should not do what you are seeing, and it's likely either a bug or an unwanted interaction with some specific hardware/drivers or third party programs.
Btw if you have any antivirus, even the built-in Microsoft one, you should try removing OT data dir from its supervision.
-
I have similar problem with hitches after latest update and installing Alaska scenery, previous version worked fine. It might be related to installing Alaska scenry, maybe too much vehicles and planes are used as static objects. If OT starts with default camera at Himalayas airport there's no hitches.
-
Well, everything would be happier on an SSD :)
But disk transfers are not large (except for video), so it definitely should not do what you are seeing, and it's likely either a bug or an unwanted interaction with some specific hardware/drivers or third party programs.
Btw if you have any antivirus, even the built-in Microsoft one, you should try removing OT data dir from its supervision.
Sigh.......
Well to be sure I disabled antivirus. Everything was fine until I switched back to the Talkeetna area. Instant pulses again, and the eng.log ballooned.
https://www.dropbox.com/s/f1j7pn31gbrxvno/english.log3?dl=0 (https://www.dropbox.com/s/f1j7pn31gbrxvno/english.log3?dl=0)
-
Ok, I have a suspect that may be stalling the pipeline there, will do some tests.
-
I have not noticed these hitches, with v0.2 of the Talkeetna scenery.
I tend to go for the highest possible graphics settings though, which at times brings the FPS below 30 (lightly visible FPS stutter), but I guess this is not what you mean..
Like cameni says, though: using an SSD makes everything happier :). It reduces loading times and write times a lot. Have not noticed any problems, even while playing from and recording video to the same disk.
My specs: i5 3570k@4.3GHz, 16GB RAM, 128GB Samsung 840 PRO, MSI GTX 660.
-
I have similar problem with hitches after latest update and installing Alaska scenery, previous version worked fine. It might be related to installing Alaska scenry, maybe too much vehicles and planes are used as static objects. If OT starts with default camera at Himalayas airport there's no hitches.
After some testing, I can confirm that for me as well, starting in other areas gives a butter-smooth Outerra. Vsync also works correctly again in other areas.
-
Ok, I seem to be having some success against this issue. I've been rethinking my computer settings and doing a lot of tests, and finally have the hitch at such a low level that I have to deliberately look for it to notice it.
Its definitely far below its previous annoyance level, though I'm still curious what the issue was.
-
Was this issue ever confirmed and any cause found? One thing I've noticed is that the issue is "contagious" which is to say if I load into Talkeetna and encounter the issue, and then go to another location entirely, the issue will persist even in the new location.
However, If I start the game in a new location and never go to the Talkeetna area, the issue never occurs......
Its very strange.
-
We have done some profiling and there are some unexpected CPU-side spikes on several calls to graphics drivers. It's hard to track them down as everything is asynchronous and the real cause is usually earlier in the pipeline, but we'll keep looking at it. Stuff is always changing there so it's a moving target too.
Some of the spikes are from the known issues (like the unoptimized multi-segment road renderer).
-
We have done some profiling and there are some unexpected CPU-side spikes on several calls to graphics drivers. It's hard to track them down as everything is asynchronous and the real cause is usually earlier in the pipeline, but we'll keep looking at it. Stuff is always changing there so it's a moving target too.
Some of the spikes are from the known issues (like the unoptimized multi-segment road renderer).
Ok. As long as I'm not completely insane......
By the way, this issue has been gone for me for quite a while with later builds.