Dears,

I know that LNM is not supporting FS9 as it goes through simconnect, but I would have liked to use the planner disconnected from the simulator; just as a mere planning tool. This should be possible, but the problem is that I cannot create the database from FS9 scenery. Now AFAIK, FSX and FS9 scenery format for facilities: airports, navaids, airspaces, airways and airspaces... So in principle it should be possible for LNM to read the FS9 sceneries and generate a DB from them. The problem is that i cannot even initiate this process to try if it works, as LNM does not find a FSX or P3D installation in my PC.... is it possible to fool LNM and impose it to read the scenery folder that i provide it? If so, how? I tried to create a fictitious fsx.exe in my FS9 installation folder and add the FSX registry key, with no success....

 

 

Sorry, but this is not doable. LNM never supported FS9 and the BGL format and the scenery library have differences.

Alex

Hi Alex,

the folder structure is indeed different, but the bgl format of the relevant files should be the same, at least according to what's on fsdeveloper's wiki. Or better, FSX BGL is adding functionalities (like for airport vehicles), but not deprecating them. Anyway might not work indeed at the end; one question stays: what is LNM checking to assess the presence of one simulator or another? A registry key? A specific path? Many multiple countless things?

 

LNM checks registry keys for FSX and P3D. For X-Plane and MSFS its files.

The registry paths are here: https://github.com/albar965/atools/blob/master/src/fs/fspaths.cpp#L108-L130

Alex

Thanks Alex.

And I was right. LNM perfectly reads FS9 sceneries, populates everything as it should and works perfectly now. Of course, no connection with FS9 itself, but ok, that's something possible.

I would suggest to add this info on your basedoc: usage on FS9 is possible provided you add the key of FSX in the registry and change the path for the scenery.cfg.

PS: great software. Just starting exploring its functions, looks great!

 

5 minutes ago, arrex said:

And I was right. LNM perfectly reads FS9 sceneries, populates everything as it should and works perfectly now. Of course, no connection with FS9 itself, but ok, that's something possible.

Wow! I did not expect this to work. I'll add a section to the FAQ.

Alex

Fantastic. Maybe you should consider to add it in a future release as an "unofficial" support; you just need to add a reg key to check and add as default export the "BlackBox Simulations Airbus". If you want to overdo, disable the "connect" functions

I'll see but no promises.

Alex

Sure, i am even suggesting to maintain fs9 as officially "Unsupported".

PS: I did more tests. Database is 100% working properly, including the magdec and addon sceneries (afcad and bglcomp format). Export format with "Blackbox simulation airbus" is good enough to generate FS9 .pnl, although not 100% perfect.

 

After some days of intense use, I have the final report on use with FS9.

Obviously offline. That's a pity as many amazing LNM functions are inhibited. But I consider this a given.

Database: i did not find any problem, with hundreds of addon and custom made scenery installed. I

Airport Rating: I don't fully understand it. How is it to be computed exactly? According to the instructions, Addon, Apron, Taxyways, Parking and Buildings should each add a "star". Most of my airports have always 2 or 3 stars, even if LNM finds more items

Example this airport should have at least 4 stars:

Grosseto (LIRS)  ★★★−−

Facilities

ALS, Add-on, Aprons, Avgas, Helipads, Jetfuel, Parking, Procedures, Taxiways, VASI

Is it a problem with FS9 or a bigger problem? Not sure. Not a big deal if it's a FS9 problem, if it's a more general problem, you can put it in the buglist....

Flight plan export: not very good here. I unsed initially the format "Blackbox simulation airbus", which is ok-ish, but not satusfactory enough. The format would require 3 easy modifications to be correct. Should be a relatively small task so I would ask if it is possible to implemented it in future versions.These are the corrections:

1. Add the static line AppVersion=9.1.40901 at the top of the file, immediately below the [flightplan] key. The mere presence of this line allows to link the waypoints with the navaids database for use with the internal navitagion module, the kneeboard etc....

2. Add decimale precision in all coordinates

• Example of current coordinates: departure_id=LSZH, N47* 27', E8* 33', +001416.00
• Example of desired coordinates: departure_id=LSZH, N47* 27.25', E8* 33.61', +001416.00

3. Slightly modify the definition of waypoints, adding ahead 3 fields used for linking with the database

• Example of current waypoint: waypoint.5=ZH553, I, N47* 25', E8* 21', +005191.94,U843
• Example of correct waypoint: waypoint.5=LS, LSZH, ZH553, ZH553, I, N47* 25.33', E8* 21.37', +005191.94,U843

Some hints here:

• the red field is the icao_region. To use for Intersections, Vor and NDB, empty for Airports and "custom" waypoints. Empty means it's a just a comma;: "waypoint.5=, "
• The greed field is only used for "terminal waypoints", and it's the referring airport name. For all other type, the field is empty
• The blue field is a repetition (for the database search) of the name of the point. Empty for "custom" waypoint

 

Regards!