Svend_Dellepude

Yes it is. But you need to keep it pressed. A momentary button won't work..

You could upload to google drive or dropbox and paste the link here

If you haven't seen it, this tool will let you manage all CMS programs

It seems a bit weird that the joy axis is scaled about 2:1 when pushing the stick from center compared to pulling from center. Maybe that is why ppl have issues with PIO if you trim perfectly for landing. I programmed my WH to have full virtual deflection when pushed about halfway. It seems more intuitive.

There is a sun filter that overlays the HUD. I normally use it when heading towards the sun.

I have a button assigned to permanently override the limiter.

If you trim for landing i think it uses more forward stick motion. Not sure though.

If possible choose POS/GPS and not POS/AINS. It's an issue with the INS drift. Also do not update anything using landmarks. That will make the CCIP fall line go crazy.

You can use the USB codes for ,.;: in the help file to make it work.

Probably still this issue.

If you are using the color mod, then thats the problem. It somehow mess the rwr scope up.

try to delete the specific input folder/file in the specific aircraft folder in you saved games\DCS folder.

Having flown this nice module for a while now, I have come to the conclussion that I don't need non linear controls for the F-14. There is something with the way the trim works in this module that is different and better working or more intuitive, than the F-5, MiG-29 and other ones. I therefor no longer wish for a non linear option. Just keep it like it is.

You could try to move the entire ...\input\F-18\ folder to the desktop from your ...\user\saved games\DCS open beta\ dir to see if that does anything. If that solves the problem you can copy the sub folders in the F-18 dir back one by one to find out what the culprit is.

Not implemented yet i suppose.

This Image shows that A/P ( autopilot) is still engaged, which would cause the problems you describe. You can just make it out on the left DDI caution line. Make sure you disable it with the paddle switch.

I know this is a bug. But, until this is resolved do this: select amraam/sparrow mode, press and release designate on an empty space on the radar format. While the radar is doing the narrow search, change weapon mode to amraam/sparrow/sidewinder. You will now have regained control of elevation in RWS.

Toggle AUTO/MAN should fix. Otherwise placing the cursor on ana empty space, press designate and then change weapon mode should do the trick. Worked before the patch.

I don't know anything about your joystick and I don't know what other modules you are refering to.

A real pilot has a 50cm stick mounted on the floor which has a very large movement in comparison to a desktop mounted joystick.

The HMD doesn't yet take altitude into account, which seems to mess up both the radar and FLIR.

https://www.raidsonic.de/products/external_cases/mm_cardreader/index_en.php?we_objectID=776 Build like a tank!

Maybe both if you're lucky..!

Use the AZ/EL page to manipulate azimuth and elevation in TWS. BIAS in it's current state only makes your life worse. EDIT: After going AUTO->BIAS->RESET I can just toggle AUTO/MAN back to MAN and I can use elevation again.

You should include a track of this happening. I've never had this happen, nor heard about this happen to others.