roland_lfor Posted February 12, 2022 Report Posted February 12, 2022 And no error is written in fsuipc7.log after the CTD. How can I know what is wrong with my script? I'm using the MSFS beta 1.23.9.0, is FSUIPC build linked to a specific MSFS version (then not compatible with beta)? Thanks
roland_lfor Posted February 13, 2022 Author Report Posted February 13, 2022 I realized that this issue came out since I maximised (by error), then minimised my output window (from Wnd library). In FSUIPC7.ini, I have deleted the entries in [ExtWindow] section to solve the issue. It seems that the Wnd library does not like Wnd.text() calls when the output window is minimised.
John Dowson Posted February 13, 2022 Report Posted February 13, 2022 1 hour ago, roland_lfor said: It seems that the Wnd library does not like Wnd.text() calls when the output window is minimised. Ok, that is strange. I will take a look when time permits to see if anything can be done. It certainly shouldn't cause a CTD. John
John Dowson Posted February 2 Report Posted February 2 On 2/13/2022 at 11:43 AM, John Dowson said: Ok, that is strange. I will take a look when time permits to see if anything can be done. It certainly shouldn't cause a CTD. I have finally gotten around to looking into this. The problem was that when you exit FSUIPC the size/position if all Wnd library windows is saved and used to set the size/position the next time you tun FSUIPC7. If the window is iconized, the size/position was still saved, but using this to restore when next run gives issues as the iconized size is then used on the window which is not initially iconised. I have fixed this by not saving the window position if/when iconzed. This update will be in the next release of FSUIPC7 (7.3.6). John
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now