• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

A most bizarre error

JB3DG

JB3DG

Resource contributor
Messages
1,325
Country
southafrica
bYzgzlJ.png


So while doing some tests with the gauge studio tool I am building, it suddenly crashed on me when I tried to save the project. When I tried to open the project again, it crashed because 2 key files were corrupted. I had to laboriously rebuild them in a hex editor by hand before I could back up and try to track this problem down. It turned out to be rather interesting as the file writer would always crash when it got to the COM1 element which was always the first one that didn't yet exist. After some messing around with permissions, I then tried copying one of the files and renaming by hand to see if the gauge tool would load it that way and that is when I discovered this rather interesting error. A little google helped me find out what it was all about.

Rather interesting.....
https://bitquabit.com/post/zombie-operating-systems-and-aspnet-mvc/
 
Well, I'm glad that you at least tracked down the proximate cause of the problem! How odd though... :yikes:
 
You must log in or register to reply here.
Back
Top