Tanuki44

In my case, all missions (v2.5 or v2.5 [re-save in 2.7 editor] or v2.7) including the acting times in 2d.

Fully agree for separate commands for switches (this already exists). At startup, synchronization of axes and switches would be simplified, toggles do not allow it. Some missions position switches automatically to help the pilot. During a mission, to correct this 'gap', it is possible to use an unassigned 'modifier' to this switch to put it back in place with no effect on this command.

I'm not sure that I understand the question... The switch of my collective has two positions ON and OFF, these two positions are recognized by DCS like two virtual buttons (BTN15 and BTN16), but it is possible that it is linked from firmware MMJOY. I setted the landing switch with these two virtual buttons, so it works like a toggle.

Have you checked the box in the Options to synchronize commands when starting the missions?

Yes, but flying with a short joystick or a replica of a true cyclic is different in the settings because of the amplitudes of movements.

This is an example for pitch or roll : My Cyclic mechanical course : -35° to +35° for 100% in Windows Joystick manager In RealLife Cyclic course is : -10° to +10° Setting Saturation X to get the most cyclical when it is positioned at + or -10°, (here 70 is the value that corresponds to 10°) beyond this position the value will not exceed 100% Saturation Y is used for the sensitivity of the Cyclic, depending on the sensors and hardware, which may explain that 100%, Gazelle is uncontrollable In the case of my cyclic, Saturation Y cannot exceed 25%, beyond it's flying on your back constantly. In summary : Saturation X = Amplitude Saturation Y = Sensitivity Then everyone settles to their liking

The deadzone is on center of the joystick, but the equilibrium of the helico is never on the center, I preferred to let 0.

The sensitivity of the roll and pitch axes can be adjusted by decreasing the saturation Y value, it is by testing that you will find what the most correspond to your hardware and your sensations of pilot in real life. A topic here :

At home, the 3 : SSAA SSLR SSAO are setting 'Off' and crashes continue....

Do you use MMJOY ? if yes, we must setting a PID / VID different for each device if not, (it's your own soft), you need change the device PID/VID and Name by yourself In "arduino-1.8.13\hardware\arduino\avr\board.txt" for exemple, if it's a ProMicro : micro.name=Arduino Micro micro.vid.0=0x2341 micro.pid.0=0x0037 micro.build.usb_product="xxxxx" for the name under W10 I have never had the worries because all are programmed and modified with MMJOY except one. I hope this will help you.

I started on 5/10 and no crash since, unless I disable compatibility, but this is only a solution in the meantime.

Have you setting the Win8 compatibility on DCS.exe and not on DCS_updater.exe ?

It's more meaningful with a change of terrain

Latest version of W10 and all updates installed

It's just a solution (perhaps) while waiting for better, hope this gives some help to developers. Otherwise, I think it solves some trigger worries in some missions, but can be suggestive ...

Since 3 days, it removed crashes at home, without being able to say that it will not happen again ... sometimes to change terrain, DCS seems blocked at the beginning of the progress bar, but always ends up starting...

Add this line in the default.lua in 'joystick' folder, You can map a joystick button {down = device_commands.Button_1, cockpit_device_id = devices.NETWORK_SYNCH_CONTROLLER, value_down = 0.0, name = _('Request Aircraft Control'), category = _('Flight Control')},

I had problems, crashes and loading time with missions created before the 2.7, some have been resolved by saving the missions with the 2.7 missions editor. Have you tried and also noted that ?

Same for 'optimizations', after several repetitive crashes voluntarily reproduced ( shift 'R' after a few minutes flight), I checked 'Compatibility Windows 8' in DCS.EXE properties.... For the moment, no crash .... Had anyone ever tried this?

+100 ... For me, Full screen deactivation and 'deleting the folder in LOCAL/TEMP as well as the XFO folder' have not changed anything (tested with Huey Module)

Amazing, no texture on the watchtower next to the 2 bunkers, the 2 others do not have this problem... (with OpenBeta 2.7)

I could be the 111 th ... but these crashes are not systematic I like to try to understand if there is a precise event that causes these crashes so I'm looking for ...

I just tested with the latest version OB (patch 2.7.0.5659) The mission works normally (I stopped it, after dropping the first charge at the station)

It's possible, I've never seen it ...

I tried a smartphone like Head Tracker, it worked pretty well, If it's integration is possible it is to try... But a little expensive