Patch discussion July 2024

[Weta43]

Interesting - FC3 just works now without my doing anything - noting to install.

Did you try any workarounds to try to get it to work before?

[Nuggetz]

Firstly thanks for the major update and hotfix. 
A couple of anomalies appear to exist for me:

No landing events recorded in the Pilots log. 
Unable to refuel/rearm at any blue base with the blue F16 in the Afghan map with unlimited fuel/weapons set in the mission editor. 
No scores recorded in the multiplayer score table. 

Not sure if this is just me or have others already reported these issues? 
 

Thanks again 

[Kiwi_Viper]

5 hours ago, YoYo said:

Yes the same. 

Plus - now I see FC3 models, installed (11 units available) + Su33 installed before, installed, works from now

Minus - after installation I see still "6" models (?) as available, so I have the same situation as you (maybe its an upgrade licences from Lock On > FC > FC3?).

yeh same except there's nothing in the available are? says 6 available but nothing to install, all the planes are where they should be and i can fly em all so dunno whats up with that

[BIGNEWY]

Just now, Kiwi_Viper said:

yeh same except there's nothing in the available are? says 6 available but nothing to install, all the planes are where they should be and i can fly em all so dunno whats up with that

it is a bug with the old fc3 pack showing. If you have the individual ones and you can fly them please ignore the other prompts for now. 

thank you 

[Kiwi_Viper]

yeh i kinda thought that no biggy im not worried bud 

[joker62]

ED, first of all thank you for your efforts in fixing the bugs in the latest update.

After fix patch 2.9.6.58056:

- the problem of recording flight time and landings has not been solved.

- the graphic stutter has decreased a little.

- new problem: radio menu > F5 (ATC) > F1 (CVN-71) > only F11 (Previous menu) or F12 (Exit), the INBOUND option no longer appears.

test in Mariana + SC + F-14. Thanks for the attention.

[BIGNEWY]

2 minutes ago, joker62 said:

ED, first of all thank you for your efforts in fixing the bugs in the latest update.

After fix patch 2.9.6.58056:

- the problem of recording flight time and landings has not been solved.

- the graphic stutter has decreased a little.

- new problem: radio menu > F5 (ATC) > F1 (CVN-71) > only F11 (Previous menu) or F12 (Exit), the INBOUND option no longer appears.

test in Mariana + SC + F-14. Thanks for the attention.

thanks for the feedback, it maybe worth a new thread for the atc issues you are seeing, a track replay example would be great. 

 

[Mordants]

On 7/23/2024 at 2:45 AM, KeyserSoze62 said:

Update did not correct the Launcher showing 5 updates available with nothing there. In fact now it shows 6 available.  It did fix the in game module manager error. No longer asking to install FC3.

 

 

 

I am showing 6 available too. Additionally I have no controls for the former FC3 modules at all. The controls page is completely blank for my A10A. I can select the airframe in my mission that has it but can do absolutely nothing with it. Just stare out the cockpit window. I have no controls apart from the Esc key to get me out. Any thoughts anyone?

Problem regarding no controls sorted by disabling DCS-Input-Command-Injector-Quaggles mod.

 

Edited July 24, 2024 by Mordants

[Volator]

23 hours ago, BIGNEWY said:

Spotting Dots - In the previous update, we adjusted this behaviour that many of you noticed. This is still very much WIP and being adjusted. We welcome your feedback and will be monitoring it.

Pre-adjustment I (non-VR user) was able to see contacts satisfyingly and more realistically after years of frustration - at the price of many VR users reporting seeing dots as huge blobs, which had a huge negative impact on multiplayer.

Now, post-adjustment, everything seems to be back to the status that I experienced in all those years before. Dots are harder to see again and enemy aircraft very easy to lose visually in a dogfight. I only checked twice in SP, but my first impression is that this new dot spotting thing is a step backwards.

[Eldur]

23 hours ago, ricktoberfest said:

The oculus (meta) beta drivers don’t work with openxr toolkit. It crashes on loading. 

 

I guess, and I hope so that it won't affect running it through Virtual Desktop just using SteamVR. Never really had any visible or noticable advantage with OXRTK, probably did everything wrong with it (I gained a few fps with turning on FFR, but that's just waaay too visible in a Quest 3 and IMHO not worth it). And since it isn't being supported by the dev anymore, its decline is evident.

 

Still waiting for my Moza AB9 anyways. And since I wanna learn some new modules, I better do that with the new setup.

[71st_Mastiff]

Im in VR and now there is no more dots!!!

[Hotdognz]

This may have been the biggest patch in a long time but the amount of bugs and issues it introduced have seen usage on our servers drop to the lowest I have seen since I started with our group 7 years ago, mid week now we hardly see any one flying (used to at least be 10 consistently).

I think personally its due to the helo scripting issues that have came with this patch, as most of our missions are helo dependent on capturing stuff these bugs have caused all our big main missions to be broken and our pilots are off playing other games.

Edited July 25, 2024 by Hotdognz

[Slippa]

Since the second buggy update (the last two were cleavers), MP servers have been unbelievably laggy.

At times it stutters, freezes then crashes to desktop. Slots at airfields are bugged too so that no-one can get in and fly anything. Rebooting and reloading after cleaning whatever files anyone suggests doesn’t always help. People with far better hardware than me are saying it’s unusable for them too. 

I had no trouble in a lightly populated mission in SP thankfully but I’m learning a few things on MP servers and getting tips and advice on things has been great. The night before last it was juddering so bad even the chat was laggy before the whole thing packed up again.

I do hope for a fix but since the last update seems to have made some things worse than the previous one I don’t know where we’re gonna be? I’d leave a track or something to help but don’t have anything like the trouble I’m having in MP if I fly offline. MP’s carnage as things are.

[draconus]

On 7/23/2024 at 4:33 PM, joker62 said:

new problem: radio menu > F5 (ATC) > F1 (CVN-71) > only F11 (Previous menu) or F12 (Exit), the INBOUND option no longer appears.

test in Mariana + SC + F-14

Unable to reproduce. Works fine for both A and B Tomcats.

[Wingnuts]

Last night I hosted a MP for three players "Foothold - Saini". All three of us suffered stuttering and freezes. Long pauses attempting to select slots. FPS counter was going from 0 to12 to 44. I ran the cleaner, dumped the FXO and Meta Shaders2 files. Folks this sucks. Before the patches I was getting a solid 90 to 100 FPS while hosting. I'm running a i12700 at 5gh with 64g of ram. things ran fine at 1920x1080.

ED please focus on a patch to repair this.

[71st_Mastiff]

3 hours ago, draconus said:

Unable to reproduce. Works fine for both A and B Tomcats.

had this issue in the Huey on Rotor heads the F10 radio sometimes is missing. and no response from the ATC. Server owners just say disconnect and rejoin. Which works, but I have to do it almost every single time to get the radio F10 menu to show up.

[Recluse]

On 7/23/2024 at 10:33 AM, joker62 said:

- new problem: radio menu > F5 (ATC) > F1 (CVN-71) > only F11 (Previous menu) or F12 (Exit), the INBOUND option no longer appears.

test in Mariana + SC + F-14. Thanks for the attention.

I have been seeing this (mainly in Multiplayer) with almost all aircraft intermittently for quite some time. It popped up again last night. For me, it usually happens after landing at a friendly base. When I try to contact ATC again to taxi and takeoff, I get the same thing (only F11 or F12 menus appear).   USUALLY once I take off, I get the menus back with the INBOUND and other options, but sometimes not.  I made a report on this (after landing issue) quite some time ago.

 

 

 

Edited July 25, 2024 by Recluse

[imacken]

On 7/23/2024 at 7:59 AM, imacken said:

Has this update fixed the Tobii ET issue with the launcher? (I’m away for a few days, so can’t test.)

Just managed to try the update.

Sadly, no fix for the Tobii/ED Launcher issue.

@BIGNEWY do you have any idea when this will be fixed?  Thanks.

[joker62]

On 7/25/2024 at 5:38 PM, draconus said:

Unable to reproduce. Works fine for both A and B Tomcats

Yes thanks, I found out where the problem was. I need to enable the 'allow airboss' option from the carrier properties window in mission editor and communications with Carrier ATC are possible again. It therefore seems that Carrier ATC is now linked to enabling the Airboss function.

Edited July 27, 2024 by joker62

[draconus]

33 minutes ago, joker62 said:

It therefore seems that Carrier ATC is now linked to enabling the Airboss function.

No, it's not.

[joker62]

53 minutes ago, draconus said:

No, it's not.

oh ok, it's probably just a circumstance. Anyway, now Carrier ATC is working again for me and that's the important thing. Thanks.

[Tea-Pig]

On 7/22/2024 at 6:19 PM, BIGNEWY said:

Spotting Dots - In the previous update, we adjusted this behaviour that many of you noticed. This is still very much WIP and being adjusted. We welcome your feedback and will be monitoring it.

These new spotting dots are working great for me. They look good at long distance and the aircraft just grow from them as they get closer with no jumpy transition. Good job ED. (VR, QuestPro, Oculus Link, RTX4090)

Canopy reflections are a problem on the re-vamped FW190 Anton. Too strong and don't respond to slider in setup menu. Also they flicker with head movement.

[scommander2]

On 7/23/2024 at 10:33 AM, joker62 said:

- new problem: radio menu > F5 (ATC) > F1 (CVN-71) > only F11 (Previous menu) or F12 (Exit), the INBOUND option no longer appears.

test in Mariana + SC + F-14. Thanks for the attention.

It was tested in the 4YA MP in Mariana:

[Kang]

Wonder what the next patch is going to bring.

I would have liked to participate in the screenshot contest currently going on, but at this point 'show the action' would mean I just submit a 4k version of the 'DCS has crashed' window and that would rightly be considered a bit passive-aggressive. Especially since most of these crashes send me straight to desktop without said window or a log entry.

[Tea-Pig]

My Oculus driver downloaded an update last night that appears to fix the OpenXR Toolkit crash issue.