User Created Content Concern

  • First, before even getting started, I want to thank all those out there creating enhanced Cultivation for Aerofly and enriching immensely the world we fly in.


    This post is not intended as a complaint, but to express a concern.


    I find that as User created content proliferates, most especially scenery, The Aerofly documents/scenery and Documents/addons/scenery folder is becoming more and more indecipherable as each content creator lends their own contributions, with completely dissimilar naming conventions and locations.


    Thus you end up with sceneries covering the same general areas residing in completely different folders with names that are not necessarily enlightening, which I believe will eventually end up in a complete mess unless some general rules are put in place.


    My first thought was of having a seperate folder for each state, with sub-folders that are required to clearly lay out the intended coverage area, such as Documents/Aerofly FS 2/Addons/scenery/Usa/California/#


    Or Documents/Aerofly FS 2/Europe/France/Paris/#


    Essentially something that allows a user, months later to go into his scenery folder and have some idea of what the heck he or she is looking at, especially if they are looking to replace something.


    Is it possible for Ipacs to state some guidelines, or what do the creators think would be good, if anything?

    Devons rig

    Intel Core i7 8700K @ 5.0GHz / 32.0GB G.SKILL TridentZ Series Dual-Channel Ram / ZOTAC GAMING GeForce® RTX 2080 Ti Triple Fan / Sound Blaster Z / Oculus Rift VR Headset / Klipsch® Promedia 2.1 Computer Speakers / ASUS ROG SWIFT PG279Q ‑ 27" IPS LED Monitor ‑ QHD / 2x Samsung SSD 850 EVO 500GB / Windows 10 Pro 64-bit /Gigabyte Z370 AORUS Gaming 5 Motherboard

  • At IPACS we follow the following conventions:

    1. folder names and file names should be lower case and mustn't contain a space, use underscores instead. Only this way user scenery will work properly on all platforms

    2. You should use a commonly accepted geological structure e.g. continent/state/name_city/name_city.tsc or continent/state/icao_airport_name/icao_airport_name .tsc with the state generally being shortened but doesn't have to be.

    Example:

    /scenery/places/europe/fr/paris_city/paris_city.tsc

    /scenery/places/europe/fr/lfpg_charles_de_gaulle/lfpg_charles_de_gaulle.tsc


    And for user scenery aerial images I would recommend a similar structure:
    /scenery/images/europe/fr/paris_city/map_00_0000_0000.ttc


    This also applies to repaints, especially the ones carrying the aircraft registration: use "n1234c" or "d_esel". Avoid any spaces, hyphens, capital letters or umlauts - all these can potentially cause problems on other operating systems.

  • @Jetpack


    Could it be possible to pin this information? Perhaps nobody will make use of it, but at least there will be a guideline to reference!

    Devons rig

    Intel Core i7 8700K @ 5.0GHz / 32.0GB G.SKILL TridentZ Series Dual-Channel Ram / ZOTAC GAMING GeForce® RTX 2080 Ti Triple Fan / Sound Blaster Z / Oculus Rift VR Headset / Klipsch® Promedia 2.1 Computer Speakers / ASUS ROG SWIFT PG279Q ‑ 27" IPS LED Monitor ‑ QHD / 2x Samsung SSD 850 EVO 500GB / Windows 10 Pro 64-bit /Gigabyte Z370 AORUS Gaming 5 Motherboard