imacken Posted August 16, 2017 Share Posted August 16, 2017 Since yesterday, I have lost all clickable cockpits in release and beta installs. 2.1 is fine. I see the cursor, but it never turns green to click! I've tried a repair on both, but no difference. Posted here rather than bugs and problems as it affected 2 installed versions. Any help appreciated! Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
ED Team BIGNEWY Posted August 16, 2017 ED Team Share Posted August 16, 2017 which aircraft? please attach your logs we need more clues :) Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status Windows 11, NVIDIA MSI RTX 3090, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 64GB DDR @3200, ASUS ROG Strix Z490-F Gaming, HP Reverb G2 Link to comment Share on other sites More sharing options...
imacken Posted August 16, 2017 Author Share Posted August 16, 2017 OK, I've worked it out! Both 1.5 installs started working OK again, so I thought 'what have I changed'. The answer was that I had swapped head tracking setup. I am currently using both TrackIR and Opentrack as I am testing them out. I have been using Opentrack for a long time without any issues, but a day or so ago I updated to 2.3.9 which may be significant. The bottom line here is that 1.5 release and beta (I know they are the sme build) clickable cockpits don't work with Opentrack 2.3.9 but are fine with TrackIR 5.4. 2.1 is OK with both. Interesting! Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
imacken Posted August 16, 2017 Author Share Posted August 16, 2017 After a couple of hours of trying to understand why this is happening, I have worked out that it is to do with full screen and alt-enter. Haven't sussed it out completely, but there is a difference in how 1.5 and 2.1 initialise. Opentrack seems to be fussy about the whole full screen thing, whereas TrackIr is not. If DCS is not in full screen, then the clickable cockpit doesn't work with Opentrack until alt-enter is hit, then it does. I'm sure something has changed recently as I never used to have this issue on 1.5. I don't use 1.5 often, except for the training missions on new aircraft or to refresh my memory! Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
imacken Posted August 17, 2017 Author Share Posted August 17, 2017 Ok, so I have now worked out the problem, and I am surprised that no one seems to have reported this. There is a major issue with 1.5.7 in that if you run it at a resolution lower than native, the mouse cursor is about half a screen offset, which is why I reported that the cockpit was no longer clickable. At the time, I didn’t fully know what was going on. Effectively, when running at a lower res, 1.5.7 opens in a window the size of the res set. On hitting alt-enter and loading a scenario, the cockpit is unusable for the reasons I stated above. This is a problem as running on 4K or 5k monitors at native res is not practical. I have tried on another computer than my own and the issue is the same. I don’t use 1.5 much, but I am very sure this did not happen in 1.5.6 as I have played that a lot in the past before I moved to Open Alpha 2 some months ago. Fortunately, this issue does not occur in 2.1.1. Is ED aware of this? Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
imacken Posted August 17, 2017 Author Share Posted August 17, 2017 Here is a screen shot to demonstrate. The tip relates to the MFD knob, but the cursor is nowhere near! Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
imacken Posted August 18, 2017 Author Share Posted August 18, 2017 Easier to see on this attahcment. It is clearly a 1.5.7 issue as I reverted my release install to 1.5.6 and there was no problem in that respect. So, 1.5.6 and 2.1.1 work fine and 1.5.7 doesn't. I'm going to raise a support ticket as nothing seems to be happening here. Intel i7 12700K · MSI Gaming X Trio RTX 4090 · ASUS ROG STRIX Z690-A Wi-Fi · MSI 32" MPG321UR QD · Samsung 970 500Gb M.2 NVMe · 2 x Samsung 850 Evo 1Tb · 2Tb HDD · 32Gb Corsair Vengance 3000MHz DDR4 · Windows 11 · Thrustmaster TPR Pedals · Tobii Eye Tracker 5 · Thrustmaster F/A-18 Hornet Grip · Virpil MongoosT-50CM3 Base · Virpil Throttle MT-50 CM3 · Virpil Alpha Prime Grip · Virpil Control Panel 2 · Thrustmaster F-16 MFDs · HTC Vive Pro 2 · Total Controls Multifunction Button Box Link to comment Share on other sites More sharing options...
Recommended Posts