Patch Notes discussion 13th, 21st and 23rd April 2023

[Blackfyre]

Quote

• Fixed: Reduce HUD/JHMCS TD diamond slewing rate. This will allow more precise slewing.
• Fixed: Attack format TDC slew rate way too slow. This will allow more rapid TDC movement to designate targets, change range scale, etc.

How little it needs to be happy sometimes

[ricktoberfest]

What about oculus runtime?  Is it still not default for oculus headsets? Currently running a registry hack to disable openxr but I’d like to not have to do that.

[NineLine]

5 minutes ago, ricktoberfest said:

What about oculus runtime?  Is it still not default for oculus headsets? Currently running a registry hack to disable openxr but I’d like to not have to do that.

Can you make a bug thread for this, Wags uses the Quest 2 and does not see this issue, so til help you more a proper bug thread if one is not already created would be best. 

 

[Baldrick33]

9 minutes ago, NineLine said:

Can you make a bug thread for this, Wags uses the Quest 2 and does not see this issue, so til help you more a proper bug thread if one is not already created would be best. 

 

I believe a relevant bug thread already exists. As I understand it the request is to use the Quest2 using the native Oculus API rather than using OpenXR (without a reg hack)

 

Edited April 13, 2023 by Baldrick33

[ricktoberfest]

9 minutes ago, Baldrick33 said:

I believe a relevant bug thread already exists. As I understand it the request is to use the Quest2 using the native Oculus API rather than using OpenXR (without a reg hack)

 

 

Exactly, except I’m on Rift S. I find the openxr implementation is more buggy than the oculus. Constantly recenterIng and seems to conflict with oculus ASW

[Rifter]

27 minutes ago, ricktoberfest said:

What about oculus runtime?  Is it still not default for oculus headsets? Currently running a registry hack to disable openxr but I’d like to not have to do that.

When registry is set to none for OpenXR Runtime (= default) the Oculus runtime will be used when starting DCS in ST or MT and an Oculus headset is recognised. So I assume Oculus runtime is default for Oculus headsets (since 2.8.3.38090). Haven't tried latest update yet.

Edited April 13, 2023 by Rifter

[SickSidewinder9]

Patch not downloading.  Errors with Steam and something about dll files?

Edit: restart fixed it (even though I had just started the computer).  Might have been AVG update, maybe something else.  Works fine now.

Edited April 13, 2023 by SickSidewinder9

[Recluse]

Thanks for the continued attention to MT fixes. Haven't done any extensive testing, but I did notice the GMT Radar (F/A-18) is still not working right . Shows the MAP returns  which makes it hard to see the actual moving targets. Messing the GAIN is a workaround, but still an issue.

 

[Gunfreak]

Is it possible to get a separate post with all the small and large fixes to MT. So those testing and bug hunting knows what's what.

[Raven (Elysian Angel)]

Excellent work on the MT performance improvements, thank you!

I no longer have the "CPU bound: main thread / rendering thread" spam with horrible stuttering! The micro-stutters are now replaced by "nano-stutters": the experience is MUCH smoother now but looking at the frametime graphs there is still some work to be done.
But this is an immense improvement! Thanks again!

[DishDoggie]

Can someone explain to me this line at the bottom of the graphics.lua file Does this have anything to do with VR output per Eye? I set it to true during last version. I didn't notice it caused any problem for me. This new update reset it back to false. I forgot to ask about it till now.

--in stereo and hmd mode you can try to use single parser for both eyes , by default is false , comment to enable it or set to true
stereo_mode_use_shared_parser = false

[Rifter]

26 minutes ago, DishDoggie said:

Can someone explain to me this line at the bottom of the graphics.lua file Does this have anything to do with VR output per Eye? I set it to true during last version. I didn't notice it caused any problem for me. This new update reset it back to false. I forgot to ask about it till now.

--in stereo and hmd mode you can try to use single parser for both eyes , by default is false , comment to enable it or set to true
stereo_mode_use_shared_parser = false

That option is old. It is for so called single pass stereo rendering. It renders both left and right eye images at the same time in VR. It enables the GPU to share culling for both eyes. The GPU iterates through all objects in the rendering scene for only one time for the culling and then renders the reminding objects that were left over after the culling process.
It can boost VR performance significantly. But sometimes it comes with rendering errors (different light effects for left and right eyes for example). This feature was never completed or approved by ED.

[SPAS79]

<jk> where's muh-1h engine patch at? </jk>

[Minhal]

Does anyone else have issues runnig Reshade in MT? ST works fine. Had no issues before the update.

[SPAS79]

11 minutes ago, Rifter said:

That option is old. It is for so called single pass stereo rendering. It renders both left and right eye images at the same time in VR. It enables the GPU to share culling for both eyes. The GPU iterates through all objects in the rendering scene for only one time for the culling and then renders the reminding objects that were left over after the culling process.
It can boost VR performance significantly. But sometimes it comes with rendering errors (different light effects for left and right eyes for example). This feature was never completed or approved by ED.

I have been seeing such lighting issues since MT started. So i have been running with it on "true" since then.

[peachmonkey]

@NineLine @BIGNEWY

is there some sort of a new combat damage effect that leaves no traces of the fuselage/wings after the fuel tank explosion? Or .. a bug?

https://forum.dcs.world/topic/323671-finally-saw-a-warbird-explode/

[DishDoggie]

10 minutes ago, SPAS79 said:

I have been seeing such lighting issues since MT started. So i have been running with it on "true" since then.

I just ran the update with it off or set to false and I think my shadows in cockpit look way better with it set to true. I will go back and set it to true again for my next try. Also @BIGNEWYSir can you tell me about this post you guys made? I just tested the Huey out and this was not in the Update? When will it come out? it is still like before.

New engine modelling methods have been in progress during development of the Mi-24P and AH-64D modules. The new UH-1H engine model was in many ways a test bed for the methods we then used in the AH-64D engines model. We’ve been gathering feedback about DCS: UH-1H over the years, and thanks to our forum users; Piston85, Ramsay and others, we have pinpointed changes to make for new engine model development. We are now finishing the deployment of the new engine model to UH-1H and are eager to let you try it. Please make sure to give us your feedback.

The new model represents fine tuning to address the following:

• Some of the old engine model parameters did not match with their real counterpart, especially in transient regimes.
• We wanted to improve temperature regime compliance to match the real world counterpart. This includes EGT other engine parameters based on altitude and outside temperature changes.
• We wanted to improve the modelling of mechanics to include a new model that accounts for the connection of the free turbine and main rotor.
• The new model has allowed us to improve details of the start-up and shutdown procedures that leverage the expanded modelling of compressors and free turbine.

This image shows that we are now accurately modelling auto-rotation situation readings on the tachometer. The real aircraft dial is on the left and the DCS: UH-1H Huey dial on the right.

[BIGNEWY]

UH-1H changes will be in a future patch 

[BIGNEWY]

40 minutes ago, peachmonkey said:

@NineLine @BIGNEWY

is there some sort of a new combat damage effect that leaves no traces of the fuselage/wings after the fuel tank explosion? Or .. a bug?

https://forum.dcs.world/topic/323671-finally-saw-a-warbird-explode/

Ive asked the team if it is intended 

thanks

[Apache 64]

vor 2 Stunden schrieb Minhal:

Does anyone else have issues runnig Reshade in MT? ST works fine. Had no issues before the update.

...no issues so far. No problems even after today's OB patch.

Reshade must be installed separately for the MT version, of course, with reference to the correct folder where the MT version is located.

[Marshallman]

32-8 fps mutliplayer apache Caucasus. Hmmmm

[Minhal]

5 minutes ago, Apache 64 said:

...no issues so far. No problems even after today's OB patch.

Reshade must be installed separately for the MT version, of course, with reference to the correct folder where the MT version is located.

Hm, then something seems to be wrong on my end.

Strange thing is: i installed Reshade in the bin-mt folder and it worked flawless with MT. Now it works with ST only despite the Reshade files all still sit in the bin-mt folder. I might just uninstall and reinstall again and see if it helps.

Cheers for letting me know!

[TheoreticalApex]

MT still does not apply to multiplayer servers even if we launch using the bin-mt executable correct?

[Pasquale1986]

3 hours ago, BIGNEWY said:

UH-1H changes will be in a future patch 

Will the UH-1H receive further updates regarding the 3D-Model an the Multicrew-AI?

BTW the MT-Performance-Boost is amazing

[DishDoggie]

My custom made 2.8 missions that ran in Version2.8.38090 will not load in this new update the load window hags in black screen and windows will give DCS not responding window. No mods in mission No mods installed in the game.