fxsttcb

Hi, Karol. Just a HU, the original thread and subsequent PMs got johnboy through it.When I copied the xml originally the the image description was truncated.<Image Name="DTI_Bkgnd.bmp" should have been; <Image Name="DTI_Bkgnd.bmp" Luminous="no"> I will scarf up yours too!(As I have with most of your F-111 stuff)...Don

Gauges that are in a [VcockpitXX] section are always available whether the VC is in view or not. One instance of the gauge in the VC is sufficient for the entire panel. I'm pretty sure Tom meant for you to verify that the Overhead.bmp is in the panel folder and the panel.cfg "file=" line for it under [Window05] and bitmap name are identical.It will not be a View incorporated into the VC, just a seperate pop-up 2D Window...Don

Not a nuisance at all! I remember, quite well, the struggle to understand xml.If it wasn't for the kindness and patience of folks here and on other sites, it would have taken much longer, through trial and error to learn.In that vein, I try to emulate their behavior, and, lately "What Would Opa Do" pops to mind. May he rest in peace. The "line of calculation" is the code that uses the variable, the rest of the code describes to the sim itself how to access and display it.XML is quite versatile. If you peruse FSX in it's entirety you will find .xml for your controls, in add-on scenery placement, and others. I got your PM and replied there also....Don

OK, so tell 'em to give us an extremely detailed planet, with accurate atmospheric conditions.If they can give me that, I'll accept it with only one plane and two airports. Then I'll buy or make the rest as I see fit. No full boogie SDK, no freeware development, their choice of add-ons offered, all that = No sale!...Don

Ha-Ha, I love it! How embarrassing!! Those missing parenthesis are things that should be second nature to me by now.Literally, hundreds of gauges, and a dozen or so panels, uploaded and shared. The last couple of days though, I have had my head tucked firmly where the sun don't shine! I had no clue what (A:AUTOPILOT NAV SELECTED,number) might actually return, so I created the digital version.It returned a 0. I had not even thought that it could be mucked up, of course! Jeroen and Doug to the rescue! Thanks again, fellas. Also, thanks to Mr Dawson, I now have in my posession a neat little xml-->C translator for those Events."xml L:Event" goes in, "C++ K: Event" comes out. Works a treat!It allowed me to complete my little selector knob, which was the source of my pain and embarrassment! Now to start learning C gauges!(Yeah, Right!)...Don

Thanks Doug! I was quite baffled why I couldn't find the problem with the event, then further confusion reigned, with the Var retuning zero...Don [edit] the extra brackets fixed the digit as you folks said it would. Thanks BTW, Doug, my handle at yahoo.com

I'll try that. I made so many different changes of spacing, characters, and punctuation I can't remember!Originally, I just copied that element from a working gauge, but could have mucked it when I changed the Variable. I also had a text element in the knob version, that returned zero so, I had bitmaps assigned to 0, 1, and 2 when I was testing that version and they wouldn't change state either. Here's the last full version I tried: <?xml version="1.0" encoding="utf-8"?><Gauge Name="Autopilot Nav Radio Select Switch" Version="1.0"> <Image Name="AP_Source_Bkgnd.bmp" Luminous="No" /> <Element> <Text X="18" Y="24" Bright="yes" Length="1" Font="Arial" Color="White" Adjust="Center" VerticalAdjust="Center" Fixed="no"> <String>%(A:AUTOPILOT NAV SELECTED,number)%!1d!</String> </Text> <!--From the SDK: "AUTOPILOT NAV SELECTED" Index of Nav radio selected "Number" --> </Element> <Element> <Visible>(A:GPS DRIVES NAV1,bool) ! </Visible> <Select> <Value>(A:AUTOPILOT NAV SELECTED,number)</Value> <Case Value="0"> <Image Name="Nav_0_Selected.bmp"></Image> </Case> <Case Value="1"> <Image Name="Nav_1_Selected.bmp"></Image> </Case> <Case Value="2"> <Image Name="Nav_2_Selected.bmp"></Image> </Case> </Select> </Element> <Mouse> <Tooltip>%Autopilot Nav/GPS Select</Tooltip> <Area Left="1" Right="35" Top="41" Bottom="76"> <Cursor Type="Hand"></Cursor> <Click>(A:GPS DRIVES NAV1,bool) if{ 1 (>K:TOGGLE_GPS_DRIVES_NAV1) }1 (>K:AP_NAV_SELECT_SET )</Click> <Tooltip>%Select Autopilot Nav 1 Mode</Tooltip> </Area> <Area Left="63" Right="97" Top="41" Bottom="76"> <Cursor Type="Hand"></Cursor> <Click>(A:GPS DRIVES NAV1,bool) if{ 1 (>K:TOGGLE_GPS_DRIVES_NAV1) }2 (>K:AP_NAV_SELECT_SET )</Click> <Tooltip>%Select Autopilot Nav 2 Mode</Tooltip> </Area> <Area Left="32" Right="66" Top="6" Bottom="40"> <Cursor Type="Hand"></Cursor> <Click>(A:GPS DRIVES NAV1,bool) ! (>K:TOGGLE_GPS_DRIVES_NAV1)</Click> <Tooltip>%Select GPS Mode</Tooltip> </Area> </Mouse></Gauge> Clicking the GPS spot toggles GPS mode properly. Clicking either NAV 1 or 2 spot turns off the GPS mode if enabled and shows me the Nav_0_Selected.bmp. I flew a couple of approaches and tried enabling it with a properly tuned NAV 2, no joy...Don

After a query for a VOR2 gauge, with a working Glideslope, over at Flightsim.com, Jim Robinson pointed us to one he created.I had made the erroneous assumption that the AP wouldn't respond to it. Father Bill(n4gix) pointed out the events necessary for that function. I proceeded to make a 3 way knob with Nav1, GPS, and Nav2, click spots.After fooling with it for a few hours, and no luck, I made the following quickie test gauge and it won't function either.I used the variable called out in the SDK and the text string returns a 0(zero)!The clickspots are recognised(changes to cursor) and the tooltips display properly. <?xml version="1.0" encoding="utf-8"?><Gauge Name="Autopilot Nav Radio Select Switch" Version="1.0"> <Image Name="AP_Dig_Source_Bkgnd.bmp" Luminous="No" /> <Element> <Text X="18" Y="24" Bright="yes" Length="1" Font="Arial" Color="White" Adjust="Center" VerticalAdjust="Center" Fixed="no"> <String>%(A:AUTOPILOT NAV SELECTED, number)%!1d!</String> </Text> </Element> <Mouse> <Area Left="0" Right="18" Top="0" Bottom="12"> <Cursor Type="Hand"></Cursor> <Click>1 (>K:AP_NAV_SELECT_SET )</Click> <Tooltip>%Select Autopilot Nav 1 Mode</Tooltip> </Area> <Area Left="0" Right="18" Top="13" Bottom="24"> <Cursor Type="Hand"></Cursor> <Click>2 (>K:AP_NAV_SELECT_SET )</Click> <Tooltip>%Select Autopilot Nav 2 Mode</Tooltip> </Area> </Mouse></Gauge> I fear there is something I've missed...Don

OK! well this is not hard, but, does require a little knowledge about bitmaps, the FSX folder structure, and panels. I'll attempt a little help. Inside the plane's main folder is a panel folder which contains the panel.cfg and bitmaps for the panel and extra windows. We will use the default A321 as an example.Open the Airbus_A321 panel.cfg in notepad. [Window Titles]Window00=Main Panel........Window12=Mini PanelHere is where you would add a new window title, numbered next. This is not necessary to add a gauge to an existing window, but useable for future reference. You would then add a same numbered [WindowXX] description following the last [Window??] in the descriptions. //--------------------------------------------------------[Window00]file_1024=airbus_a321_panel_background.bmpfile_1024_night=airbus_a321_panel_background_night.bmpsize_mm=1024position=7visible=1ident=MAIN_PANEL gauge00=Airbus_A321!altimeter_backup, 676,505// Notice only 2 numbers. This gauge uses it's default size.......gauge08=Airbus_A321!ecams, 788, 521, 215, 214// This is positioned and sized using all 4 available entries......gauge36=n_number_plaque!n_number_plaque, 258,429,67,19Place your new gauge here ie: gauge37=TrimGauges!DigElevTrim, X position,Y position, X size, Y size Gauge36 is the last gauge in [Window00] so the next "new" gauge obviously is 37. X position, Y positon, X size, and Y size, all refer to bitmap pixels.positions = bitmap coordinates, sizes = pixel count.open the airbus_a321_panel_background.bmp.Using the "select" tool you will be able to move the cursor to x=788 and y=521.That will be the upper left corner of where the "ecams" gauge is placed on the panel.If you drag the rectangle, from that point, until it is 215 pixels wide(X size) by 214 tall(Y size) you will see how the gauge is placed and sized. Most gauges can be sized according to need, but, you should maintain the aspect ratio so they aren't distorted.For instance the DigElevTrim background bitmap is 66pix wide by 32pix tall. Lets install it!Pick a spot where you want it using the select tool on the Backgound bitmap of the Panel Window you intend for it to show up. Note the pixel coordinates for the upper left corner, those will be the entries in the panel.cfg for X/Y position.gaugeXX=TrimGauges!DigElevTrim, X,Y,66,32 Now, with the rectangle positioned drag it to the width where it will fit the place on the bitmap, note the pixel width of the rectangle, say 28 pixels. That will be the X size. Replace 66 in the gauge= line with the new number.To maintain the proper ratio, Divide 28 by 66, and multiply 32.The result rounded to the nearest whole number will be the Y size. Replace 32 in the gauge= line with the new number. Now you can close any stuff that we opened while doing this. DO NOT Save Changes!Now that you have a little familiarity you can attack the intended target! For a complete explanation of gauges and panels refer to the SDK. For a full boogie WYSIWYG panel editor FS Panel Studio, can't be beat.At $25 it is by far the absolute best add-on in my repertoire. Sorry so windy! You asked for it! It could have been longer, but, that almost sums up my knowledge of gauge placement! Enjoy...Don

Quite odd! I just stuck it in the plane I am flying and it works fine for me!I tried different sizes in the panel.cfg and it tracks different scaling OK too.I'll repost the code taken directly from it, just in case.Make sure the saved file's Encoding is set to UTF-8 or it won't work...Don <?xml version="1.0" encoding="utf-8"?><Gauge Name="Digital Trim Indicator" Version="1.0"> <Image Name="DTI_Bkgnd.bmp" Luminous="no"> <Transparent>Yes</Transparent> </Image> <Element> <Visible>(A:CIRCUIT GENERAL PANEL ON, bool)</Visible> <Position X="0" Y="0" /> <Text X="66" Y="32" Bright="Yes" Length="4" Font="Quartz" Color="Orange" Adjust="Center" VerticalAdjust="Center" Multiline="No" Fixed="no"> <String>%((A:Elevator Trim Position,degrees))%!2.1f!</String> </Text> </Element></Gauge> [edit]I copied my first post and ran it through my line by line comparison spreadsheet and there was indeed an error in the <Image description. It was truncated at the end of "DTI_Bkgnd.bmp" How that happened is beyond me!

Seeing as this has already been Bumped! I'll ask! I could not find the cabin pressure xml that was linked by vololiberista in post #13 over at FFDS.I tried searching their forums for "Cabin", "Pressure", "Altitude", and various combinations of those terms and got zilch, none, nada, results.Anyone know the title or how I can retrieve that info? Thanks...Don [edit]Never Mind! Found it! Thanks anyhoooo...

Launch MS paint, on the upper left drop down is "Properties" make it 66 pix wide by 32 high, use the bucket tool and make it black(top left color)...Don

Change the [Window Titles] and [WindowXX] number to be next available. The Shift+number should be 1 less, to a max of "Shift+9".You'll probably want to change the window_size= and window_pos= to suit. It is BIG and right as is...Don [Window Titles]...WindowXX=EICAS ............ [WindowXX]Background_color=0,0,0size_mm=266,373window_size_ratio=1.000position=0visible=0ident=90window_size= 0.460, 0.880window_pos= 0.530, 0.070gauge00=Lear_45_XML!eicas, 0,0,266,373

This is just a simple one. Whole degrees and tenths. Only the digits show, the rest is transparent.Change "Orange" to whatever color you want, and "Quartz" to your font choice, noting that not all Windows fonts are available. Check the sims "Fonts" folder.Make a Black(0,0,0) bitmap 66x32, name it DTI_bkgnd.bmp.Copy all the code into notepad, save it with whatever name you want .xml as Encoding: UTF-8 in a named folder(my gauges) then put it in your panel.cfg ...Don <?xml version="1.0" encoding="utf-8"?><Gauge Name="Digital Trim Indicator" Version="1.0"> <Image Name="DTI_Bkgnd.bmp" <Transparent>Yes</Transparent> </Image> <Element> <Visible>(A:CIRCUIT GENERAL PANEL ON, bool)</Visible> <Position X="0" Y="0" /> <Text X="66" Y="32" Bright="Yes" Length="4" Font="Quartz" Color="Orange" Adjust="Center" VerticalAdjust="Center" Multiline="No" Fixed="no"> <String>%((A:Elevator Trim Position,degrees))%!2.1f!</String> </Text> </Element></Gauge>

You can extract the cab yourself using the same app you use to unzip downloads.A .cab is nothing but a compressed folder and the sim does not care if the gauge and it's bitmaps are cabbed or in a normal folder.Once extracted, you can edit the xml and bitmaps, after backing them up, of course. If you want to recab it, you'll need to have the SDK installed. Cabdir.exe will reside in SDK\SimObject Creation Kit\Cabdir SDK.Copy the folder with the .xml and .bmps to that folder and drag it onto Cabdir.exe.The end result should be found in C:\Users\User Name\AppData\local\VirtualStore for Windows 7, other OS are similar...Don

What I got out of that pretty much confirms the supposition that 100% SB-K series will go 4.4GHz or higher.100 D2 chips tested, 50 hit the wall at 4.4-4.5GHz, the other 50 kept on truckin' 'til 40 of them hit the wall at 4.6-4.7GHz, and ultimately the last 10 gave up at 4.8-5+GHz...Don

If that's the Missouri(BB-63) I'll eat my hat! It definately is not a superimposed photo of Big Mo moored anywhere. A whole lotta guns are missing and that ship is nowhere near big enough.The Missouri is 887ft long and has a beam of 108ft. That is just slightly smaller than the aircraft carrier USS Midway CV-41.If it's a BB-63 modeling attempt, it is pitiful at best.It ain't the T-AGS 63 USNS Henson, CG 63 Cowpens or DDG 63 Stethem(no other USS #63s), What other country's battlewagons have the 63 designation?I've been around plenty of Navy and other shipping docks and never saw one without mooring bits and ropes anywhere either. That leads me to believe that, whatever it is, it is a model.Sure got my curiosity crankin'! Maybe their "new" marketing strategy will work. ...Don

What cooling solution do you have on the 975? It should go 4.1-4.3+GHz 24/7 with a top-o-the-line air cooler and careful OC.Keep your max temps in the low-mid 70C range. Use 50 passes on LinX to stress test your OC. At 50 passes and you haven't gone over 80C, you should be good to go for 24/7 ops.Giving up all the extra PCIe capabilities of the X58, IMO, wouldn't be worth it. When the X79 is released Q4, with similar capabilities and the speed of Sandy Bridge chips, then it may be time to upgrade...Don

Thank You, Bob...Don

It might be as simple as; right click the view window and go to "cockpit" vs "virtual cockpit" mode...Don

In the gauge example above, the Axis declarations, in the elements, aren't closed. No "/" before end ">" <Axis X="0" Y="0"> Needs to be <Axis X="0" Y="0"/> for the gauge to work...Don

While you cannot create a VC in FSPS, you can edit the VC windows once the panel.cfg is loaded.Move? That depends on how the surface plane the gauge sits on is modeled. If the area is large and addressable, the gauge can be moved within the constraints of the modeled plane.Delete? Easy, just eliminate it in the panel.cfg or "delete" in FSPS.Add? That also depends on the criteria described above(move).Most VC tweaks I make involve "Swap" or slight sizing changes.You can generally move a gauge right and/or down a small amount without completely losing it. It is generally easy to make it smaller with it completely inside it's original footprint.You will notice quickly if the surface was modeled to the exact size, and original placement, when a portion of the gauge is no longer shown. Lots of T&E...Don

The only folks that can actually help you are Abacus. Did you e-mail them, custsupp@abacuspub.com, as Bill suggested?

You missed a spot...

Hi Noel, You found the same thing that most of us have. Leaving the Vcore in Auto scares the bejeezus out of me. I was testing a first gen P67 with a 2500K, and found Vcore at 1.5v with CPUz. Scary.If I am manually clocking the CPU, RAM or Northie, I set it manually to what auto gives me, then lower it until I get a failure, then bump it back up one or two increments.The Vid is basically the starting point for Vcore when in Auto...Don