Tanuki44

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

Good news, let us hope the next updates will not break again

Indeed, I just tested, the mission does not take place after the message of the tower to prepare for takeoff. I tried with the mission of version 2.5 with the beta 2.7, it does not even start. And French translations are partially broken ... In the mission 4, Wolf1 has a lot of trouble landing to dropp off the troops at the 1st LZ in the mountains... sloping ground (again ???)

After search, I changed libaries for the management of TouchPad PS2 ( https://github.com/kristopher/PS2-Mouse-Arduino ) and also for rotary encoder. ( http://www.pjrc.com/teensy/td_libs_Encoder.html ) No more crash . I made a change on the 'Push' button of the wheel, it works in mode 'toggle' for the slow and fast. I also added a keyboard 12 keys to emulate the F1-F12. Arduino Code for Pro Micro handmouse.ino

Have you executed all the 'instructions' indicated by the co-pilot (A summary is visible by the radio - F10 menu) In general, something is missing for the scenario to continue ...

Even if I understand what you explain, I will have to seek how to put this into practice Thanks.

Thank you for your comment, but as indicated, I do not have great skills in this type of coding. I only assemble some code from the example found on the net. Overall, the mouse wheel works properly with the interrupt when there is not the PS2 trackpad. But when I add PS2 trackpad is a problem. I will try to understand " you should look into other code based techniques such as a confidence counter"

Reuse a trackpad on a old laptop Trackpad source1 Trackpad source2 Known issues : Sometimes the device is not recognized at startup W10 or hangs during operation, It's better to add a button to reset it easily. Can not use interrupt for the wheel (incompatible with the PS2 trackpad ???) the rotation of the wheel should not be too fast, To quickly advance, press the wheel at the same time accelerates incrementation. I am not very competent with Arduino coding, any suggestion will be welcome My arduino code

Thank you for this comment. Of course, I can put these infos and the sources that helped me. I'm always looking for a solution to improve the button 'wheel mouse'. I will gather and publish these elements.

Here is a setting of SnapView that can help (already indicated, sometime ago, but I forgot by whom ) [8] = {--LWin + Num7 : Snap View 7 viewAngle = 20.000000,--FOV hAngle = -10.978332, vAngle = -51.987301, x_trans = 0.164246, y_trans = 0.067000, z_trans = -0.142609, rollAngle = 0.000000, cockpit_version = 0, },

That's it's good, this requires that setting W10 to the desired resolution in DCS.

Finally, I succeeded forcing the 'progressive' mode on the graphics card, But that does not explain why the resolution chosen in the DCS parameters did not force the mode as in 2.5 version

On W10, my desktop is in 1600x900 progressive, my DCS resolution is setting on 1920x1080, automatically resolution change progressive and works perfectly in 2.5. With the version 2.7, I kept the same setting, but DCS stays in 1600x900 p, the resolution of DCS is always the same as that of W10. I tried to put W10 in 1920x1080, but W10 force in interlaced mode, DCS goes well in 1920 but remains interlaced and not gradual, it's a horror , a lot of glitters. Was the only solution to stay in 1600x900? I hope I have been clear enough with my poor english

In Mission Editor

I confirm and this is on the 'cockpit' canal, it is much less or not in flight.