bladerunner900 wrote:I did a bit more digging and found the following. In the number.xml file, there is a line for the font like so...
Changing it to...
<FontFace>times new roman</FontFace>
There is a line above it that controls the colour, but your going to have to experiment with that. Unless you can persuade whoever designed the panel to tell you the correct codes. Base colours seem to work, red for example changes it to... red.
I took bladerunner's findings and ran with it for a couple of hours. I was determined to get the n-number properly displayed in the vc, as I created it in my panel texture:
In A2A_C172/panel/number.xml, I changed this:
FontFace>courier new bold</FontFace>
At least the font is getting close:
Like bladerunner said, changing the color of the font requires editing the line:
After searching through all of the XML files in the panel folder, I found the following colors being used:
Goldenrod was closest to the color I want, but not a good match:
When poking around engine_details.xml, I found this line:
Ahah! That looks familiar! 4b4b4b represents a hexadecimal color code. So all I need to do is sample the color I want in Photoshop, and note the color code, right? Well the hex code that displays a beige color in Photoshop, gives me this in the 172:
So I played around with different hex codes and eventually found one that works. But then I noticed this line in number.xml:
<Image id="number_bg.bmp" Name="number_bg.bmp">
What happens if I just replace the gauge background image (number_bg.bmp) with my custom n-number, and set the font color to "transparent?"
That's more like it. Problem is, the n-number will look like this for all of my A2A 172's. Fortunately it's easy to change.
I will certainly include this as an optional element, assuming it doesn't create any simconnect issues.
Thanks again to bladerunner for leading me down this path.