Hi, This is most probably something stupidly simple, but I created the images for a gauge with Adobe Photoshop using layers and used Microsoft's psd2xml.exe from the FSX SDK to generate the basic XML file structure and bitmaps. I then used Microsoft's aces.exe to view the gauge. The XML script looked okay in aces.exe and the bitmap images appear to be okay. I then placed the gauge in a panel but it didn't appear in FSX. I then loaded the panel into FS Panel Studio for FSX and when my gauge is loading it says "No Bitmap found for gauge 37". The bitmap files are in the same directory as the XML file and have the same name and case as in the XML script. I have also tried loading the gauge after making it a CAB with the same results. Just in case it was my bmp files that couldn't be loaded I used psd2xml.exe with the example psd2xml.psd supplied with the SDK to create the voltmeter gauge example. After adding it to a panel I have the same problem and FS Panel Studio for FSX says "No Bitmap found for gauge 38". The gauge outline can be selected but is transparent and shows no images when selected for editing. Below is the XML script generated for the psd2xml gauge example by psd2xml.exe (unfortunately the indentation disappears when the post is submitted). The BMP files load okay in aces.exe and are in the same directory (or folder as they are now known) as the psd2xml.xml file. But they are not found by FS or FS Panel Studio. Any clues to why the BMP files are not being found and loaded? <?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0"> <Descr>AceXML Document</Descr> <Filename>Psd2XmlSample.xml</Filename> <SimGauge.Gauge id="Psd2XmlSample" ArtDirectory="C:\Program Files\Microsoft Flight Simulator X SDK\SDK\SimObject Creation Kit\Panels and Gauges SDK\"> <FloatPosition>0.000,0.000</FloatPosition> <Size>88,87</Size> <Image Name="voltmeter_background.bmp"> </Image> <Element> <FloatPosition>10.000,20.000</FloatPosition> <Image Name="voltmeter_needle.bmp"> <Axis>1.000,34.857</Axis> </Image> <Rotation> <PointsTo>NORTH</PointsTo> </Rotation> <MaskImage Name="voltmeter_needle_window.bmp"> <Axis>33.844,32.600</Axis> </MaskImage> </Element> </SimGauge.Gauge></SimBase.Document>Tony

(unfortunately the indentation disappears when the post is submitted

Tony, when posting "code" of any sort, click on the "Code" icon in the toolbar (last icon!) to insert {Code}{/Code} (with square brackets) then paste the code or script between those formatting tags. This will preserve the code or script's indenting.

<?xml version="1.0" encoding="UTF-8"?><SimBase.Document Type="AceXML" version="1,0">  <Descr>AceXML Document</Descr>  <Filename>Psd2XmlSample.xml</Filename>  <SimGauge.Gauge id="Psd2XmlSample" ArtDirectory="C:\Program Files\Microsoft Flight Simulator X SDK\SDK\SimObject Creation Kit\Panels and Gauges SDK\">	<FloatPosition>0.000,0.000</FloatPosition>	<Size>88,87</Size>	<Image Name="voltmeter_background.bmp">	</Image>	<Element>	  <FloatPosition>10.000,20.000</FloatPosition>	  <Image Name="voltmeter_needle.bmp">		<Axis>1.000,34.857</Axis>	  </Image>	  <Rotation>		<PointsTo>NORTH</PointsTo>	  </Rotation>	  <MaskImage Name="voltmeter_needle_window.bmp">		<Axis>33.844,32.600</Axis>	  </MaskImage>	</Element>  </SimGauge.Gauge></SimBase.Document>

Now I don't ordinarily use the new FSX XML Schema because to me it is way too unwieldly and verbose. However, even when using the FS9 XML Schema, I've encountered instances where FS Panel Studio (FSPS) would not "see" the background bitmap in only one of two otherwise identical scripts!I've even had instances where FSPS did display a gauge properly - ONCE - then on subsequent loading of the panel.cfg suddenly became stupid and could no longer "see" the background bitmap!Stranger still, I've taken the exact XML script from a "failing gauge," pasted it into a newly named .xml file and had FSPS display the "new version" side-by-side with the "failed version..." :( I've never discovered the "why" of this, and confess that none of this is in the least helpful towards answering your question. I only write to let you know that "you are not alone" in encountering this mystery! :(For example, consider the XML script for these two gauges, both of which use the exact same bitmap. FSPS complains about the PFD not having a bitmap, but happily "sees and displays" the same bitmap in the MFD version! Both "gauges" will load and run perfectly fine in both FS9 and FSX however... :(

<Gauge Name="G1000_MFD" Version="1.0">	<Image Name="G1000_PFD_bgnd.bmp"/>	/// snipped out for brevity ///</Gauge>//////////////////////////////////////////////////////////////////////////////////////////////////////////<Gauge Name="ESDG_PFD" Version="1.0">	<Image Name="G1000_PFD_bgnd.bmp"/>	/// snipped out for brevity ///</Gauge>

Thank you Fr. Bill for pointing out how to add code to the post. I wondered how to stop the formatting from disappearing. Thank you also for mentioning the problems you have come across with XML gauges which gives some comfort. But at least your gauges show in FS9 and FSX. My efforts don't show in either, which is why I used FSPS to see if they were in the panel and that I hadn't made some mistake in editing the panel.cfg. If I add a gauge to a panel with FSPS my gauges show in the list of gauges available. Also the XML file is read. So I am completely foxed and frustrated.

Thank you Fr. Bill for pointing out how to add code to the post. I wondered how to stop the formatting from disappearing. Thank you also for mentioning the problems you have come across with XML gauges which gives some comfort. But at least your gauges show in FS9 and FSX. My efforts don't show in either, which is why I used FSPS to see if they were in the panel and that I hadn't made some mistake in editing the panel.cfg. If I add a gauge to a panel with FSPS my gauges show in the list of gauges available. Also the XML file is read. So I am completely foxed and frustrated.

Well, I too have occasionally run into an instance where an otherwise syntactically perfect XML script would simply NOT load/display in the sim...In every instance though, I've found that by recreating the same XML script in a new .xml file, and giving it a slighty different name......that one would load and display perfectly! One possible reason might lie in the filename used; possibly it includes a "reserved word" that the XML parsing engine gets confused by... :(