In my ESSA project I have had troubles on and off when compiling - but have also succeed in adding taxiaprons, deleting others and changing taxisigns. And all of a sudden the compiling errors. The latest changes were to change to taxiways center lights and border lights - and some taxi sign size changes from 3 to 4 (1 being the default for MSFS2020). I dont't understand the error descriptions "Exceeds limitation pattern i -?\d*\.?\d*[FM]?." (Swedish wording). Attaching screenshot of compiler window and airport backup file.
-
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 Parse error - on airport earlier compiled
- Thread starter Sueede
- Start date
- Messages
- 34,981
- Country
OK - this relates to runway deformations and the comma separator that is getting in due to culture settings is not a valid character. I need to find out why this is happening. I might hazard a guess though
EDIT - found it. I will fix it for the next release meantime this will cause errors unless the culture is en-US
EDIT - found it. I will fix it for the next release meantime this will cause errors unless the culture is en-US
- Messages
- 34,981
- Country
I think it is something to do with the way the source xml is generated. If it has commas in it then there is no proper mechanism to change them. If they are loaded by xml via the decompiler it catches it. I think I fixed it for one set of conditions (decompiler) but not if the XML is already populated with comma separators. The xml needs recreating. A save might do it. This may not be quite as trivial as I thought 
- Messages
- 34,981
- Country
Well as far as I can tell there is nothing in the XML (other than perhaps name strings which uses a comma in a valid way. I would almost say that replacing commas with stops would be safe and remove any cultural references in an XML file. Not saying this is the correct answer but it might be a workaround
I reverted back to the Alpha 11 version to see what would change (the idea came from another thread where some issue was handled that way).
After replacing the four Alpha12 patch files with the equally named Alpha11 files I opened the ESSA project and got two successive error messages - see attachments - but no such reaction to openening another but smaller project (ESNU). Both were created from stock. Does these small messages explain anything to you?
EDIT 1: BTW - I opened the ESSA XML file and searched for commas. The search didn't find any.
EDIT 2: Created still another project from stock. This time EDDH. Changed a couple of taxisigns in size and lettering and built the project. Perfect build, no errors.
After replacing the four Alpha12 patch files with the equally named Alpha11 files I opened the ESSA project and got two successive error messages - see attachments - but no such reaction to openening another but smaller project (ESNU). Both were created from stock. Does these small messages explain anything to you?
EDIT 1: BTW - I opened the ESSA XML file and searched for commas. The search didn't find any.
EDIT 2: Created still another project from stock. This time EDDH. Changed a couple of taxisigns in size and lettering and built the project. Perfect build, no errors.
Attachments
Last edited:
- Messages
- 34,981
- Country
Yes - that relates to the contents of the ade project file and there are new elements in alpha 12 that are not in alpha 11 which is why there is an error
- Messages
- 34,981
- Country
Well I have looked at this and I can find the runway deformation which a comma separator. However re-saving the project appears to clear it. I am working with France/French as my current culture and not having any issues with the comma separator reaching the xml source code. I am adding code to force the number separator in ADE to "." I will release this in the next update but meantime I cannot replicate the issue in alpha 12 and I found that resaving the project solved the issue of the runway deformation altitude. I have also doubly forced that to a "." when generating XML
SOLVED for now. There were a lot of taxisigns that were incorrect (either ended with position (black bottom, yellow letter frp, default)) or had an ending type letter (from my changing the former). After correctng these by way of your error window (from the red button down left) it now built a project without errors. Now comma/dot error after all.
- Messages
- 34,981
- Country
OK - that's good