demonesque

The incorrect sea-level height on the map from Mr_sukebe makes total sense as it is always 900ft AGL even if you are at the top of a mountain. If that is the problem surely that can't be too hard a fix???

After the Winter update to the SA map I got at least 40mins trouble free having deleted the fxo and metashaders2 folders first. But when I landed the problem came back again and stayed.

Ah Crud. I thought the core dcs vram fix of the last update had made a difference cause my 2 test missions worked perfectly. But when I tried a full mission the stepped fps drop came back . Then when I tried my test missions again the step was back in those too . Back to square 1.

Yeah. Most of my settings are already way lower than the medium settings you are using in your screen shot. I'm sure I could neuter dcs to the point where there was so little load on the gpu that the problem did not trigger but the result in vr would be truly awful. Unfortunately I'll just have to fly the maps that actually work and hope this will get fixed one day. It does explain why there aren't many missions posted for this map. Which is unfortunate cause I love how it looks.

Think I have to go with Biggs on this one. Keep using it for a while and see how it goes. I turned my textures right down to low and thought that was a fix even in vr. (Which should be way more aggressive than 'optimised') Then 20 mins of use later.....

So briefly I thought @Holbeachs workaround of reducing gpu load by reducing the aircraft textures was going to work for the mossie in vr. Untill it didn't. Then using his latest .miz file I thought he had performed some wizardry because for the first time ever the F-14 was faultless over port Stanley. But after flying for a long while then exiting and restarting the miz it finally failed. Then once that had eventually failed, I was able to replace that plane in the mission editor with every airframe I have and they all failed. Even the 'light load' aircraft that I thought did not have the issue. So now I am dispondent. All I can report with any certainty is that the problem does occur in the following modules in VR: Mossie, F-14, Harrier, F-15C, P-51, Ka50, Hind. With typically 30-40fps at med alt over port Stanley dropping suddenly with that fps step to 11 fps at low alt.

I get the issue in VR with the mossie and the F-14 as well, so it isn't just the F4 triggering it.

@Biggus I haven't heard anywhere of it happening on the Kola map. But that map was made by Orbix anyway wasn't it?

@Biggus yeah the faulty shader or similar makes more sense to me too because the other suggestions don't explan why sometimes the problem does not occur and I can get 60 fps at 20 ft agl for a short while every now and then.

Well that is still inconclusive. The Mosquito does not have the issue in 2D transitioning smoothly from 160fps at mid altitude to 145 at 20ft as you would expect. But the F14 still jumps in 2d at the 900ft mark on my rig from 115 fps to 40 fps. So I cant draw any usefull conclusions at all. (And no @Holbeach I can't go back to flying flat screen anymore. I'm having too much fun on the dark side)

I will be interested to see whether as you build up your mission more and more complex, you have to move your sliders further and further to the left to stop the problem happening. I think we have almost determined it is not really one identifiable setting causing the issue. My theory is that it is related to a threshold of the amount of load on your gpu as I did not have this problem in 2d but did have it when I switched to vr. I guess I should try a test back in 2d some time and report back.

Also politely, as reported previously, on the occasional times I (and the others) have got this issue not to occur for a short while, I have had my full 60 fps down to 20ft agl in my test mission. Not the neutered 13fps. So I know my hardware can do it. It is a bottle neck on this map that does not occur on other maps in the same way. Respectfully, programming errors are not a reason to upgrade hardware.

Interesting. I dont own the F4 so it will be interesting to see it this fixes that plane for @Holbeach . However as I am pushing my machine fairly hard to run VR it happens on almost all aircraft. I was using the F14 in Holbeach's test mission and the Mossie in my own nearly blank test mission. But as I say, only on this map, and only at low level. I accept the limitations of my machine and vr on all other maps of 35-55 fps under load as @Hawkeye_UK is talking about. That is acceptable and includes the Marianas. But there is something different and obscure going on here on this one map. (See images from previous posts with severe stepped drops in fps below 900ft AGL)

Also Czar, it is not just after climbing that this problem occurs. Using Holbeach's mission I have the problem from mission start on the runway, so it is not an initial altitude dependent trigger. At least for this system.

I also agree with what you are both saying here. The problem is made worse by the amount of load that is on your machine, for instance with mine being pushed into vr it happens almost all the time except when using a 'light load' aircraft like the p51. But it is even possible to get it to trigger with that sometimes. Just like it is some times possible for it not to trigger for a while with the higher load aircraft as well. There is something different with the way this map is put together just like you say.

Ok. So maybe only happening on 30 series and earlier GPUs. Anything else we can conclude?

Well that doesn't seem to have anything in common cause my next question was were we all using older GPUs. But you are using 30 series architecture. Now I'm stumped again.

So in the spirit of working without developer responses.... Are you guys by any chance using Reshade? Or ParkControl? Are either of those common factors?

@Holbeach oh I thought you were vr as well. I'm quite happy with 35-45 fps but 11 has me sliding off the runway and feeling vertigo. No other map does this, not Marianas either. So as we all note, there is something going on.

@Holbeach I used your .miz file and swapped the F4 for my F14. For me the drop starts immediately on the runway ay 11 fps. Once climbed away I run at an average of 45 fps everywhere else till I drop down again. I tried running it several times but it always started at 11 fps on the runway. I tried flying low for some distance to see if it would clear up like you reported but it did not for me. As I had a radar alt. I measured it and got the same 800 to 900 ft agl that you say. I am not sure what this all proves but there you go. (I am using vr, open composite, pimaxXR runtime, openxr toolkit, quadviews enabled, ParkControl CPU management. Any common factors there? But as the other maps work as per normal I dont see why it should be that) I also love the look and flying in the the mountains in the SA map and wish it worked properly. Your mission makes the Maldivas look really pretty. (But landing in a slide show is terrible. And forget dogfighting in a warbird after spiraling to the ground.)

I'm finding it happens fairly consistently when using the mossie or the tomcat in VR.

Yeah. I did some more testing at different locations with different airframes and in VR at least, it seems that the behavior is still the same as before after this latest patch: Occasionally it will work ok at low altitudes, but most of the time it still has the drastic stepped fps drop when the altitude gets below 500ft.

Unfortunately for me when I deleted my fxo and metashaders2 folders and tried my blank test mission, it still had the same stepped behavior.

Thanks for the reminder about the NVCP power management as mine had reset, but that did not change the behavior of the 'steps' in fps shown the image in above thread. A good thought about testing Marianas and while it has lower fps over the towns due to the detail (varies around 30 or so), that is acceptable as it is consistent and smooth. I also accept this is a free ed map that was a test of new terrain tech at the time. I have not found any areas of Sth A map that do not display this stepped fps behavior yet. Will report here if I do. Turning off object shadows made no difference. My test spot has only roads anyway. I also tried with no object shadows and all tree sliders and grass sliders and scenery details all the way down all at once, and the behavior is still the same. The thing is, I know my machine can render down low at the 60fps or close to it in this area because of the few times that I have mucked around long enough for the issue to stop temporarily. Then when it starts again it does seem to be like a stepped bottle neck of some sort has been re-introduced in the code that does not happen on other maps. I have no idea what that would be. (Full disclosure, my machine is only mid range. None the less, there is something unusual going on here compared to other maps.)

Both trees sliders make no difference and neither does the scenery details slider, or the grass slider. What I have found was if I changed the aircraft using the mission editor in my test mission to something like the P-51D-25 I could get the problem to dissappear UNTILL I used the F10 map. So confirming in vr what Holbeach is reporting for f10 too. (Though it did not always happen after f10. ) However with some playing around i was able to switch back to the mossie eventually and have the problem gone, as long as I did not want to use f10. Trying to see if this could be expanded to a workaround for normal missions.... maybe...