[akenbosch]

want the picture of khonsu in a hitler outfit to back up my claim of vasudans-are-evil?

[Snail]

want the picture of khonsu in a hitler outfit to back up my claim of vasudans-are-evil?

Jews come and eat you up.
Germans come and eat you up.
Vasudans come and eat you up*

* - Well your head at least.

Why are Vasudans evil? Without the fishes, Sol would be a giant crop circle by 2335.

[Unknown Target]

Yes, he is. Now stop picking on him, it's really grating.

[Snail]

Huh? It's not like I was picking on him?

[Unknown Target]

Oops. I was replying to the banter on the previous page, I didn't see that there was another page. Still, stop doing it, it's done in almost every thread he posts in.

Continue as you were

[WMCoolmon]

its just that none of us understand that mass of code you call hudparse.h and hudparse.cpp.

Well the code segment you quoted is supposed to be the most complex code you'll have to mess with in those files. I listed out what each field does in step 3. I guess it's not indented consistently, but it's just your standard kind of situation of creating a new array and initializing it with a bunch of default values. The same thing is done in parse/sexp.cpp, so I figured it would be Freespace coder-friendly.

[akenbosch]

the only code i know is how to create a simple DOS-based mad-lib program 

[WMCoolmon]

That actually sounds kind of fun

[Vasudan Admiral]

WMC: I'm unclear if what you're saying here is what a coder would need to do or what a TBL modder could do.
I *think* what you're saying is that the reason it appears to be half finished is that you've not gone right through hard-coding default HUD_guages.tbl compatible entries for each existing HUD item?

If that's correct, does that mean I could re-create the rest of the standard HUD guages using the tbl already (Ie, without touching the code)?

[Nuke]

it sounds to me like theres a rather large volume of rather unexciting code to write, and noone wants to do iut

[Cobra]

Write the code, people, we want a functioning cockpit.

[WMCoolmon]

WMC: I'm unclear if what you're saying here is what a coder would need to do or what a TBL modder could do.
I *think* what you're saying is that the reason it appears to be half finished is that you've not gone right through hard-coding default HUD_guages.tbl compatible entries for each existing HUD item?

If that's correct, does that mean I could re-create the rest of the standard HUD guages using the tbl already (Ie, without touching the code)?

Er, from a modding persepctive it means that you only have access to the gauges in the table that are included in the reposted code segment. All of the other gauges use hardcoded :V: defaults that are outside the control of the hud_gauges.tbl system.

What needs to be done is that a coder needs to add the data for those gauges into the hud_gauges array, and change the hardcoded :V: gauges to use the hud_gauges variables. (The many-step procedure I outlined above). It's not that hard, and Nuke is spot-on about it being a lot of uninteresting code to write. It's not even that likely to cause bugs unless you mess up basic syntax or miscopy a number.

Speaking of which, that actually makes me realize that I left a step out. The "Num_gauge_types" needs to be set to the number of default gauges in the array. Right now it looks like it's off by one.

[Vasudan Admiral]

WMC: Ok, thanks. A pity it's code changes though - I'm not at that level yet or I'd already be working on it.

==========

Right, new layout. It's pretty much all vectors, and so I can easily turn it into a new HUD graphics set.

Full feature set:


Typical feature set:


And my favourite look - what it could end up like after just having a glow added:


Any suggestions or anything for this layout?

====================

Well aside from layout fiddling, I think I'm now at the limit of what I can do to get internal cockpits working without a coders help. It really needs the functionality I listed before to be implemented before it can be taken further. :\

[MetalDestroyer]

How about directives, monitoring, and in game chatter ?

[aRaven]

looks pretty nice with the glow...the cockpit could be more detailed though, but this thread is not about the cockpit themselves I figured.

But what about widescreen monitors like the one I use? will the HUD be properly displayed on 16:10 and 16:9 formats?

[TrashMan]

keep hte escort list and wingman list out of the cockpit..leave it where it was (a projection on the helmet glass)

Another problem I see is the ship status...it's nice when you got a smal lfighter with exactly 5 subsystems....but what I fly a bomber with 4 engines and 4 turrets??

Everything else looks...schweeeeet

[Wanderer]

What i am worried is the equipment (monitors etc) and resolution (as well as width:height ratio) dependency of these cockpits

[Vasudan Admiral]

How about directives, monitoring, and in game chatter ?

Yeah, forgot to put in the messages, objective complete/failed messages, lag indicator, comm system, escort list and directives - they're supposed to just be in their original places. Some of them can quickly get far too big to fit on the console screens.

looks pretty nice with the glow...the cockpit could be more detailed though, but this thread is not about the cockpit themselves I figured.

But what about widescreen monitors like the one I use? will the HUD be properly displayed on 16:10 and 16:9 formats?

I couldn't really detail it up too much more than I already have - it's supposed to be based on the one seen in the FS1 intro. Remember it's still an in-game model that uses a 1024 res map with shine and glowmaps (if it ends up not using RTT stuff though, I can probably cut it down to 1024x512)

As to the widescreen (and ratio) dependancy - yeah it's a problem, but again I don't have the means to solve it. We need a coder.

keep hte escort list and wingman list out of the cockpit..leave it where it was (a projection on the helmet glass)

Another problem I see is the ship status...it's nice when you got a smal lfighter with exactly 5 subsystems....but what I fly a bomber with 4 engines and 4 turrets??

Everything else looks...schweeeeet

The ship status thing isn't really a problem - the list can just be truncated to display 5 as a max, or it could scroll through them. Again it'd need a coders help for that though.

BTW, the idea is that nothing is projected to the pilots helmet, simply because the FS pilots helmet has no faceplate glass anyway. I'd envisiage the directives and escort list appearing as holographic projections in mid-air.

[Unknown Target]

Well if mouselook and whatnot ever gets implemented, you could always add another screen between the pilot's legs, like several jet fighters have today. You could probably fit most nonessential stuff there.

[Hades]

Woah... Much better but, the Black areas could be abit more erm...MOre detailed or like have GreenGlow like in the cutscene IIRC.