Patch discussion September 2024

[koen330]

Tried DCS cleanup and repair...no success

Guess i wait for the hot patch that is planned for today....

Can i still use the updater? that is the only thing that works for the moment

[koen330]

5 hours ago, BIGNEWY said:

can you PM me with your dcs log I will try to assist you 

also please ensure you have this redistributable from Microsoft installed,

https://aka.ms/vs/17/release/vc_redist.x64.exe

Thank you BIGNEWY, you are my hero for the day...:)

It was a easy fix, but I would have never been able to find that solution on my own...

Edited October 2, 2024 by koen330

[draconus]

1 hour ago, BIGNEWY said:

Next planned update: 2nd October 2024 - hotfix ( subject to change )

Will it include Spotting Dots Off option for VR?

Edit: I've seen the changelog but maybe...

Edited October 2, 2024 by draconus

[BIGNEWY]

DCS World
Crash when switching to F10 view - fixed

https://www.digitalcombatsimulator.com/en/news/changelog/stable/2.9.8.1214/

patch will be live soon

[BIGNEWY]

patch is live

[Gary]

My Tobii 5 has now stopped working - anyone else with this issue?

Been running MT vedrsion for a while now and always been ok before today's update (providing you disable the launch screen - not sure if this is fixed now?)

Noticed the HeadTracker.dll was only in the Bin folder so copied a copy across to the Bin-Mt folder but still no joy.

Headtracker is picked up in the controls screen but can't get it to work - any ideas anyone please?

Regards,

Gary

[peachmonkey]

hi, @BIGNEWY, @NineLine,

I don't know where else to post this, but can your team please look into or at least acknowledge a graphics/layer bug that was introduced into Anton A8 in July patch? 

 

[Guest]

vor 4 Stunden schrieb Gary:

My Tobii 5 has now stopped working - anyone else with this issue?

Been running MT vedrsion for a while now and always been ok before today's update (providing you disable the launch screen - not sure if this is fixed now?)

Noticed the HeadTracker.dll was only in the Bin folder so copied a copy across to the Bin-Mt folder but still no joy.

Headtracker is picked up in the controls screen but can't get it to work - any ideas anyone please?

Regards,

Gary

Hi Gary, I had the same problem with the Tobii Eyetracker after the DCS update. I no longer start DCS from the BIN-MT directory but use the program from the BIN directory. Now the Tobii Eyetracker works again. Since the last update there is no ST version of DCS anymore. In the start screen, the MT for the MT version is also shown here at the bottom right of the version number. Try it out. Greetings Martin (RedHorse)

Translated with DeepL.com (free version)

[Q3ark]

5 hours ago, Gary said:

My Tobii 5 has now stopped working - anyone else with this issue?

Been running MT vedrsion for a while now and always been ok before today's update (providing you disable the launch screen - not sure if this is fixed now?)

Noticed the HeadTracker.dll was only in the Bin folder so copied a copy across to the Bin-Mt folder but still no joy.

Headtracker is picked up in the controls screen but can't get it to work - any ideas anyone please?

Regards,

Gary

Friend of mine having the same problem with their trackIR.

[Gunfreak]

So how do I make sure DCS is using mbucchia quad view and not pimaxes own quadview?

[miguelaco]

If you're using QuadViewsCompanion, you can check the option "Focus View" to only render the high resolution region. If it works, then you can be sure you're using mbucchia's QVF. The option can also be enabled directly in the config file, but it's easier this way.

Another way, less practical is in DCS launcher Options>VR, you have a new option to enable QuadViews. Next to it you should see a warning sign and it will tell you which api layers are enabled in your system.

Edited October 3, 2024 by miguelaco

[Gierasimov]

17 hours ago, Q3ark said:

Friend of mine having the same problem with their trackIR.

TrackIR not working in DCS is caused by two last updates of Natural Point software. Uninstall, install lower version and TrackIR is back.

[Bucic]

24 minutes ago, Gierasimov said:

TrackIR not working in DCS is caused by two last updates of Natural Point software. Uninstall, install lower version and TrackIR is back.

Any feedback on OpenTrack? I haven't updated it since January

[T24_Martin]

Hi! Since the patch Quad Views is not working for me. Running Crystal OG with just Pimax Play OpenXR and Quad Views. It worked fine after the big update (as soon as somebody told me, to enable QV in the DCS settings ;)). Since the patch it doesn't work any more.

[BIGNEWY]

17 minutes ago, T24_Martin said:

Hi! Since the patch Quad Views is not working for me. Running Crystal OG with just Pimax Play OpenXR and Quad Views. It worked fine after the big update (as soon as somebody told me, to enable QV in the DCS settings ;)). Since the patch it doesn't work any more.

Please double check the quadview are enabled in PIMAX Play, if you hover the mouse over the quadview setting in DCS you may see a warning for conflicting API layers. 

[T24_Martin]

vor 8 Minuten schrieb BIGNEWY:

Please double check the quadview are enabled in PIMAX Play, if you hover the mouse over the quadview setting in DCS you may see a warning for conflicting API layers. 

Hi! I did. No warning in DCS and QV enabled in Pimax play. Restarted the headset, re-calibrated eye tracking, but no success! 

[BIGNEWY]

10 minutes ago, T24_Martin said:

Hi! I did. No warning in DCS and QV enabled in Pimax play. Restarted the headset, re-calibrated eye tracking, but no success! 

please pm me with your dcs log I will try to assist you 

[MAXsenna]

Any feedback on OpenTrack? I haven't updated it since January

It works fine, I'm even on the latest pre-release version. Don't ask me why, just felt like it. My previous version was from last year.

Sent from my SM-A536B using Tapatalk

[f14billy]

5 hours ago, T24_Martin said:

Hi! I did. No warning in DCS and QV enabled in Pimax play. Restarted the headset, re-calibrated eye tracking, but no success! 

You may try reinstalling Quad Views 1.1.3 and see if that works. I have it installed and despite the DCS warning it works perfectly.

[westr]

I’ve had no improvement with this patch. Which is a disappointment as I was hoping to see a slight improvement in VR when I heard about the optimisation on VRAM. 
I didn’t give any feedback at first because I wanted to fully try and tweak everything my end to make sure I wasn’t jumping the gun. I have no doubts that the team have put huge effort into this patch with lots of added features and I accept that all systems are different and some people have seen an improvement, it’s just not worked any better for me.

I wait with anticipation for the implementation of Vulcan and shall keep my fingers crossed. 
What I can say is that I have seen no deteriorating performance, it is more or less the same. 
I run motion vector in Steam VR settings which restricts my FPS to 45.

If I can maintain 45 it is smooth experience and the sim runs nice. 
Some of my modules run a fine 45fps like the F16 and F18 even with storms and rain In Caucasus. But others struggle, for example the new Phantom. 
I thought I would try and run with motion vector off and noticed a drop of around 10-12 fps and noticeable stuttering with that setting so I just put it back on. 

What I have noticed since earlier this year which coincided with a massive fps drop when using the F10 map view, is random drops by around 15fps while running a flight. Alt tabbing then tabbing back into the sim and sometimes Alt and enter will make the FPS jump back to 45. 
I also completely avoid the F10 map view now because it’s such a pain to get the FPS back once I do it. I would really appreciate a work around of this problem as I know it never used to happen. 
I haven’t tried the Syria Sinai and South Atlantic maps as I have them on another install on another drive and haven’t updated that yet. So maybe I will see an advantage on those maps.

[Joe1978]

hace 39 minutos, westr dijo:

I’ve had no improvement with this patch. Which is a disappointment as I was hoping to see a slight improvement in VR when I heard about the optimisation on VRAM. 
I didn’t give any feedback at first because I wanted to fully try and tweak everything my end to make sure I wasn’t jumping the gun. I have no doubts that the team have put huge effort into this patch with lots of added features and I accept that all systems are different and some people have seen an improvement, it’s just not worked any better for me.

I wait with anticipation for the implementation of Vulcan and shall keep my fingers crossed. 
What I can say is that I have seen no deteriorating performance, it is more or less the same. 
I run motion vector in Steam VR settings which restricts my FPS to 45.

If I can maintain 45 it is smooth experience and the sim runs nice. 
Some of my modules run a fine 45fps like the F16 and F18 even with storms and rain In Caucasus. But others struggle, for example the new Phantom. 
I thought I would try and run with motion vector off and noticed a drop of around 10-12 fps and noticeable stuttering with that setting so I just put it back on. 

What I have noticed since earlier this year which coincided with a massive fps drop when using the F10 map view, is random drops by around 15fps while running a flight. Alt tabbing then tabbing back into the sim and sometimes Alt and enter will make the FPS jump back to 45. 
I also completely avoid the F10 map view now because it’s such a pain to get the FPS back once I do it. I would really appreciate a work around of this problem as I know it never used to happen. 
I haven’t tried the Syria Sinai and South Atlantic maps as I have them on another install on another drive and haven’t updated that yet. So maybe I will see an advantage on those maps.

Yes, the same for me. I thought that VRAM optimization would positively affect performance, in fact Bignewy announced this as a radical improvement for VR (or so I understood it)... but no, in my case it has not been like that either.

Essentially, I must maintain the same low settings for two or three updates. I can maintain 45-80 FPS on land and at a very low altitude but I suffer constant stuttering, FPS drops, etc. with textures at medium. 

I would like for an explanation to be provided to the community regarding the nature of this VRAM optimization and the reason why DCS still utilizes the full 10GB of VRAM on my card without any noticeable improvement. Additionally, I have observed multiple videos from users that display the VRAM usage before and after the update, which appears to be unchanged. 

[MadKreator]

9 hours ago, Gierasimov said:

TrackIR not working in DCS is caused by two last updates of Natural Point software. Uninstall, install lower version and TrackIR is back.

 I just installed v 5.5.2 of TrackIR software last night and it worked fine in DCS… Once I got the software to open.. .Kept getting DLL errors but I just had to run repairs on Visual c++ 2012and 2013 in windows. But compatibility with DCS in TrackIR v 5.5.2 seems to be just fine

[scommander2]

6 hours ago, Joe1978 said:

Yes, the same for me. I thought that VRAM optimization would positively affect performance

Yes, I am facing the same issue. DCS takes almost 12GB VRAM and the range of the FPS change is huge around 30 to 80, especially applied the hotfix.  

[Rex]

On 10/1/2024 at 4:37 AM, Glide said:

Did you fly it?  Both the TF-51D and the F-16 have new rudder code, and it's very broken. 

Eh?  In what way?

I just flew the F-16 and the rudder worked great.

Edited October 4, 2024 by Rex

[Chief_Biv]

15 hours ago, T24_Martin said:

Hi! I did. No warning in DCS and QV enabled in Pimax play. Restarted the headset, re-calibrated eye tracking, but no success! 

If you have QV enabled in the new Pimax Play you have to disable the OpenXR Toolkit. They are not compatible.