Build Your Own .gau File Question

If you mean,
have you gotta be a programmer to build new gauges?
I suppose the answer is; if you build a new gauge, you will be a programmer.
Gauges are very like windows DLL files. They have to be compiled from a set of source codes. You can get some simple templates from the MS FS2k2 panel SDK. That tute you link has more complex gauges. But you do need a compiler of some sort. MS Visual C ++ might be a good place to start.
 
Simonu


In a way, yes. Though one would never guess it from my truly bonehead posting on “Flattens” yesterday, I wrote “c” code for many, many years and it’s, though a bit rusty, my baby, (were also a few years of VB 6.0 and C#). But yes, overall, you answered my question precisely. I guess it irks me more than a little that designer’s herein are having to go through all that to build a panel. “c” is an elegant lady but it takes a very long time to really know her.

Perhaps what I am working on now will help. I spent the weekend unraveling the Gauges.h header. I not there yet but I’m close and I’ve already learned a lot. I had been exploring the whole dll module, talk to FS/CFS2 thing, so this seems to be a good next step. When I get there I’ll be glad to share any info I find. Beyond that I don’t know and I guess I’ll just have to wait and see.

And can I take a moment to gripe about M$. I was always taught that Macro’s (“c” not FS scenery) are sometimes useful to hide cryptic operations or def’s but the actual “c” code should be made far more readable. The author of Gauges.h has buried what is being done by layers of poorly chosen Macros and typedef’s as well. I’m always hesitant of being too critical, but on this one, sorry, what a piece of junk.

I have toyed with just rewriting the whole thing but, as it seems everyone is used to what we have, to take it that far may not be justified.


Thanks for responding,
Sam aka: “Ali Cat”
 
Hi Sam/AC,
Sounds good to me!

New blood and brings something to the table, like it...:applause:

Panel editors are out there, but an easy(ier?) way of making/modding gauges would be interesting.

Cheers

Shessi
 
Shessi,

Thanks for the encouragement. Its true that long term I am hunting for a significant project but right now I don’t feel expert enough at CFS2 to know what that might be. Perhaps that would be a good thread to start if someone is willing. CFS2 – what remains to be fixed, improved, or even just a wish list. I know Rhumbaflappy has detailed at least one issue that really needs work.

Anyway, just an idea,
Sam/AC
 
The payware version of cfgedit can extract the bitmaps from pre existing gauges. A task that can also be done with freeware hacking tools. GUIs exist for creating FS8/9 xml gauges.
I spent a lot of time staring at those C sources but I couldn't realy make head or tail of them.
But I am not a C programmer having devoted my time to the study of BGL.

Ali Cat. If you were to uncover any of the innerworkings of CFS2 through studying those gauge headers I would be very interested to know what you find. I fear however that MS haven't included any info that would be really useful. On the other gauge thread I posted a tool
You might like to take a look at some of the CFS2 modules with it. We should not discuss r3v3rs3 3ngin33ring on an open forum. If you were to uncover any arcane secrets please feel free to share;-) PM for direct contact.
Good hunting
 
Sam/AC,
Be careful what you wish for...

Just hang around and ask, and you'll get more than enough ideas!

The inner workings of CFS2 would be the Holy Grail. There are so many in-built/pre-set settings in the sim ie, starting height of Quick Combat, sky colour, day-light hours length in different parts of the world and at different times of the year, no changing seasons, the way ai aircraft act/fly, the way enemy aircraft act, general lack of randomness..I could go on.

As Simon-sez, just keep it under your hat, you never know who's listening ;)

More power to your Borland!

Cheers Shessi
 
Ali Cat,

Since CFS2's debut, aftermarket gauge-building for the sim has been the sole domain of a very select few in the community. I hail your enthusiasm and savvy in understanding the basics of the underlying code. Apart from the "custom designed" MS gauges provided for the stockers and the limited offerings designed by the community, most available options for the WW2-era have been nothing more than dated 'hand-me-downs' from CFS1, or worse, FS98. While they might serve the visual purposes, the mouseability of these FS98 types is completely non-existent in the main window (view) of 2D panels unless one sets the main view to "render_3d_window=0". Unfortunately, this setting reduces the capacity to view the combat targeting window and scrolling text in the main view because canopy framing now interferes. This is why native CFS2 gauge programming is so vital. It allows common ground for both 3d rendering in the main view and full mouseability of the gauges themselves. This is what the stockers have by default.

The talented CFS2 gauge guys moved on with the advent of CFS3 and FS2004 and the now ubiquitous use of XML programming. They've become the 'go-to' guys for all the new payware and freeware models in CFS3 and FS worlds. So today, with our beloved sim now a decade older, there's a lamentable dearth of fresh, native gauge add-ons to choose from. A guy could build a new native CFS2 model or port over an FS conversion, but the panel is still being outfitted with gauges eight to nine years old.

You may have heard this already, but for this path that you've seemingly chosen, i would recommend that you contact Moparmike, a veteran SOH member and a genius gauge-maker for CFS2. Even though he's now 'the guy' for the other sims, he remains a valuable resource for CFS2 gauge work. I'll end my long-winded post by saying anything you can accomplish in this niche would be greatly appreciated. :salute:
 
Will Get Back to You

Due to the substantive nature of the comments on this thread I have not yet responded. I will soon when I have time for more than a casual reply.

Simonu – I sent you a PM but am not sure it went through. If not let me know – PM or otherwise.
 
Holly friggin cow!

Through numerous little I have no idea what to do next problems I’ve made a small milestone (at least for me). I just have to share this with all of you. Checkout the Pic below.


View attachment 25458

Did you notice an unusual gauge in the bottom left? Google’s telling me its a P-40 undercarrage indicator but that "ain’t tha" point. This is my 1st gauge! Yea, via "c" coding and that horrendous gauges.h file. It doesn’t do anything yet and I’ve got some MAKE_NEEDLE work (don’t ask), but god its feels good to get this far.

Bearcat: I was going to post a I’m into this gauges thing now but "lets calm it down" response, for gauges aren’t my interest. Before I say what I’m getting ready to say let it be known I’m making no promises. But right here right now – wow, I’m hooked.


Sam aka: "Ali Cat"
 
Looks like a good start Ali Cat. The open architecture of this sim does allow for some pretty interesting and addictive opportunities on the side for fiddling and tweaking. As long as you're having fun, its all good...
 
The Next Step?

For yet another learning exercise I’m going to get the following gauge to function properly.

View attachment 25527

Does anyone know how this one works? It seems clear that the needle above the plane should move from up to down (west to south). And I’m guessing the other three (left wing, right wing and tail) move accordingly as well. Some info on the gauge can be found at –

http://www.warbirdsite.com/museumP-40.html

Also, does the text on the needles say "OFF" and their sort’a triangular shaped?

Bearcat: I neglected to thank you for your post above. It did very definitely help.
Sam aka: "Ali Cat"
 
Ali Cat,
I think that it lights up and blinks red when you gear or flaps are down and you are at breaking speed on either.

I have to go fly my jets and see which one has a similar gauge to that. I am thinking it is the Alpha A-6.
 
Yes and No.

It is not Alpha's A-6.

It is: CFS2 A6 Intruder Panel by Clayton Girven.
I think it is listed as:
gauge12=fsd_warn.flaps, 316, 460, 25, 12
gauge13=fsd_warn.gear, 287, 460, 26, 13

If not that, then perhaps:
gauge26=F16-flap, 131, 560, 14, 38
 
I need some gauges

I need a set of 4 gauges(all related), for which I have the BMP's made up.
This would be a set of flap lights for use in CFS2. If anyone wants to make
them, let me know. ckissling
 
Devildog & ckissling

Devildog:

Now I’m really confused. The warbirdsite.com link above says "P-40 KITTYHAWK UNDERCARRIAGE INDICATOR". Note my guage pic above is not from CFS2 or a .gau file. With more searching I did find some info of possible relevance at the following site.

http://www.warbirdforum.com/manual.htm

Most notably "An indicator on the instrument panel shows the position of the landing gear at all times when main battery switch is turned on."

And at the top of this manal is " … the title page says Tomahawk I. However, internal evidence (the engine designation and references to the RAF blocks from which the China-bound Tomahawks were taken) tie it to the Tomahawk IIBs sent to Burma for the AVG." I and II’s – these are the P-40A & B? Note the warbirdsite.com link shows this gauge in a P-40E panel. Anyway, don’t knock yourself out on this one unless you're into it – just thought I’d ask before I got too far animating the gauge.

On a separate note I followed your trials and tribulations with the "Aces High" campaigns. Looks like some really nice work. Your persistence is to be admired. Some day I’m going to take a break from this CFS2 under the hood stuff and actually play the game. Aces High is on my short list.

ckissling:

If your still willing I’ll take a crack at your gauge project. New at this posting "thang" but how about if you send me a PM with your e-mail, I’ll E-mail you back and we’ll go from there.


Sorry for the slow response,
Sam aka: "Ali Cat"
 
Ali Cat

I have seen a gauge like that, I'll see if I can find it.
I will send you a PM, I hope I can upload as I have a new web mail handler.
ckissling
 
Bearcat – "I call"

… I mean the wager that "seemingly" is before me. Let me explain.

I’m making progress with the gauges.h file and in broad strokes at least it’s starting to make some sense. There is still much to unravel in this beast but the last few test gauges I’ve made, after I polished the code a bit, I am struck by how simple they are. The problem here is as I stated above. It’s the convoluted style of this header.

At a minimum I will soon post a "Your 1st Gauge Starter Kit" – maybe with a code sample and a tute? You guys are so sharp – you can do this, I know it.

As for a gauges.h rewrite – well I’ve been giving that a lot of thought. But let me 1st win this round. I think I’ve got the high cards.


Known for stretching a metaphor,
Sam aka: "Ali Cat"
 
LOL...well, like i said in my "seemingly" comment, contacting Moparmike is your best route to success in working out the code. He's been designing gauges for years and can give you the shortcuts to getting up to speed in these things.
 
You must log in or register to reply here.
Back
Top