Svend_Dellepude

I had old missions that had me sliding around, but new ones don't. This one should have the slide issue F-18 PG FUN.miz

In all respect. This is not a hardware issue.

depressing TDC and then OSB19 on radar page (azimuth OSB) and then press TDC again will lock the radar azimuth to the cursor instead of the nose of the A/C. Pressing azimuth numerous times while radar is in track mode can select azimuth of more than 140dgs and get the radar stuck outside the boundaries. radar azimuth.trk Logs.zip

Devs and testers have many different versions for different reasons.

The Radar seems to get stuck at extreme angles in both elevation and azimuth. Drive radar elevation all the way to the topstop and get nose below waterline: radar gets stuck when returning to line one. Drive radar all the way down to bottomstop and get nose above the waterline: Radar gets stuck when starting the last scan line. In azimuth the radar gets stuck while rolling 90dgs while having the radar perform a lock scan in extreme left or right. radar elevation.trk Logs.zip sys.zip

TARGET script editor is a great tool. programming is almost unlimited. For the A-10 though it makes little sense.

Tracks might not replay correct from version to version, depending on what's been changed.

I guess time will answer that question. :) It have been asked a number of times on this very forum, with no definitive answer.

Falling over itself with 11 tracks in this thread? No disrespect Sir, but maybe that a bit exaggerated.

I find it a bit odd too, but maybe we should try it out. Besides, manipulating OSB's on the right DDI requires you to take your hand of the stick. Not really convinient while maneuvering.

This makes it a different experience all together for those with a TMWH. https://deltasimelectronics.com/products/thumbstick-slew-sensor-adapter Thread here: https://forums.eagle.ru/showthread.php?t=200198&page=19 Not affiliated with this product, but I did get one myself.

Everybody makes mistakes..

It was meant as a humorous remark to the OP, but I guess you guys haven't been in the FC3 area lately. https://forums.eagle.ru/showthread.php?t=137234

How many times was a R-27r fired in Syria?

Maybe ED needs help..?

No no no. I wanna know it all ends. :)

FC4 is coming.

F-16 all the way!!! :D

Because the button state is not syncronized to the cockpit state unless you tick the 'sync' box in options. Dunno if this works in the F-18 yet though. Alternatively, next time you enter the F-18 cockpit, leave the throttles in the midrange, unpause sim, move throttles to OFF and now ingame throttles should work the first time.

Yeah, sorry.That was the one i thought i posted, but realise it wasn't. Haven't seen it since install some time ago. :doh: The Noctua is working fine in my rig. O/C to 4.3Mhz.

If you want to help, then provide the team with some tracks, please. Just complaining about WIP stuff not working is not gonna solve anything.

I'm just explaining how it is ingame right now. Not how it is IRL or how it should be. If you apply force either negative or positive while rippling bombs, you will not get the spacing you entered into the FCC.

Good you sorted it. Yes, you should be at 1G at release to get the spacing right.

Are you at 1G when releasing?

In these times you can never really know. :D