... for now.
Does anyone here know the workings of this dds texture in the FSX/texture folder.
I thought I did...
OK, the problem - I have the DirectX SDK and the DirectX TextureTool. I have created a new GlobalEnv_AC_Chrome.dds image and it works on other aircraft. I have got that bit right and I can see the GlobalEnv_AC_Chrome working on other planes, for example the P51 racer. I now have three GlobalEnv_AC_Chrome files - the default, the one that came with the Icarus Pitts and my own New one.
They ALL work on other planes - the P-51 is shown here:

If you look closely at the enlargements, you will see the differences (clue: observe the Mustang nose and the reflection there)
BUT I cannot get the GlobalEnv_AC_Chrome to work at all on the Eagles anymore, irrespective of which one is in the FSX/Texture folder.
No matter what I do, the Eagles all show NO GlobalEnv_AC_Chrome see here:

Does anyone have any idea as to why the IRIS Eagle no longer looks for the global envmap?
This is what that Eagle should look like:

Does anyone here know the workings of this dds texture in the FSX/texture folder.
I thought I did...
OK, the problem - I have the DirectX SDK and the DirectX TextureTool. I have created a new GlobalEnv_AC_Chrome.dds image and it works on other aircraft. I have got that bit right and I can see the GlobalEnv_AC_Chrome working on other planes, for example the P51 racer. I now have three GlobalEnv_AC_Chrome files - the default, the one that came with the Icarus Pitts and my own New one.
They ALL work on other planes - the P-51 is shown here:



If you look closely at the enlargements, you will see the differences (clue: observe the Mustang nose and the reflection there)
BUT I cannot get the GlobalEnv_AC_Chrome to work at all on the Eagles anymore, irrespective of which one is in the FSX/Texture folder.
No matter what I do, the Eagles all show NO GlobalEnv_AC_Chrome see here:

Does anyone have any idea as to why the IRIS Eagle no longer looks for the global envmap?
This is what that Eagle should look like:
