Kola and VR impressions ?

[X_legio]

Someone  tested Kola in VR ?

[speed-of-heat]

yep , works OK , not perfect, by any stretch , above about 6k 90FPS is certainly easy to achieve in the weeds no worse than say the Marianas is today ... which considering the size and newness is pretty good

[Hempstead]

I got 7 FPS in VR, far worse than Mariana.

 

[speed-of-heat]

where were you ? 

[diamond26]

Generally speaking the map is behaving really well for its size and nature. Better than South Atlantic. I had to reduce  Forest Detail factor to 0.5 to keep 72 FPS at low levels.

[Qcumber]

4 hours on the map so far. Performance is pretty good but is hit a lot low over trees. I get 72 FPS in most places. Below about 1000ft over trees drops it to 50-60 FPS. I am still playing with settings but turning landscape shadows off appears to help with trees. 

[Mr_sukebe]

So far, just one issue.  In general, good performance, fairly comparable to Caucasus.

This is using a Quest Pro with DFR.  Ground textures low, medium draw distance.

Have flown the Mig 19, Mig 21 and Viggen at a variety of altitudes.  Above 1000', pretty much always 72fps.

In the Viggen and on the deck, generally in the 60s.  Near the base, a little lower.

The issue was towards the end of a 2 hour session in the Migs, when the frame rate dropped to sub 30 fps.  The felt like a VRAM memory leak.  I changed the Hangar to "black" and I haven't seen another re-occurence as yet.   The Hangar is a single file that you drop into the main DCS directory, such that on first loading DCS, you don't see a hangar, it's just empty black space.  Apparently it saves VRAM memory.

Edited May 4, 2024 by Mr_sukebe

[Hempstead]

23 hours ago, speed-of-heat said:

where were you ? 

Starting hot on runway of Kemi Tornio... 7 fps... 

Starting at 6,000 agl over Kemi Tornio heading north, 33 fps... turn around heading toward Kemi Tornio... as soon as I get close to the town, 22 fps, and terrible, unplayable flickering.

 

[Qcumber]

19 hours ago, Mr_sukebe said:

Have flown the Mig 19, Mig 21 and Viggen at a variety of altitudes.  Above 1000', pretty much always 72fps.

In the Viggen and on the deck, generally in the 60s.  Near the base, a little lower.

I'm getting similar results. West coast only tested so far. Bodo in the ground is about 60 FPS in F16, F5 and K4. A bit lower in the Mosquito. Above a 1000ft or so and it's a steady 72 FPS. Low over forests areas and it drops to 50-60 FPS. 

Overall it looks pretty good with some caveats. Water-ground transition is not good. But that applies to most maps. The mountains in the low texture regions look better than Caucasus so there is hope that this will get even better. I'll probably use this map mainly for the fjords and for WW2 action rather than it's intended use. 

16 minutes ago, Hempstead said:

Starting hot on runway of Kemi Tornio... 7 fps... 

Starting at 6,000 agl over Kemi Tornio heading north, 33 fps... turn around heading toward Kemi Tornio... as soon as I get close to the town, 22 fps, and terrible, unplayable flickering.

 

I'll try that out later and see how it looks for me. What aircraft did you use? What's your hardware setup? 

[NAM]

2 hours ago, Hempstead said:

Starting hot on runway of Kemi Tornio... 7 fps... 

Starting at 6,000 agl over Kemi Tornio heading north, 33 fps... turn around heading toward Kemi Tornio... as soon as I get close to the town, 22 fps, and terrible, unplayable flickering.

 

on HPG2 setting 60hz

... In apache, Kemi Tornio... on runway 55fps (CPU-limited) and surround town 56-60ps (GPU-limited), mountain areas full 60fps (capped at 60hz).

Performance-wise on par with other maps...

Quite pleased with the map so far.

 

Edited May 5, 2024 by NAM

[Qcumber]

17 minutes ago, NAM said:

on HPG2 setting 60hz

... In apache, Kemi Tornio... on runway 55fps (CPU-limited) and surround town 56-60ps (GPU-limited), mountain areas full 60fps (capped at 60hz).

Performance-wise on par with other maps...

Quite pleased with the map so far.

 

 

I tried with an F5 parking hot at Kemi Tornio. I managed 72 fps (just) on the ground and 72 easily above about 1000ft. I don’t have the apache but I’ve hear it’s a resource hog. The rural textures look worse in this region than the west coast. I think the mountains look pretty good. 

[NAM]

8 minutes ago, Qcumber said:

I tried with an F5 parking hot at Kemi Tornio. I managed 72 fps (just) on the ground and 72 easily above about 1000ft. I don’t have the apache but I’ve hear it’s a resource hog. The rural textures look worse in this region than the west coast. I think the mountains look pretty good. 

Apache, lesser extend Mi24 used to be resource hog.. Few years ago, I remembered getting in the low 30s.

But now, DCS multi-thread and VR utils like quad-view and OptiScaler (DLSS for AMD card).

I can get even max 72fps for Pico4 and 60fps for HPG2 in Apache/Mi24.

My hardware AMD 5800x3D, 6900XT Overclock.

[Hempstead]

3 hours ago, Qcumber said:

I'm getting similar results. West coast only tested so far. Bodo in the ground is about 60 FPS in F16, F5 and K4. A bit lower in the Mosquito. Above a 1000ft or so and it's a steady 72 FPS. Low over forests areas and it drops to 50-60 FPS. 

Overall it looks pretty good with some caveats. Water-ground transition is not good. But that applies to most maps. The mountains in the low texture regions look better than Caucasus so there is hope that this will get even better. I'll probably use this map mainly for the fjords and for WW2 action rather than it's intended use. 

I'll try that out later and see how it looks for me. What aircraft did you use? What's your hardware setup? 

In an F-16, Intel Core i9 7900X (10 physical cores, 4.2GHz), 64GB RAM, RTX-3080, and a Quest Pro, Win10, all SSD-M2. I rate limit it to 45fps in DCS VR... and am able to get 45fps in NTTR map. 

[speed-of-heat]

@Hempstead so i can't replicate those results (certainly not 7 FPS) I seem to be getting an average of 50-70 on the deck and 90 above about 6k feet... 

and of course i was recording at the time ...  my machine specs are in my sig.

[TED]

I've been testing and flying more now in both f16 and f18 and mostly around the high detailed areas. My test mission now is a combination of a low level strike mission from Bas100 with 4 jets. A bunch of other packages flying around hitting other targets nearby as well as a fee packages of Russian fighters coming in. All in all I'm very happy with the vr performance and have not experienced any issues at all, even flying low level in formation over the trees. 

I'm using my usual dcs settings, with all max or high, msaa x2. No upsampling. Pico 4 and pimax 8kx. I'm starting to really like this map. 

[Qcumber]

3 hours ago, TED said:

I've been testing and flying more now in both f16 and f18 and mostly around the high detailed areas. My test mission now is a combination of a low level strike mission from Bas100 with 4 jets. A bunch of other packages flying around hitting other targets nearby as well as a fee packages of Russian fighters coming in. All in all I'm very happy with the vr performance and have not experienced any issues at all, even flying low level in formation over the trees. 

I'm using my usual dcs settings, with all max or high, msaa x2. No upsampling. Pico 4 and pimax 8kx. I'm starting to really like this map. 

I like it too. It does have some performance issues but the fjord experience is great. I set up a 109 mission intercepting a low level mosquito strike (2x109s vs 4 mossies). 72 FPS all the way. MSAA x2, QVFR with quest pro. 

[Hempstead]

On 5/6/2024 at 7:05 AM, speed-of-heat said:

@Hempstead so i can't replicate those results (certainly not 7 FPS) I seem to be getting an average of 50-70 on the deck and 90 above about 6k feet... 

and of course i was recording at the time ...  my machine specs are in my sig.

I am not 100% sure... but what I have been seeing this past week is that the Kola map triggers it particularly often. But it seems to be cause by Oculus runtime.

I don't turn off my computers... so since the latest release of Oculus runtime update... If I leave Oculus desktop runtime running (I usually do) for a long time, then the kola map triggers it almost every time. But, this also happens to even the NTTR map now, which never happened before. Now, if if happens, not matter what I do it will have very low FPS, even if I quit the game and go back to the welcome screen of DCS, I get 15 fps (with a 100% GPU usage). Eh? There shouldn't be much 3D rendering going on when I am in the welcome screen! And it will persist until I quite to desktop and come back. However, if I don't restart Oculus runtime, and launch DCS again, I will get 45fps (I set the limit to 45fps) in the welcome screen. But as soon as I get to Kola map again, it will trigger immediately.

 

But, if I restart Oculus... or reboot, other maps will be fine... but Kola will trigger it if I head toward the sea of Kemi.

 

So, this all seems like some VRAM leak problem. But I have not really isolated the problem yet... It's just that Kola seems to be the sure way to trigger it.