Nereid

As the topic says: If the Recall/Acknowlede Switch id bound to a button on a joystick, it won't work. It works if it is bound to a key. Correction: It works in the pilot seat. It doesn't work for the copilot. VERY annoying.

This would not only disable the E-cores but logical cores (hyperthreading) too. I would suggest FFFF for the 8 core to set an affinity for the first 16 cores (because your 14900K has 24 logical cores). PS: And by using only the first 8 cores you may disable some physical cores too. I'm not sure if logical cores are the later 8 or the odd numbered onse.

Just tested. It is working fine for me. It took about a second to get control and it was not as chaotic as it was a few months ago. Even with wind. I was quite surprised that I did not struggle at all, because I was expecting a bit of a struggle. And there was no need to reset the trim either. But I'm not playing DCS that often at the moment. So maybe I was just lucky.

In the latest patch it seems to be way better now.

I would tend to agree.

Then again the question remains unanswered: Why does an unarmed fuse detonate the bomb if two fues are used but not if one fuse is used? And we do have the option to use two fuses (that is undenyable). This has nothing todo with head or tail fuses

Ah. Thanks. Let's hope they fix it soon. This oscillation makes any targeting in the C/PG seat nearly impossible.

I was switching from pilot to G/CP and ordered George (as a pilot then) to hover. But he fails to hold a steady heading to the target completely. Every few seconds he rotates to the right about 15 to 20 degrees and is then comming back, only to start his rotation to the right again. Even I with my limited skills in a hover would do this better - especially with ATT hold on. EDIT: I have uploaded a TRK-File. It was easy to reproduce. The mission starts in the air so I had to get into a stable hover first. This was done at 05:31:20, heading 30°. I was holding this heading for about 15 seconds and then I switched to C/PG. George took over and at 05:32:00 he had quite a lot problems to hold a constant heading. There is A LOT room for improvement I would say. George-Hover-Problem.trk

They will have do redo it anyway when the new ATC comes out. So maybe it's not worth the time to analyze and fix this.Well, I'm a developer myself and maybe I wouldn't try to fix the problem either. But a few words about it would be nice.

ATC will send you to the wrong direction too. I you follow its orders you will takeoff with the wind instead against it. At least on Ford it does it this way.

Is the ATC not choosinbg the runway depending on wind direction? I'm at Ford, Parking lot 2, wind comes from 41° (7 m/s) and ATC sends me to runway 23. I would say runway 05 would be the better choice.

I tend to agree. If not there is a detailed explanation neccessary in the manual. And if I remeber it correctly the default is 0 seconds for both fuses and both are installed by default. If you change just one of them and deliver them low, it will be a nasty surprise...

So the tail fuse is armed when the nose fuse is armed? Because the bomb detonates with a unarmed tail fuse too... And THAT was my question.

So as Bozon asked: Why is there a nose/tail fusing selector in the panel? Why does an unarmed fuse cause a detonation? Then an unarmed nose fuse wiithout a tail fuse should detonate too. Or does the nose/tail selector arms both fuses and is there just for eye candy? Don't get me wrong: Maybe it worked that way for some strange reasons. But chances are it is just wrong.

I was testing fuse delays on 500 lb short tails and set the nose fuse to 11 and the tail fuse to 0 seconds. I though if I just arm the nose fuse in the cockpit the bomb would detonate 11 seconds after impact because of the delay of the nose fuse the tail fuse isn't armed. But it detonates instantly after impact. Is this correct or a bug? If I set both fuses to 11 seconds the delay works. And was does "plugged" mean for a fuse? No fuse?