• 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.

Error reporting

arno

arno

Administrator
Staff member
FSDevConf team
Resource contributor
Messages
34,020
Country
netherlands
Hi all,

ModelConverterX has had a feature to report crashes and errors to me so that I can debug them. About half a year ago I had to change how this was done due to some changes in the bug tracking software I use. But since then I notice that I do not get error reports from users anymore. But when I test it on my local system the reports are getting through.

So I would like to ask a few users to download this test tool that attempts to write an error report and run it on your machine. Please run if from the command line with this command:

Code: 
ErrorTrackingTest.exe.exe > log.txt

If a few of you can try this once and post the log file you get here, I can hopefully figure out why it is not working consistently. Thanks!

 
Last edited:
Thanks for pointing out the typo.

Your error report came through correctly.
 
I just downloaded the zip, unpacked it to the desktop and ran the command from a command window and got the following error message:

"'ErrorTrackingTest.exe' is not recognized as an internal or external command,
operable program or batch file."

I tried it both when MCX was running and when it was not and got the same error message.
 
OOPS! My bad!
I just ran it again from the correct folder and got the attached log file. Hope that helps.
 

Attachments

Thanks, I think I have found why this test tool works (also for those who tried it) and from the tools it doesn't. Some DLL files were automatically added from an offline Visual Studio nuget, but the machine where I build the development releases automatically does not have Visual Studio installed. So these are missing from the development releases.
 
Last edited:
You must log in or register to reply here.
Back
Top