• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.

    Post 16 Update

    Post 17 Warning

Guage editing problem

B

Bone

Charter Member
I have re-guaged a number of port overs with great results, but now I've hit a snag. I've got the freeware FSD T-38A flying around in FSX Accell, except I can't seem to get it to take the new guages. I've edited the new guage names into the CFG virtual cockpit header, but none of the guages show up when I fly...only a static image of the panel will show. I've experimented with some coordinate changes hoping to get a guage to peak out from behind the bitmap image, but no dice.

Any ideas?
 
I'll assume you know which gauges will and will not work.. and how a "cookie cutter" VC panel works..

So.. if NO gauges show at all; no matter what you do with coordinates; it sounds like a syntax error that renders a big part of the panel.cfg void.
 
I've used these same guages in other PO's, and they work great. The panel image in the T38A doesn't have the black holes where a missing guage is, like the other PO's I've done. It's just an image of the entire panel.

What sort of syntax error do you have in mind? I've gone over the cfg and compared it to others, but nothing seems to be different.
 
The black holes aren't really telling. They can make for a more realistic looking panel background.. but those details can be the gauges themselves. The bitmap for the panel itself IS the background. Then.. the gauges are actual, individual polygons... with the gauges "mapped" to them, inside of the modeling program. That's where the coordinate system gets thrown out the window. The gauges are mapped onto the polygons form a big "sheet" of gauges (a bitmap that isn't even needed after the mapping), and then that "sheet" is "cookie-cut" onto all of the individual (otherwise invisible) polygons.

For example.. if you try to move a gauge to the right (by coordinates).. it will partially disappear from THAT polygon, and most likely START to appear on one of the other polygons.. with no real rhyme or reason to it. Once a gauge is mapped to its polygon.. THEN the modeler need only move that polygon where he needs it to be. THat lends itself well to multiple panels at multiple angles (like overheads or center consoles).

I'd have to see copies of the panel.cfg files, before speculating on syntax.. else we just might trade a dozen posts trying to debug it.
 
You must log in or register to reply here.
Back
Top