Having not seen this tool I can only guess as to what it is trying to do. With FS2004 you write the XML code in Notepad and then bang this file, plus the bitmaps, into a CAB file using VCAB.exe. By the sound of it ACE.exe appears to be doing all this in one operation. All I can tell you is that your old FS2004 XML files and bitmaps still work in FSX. In FS2004 you could keep all these files "loose" i.e. not wrap them up in a CAB, and they would still work. I've not tested this in FSX so I can't say whether the CAB route is now mandatory or not. bones -----Original Message----- From: jhb_airlines-bounce@xxxxxxxxxxxxx [mailto:jhb_airlines-bounce@xxxxxxxxxxxxx] On Behalf Of FrankTurley@xxxxxxx Sent: 17 October 2006 20:20 To: jhb_airlines@xxxxxxxxxxxxx Subject: [jhb_airlines] FSX - XML Gauges I don't know if anyone else has ventured into the Panels and Gauges SDK, but there's a few things to be aware of. (a) The provided ACE.EXE tool doesn't read my existing XML source code. This is probably no bad thing, as I've been forced to try to create a new gauge from scratch, which has taught me a few things about ACE, rather than bodging existing code. (b) The way ACE works is that you create a new project, then you create a gauge object as a single child of the project, and the gauge has a number of child objects, e.g. for .bmp files, for text elements used as labels and also evaluated objects, e.g. derived from the A variables list. (c) Don't expect to master the process in five minutes, the SDK is quite comprehensive and has lots to read. (d) I haven't managed to get my gauge working yet, so I can't tell you if it will work in both FSX and FS2004. My brain is worn out tonight, I'll resume gauge debugging on Thursday, tomorrow I think we are flying in Eire. Frank T.