Gooneybird565

Did not delete abarthel-little_navmap.log, simply installed 2.8.12rc2. All scenery libraries loaded without troubles, including inactive, and add-ons.xml! Thank you first for the software, and for the top-effective support as well! Have a good day Philippe

Strange.... From the C:\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg, I did delete the entry for Global Vector, on my rig [Package.15] PATH=F:\P3D_Externes\ORBX_library\p3dv5\Global Vector ACTIVE=true REQUIRED=false and unexpectedly... after several attempts to load the P3D v5 scenery, which crashed LNM when processing Vector stuff, the process finally was completed and created the database, with reduced figures on various item counts. No idea what happened so far. Will re-run the process later, who knows...

Alex, Logfile gone via e-mail Philippe

Short report... On my rig, LNM is installed into a specific library, C:\Flight Sim Utilities, with various other flightsim related programs. All programs installed as administrator. My flightsim HDD is F:\, installed simulators are P3D v5, X-Plane 12, and P3D v6. With LNM win64-2.8.11, and before installing P3D6, I could load scenery libraries for XP12, and for P3D5 using the add-on.xml packs. After installing P3D6, also installed LNM win64-2.8.12.rc1 (no registry trick used!). XP12 is found, and scenery library loads ok P3D6 is found, and scenery library loads ok, with, or without using the add-on.xml packs. P3D5 is also found, but suggests re-loading scenery due to "aged" data, and scenery library will only load if not using the add-on.xml packs. Trying to load P3D5 scenery using the add-on.xml packs will not complete, and LNM quits without warning. (All P3D add-ons installed into F:\P3D_Externes here, both P3D's having at least access to one same textures add-on - Terra Emergence Project) Troubles at my side?

Hi Alex, P3D6 installed at my side on separate disk (F:\). On my rig, C:\ProgramData\Lockheed Martin\Prepar3D v6 (%PROGRAMDATA%\Lockheed Martin\Prepar3D v6 works perfectly) Ordinateur\HKEY_CURRENT_USER\SOFTWARE\Lockheed Martin\Prepar3d v6 (AppPath being one of the entries with value F:\Prepar3D v6\) Have a good day Philippe

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

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

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

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

Hello, everybody Not sure being at the right place, but posted here about some findings on my sim when using VMRGenerator... Thank you for your help and comprehension Blue skies Philippe

Depending which scenery type you are looking for... As long as the scenery you are looking for does not contain "active elements" so to say, understand .dll, .gau; .exe files which until now were coded in 32bits mode, and that there is no FS9 (port-over, original modelled element, etc...), you can install the scenery and check how it works. P3Dv4 is 64bits code only, and accepts FSX native stuff other than the above mentionned active elements. For instance, if your addon uses for instance dsd_sound gauge programmed by Doug Dawson, you will need to go to his site or other usual site to collect the latest version, coded in x64 mode. With elements of FS9 origin, you will have display or rendition problems, not to say sim crashes. I have very few addon scenery on my P3Dv4.1, but am running without problems the FSX Barra airport, or various RAF air bases (FSX versions) as released by Terry Boissel, as well as the necessary objects libraries (also FSX versions). Blue skies

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

All OK, my friend! Africa gives me 48 files for total 8.74 Gb Still of pile to download... Thank you for all that work and Blue Skies Philippe

Hi folks! Recently been downloading various files via direct download links (I use no download manager, and 7z is my standard unzipper) : * Australia and Oceania OK and unzipped * Antarctica OK, can be opened and unzipped * Africa-001 OK, can be opened and unzipped Africa-002 has exactly the same bytes number than Africa-001, but I can not open or unzip it whichever attempt. Anything wrong with the hosted #2 file? Thank you for your help and assistance Sorry, disregard about not opening Africa-002, found the answer under the post "North America part 2 download" But 4.4 Gb + 4.4Gb are not equal to 9.4 Gb... Greetings from Paris, France Philippe

Mark, Thank you for return In fact I already have whole planet coverage from FSGenesis (started purchasing in 2007...), and was purchasing their 19m LOD NewtMap products when made available, to upgrade definition as much as possible. Anyway thank you for the info about Freemesh, will have a look. Philippe

Hi, all, First of all, not knowing whether this is the right place to report following problem. So, moderators, when at the wrong place, feel free to move this post. On Oct. 30, I did place an order with FSGenesis for a total of five chinese regions meshes (NextMap products at LOD 19m). I received the purchase order confirmation, #100002456 (placed on october 30, 2015 1:44:50 AM MDT), as well as an other e-mail with all relevant serial numbers. When I could download FSG-1375 up to FSG-1385, I never could download FSG 1365 and FSG-1370 (Tibet and Xinjiang), always getting a message from the server, "An error occurred while getting the requested content. Please contact the store owner." I have been using the contact page of their site to place various messages (all of which kind and polite...) about my misfortune, and being missing any return, also sent e-mails to their techsupport and sales e-mail addresses. Meanwhile received a reminder from them, about an item still remaining in purchasing cart, but purchase not completed, namely for the Tibet product (which is already included into my P/O #100002456...), but could be a wrong entry on my side. And still no answer, movement, or whatsoever from FSGenesis, apart some newsletters about special offers, rebates, etc... I am just wondering if there is actually somebody to read messages or mails left by customers, or if this is all automtically directed to the wastebin.... I did download freeware stuff from FSGenesis (Justim Tyme at these times), then purchased a lot of payware from FSGenesis (first site), then from FS Pilot Shop, and finally from FSGenesis (new site) when I could find that site active again. Alltogether, I can say that adding all the items purchased, I could have been purchasing parts to build a middle to rather high-end computer, or in other words, purchased several times a product like FSGlobal Ultimate, or FTX compatible... I do not regret all my buyings, as I really enjoy the products, and this was my own choice to go that way. I am only highly disappointed by the attitude of the merchant acting under what was, at least in the past, really A name for the flightsimming community. I will keep all the files I have been purchasing in the past, but as long as I am not able to download my two last purchased items, I will certainly put one more cent into their products. To me this is tipically a non-delivery, not to say refusal to deliver items for which they actually cashed the payment! And checking their site, just finding that this month, the only purchase option seems now to be only with CD backup, understand USD 4.95 additional to the displayed product price... I do not know where they have been learning commerce, marketing, and customer service efficiency, but would certainly not recommend that school! So far, I did have good times with their products, and I know now that these times are probably over, although I would have been interested into some of their future products (Asian mountainous areas for instance...) Sorry with this long piece of litterature, but thought I had to let the community have the information, at least about totally absent customer service... Anyway, am still enjoying flying (P3D v3 here now), and further wish you all blue skies and nice flights Greetings from Paris, France Philippe

Hi folks, I did, with an HD7870, in the late spring of this year... CCC software pack 14.4 for win7 x64. All was displaying fine when starting the flight, but after a certain flight time, pikes, tears, blue or white ground textures on some ground places, vertical flat geometrical figures with ground textures appeared. Other problem : some aircrafts designed mostly for FS9 or containing earlier design stuff do display some exotic way (you see the sky, or the airport objects, through various parts of the aircraft... As I mostly fly the MAAM-Sim R4D/DC3, I decided to revert back to DX9, and uninstalled the DC10 SF. Also read at these times on various posts and forums that ATI was not the most appropriate video hardware for FSX and DX10. Possibly a later driver should correct these misfits... I reported my driver problems to ATI via their concerned webpage, but no feed back so far... Also read from various posts that ATI cards were performing pretty good under DX11 with P3D. So this might be my next option for flightsimming... Blue skies