investigating unplayable in VR

[Pillowcat]

Last update came with more aggressive vram emptying with which it seems devs jump on the rake of vram fragmentation, so it becomes sort of failed tetris level.

Edited October 23, 2024 by Pillowcat

[Johnny Dioxin]

I just tried it for the first time. I just did a clean, fresh install of DCS World and there have been no updates (cos I just did it, so...).

No mods at all and while I was so happy with an average 67fps in my F-16C on a busy Persian Gulf mission with my new Crystal Light (at 70% res and 90Hz), the fps in a cold & dark Chinook, in the start-up training mission, is 22-23. On external view it rises to average 46fps, as soon as I got back into the VC it drops to 22-23 again. There was obvious stuttering as the Hummer drives past. I was too concerned to do more than the first few steps of the start-up, after what I experienced when the Apache was released (which was waaay worse) and which is now performing very well.

I think this one just needs some time, like those before it. I'll revisit next year - still have a Kiowa to learn.

Edited October 23, 2024 by Johnny Dioxin
fingers outpacing brain

[YoYo]

15 minutes ago, Johnny Dioxin said:

I just tried it for the first time. I just did a clean, fresh install of DCS World and there have been no updates (cos I just did it, so...).

No mods at all and while I was so happy with an average 67fps in my F-16C on a busy Persian Gulf mission with my new Crystal Light (at 70% res and 90Hz), the fps in a cold & dark Chinook, in the start-up training mission, is 22-23. On external view it rises to average 46fps, as soon as I got back into the VC it drops to 22-23 again. There was obvious stuttering as the Hummer drives past. I was too concerned to do more than the first few steps of the start-up, after what I experienced when the Apache was released (which was waaay worse) and which is now performing very well.

I think this one just needs some time, like those before it. I'll revisit next year - still have a Kiowa to learn.

 

I'll check Chinook again then, I haven't flown on CH-47 since the last update, maybe something happened. I haven't complained lately and I had a constant 72 fps in VR (at 72Hz) with quite high resolution.

[Johnny Dioxin]

Just an additional note - the above posted results were in ST. Today I tried it in MT and it was a whole lot worse. My mistake on the res posted before - I'm actually at 100% in DCS World.

The cockpit textures took several minutes to load in - long after the 'instructor' had finished his intro spiel. The framerate started at 45 and as each section of the cockpit textures loaded in, the framerate dropped until it was in the mid-teens. The frametime for GPU was in the mid 40's and for the CPU the mid 20's. The graphs in fpsVR were all a solid wall of red. The VRAM was at 15.3GB out of the available 15.7 which I thought would be a good thing, but seems not.

Anyway, when I exited the Chinook mission because it would be hopeless to continue, the sim froze and VR crashed. This is actually a good example of why I stay on ST at the moment.

So definitely a "Wait, out" for now.

[BIGNEWY]

26 minutes ago, Johnny Dioxin said:

Just an additional note - the above posted results were in ST. Today I tried it in MT and it was a whole lot worse. My mistake on the res posted before - I'm actually at 100% in DCS World.

The cockpit textures took several minutes to load in - long after the 'instructor' had finished his intro spiel. The framerate started at 45 and as each section of the cockpit textures loaded in, the framerate dropped until it was in the mid-teens. The frametime for GPU was in the mid 40's and for the CPU the mid 20's. The graphs in fpsVR were all a solid wall of red. The VRAM was at 15.3GB out of the available 15.7 which I thought would be a good thing, but seems not.

Anyway, when I exited the Chinook mission because it would be hopeless to continue, the sim froze and VR crashed. This is actually a good example of why I stay on ST at the moment.

So definitely a "Wait, out" for now.

You should post your dcs log if you are crashing so we can take a look, ST is dead if you are having issues with MT we need to see the data, it will help. 

[YoYo]

1 hour ago, Johnny Dioxin said:

Just an additional note - the above posted results were in ST. Today I tried it in MT and it was a whole lot worse. My mistake on the res posted before - I'm actually at 100% in DCS World.

The cockpit textures took several minutes to load in - long after the 'instructor' had finished his intro spiel. The framerate started at 45 and as each section of the cockpit textures loaded in, the framerate dropped until it was in the mid-teens. The frametime for GPU was in the mid 40's and for the CPU the mid 20's. The graphs in fpsVR were all a solid wall of red. The VRAM was at 15.3GB out of the available 15.7 which I thought would be a good thing, but seems not.

Anyway, when I exited the Chinook mission because it would be hopeless to continue, the sim froze and VR crashed. This is actually a good example of why I stay on ST at the moment.

So definitely a "Wait, out" for now.

Add the mission track too.

[Johnny Dioxin]

10 hours ago, BIGNEWY said:

You should post your dcs log if you are crashing so we can take a look, ST is dead if you are having issues with MT we need to see the data, it will help. 

I thought it was simply overloading the graphics card, but it turns out it's something to do with my headset and the freeze was caused by a SteamVR crash. SteamVR is currently unable to find my headset (but the Pimax software is finding it - so it's a SteamVR or Pimax software issue). I tried to run in OpenXR/PimaxXR, but for some reason SteamVR is still starting up, and that stops everything. Hopefully find a fix to get it at least working in OpenXR while Pimax support get their backsides in gear and look at my issue, which they currently aren't doing as they fobbed me off to their support FAQ.

Anyway, OT but explains the freeze up in MT.

Edited October 24, 2024 by Johnny Dioxin

[YoYo]

I flew Chinook today and everything is still ok for me, textures take longer to load but I have a constant 72 FPS, no any drops and problems for me, but ok, I have 24 GB VRAM.

[grim_reaper68]

As the chinook load the Vram at 21GB on Caucasus, no wonder if there are less Vram that the FPS drops at 22 fps. I had the same issue (non VR) with my old 8GB VRAM GPU 

[ST0RM]

Noticing more FPS drops from a Cold Start mission than from a Hot Started one. 

[MAXsenna]

5 hours ago, ST0RM said:

Noticing more FPS drops from a Cold Start mission than from a Hot Started one. 

How many other units around in the cold start? Especially how many CH-47Fs. 

[ST0RM]

29 minutes ago, MAXsenna said:

How many other units around in the cold start? Especially how many CH-47Fs. 

Default Afghanistan Cold Start mission. So 2-3 close by. Plus the flying Apaches

[MAXsenna]

Default Afghanistan Cold Start mission. So 2-3 close by. Plus the flying Apaches

Compared to the hot start mission? It escapes me how many there are. Try to remove them, and see if it's better. Those AI sucks the VRAM out of your GPU!

Sent from my SM-A536B using Tapatalk