davidk64 Posted June 24 Report Share Posted June 24 I read in another post on the forum of a user having trouble seeing the console window and he found that there was an entry in the fsuipc6.ini file ConsoleWindow=0,0,0,0 Once deleted the problem went away. This post is to advise I have encountered the same issue. If I start logging, then stop logging and exit P3D then check the ini file the entry above gets added. A work around is to right click on the console entry in the taskbar and select "size" then use arrow keys to enlarge the window. The issue is repeatable for my setup but presumably 99.9% of users don't encounter it! I imagine trying to work out what in my environment is triggering the issue would be difficult and time consuming. It's hard to imagine the user wanting the console window to be 0 pixels square so maybe a check could be added to the code that creates this line alerting the user there is a problem with their environment? Link to comment Share on other sites More sharing options...
John Dowson Posted June 25 Report Share Posted June 25 I have not heard of this happening before, and this functionality has been around for many years. The ConsoleWindow entry should only ever be written if/when the console window is actually open, and not when any logging is activated. I don't know why it is adding that entry for you, but I guess I can not write the entry if the values are 0. John Link to comment Share on other sites More sharing options...
davidk64 Posted June 25 Author Report Share Posted June 25 After a lot of searching, I found the post! Link to comment Share on other sites More sharing options...
John Dowson Posted June 25 Report Share Posted June 25 25 minutes ago, davidk64 said: After a lot of searching, I found the post! That is 12 years old - way before my time! As I said, I will prevent FSUIPC from writing an entry with all 0's, but I do not know why this is being written occasionally, It should only write that entry if the console window is open, and the position/size is retrieved from windows. John Link to comment Share on other sites More sharing options...
davidk64 Posted June 27 Author Report Share Posted June 27 Thanks John, that may save a future user some time head scratching. Curiously while using the console window to get my switch panel working, I have had no repeat of this issue. I had the thought it was because I was just checking and unchecking the option to display logging in console and was not pressing the stop logging button. But when I tested this and tried to repeat the issue I couldn't! I am surrounded in mystery 🙂 Link to comment Share on other sites More sharing options...
John Dowson Posted June 27 Report Share Posted June 27 Yes, strange. I think this is a windows issue, where it is occasionally returning a null/zero size/position when asked for the window coordinates. Anyway, I have added a check to both FSUIPC6 and FSUIPC7 to not write the ConsoleWindow entry if the size (width and height) is below a certain value. But this is a very occasional issue I think. A more common issue is having the window positioned off-screen, which can also happen, and the fix is the same - remove the ConsoleWindow entry. 1 Link to comment Share on other sites More sharing options...
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