Schlomo1933

Don’t need to to that. Just hit the autopilot disconnect button on the stick after engine 2 starts to spool up.

Don’t understand why this issue exists …. the mig29 ff has the same flightmodel as the MiG 29 fc3 so the mig 29 fc3 has the same bug (was also reported several times) for a long long time. And no one from Ed cared about it.

its first time i report a bug and its later fixed for me. But for not for anyone else

U don’t understand the problem that I had and flappie still has. Pls read my first post carefully

@Flappie I double checked the rotorbrake . I move my controller (Saitek throttle quadrant) upwards. the rotorbrake handle moves downwards in DCS. Then I can start the engines. btw: maybe it will help , if you delete this axis and rebind it

For me it’s now in the down position to start the engine. Strange … But I feel more and more disappointed from Ed . The shark gets almost forgotten since the pay update. now u can argue that not many people fly the shark… so the shark is low priority. But with these bugs at the moment, the shark is unplayable at realistic settings. That’s why so less people fly the shark brought! - axis have wrong directions - the abris is freezing - there are a lot of Button bindings missing for on and off. Just toggle are available -autopilot behaves strange in route mode by changing the course and so on…. and all those bugs are present since release. shame on ED …

It’s fixed now.

It’s now 10/2025 . This bug still exists.

Put this please into the bug section . That’s clearly a bug

That would be 100% unrealistic. The ka50 has just the one brake handle on the cyclic . Same as Mi8 and Mi24.

+1 Not just hot start. Also after cold n dark start. Map freezes at some random points while in flight. if you try to change the map size. Waypoints will not scale with it and map freezes instantly.

@BIGNEWY can you please take a look to this thread?

Is it possible that some registri changes from old windows installation was adapted by new windows installation?

@Special K No , i dont run DCS as Admin . And no , i dont use the nvidia overlay @Special K, @scommander2 thank you guys so much for your time and help.

but why just one core for the graphic ? And why so high ?

@scommander2 yes this was in flight. @Special K what u mean with io-pool . Do you mean Input Devices ?

What feels a bit strange for me is: The task manager shows me 32 cores but my processor has just 24 cores and 32 threats.

That’s the question. In all other games all cores work normal. How I said , it’s a fresh win 11 installation… Here is how it’s working via task manager as test . 1. Pic core 0-7 is active 2. pic core is 0-15 active with all cores active: number 0 gets to 100% and cores 1-15 goes like to idle, while 16-32 goes also active

I have nothing running. as i told you i have a clean windows installation. i had just Parkcontrol one time activated to deaktivate coreparking. but its not running anymore just started once. The only things i installed myself is the razr software for my keyboard and the oculus link app for my quest3 VR headset. I made u some screenshots from the backround takes in taskmanager. maybe u will find some strange things. Btw: i installed also now Gforce Expierience to go shure that the nVidia Overlay is disabled. .

I dont have the nvidia overlay, because i dont have nVidia Expierience installed.

Performance with all different settings good 72 fps most of the time (sometimes over Berlin Germanymap it goes down to 36) but temps are over 70 degrees…. but I can’t understand that iam the only one where core 0 and 1 are maxed out don’t know what I can do now.

@Dangerzone thank you for the advice , i have done it . Gigabyte Downloadservice and the Gigabyte Updateservice are not more shown in the tasklist. But the GbtCloudMatrix is still shown in the DxDiag @scommander2 i tried this. Here are screenshots from taskmanager 1- is Core 0-7 active 2-is Core 0-15 active

I tried to deinstall the Gigabyte Center , but the the Gigabyte Downloadservice and the Gigabyte Updateservice are not possible to delete. Here is the DxDiag.log and 3 screenshots how it looks in the Taskmanager. -First Screenshot is Idle -second Screenshot is DCS in Menu VR -third screenshot is DCS flyingin VR DxDiag.txt

It’s while flying everytime

hera are also the logs from last flight debrief.logdcs.log.olddcs.log