The gumbo of stutters, pauses, freeze and other ingredients

[Skuzzy]

What you are describing sounds like a USB power brownout, where the voltage/current level drops below what the headset needs to run.  Certainly can happen if you are not careful with how you distribute power loads across the USB hubs of the computer.

[Dobs]

DX11 freezes getting worse...longer in duration.

Can't believe the majority of the population see's this, and it can't be duplicated by the developers.

[Bruv119]

I switched back to DX11 with the new computer and they are still there and noticeable. 

It's odd because a few patches ago I swear I can remember them being cured in DX11 for a patch or two.   

Also what AKAK said about the CV things get choppy in and around the boat with the graphics up.  It is only the boat everywhere else is fine.

[Mister Fork]

Here's a funny bit, in my Oculus, I get ZERO freezes.  Smooth as a baby's bottom.  Switch back to normal mode, and it sometimes feels like I'm in the matrix. In-game pauses, sound stutters.

What's frustrating (being a former programmer) is that chances are it's something very very simple causing it.  But with hundreds of thousands lines of code, you'd almost need something as powerful as Watson Analytics to look at it...and it ain't cheap. 

Probably a semi-colon or  a bracket out of place somewhere 

That said, the game isn't unplayable at all. Just a small nuisance.

[Skuzzy]

Really need to pay attention to the terrain and where on the terrain you are when it happens.  It is one of the many variables we need to try and reproduce it.

[Drano]

Really need to pay attention to the terrain and where on the terrain you are when it happens.  It is one of the many variables we need to try and reproduce it.

No problem. Will the psave command capture that info for you?

And is there anything else that we can do on our end that'll help you track it down? The game doesn't crash so there's no report there to send you. It's so unpredictable. Like catching a friggin quark! You know they're there but when and where they're gonna hit is total randomness.

Sent from my XT1585 using Tapatalk

[Skuzzy]

psave only captures the position on the terrain.  It does not capture the terrain name.

It is really looking like it is a series of events which leads to the manifestation of it and if you do not get the exact series right you cannot duplicate it.  Even the timing of the events is crucial.  Crazy making.

[zampheer]

Using DX11.

WTF????  Really...this is bad... I'm getting 1 - 3 second freezes at least twice every 10 minutes.  You gotta be kidding me this is really really bad.  Can we get some idea from HiTech that they are even working on this?

I mean, I suck as a player.  But flying for 5-10 minutes to get to a field and engage.  Then do auger in because the game freezes on a straffing pass.  Not fun anymore.

[bustr]

psave only captures the position on the terrain.  It does not capture the terrain name.

It is really looking like it is a series of events which leads to the manifestation of it and if you do not get the exact series right you cannot duplicate it.  Even the timing of the events is crucial.  Crazy making.

Hmmmmm, still captures the terrain name on my PC unless I get a special download.

-1388,2026,-8102,0.0,0.0,94.2
gunnery
FOV = 58.7

[The Fugitive]

Using DX11.

WTF????  Really...this is bad... I'm getting 1 - 3 second freezes at least twice every 10 minutes.  You gotta be kidding me this is really really bad.  Can we get some idea from HiTech that they are even working on this?

I mean, I suck as a player.  But flying for 5-10 minutes to get to a field and engage.  Then do auger in because the game freezes on a straffing pass.  Not fun anymore.

Did you even READ the post just before yours, never mind the whole thread. Skuzzy said they are working on it and it is very hard to duplicate. Or did you post just to complain?

[Skuzzy]

Hmmmmm, still captures the terrain name on my PC unless I get a special download.

-1388,2026,-8102,0.0,0.0,94.2
gunnery
FOV = 58.7

I stand corrected then.  Must have been added during the Beta.

And it is not just a location issue.  It seems to be related to several events conspiring to create the problem.  If you are having a chronic problem with this (i.e. it happens every minute or two), it could be something else.  A DXDIAG output might be revealing in that case.

[zampheer]

Did you even READ the post just before yours, never mind the whole thread. Skuzzy said they are working on it and it is very hard to duplicate. Or did you post just to complain?

Guilty as charged ($15/month)  Sorry, just very frustrating.  Glad to hear they're looking at it.  Maybe a notice in game might help instead of in the forums.  I don't know who Skuzzy is (what's Skuzzy's role...moderator or developer?) and there is not a sticky on this issue...is there?  And from the guys I've mentioned it to in game it's pretty pervasive.

If they're trying to catch it...that's gonna be a long wait.  I suspect they need to instrument the code and start pulling data from users.

Good luck.  Will be looking out for a notice in the upgrade notes.

[JimmyC]

Zampheer.. just use DX9 to launch game
thats what we all are doing
its in your aces high folder aceshigh9.exe

[Bizman]

FWIW, yesternight I noticed that at a distance the port showed as a rectangle of sea with a bonfire in the middle of it. When I got closer, there was a .5 second freeze, after which the port looked normal. However, although I could duplicate the rectangularity, the freeze didn't reappear.

231825,15820,-293386,-41.7,-21.3,76.8
buzzsaw
FOV = 58.7

I also had a similar freeze before that occurring when someone spoke on range. Again, that was a one time event and may have been purely coincidental.

I tend to get the freezes at some 15 minutes intervals, one at a time.

DX11.

[FESS67]

See Rule #4