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

MSFS20 Internal compiler error C2034 (Solved)

T

Tzetsin

Messages
42
Country
canada
Does anyone recognize this error?

I keep getting this error when i try and build my package. It causes the package building to fail completely.

I've opened backup files and was able to successfully create the package, but after a bit of time it fails again.

So far I've tried rebuilding every file i can and nothing seems to work, i'm at my whits end.
 

Attachments

  • Parse Error.PNG
    Parse Error.PNG
    36.5 KB · Views: 304
Last edited:
Since yesterday's update some Dev's have encountered compilation problems .... and this even if the SDK is normally unchanged :rolleyes:
 
All compilation is done in the sim. The SDK doesn't affect it at all.
 
Tzetsin said:
Does anyone recognize this error?

I keep getting this error when i try and build my package. It causes the package building to fail completely.

I've opened backup files and was able to successfully create the package, but after a bit of time it fails again.

So far I've tried rebuilding every file i can and nothing seems to work, i'm at my whits end.
Click to expand...

Hej Cedrice and Tzetsin

I have the excact same problem, the compilation have worked on and off the for last few days, and im stucked with the Error message in a very large project ;O(

" INTERNAL COMPILER ERROR #C2430: unrecoverable error parsing XML!

I have also tried to roll back the project, but when the compilation is stucked i dosent change a thing, then the next morning everything was back to normal, unfortunately not after yesterday evening, where the process has been stucked. completely ;O(
 
Last edited:
I had a problem, but only concerning the compilation with a MaterialsLib asset
 
Ok I solved this issue.

Turns out it was a single item in the xml file. Im not a code guy at all, but I assume that these are illegal characters or just out of place, I don't know, but either way when I renamed that item the fatal error went away and I was able to build the package normally.

error.PNG


I don't know why it was generated that way, but it was generated that way multiple times. I would start over from a backup, only to have this error pop up again... and again... and again...

If there are any superstitious people out there, this problem child of mine was parking number "13"....
 
Tzetsin said:
Ok I solved this issue.

Turns out it was a single item in the xml file. Im not a code guy at all, but I assume that these are illegal characters or just out of place, I don't know, but either way when I renamed that item the fatal error went away and I was able to build the package normally.

View attachment 70182

I don't know why it was generated that way, but it was generated that way multiple times. I would start over from a backup, only to have this error pop up again... and again... and again...

If there are any superstitious people out there, this problem child of mine was parking number "13"....
Click to expand...
Hej Again
This could very well be my problem, but my xml file are giant and Im no shark when it comes to finding faults in it, so how did you mannage to find it, Thanks for your kind reply
 
Cédrice said:
Beware of (copy) (copy) (copy) ..... it has trouble digesting too
Click to expand...
You are absolutely right, after reading trough a couple of thousand lines i found 3 errors, all in copy lines, and reg. painted lines. It was programming langue, but editing them out, i was able to compile, all is ok, Many Thanks for Your advice ;O)
 
there is a really simple method to find the offending object(s) that doesnt involve searching through the code.

I use the group function for everything, so after making a backup of my files, then making two more backups just in case, i loaded everything up in the sim and started deleting groups one at a time, saving, then try to build the package. I kept deleting things and saving/building until i was able to build the package error free. Then i ctrl Z untill my groups were all back, then deleted just the last group i deleted before i was able to build to confirm that it was only that particular group that had a problem (in case there were multiple errors)

then i did the same thing and systematically deleted the objects from the group until i was able to successfully build.

then i ctrl z to undo the last object and deleted everything except the one i found to have an error, saved it and then went to my xml file which only had a single entry at this point to look at the code.

after all that i was able to pinpoint the error, but in practice simply renaming everything to match my groups would have solved it, though i then wouldn’t have learned anything so it was time well spent hunting down the problem :)
 
Tzetsin said:
there is a really simple method to find the offending object(s) that doesnt involve searching through the code.

I use the group function for everything, so after making a backup of my files, then making two more backups just in case, i loaded everything up in the sim and started deleting groups one at a time, saving, then try to build the package. I kept deleting things and saving/building until i was able to build the package error free. Then i ctrl Z untill my groups were all back, then deleted just the last group i deleted before i was able to build to confirm that it was only that particular group that had a problem (in case there were multiple errors)

then i did the same thing and systematically deleted the objects from the group until i was able to successfully build.

then i ctrl z to undo the last object and deleted everything except the one i found to have an error, saved it and then went to my xml file which only had a single entry at this point to look at the code.

after all that i was able to pinpoint the error, but in practice simply renaming everything to match my groups would have solved it, though i then wouldn’t have learned anything so it was time well spent hunting down the problem :)
Click to expand...
Thanks for this usefull tip ;O)
 
I have the same error and have no idea what caused it. My xml file is 42500 lines and the error message doesn't say which line number is the issue!
 
You must log in or register to reply here.
Back
Top