General Category > General Discussion
Prepar3D 4 announced: FSDT is ready!
nigelgrant:
I downloaded and installed P3Dv4 successfully then installed my FSDT sceneries, ie Vancouver, Geneva, Zurich, Honolulu, and Hawaiian Airports 1 and 2. All went very well and I was most impressed by your new installation system. The airports look really good in this new 64 bit simulator.
But I have a question – all the FSDT sceneries are layered at the top of the scenery library in P3D and cannot be moved to another layer location– why is this?
I greatly appreciate your updating your sceneries to P3D_4, particularly for free.
Regards
Nigel
Vancouver
Ps I posted a similar message last night but it appears to have disappeared.
virtuali:
--- Quote from: nigelgrant on June 03, 2017, 06:41:44 pm ---But I have a question – all the FSDT sceneries are layered at the top of the scenery library in P3D and cannot be moved to another layer location– why is this?
--- End quote ---
We don't exactly know why.
Or, more precisely, we know this happens because these sceneries are not in the scenery.cfg anymore, but we don't know why LM has decided to lock the ability to rearrange areas added with the new add-on.xml method in the UI of the Scenery Library page. The system surely supports a layering system so, if someone really wanted to do it, he can always work on the various add-on.xml files in the Documents\Prepar3d v4 folder, and add a <Layer> tag, with a number indicating the priority in relationship with the other items in the Scenery Library.
We asked LM for clarifications, and if they have plans to add this feature in an upgrade. Or, it's possible that some 3rd party developer might come up with a solution. There's nothing in the new system that prevents rearranging, just it's not exposed in the sim UI.
nigelgrant:
Hi Umberto
Thx for the quick response and explanation - I have some learning to do!
regards
Nigel
Brian S:
Hey FSDT, can you explain why AFCAD's now compiled in Airport Design Editor cause issues with the runways in your KMEM scenery in V4? Worked fine in V3. I reinstalled KMEM in V4 with my custom AFCAD (renamed the .BGL to .bac of your AFCAD so it would not conflict) so my FedEx AI planes (based on real world schedules, so they are over 100) have a place to park without disappearing. Unfortunately, the runway numbers and markings are not visible any longer and the runways do not look right, so obviously it's the custom AFCAD. I recompiled in ADE with the V4 SDK, same issue. I put your AFCAD back in and it display's fine. So obviously something in V4 or KMEM in V4 is different. My V3 custom AFCADS at your other airports work fine in V4. Any thoughts on what may cause this? If no fix it will be a complete re-do on hundreds of parking spots using your new one as a base. I do see though it seems you have more spots this time, but I customize my work a bit more and make sure I have spots for Mountain Air Cargo ATRS and C208's. New techniques on the runways in V4?
virtuali:
Our AFCAD is 100% SDK compliant, it's compiled with the standard Bglcomp.exe, and doesn't have anything strange or unusual. You should just be sure the editor you use supports everything, and doesn't change something with another default.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version