I just went through the process of adding this "texture" to the A380 after reading the source code, for when you are taxiing around an airport.

  The output texture "file" is in essence a virtual file. So the texture is created in memory and given a path reference (it's never actually persisted to the file system),
  So when you add the instrument to the aircraft, you must exactly use the virtual path, I never knew this was possible, it's a simple but highly effective idea.


On Thu, 2011-09-29 at 21:32 +0100, Robbo wrote:

I am trying to familiarise myself with Flightgear's source code so that I may try and contribute.  I am currently looking at the 'groundradar' instrument module and there is something within that is causing me some confusion.

Essentially, there is a 'texture' declared as follows:
static const char* default_texture_name = "Aircraft/Instruments/Textures/od_groundradar.rgb";

This is then used by the following method:
void GroundRadar::createTexture(const char* texture_name)

in the following way:
FGTextureManager::addTexture(texture_name, getTexture());

Now all is good at this point until I go and look for this file, which i expected to find in data/Aircraft/Instruments/Textures/, however, this file does not appear there, nor does it appear anywhere else on my filesystem either.

I thought, well maybe the code is not actually using this texture, since its a 'default_texture', however, when i change the name to point to something else which also does not exist, then, the once black background becomes white!

So I am assuming that this file MUST be somewhere, but I have no idea where it is, can anyone assist me with this?


All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
_______________________________________________ Flightgear-devel mailing list