• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

How do you name your textures/objects?

Messages
130
Country
germany
Hi all.

After looking at some addon sceneries from different designers, I stumbled upon file names like A201.bmp for a building texture or A201.bgl for an object.

I give them names like t1.bgl or t1.bmp to define that these files belong to terminal 1, because I think it's better to use names that allow you a bit to read out, what this file includes.

But what about A201.bmp or *.bgl? Personally, I can't associate anything with this. No chance of saying, it's a building or a car. So how do you handle this? Are you giving names, that allow flightsimmers a bit to read out, what a file includes or do you use names that say nothing about the content? Or do you have some kind of grid and you say "Building z is located in grid A4 and it's the fifth object with a bgl, so i name it A45.bgl"?


Hope to get some input from you all. Greetings.

Daniel
 
Hello,

Of course I give the file a name that describes the content of the .bgl or .bmp, because once converted the .bmp into a DXT-file for example there is nothing to see than an icon like all the others.
Codes like 12345.bmp are too weird... however, it looks more professional if the scenery is ment to be released.
.

Greetz. José.
 
Maybe it looks more professional... but it's not user-friendly. For example if you have to search the whole scenery-folder to find the bgl where ststic aircraft are in, it's just stupid. Why not call it static-aircrafts.bgl, so the user can spot it with one look and can deactivate it?
I find it very useful if programmers give reasonable names for both bgl and bmp. The FS is kind of an open source program, so it should be rather natural that the addon-market is too. :)

I find it most difficult to create GUIDs for api-macros. :D
But for scenery and textures, for now I only had to use less than 100, so it's still easy to overview. If you use hundreds of textures it may be useful to create names with numbers and not just "the-hangar-thats-behind-this-other-hangar-next-to-the-tower-at-the-northwest-edge-of-the-apron-at-night-1.bgl" :D :D
 
Last edited:
Hi Daniel,

For most of my projects I use the last two letters of the ICAO ident as the first letters of the texture. This is because they are part of a bigger scenery (nationwide) and that makes it easier to see to which airport they belong.

After that I use something that describes the texture. For example by refering to the hanger name or calling it simply tower for the control tower :). If an object has multiple textures I add things like door, roof, etc in the name as well.

The only problem for user of the scenery might be that I usually do this in Dutch, so it could still become abacadabra to most :). Here are a few examples:

StHangaar3Deur.bmp
StHangaar1Muur.bmp
StTorenRaamBoven.bmp
 
Back
Top