User talk:I4dnf

Thankyou for editing the pages and everything I4dnf!

I honestly didn't know how to do all that! :D

I shall try and edit the names of those images!

I just wanted to contribute as much as I could to this Newsletter to contribute something back to the FG Community.

How do I change the file names of the images?

---

Hello I4dnf,

I just looked through "Modeling Guidelines draft" and especially "Texturing Guidelines" and I'm a bit confused now. First it says to combine all parts of a model to a single texture file. But then it says that different parts of a texture-file for different parts of a model should be not used. Split the texture into smaller parts then. That sounds like a contradiction to me. The same here for me :"If using the same texture on multiple models, use a single file, don't make different copies"

Am I right or wrong here in following things? When a model (e.g. aircraft) containing different objects (eg. doors, flaps, gear) uses just one texturefile, (all objects mapped in one single texturefile) then the GPU loads the texturefile for each object seperatly? Or does it load only once?

I have six instruments-models (one object). All instrument-models are seperated, and wrapped in a seperated .xml, but each of their texturefiles are combined in one single texturefile. Means the 6 different models just use the same one single texturefile. Does the GPU here loads the texturefile again for each model? 6 x the same file?

When I made the EC135 with the selectable configurations (selectable objects of the aircraft like different reardoors, radom together with non-configurable objects like the frontdoors, skid...) switching liveries was very slow. Then I grouped (not joined/merged!)all objects in Blender together, switching liveries was much faster. So this let me assume that the GPU loads for each object the texturefile again.

I'm a bit confused, and I can see different examples of in FGdata.

Cheers --HHS 10:03, 8 April 2012 (EDT)

Hi HHS,

In principle each texture should be loaded once, even if referenced by multiple objects, but that might not work sometimes.

Quick example #1: if the gear appearance doesn't change with every livery, it's a waste of texture space to put it on the same texture (and you loose flexibility).

Quick example #2: if all the wheels of the different gears are the same, you can use the same texture for all 6.

Wrong example is: you have 6 instruments sharing parts of the same texture, but you only show 2 of them at a time, in this case 2/3 of the texture is wasting memory.

Hope this clears some things,

I4dnf 11:03, 8 April 2012 (EDT)