Recommended Posts

Was very recently informed by a fellow pilot about VMRGenerator. Consequently downloaded latest version (8.3), and did run it a couple of times until getting most of the errors or missing information fixed.

My main issue remains about the VMRGenerator.log... I am running P3Dv4.1, and have quite an extensive simobjects.cfg file on board.

Well, a huge pile of aircrafts so far are still missing atc_parking_codes entries, which I can fix slowly but surely. However, my main concern is about P3D's stock aircrafts, where I am finding strange comments into the log, for instance

F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\beech_baron_58\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\beech_baron_58\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Beech_King_Air_350\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Beech_King_Air_350\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Bombardier_CRJ_700\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Bombardier_CRJ_700\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\C130J_AI\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\C130J_AI\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Commercial_Airliner\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Commercial_Airliner\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DH_Dash8_100\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\DH_Dash8_100\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\F-14\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\F-14\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\F15\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\F15\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\F16\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\F16\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Fury_1500\Aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Fury_1500\Aircraft.cfg
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\JF_L049\L049_Paintkit\JF_L049_PAINTKIT\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\KAI_T50\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\KAI_T50\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Lear45\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Lear45\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Maule_M7_260C\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Maule_M7_260C\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Maule_M7_260C_Ski\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Maule_M7_260C_Ski\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Mooney_Bravo\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Mooney_Bravo\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\MV-22\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\MV-22\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PA28_180\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\PA28_180\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Piper_J3Cub\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Piper_J3Cub\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\RQ170\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\RQ170\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Tornado\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\Tornado\aircraft.cfg
F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\TU-95\aircraft.cfg does not contain a [fltsim.x] section
Ignored: Line Atc_model= is missing in F:\Lockheed Martin\Prepar3D v4\SimObjects\Airplanes\TU-95\aircraft.cfg

Have been trying with atc_model and Atc_model, but result is the same.
There are [fltsim.0] and up in each aircraft.cfg files.
The atc_model entries do comply with the ICAO documentation available on line (BE58, B350, A321, DH8A, F14, F15, F16) for some I already did check, and the remaining stock aircrafts are being checked.

But why these 2 messages for each stock aircraft, when some are fully compliants, and others non-compliants on atc_model only?

Thank you for your comprehension and assistance.

Blue skies

 

 

 

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

HI,

You are scanning the wrong folder... SimObjects\Airplanes is a folder with Flyable aircraft.

VMRGenerator is about AI aircraft. Normally they are (and should be) installed in a folder different from Airplanes.

Nico

 

Share this post


Link to post
Share on other sites

Nico,

Thank you for your return.
I do fly much more small to medium aircrafts than big airliners, and also prefer VFR, or flying between smaller airports, or bush flying in remote locations together with some good fellow pilots.

Being running P3Dv4.1 with 16Gb of RAM, I was considering using also the flyable aircrafts to display other pilots on line, when their aircraft is one of the aircrafts (stock, or addon) installed into my simulator, to see them as they actually are (thus my scan also of the P3D stock airplanes folders).
Is this possible with the latest version of VMRGenerator, or does this version automatically exclude or bypass the stock aircrafts, thus the funny remarks about missing data?
Will I have to write/add by hand the relevant matching rules, instead of installing AI versions of aircrafts I already have as flyable models?

My setup is done in a way that all third party aircrafts are outside P3D, with specific folders for flyable, MP (bush flying away from medium to heavy traffic areas), and AI liners. And I am scanning them all, but am wondering abouth the "strange" reports on stock aircrafts.

But I would also like to thank you for that very interesting program, about which I am learning a little bit more each time I use it, and of course each time I get some additional information... ;-)

Any additional information or advice will be appreciated.

Have a good day, and blue skies

Philippe

 

Share this post


Link to post
Share on other sites

Hi Philippe,

VMRGenerator is not excluding Stock aircraft. However, most of them siimply do not comply to the VMRgenerator requirements for being recognised as AI aircraft for vPilot. That's why you get these (what you call strange) reports ...

Note that the Atc_model= line is expected to be in the [General] section of the aircraft.cfg file (not in a [fltsim.x] section). Maybe that helps you a bit further...

Nico

Share this post


Link to post
Share on other sites

Niko,

Meanwhile was prompted by the software to get the latest version, which is for me the x64 v9.0...

The stock aircrafts supplied with P3D v4.1 do have completely normal structure when displayed in any simple text editor, understand the [fltsim.xx] sections are there, and the atc_model is in the [General] section.
Using the standard Notepad supplied by W10 (when you want to "save as", you see a field evidencing the coding of the file, which I never remarked before...), I found out that all the stock aircrafts reporting errors in the VMRGenerator.log have ther aircraft.cfg files reporting Unicode encoding.
So I tested various encodings (the few choices are ANSI, Unicode, Unicode big endian, and UTF-8), and selecting ANSI as well as stating an atc_parking_code=PVT, did let the relevant aircraft free of any remarks inside the VMRGenerator.log and placed it inside the AI Matching Rules Generated.vmr file.

Now, using a more powerful text editor, for instance Notepad++...
Opening an aircraft.cfg file (reported to be Unicode by Windows standard Notepad), and clicking on the encoding menu tab, it shows an UTF-16LE encoding. Selecting then "Encode in UTF-8 (without BOM)" will also get the aircraft outside of the VMRGenerator.log, and place the aircraft inside the AI Matching Rules Generated.vmr file if any atc_parking_code has been added to the aircraft.cfg.

So it looks to be an aircraft.cfg file character encoding issue.

I have presently a long haul flight running, so will check once it is completed what my P3D thinks about the few files encoding changes.

Blue skies

Philippe

Share this post


Link to post
Share on other sites

Well, did start my P3D v4.1 again, and so far no specific trouble with the aircraft.cfg files which I did save with an other encoding than the original one...
Question being how long will P3D accept various encodings of the aircraft.cfg's amongst others, as if I am not confusing, I read already a while ago that LM moved to a UTF-16 encoding.

Blue skies

Philippe

Share this post


Link to post
Share on other sites
18 hours ago, Gooneybird565 said:

So it looks to be an aircraft.cfg file character encoding issue.

Hi Philippe,

Aha, thank you for that valuable observation. 

Nico

Share this post


Link to post
Share on other sites

As an aside, I updated my version of VPilot yesterday and noticed that it now does an automatic scan of the SimObjects folder.

You can then select which folders you want VPilot to use in model matching.  Very Cool..

Share this post


Link to post
Share on other sites

Hi Ernest,

I did not go that far into software updating, but do you mean that vPilot being now scanning by itself, generates directly the matching rules, and when yes, does it generate directly some specific file containing these matching rules?

Or does it only let you confirm which Simobjects folders you intend to use for your AI displays, and passes the information to the program that will generate the matching rules?

Or perhaps my questions are coming too early, and some time is needed to check how the new version is working...

Anyway, blue skies and happy flights

Philippe

 

Share this post


Link to post
Share on other sites

FYI:

The latest version of VMRgenerator can read UTF16 coded files too.

Nico

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now