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

Re.r23

T

toktiny

Messages
24
Country
ireland
HI Russell,

I have found a small problem with R23. It is in the de-compiling area. I have tried to de-compile some airports and it works perfectly however in other airports such as EBBR,EGLL,LFPG and others it would not de-compile.

As an example of what happens I will take the three airports above :

EBBR File0601 APX49130 Crashes while de-compiling Airport EDLD
EGLL File0501 APX47130 Crashes while de-compiling Airport EGFF
LFPG File0601 APX48140 Crashes while de-compiling Airport LFPB

Now what I did was to remove R23 and reload R22 and with the old method of de-compiling I decompiled the above APX's and then using R22 I selected firstly the airports that R23 had crashed on EDLD,EGFF,LFPB and they de-compiled perfectly. I then did the same with EBBR,EGLL,LFPG and they also de-compiled perfectly.

I was wondering is it a question that there are too many airports in some of the APX's and R23 crashes when it meets its quota ? Just a thaught.

Regards

TokTiny
 
EGLL is Heathrow isn't it? I successfully decompiled that bgl file and opened the airport during testing.

What happens when it crashes? Does it just simply freeze or does it crash to desktop?

It does need a lot of memory to decompile the larger bgls, up to 256MB, do you know how much memory your system has and how much FSX Planner is using at the time?

-Russell
 
@Tokiny

For extracting and saving default FSX airports as an xml file I always use the programm SDE. Never had problems with it (EBBR, EGLL and LFPG work fine too) So it doesn´t matter what Flightplanner version you use. No problems with APX..multiple airport files.
 
Last edited:
Re: R23

Hi Russell,

To answer your questions :

1. Yes this is Heathrow and the other two are Brussells and C.De Gaule

2. It freezes does not crash

3. I have got 2G/B of memory

4. I have read the other post regarding R23 and from it I used the test which you suggested to test memory usage. You said it should show a MAX of 256MB,TOTAL of 256 MB and last FREE not less than 1 MB.

If we take solely the EGLL Airport as a test, my readings taking the same XML for both R22 and R23 in the order of FREE - TOTAL - MAX are as follows :

START-UP IN-PROCESS
R22 8.73 40.28 63.56 24.46 40.28 63.56 ( DeCompiles OK)
R23 2.21 4.94 63.56 .57 63.56 63.56 ( Freezes )

From this I can deduct two things R22 does not require as much memory as R23 and these readings as regards memory do not comply with what you say they should be. I cant understand with 2 G/B of memory why this should be, any ideas ?

You also asked the other gentleman to see if there was anything in the LOG file and below is what I found in mine :

ERROR: [19-Aug-2007 19:15:27]
java.net.MalformedURLException: unknown protocol: c
java.net.URL.<init>(Unknown Source)
java.net.URL.<init>(Unknown Source)
java.net.URL.<init>(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.setupCurrentEntity(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startEntity(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLEntityManager.startDTDEntity(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLDTDScannerImpl.setInputSource(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.dispatch(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$DTDDriver.next(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl$PrologDriver.next(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(Unknown Source)
com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(Unknown Source)
com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(Unknown Source)
com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(Unknown Source)
com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(Unknown Source)
javax.xml.parsers.DocumentBuilder.parse(Unknown Source)
com.zbluesoftware.fsxp.engine.RecentFileEngine.readRecentFiles(RecentFileEngine.java:167)
com.zbluesoftware.fsxp.engine.RecentFileEngine.<init>(RecentFileEngine.java:59)
com.zbluesoftware.fsxp.engine.RecentFileEngine.getInstance(RecentFileEngine.java:71)
com.zbluesoftware.fsxp.FSXPlanner.<init>(FSXPlanner.java:144)
com.zbluesoftware.fsxp.FSXPlanner.main(FSXPlanner.java:102)


This may mean something to you but I am afraid it is way over my head to mean anything !!

Lastly in case it is relevent the Java I am using is the one you directed me to in an earlier letter : JRE 1.6.0_02

Many thanks

Regards

Toni
 
Is it crashing on opening the xml file or decompiling the bgl file? Release 22 didn't decompile the bgl's. It seems to me that you are saying that the same xml file opens in R22, but not in R23. Is that correct?

Also, are your bgl files stock, or have any changes been made to them?

-Russell
 
Re. R23

Sorry Russell that is what I meant.

Second question : No these BGL's are as they came with no change.

How is the difference between what you say should be there MAX 256 MB against what is showing as MAX 63.56 MB in memory ?

Could this be an adjustment of memory usage or allocation in my system ?

Regards

Toni
 
toktiny said:
How is the difference between what you say should be there MAX 256 MB against what is showing as MAX 63.56 MB in memory ?

Could this be an adjustment of memory usage or allocation in my system ?
Click to expand...

It should say Max of ~256 MB. This is the total memory that FSX Planner is allowed to use. The Total starts out at ~64MB. This is the total amount that is currently allocated by the JVM for the app. Free is the amount of the Total that is currently available. So if free goes to zero, then the total will increase until it hits 256 MB at which point you'll have problems.

In my testing with the biggest bgl files 256 Max was sufficient.

So for you does it say Max of 64MB or 256MB? If it says 64MB then something is strange. The exe file is supposed to set it to 256 MB. If you are launching FSX Planner by double clicking on the FSX Planner.jar file then you will only get 64MB available. FSX Planner.exe should be used to get the full 256MB.

-Russell
 
Russell you have put your finger on it. I was using the desktop icon which I set up for R22 for FSX Planner.jar .I did not anticipate that the start up for R23 was any different.

Now by using FSX Planner.exe as you say gives it the 256 MB Max which in turn is now plenty of memory for the Big Files. Tried EGLL and it decompiles perfectly.

Many thanks for all your help and FSX Planner gets better all the time.

Keep up the great work you are doing for all us simmers.

Regards

Toni
 
You must log in or register to reply here.
Back
Top