Schlomo1933

Thank you @Special K for your answer. - I updated now my graphiccard to a rtx5090 - updated my bios to version: FK - Disabled the XMP Profile for my RAM with my board driver im not 100% shure... i have a gigabyte aorus Elite AX Bord revision 1.1 But on the Gigabyte Downloadpage i cannot find revision 1.1 . Just 1.0 and 1.X . So u used the driver for 1.X. Is this correct ? Can u confirm this or maybe im a bit stupid ... My 1st Core is still maxed out ... Here is the new DXDiag file . Thank you very much for your time and help DxDiag.txt

asw keybinds ( like strg+4 )stopped working for me after latest oculus update ? anyone else ?

Maybe there is setting wrong with my bios ? I have a gigabyte z790 Aorus elite AX board v1.1 and an intel i9 13900k. Are there any specific settings in bios I have to select ? I have the intel preset profile running and activated xmp 1 for my ram. onboard graphic is switched off. any suggestion?

its the same , makes no difference

For me is also 1 core maxed out. Please @Special K , @Flappie could you please take a look in my Logs ? -I have a clean Win11 Pro install - Cores are unparked dcs.log.old dcs.log debrief.log DxDiag.txt

I found a fix for my stutters !!! I deleted my oculus link app on pc . Reinstalled it and now it’s smooth. Hell yeah !!! but thx to all who tried to help

Quest3, Rtx 3090 , i9 13th gen …. Absolute stutter mess over Berlin , Hamburg and so on…. any ideas?

@reflected had the same problem as you a half year ago. Since then no more problems. What I have done. 1. Delete the meta app on your pc. 2.download and install it again 3.make a hard reset of the quest3 (u will find a tutorial in the quest3 troubleshooting forum) download oculus traytool and check that it uses the correct codec and change the bitrate to 500.

Any news when it’s fixed ?

Thanks for your advices. The thing is, in the phantom (which is older) braking without the chute (I know, use always the f…. Chute) is much easier than in the f14. The Phantom is much more stable while braking than the tomcat And this behavior is just there since the suspension was tweaked by headblur. I dont think it’s a bug. But maybe it’s a bit overdone.

Thank you !

If you need to setup deadzones, curves or saturation : do this directly in the software from the FFB Stick. Not in DCS ☝

Check if your stick is balanced. I have the Rhino FFB base with the gunfighter ultimate grip connected. So the stick is always alittle bit aft and right. Caused by the wheight of the gunfighter. But in the rhino software u can adjust a counterbalance . So in DCS my Stick is on the exact trimmed position.

In the tomcat the antiskid is not working for me. If I touch the brakes a little bit to much after landing, the tomcat starts sliding to one or the other side. Sometimes this will end in a spin. I have this issue since a while now (but can’t exactly tell since when, maybe since the suspension was tweaked). -if I look at the control indicator (alt-enter) the brakes look fine on each input. -I also don’t have red marks in the control setup (brake-axis) window -and also no double bindings (I use the thrustmaster pendulum) btw: f-18, f-16, F-4e the antiskid work just fine. has anyone same issue? If not, has anyone a idea why I have this problem?

Any news on this ?

+1 parking brake was stuck on yesterday for also. Forgot to make a trackfile. Next time …

+1

DCS BS3 has no contrast lock. It’s just a fake lock. (This was never changed since BS1, because the DCS engine can’t handle contrast locks) BTW… The real Ka-50 wasn’t designed for night attacks. Because he has no flir. But the shark can operate at night with illumination rockets for a short time .

@Tom Kazansky that’s maybe your Anti Virus Programm . Set the user folder and the DCS folder as exception in your AV

bump

In the Apache wipers are working fine and remove rain (quest3)

yesterday the vdi screen was working for me as intended. i tryed 6 times wis complete restard of DCS and my PC. In every first missionstart the vdi was working. But today the bug was here again. VDI just strarted to work after mission restart.

Again……You are too heavy loaded for hovering. As you said by yourself, same as all the other who had trouble …

@munkwolf are u not more supporting DCS with your keybinds ? Its been very quite around you for some time now ...

Sound for me like bugs. So post it please in the Bug Section.