Thomas_GER

Thank you - very helpful

Ah ok - but that means that the moving map works without the GPS. I assumed that also the moving map should not work

Hi all, when I setup CW Germany in a time period for example in 1985 I see that the GPS of the KA50s does not work anymore….but not so for the Apache. Shouldn‘t the GPS as well as the FCR be inoperative in this time period?

Ok….good to know: In the 9800X3D enabling the X3D Turbo Mode DISABLES SMT, although SMT is set to Auto. I will test now with X3D Turbo Mode OFF Update: O - M - G……thank you for pointing me on that. Turning off the Turbo Mode shows now physical and logical cores and the balancing works buttersmooth.

I double checked - SMT is activated (or on AUTO, there are only 2 options either AUTO or DISABLED) I will have to dig into deeper cause there is also a X3D Turbo Mode where it is stated that the CCD function gets disabled….whatever this means.

No it is the opposit - at least for me: If I do NOT setup any affinity I see this behavior. Then I jump in and set affinity (where I leave 1 or 2 cores that I do not designate to DCS) and it works. Had exactly the same today in a MultiPlayer mission. Tried to slot and it took for eeeeeever. Then changed affinity and bam....I was in the slot. Please find the log here. I could re-produce this issue 3x now. It is usally one of the render Cores, according to process lasso it is Core 1 (so not "0" but "1") dcs.log

I can confirm that I have the same phenomenon with an AMD 9800X3D. But it does not occur everytime I start DCS. However if it occurs then it even shows up when I am just in the mission editor. And when start a mission and jump into a slot it takes forever to get into the cockpit. Usually when I change the Core Affinity in Process Lasso when this happens - it kind of "unblocks" or speeds up DCS and I find my self in the cockpit immediately.null dcs.20250308-094914.crash dcs.20250308-094914.dmp dcs.log.old

I got an update on this topic here. Did several tests and could narrow the issue down to 2 possible root causes: 1.) AV1 Codec I had a stable performance lately but I used mainly the HEVC 10-bit Codec. As soon as I switched to AV1 I got immediately a headset freeze - so there seems to be something causing the issue in combination with AV1 2.) Resolution and Frame Rate I got the impression that with too high graphics AND frame rates settings I get also a freeze. Therefore I had to realize that the labels of the graphics settings (High, Ultra, Godlike) in combination with the mentioned graphics cards in Virtual Desktop is misleading. In the VD discord I read that the graphic setting of "High" equals to 1.2 of the Quest3-Resolution, "Ultra" is 1.3 times the resolution and "Godlike" is 1.5 In the Quest Link app I never used more than 1.2 - so this is something to keep in mind when playing around with the graphic. And it is something that explains how much data has to be processed and streamed to the headset. This is the resolution per eye (!) produced by VD with the given graphic modes: Quest 2/Pico Neo 3/Quest Pro/Quest 3 Potato: 1440x1536 Low: 1728x1824 Medium: 2016x2112 High: 2496x2592 Ultra: 2688x2784 Godlike: 3072x3216 (Quest Pro/Quest 3)

Sound good. I can clearly produce massive stutters in the Apache when I look down right. This is really crazy as I get nowhere else those stutters. Seems to be the case that there is something (MFD with the Map on it?) that drags a lot of performance. So reducing Hz should help.

So my takeaway is to set the codec to NOT av1. will test this and give feedback here.

I am suffering exactly the same issue. Are you guys using Virtual Desktop with OpenXR or with SteamVR? I saw posts somewhere else where it was assumed that OpenXR might be a root cause for the freeze.

The multiplayer capability is a fair point. This is something I will also check out.

I was on Server 2 - that was the error - although I never changed any setting concerning the server. Nice work with the update - the error messages are gone now.

I purchased it and played the first mission. My first impression is both positive and negative. I like the voiceovers, the briefing material is very good and the mission itself is nicely structured. But what annoys me to no end is the fact that not a single radio frequency is preset, so that I as a pilot have to change all the frequencies. On the way to the AO, I first have to manually set the ground frequency, then the tower, then departure and then AWACS. This was solved much better in the “Four Horseman” campaign - just as it would be in reality, namely that certain frequencies are already preset and that the frequency changes are made by the CPG. The CPG also says “Fence In” - but does nothing. This is also done better in “The Four Horseman”. Perhaps this can be fixed with the next update.

My DCE Manager states that it has a new version available but just downloads an empty ZIP File. Where can I find the new version?