DragonflightDesign
Resource contributor
- Messages
- 1,082
- Country
I'd like to use a very much more coarse and accurate expression but... This applies to both FSX and P3D. Initially, I'm going to keep it simple and start digging deeper with detail if necssary.
None of my SimConnect stuff works correctly to start with. Many switches simply don't work and those that do still work, operate all the other switches as well. They also try to operate the control levers (mixture, throttle, etc.). My save flight routines no longer work in either FSX or P3D. In FSX, if I leave Notepad++ open during a flight save, it tells me that the .flt file has been changed and do I want to reload it? Yes please - only, no change, no additions where I'm writing to it. Ditto the P3D fxml file. Running the debugger while the relevant flightsim is active shows that the code is being stepped through correctly.
No change if 'Run as administrator'.
What part of 'it's my ##@@!!!# PC' doesn't Windows 10 understand? I've had the misfortune to have been forced to work with this POS since the beta days and I don't like it any more now than I did then. I had to rebuild my PC after a M/B failure and found that the current generation of motherboards that are compatible with Intel Coffee Lake all seem to require Windows 10.
I suppose the only good side is that I found this problem now and not at beta test/release point.
[Edit] Neither FSX nor P3D is on the C:\ drive. Both are on the D:\ drive.
None of my SimConnect stuff works correctly to start with. Many switches simply don't work and those that do still work, operate all the other switches as well. They also try to operate the control levers (mixture, throttle, etc.). My save flight routines no longer work in either FSX or P3D. In FSX, if I leave Notepad++ open during a flight save, it tells me that the .flt file has been changed and do I want to reload it? Yes please - only, no change, no additions where I'm writing to it. Ditto the P3D fxml file. Running the debugger while the relevant flightsim is active shows that the code is being stepped through correctly.
No change if 'Run as administrator'.
What part of 'it's my ##@@!!!# PC' doesn't Windows 10 understand? I've had the misfortune to have been forced to work with this POS since the beta days and I don't like it any more now than I did then. I had to rebuild my PC after a M/B failure and found that the current generation of motherboards that are compatible with Intel Coffee Lake all seem to require Windows 10.
I suppose the only good side is that I found this problem now and not at beta test/release point.
[Edit] Neither FSX nor P3D is on the C:\ drive. Both are on the D:\ drive.