• 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.

FSX 1024 or 4096?

Messages
629
Country
unitedstates
Hi all!

Is it best to use 52 1024x1024 ground tiles or 13 4096x4096(assuming the simmer has the MAX_LOAD=4096)?

Thanks, Ryan
 
Less textures is always better, so I would go for the last.
 
Hi all!

Is it best to use 52 1024x1024 ground tiles or 13 4096x4096(assuming the simmer has the MAX_LOAD=4096)?

Thanks, Ryan

Hi Ryan,
Just want to point out that 4096 sheets are 16x larger (pixel for pixel) than 1024 sheets and not 4x. So 52 sheets of 1024 at the same resolution is 3.25 sheets of 4096. Which drawcall wise is even better:) The scenery that we're working on right now has the base drawn on 4x4096 sheets - but the FS9 version (1024) at the same resolution has to use 64.
Cheers,Ian
 
We used the method of less larger textures instead of many smaller ones for a while now, and it's a very well known optimization technique, which almost everybody in the "real" game business uses.

It has to do with minimizing both drawcalls, but also "state changes", which is the number of times the graphic engine must stop drawing with a material, load a new one, draw with that, and so on.

The FSX exporter tries to do some state change optimization, by sorting objects by textures so, at least, all objects with the same texture will be packed together and IF they form a single drawcall, also drawn together but, of course, if you help it by minimizing the overall number of textures, it's even better.

And, you want to be smart in making textures. Don't just stitch them together randomly, but use some criteria because, sometimes it might be worth separating them instead of grouping, depending on the material properties.

For example, assume you have many objects mapped on a single 4096x4096 texture sheet which is almost full and they don't require any specular, alpha, or bump mapping. Now, you add a new object and its texture does fit in a remaining blank space of the previous texture, but this new object NEEDS to have an alpha channel, or a bump or specular app. You might be tempted to use the remaining space in the texture sheet, but doing this you are forcing to add an entire alpha channel and/or an additional specular and/or bump texture to the BIG texture sheet JUST to have this object fit the remaining blank space.

You would be better leaving the blank space and creating a new smaller texture just for that object in this case. Of course, along the scenery development you might realize you'll need several other objects with alpha and specular+bump, so you might end up doing a single large texture for THEM instead.

Basically, you want to group into as few large textures as possible, dividing by material properties. All the objects with just diffuse material in a single large textures, all objects with an alpha channel used for transparency in another one, all objects with a specular map only in another texture, all objects with specular+bump in another one.

Note that, even if you are fitting everything in a single texture, FSX will separate drawcalls ANYWAY, if you apply different material properties to them so, if material properties are not the same, the objects are going to be drawn separately in any case, regardless if they belong on the same texture or not.
 
We used the method of less larger textures instead of many smaller ones for a while now, and it's a very well known optimization technique, which almost everybody in the "real" game business uses.

It has to do with minimizing both drawcalls, but also "state changes", which is the number of times the graphic engine must stop drawing with a material, load a new one, draw with that, and so on.

The FSX exporter tries to do some state change optimization, by sorting objects by textures so, at least, all objects with the same texture will be packed together and IF they form a single drawcall, also drawn together but, of course, if you help it by minimizing the overall number of textures, it's even better.

And, you want to be smart in making textures. Don't just stitch them together randomly, but use some criteria because, sometimes it might be worth separating them instead of grouping, depending on the material properties.

For example, assume you have many objects mapped on a single 4096x4096 texture sheet which is almost full and they don't require any specular, alpha, or bump mapping. Now, you add a new object and its texture does fit in a remaining blank space of the previous texture, but this new object NEEDS to have an alpha channel, or a bump or specular app. You might be tempted to use the remaining space in the texture sheet, but doing this you are forcing to add an entire alpha channel and/or an additional specular and/or bump texture to the BIG texture sheet JUST to have this object fit the remaining blank space.

You would be better leaving the blank space and creating a new smaller texture just for that object in this case. Of course, along the scenery development you might realize you'll need several other objects with alpha and specular+bump, so you might end up doing a single large texture for THEM instead.

Basically, you want to group into as few large textures as possible, dividing by material properties. All the objects with just diffuse material in a single large textures, all objects with an alpha channel used for transparency in another one, all objects with a specular map only in another texture, all objects with specular+bump in another one.

Note that, even if you are fitting everything in a single texture, FSX will separate drawcalls ANYWAY, if you apply different material properties to them so, if material properties are not the same, the objects are going to be drawn separately in any case, regardless if they belong on the same texture or not.

Umberto,

Thank you for this valuable information.
 
Back
Top