F4E module stuck at 32fps in VR

[Blackhawk163]

No other module that I have does this. DCS reports this as being CPU bound in red. Upon exiting the flight DCS is then stuck at 32FPS regardless of the module. Something is locking this up and for the life of me I cannot figure it out. I've uninstalled the module and reinstalled to no luck. 

I don't remember when this started exactly, maybe when I bought the 5080.  I tried this in 2d and no problems, smooth as silk. 

 

At wits end here with it.

[Zabuzard]

After you exit the Phantom flight, returned to the main menu or entered another flight with a non-HB module and still see the "locked 32 FPS", can you try opening Task Manager and kill the HeatblurUI process?

Does that unlock your FPS again? If so, you might be running an unfortunate software or hardware setup that doesnt like CEF at all (thats the tech behind the UI). We have seen that during testing with a very small amount of users and spend a lot of time putting in fixes until they were not affected anymore. Possibly you are being affected still for some reason. But step by step, lets see if its really the HeatblurUI process or not  

Edited April 19 by Zabuzard

[Blackhawk163]

I’ll do that (just lost power as of this writing lol) soonest. I do know that the module absolutely hates openxr toolkit. I was able to identify the conflict there. When running with it disabled there’s no problem. Enable it and the problem returns. This is new I think as I’m pretty sure I was running opxrtk back in October. 

[Qcumber]

Have you run a log file through the discord log analyser? It would be worth doing this before anything else. 

https://discord.com/channels/542985647502393346/1179171301651402802

 

[Raven (Elysian Angel)]

12 hours ago, Blackhawk163 said:

This is new I think

Not really. A good while ago ED strongly discouraged using openxr toolkit as it was incompatible with DCS after an update. I don’t really remember the specifics.

[Blackhawk163]

9 hours ago, Raven (Elysian Angel) said:

Not really. A good while ago ED strongly discouraged using openxr toolkit as it was incompatible with DCS after an update. I don’t really remember the specifics.

I would agreed if all the modules did this, but as it stands, at least in my case and computer configuration, it (opxrtk) is only incompatible with the F4 module. I think it’s a combination of things in my case, perhaps it’s the 5080 vs the 4080s that I had before, could be a driver issue with the 5000 series. 

 

What I do know is that I failed troubleshooting 101 before I made this thread (and the other in the DCS core one too) by not disabling any software not needed to run DCS.

Once I ran it with OPXRTk off everything was fine. Now I guess the question is why this is the case with the F4. 

[Raven (Elysian Angel)]

23 minutes ago, Blackhawk163 said:

Now I guess the question is why this is the case with the F4

It’s probably deep on a programming level. Perhaps it’s related to HearblurUI, or how a specific subsystem is modelled? Who knows: there’s plenty that makes Hearblur stand out from the other modules and that’s especially true with the F-4E

[Zabuzard]

It would be neat if you can try what I asked above regarding the HeatblurUI.exe.

It is something we did observe during initial testing and tweaking, so its not an unknown issue. Its just that we thought we eliminated it fully. So if you are actually running into that issue, would be great to know  

[Blackhawk163]

20 hours ago, Zabuzard said:

It would be neat if you can try what I asked above regarding the HeatblurUI.exe.

It is something we did observe during initial testing and tweaking, so its not an unknown issue. Its just that we thought we eliminated it fully. So if you are actually running into that issue, would be great to know  

Task manager reported 12 instances of HBUI running, of which I was able to stop 9, with the remaining 3 being unable to force quit (as soon as I stopped one of the three it would spring back up).  This is with OPXRTK enabled, which still results in the F4 being the only module that I have as incompatible with it as it locks down to 32fps. 

 

Behavior not present if OXRTK not enabled, although all but 3 instances of HBUI can't be stopped until DCS is restarted.

 

 

Edited May 5 by Blackhawk163