Trueborn

I haven't noticed that, but it could be related to the delta T in the time warp (ie, it thinks it has been 5 seconds since you started discharging batteries when in real time it was only one frame). If it continues, I might have to do some more significant debugging. Here is a new version compiled with the new DLLs. It didn't look like anything was affected, but if anyone notices anything let me know.

So I am trying to determine when a part on the active vessel has been destroyed, or is about to be destroyed so I can change a UI element. Do I need to be adding something to GameEvents.onPartDestroyed, or is that the opposite of what I want to do? I guess I'm asking for a quick rundown of the GameEvents system. Thanks.

Currently, no. The HUD does display ground speed, but nothing dedicated to it for ground vehicles. If I did put it in, it would be in the NAV gauge as a ground speed readout, most likely. Thanks, ap0r, I forgot to mention that one as well. I think my timer might be checking for 5ms instead of 5 seconds... I'll work on that as well.

Here is the next version. It uses the new texture, and has the ability to disable individual annunciators by clicking on them. There are a couple of alignment problems, but I wanted to get it out for you to look at. The only light issues I know for sure are the gear transit indication doesn't work correctly, and abort still doesn't do anything. The scaling has changed a bit as well, and I will have to find a place to put it in the settings window. Feedback on this version?

Thanks.

Looks great to me.

I think that's the way we should go. Trying to decide if I like it with the red off texture or a grey off texture for the disable lights. Could you bring down the brightness of the on lights just a touch? Maybe not run them quite a high up to white.

I like the corner light, actually. It is distinct enough, but not too obtrusive.

I believe I have fixed that, but you'll have to wait for the next build. Plain white might work. I'll play with a few colors while I'm testing things out. I think candy cane makes it look too much like it is broken, not off. Also, it doesn't look as much like it is being lit from behind then.

That is good, yes. Please move GEAR UP to where GEAR TRN is, and put "STALL" in above it. Also, move LIGHTS to where PE LOW is now, move PANEL DP up one, and put PE LOW where PANEL DEP is now. I just don't like one orbital light being so far from the rest, and I think lights works fine next to brakes. I'm not 100% on the blue, but I can change that myself. Does anyone have any other recommendations? I would almost like a kind of orange, but that seems like it might not be far enough away from the red/yellow. Maybe a much lighter or darker grey?

I'll look at that as well, Stoney. That's odd, percy. If there is no storage for oxidizer, it shouldn't trigger that light; I'll look at it further though. I like your gear transit idea (which is indeed how most aircraft gear lights work). Maybe the stall light can work in its place (I doubt a stick shaker is practical in this case). I will think about logical ways to split the panel, but I don't think it will be my immediate priority.

Yeah, I like the idea of clicking on the MW/MC to show/hide the annunciator panel; I'll put that in as well. If you could, please add another column with LOX LOW, NO LOX, XENON LOW, NO XENON lights, and add some kind of blue (or whatever you feel works best for "disabled").

GPWS (which you are describing above - Ground Proximity Warning System) is a somewhat more advanced system, and is actually included in the HUD (without the audio). I don't plan on incorporating audio at the moment, but who knows in the future. Yes, I am trying to decide how I want to handle the nuisance BATT DISCH warnings. I'll probably put some sort of timer on it, so it only activates after X seconds, or over a higher threshold. I will look into the no fuel issue, but are you using combined tanks and just loading no O2 in them? If that's the case, the gauge is detecting the fact that you have 0 of (some amount of O2 above 0) oxygen on board, and correctly illuminates the low fuel warning. The best solution then is probably to have a separate low/no O2 light (and xenon, by extension), requiring a texture re-work. I can also add an inhibitor function, that disables individual annunciators (turns them... blue?) when clicked on. There is a stall warning on the air gauge, and SAS is in the HUD and main UI, so I'm not inclined to duplicate that.

Here is version 1.7.3c (beta release). It adds the master warning/caution buttons, as well as the annunciator panel. All of the annunciators work except the abort light (still working on that). The master warning/caution lights will illuminate when an associated light comes on, and stay on until clicked. Clicking them will also show the annunciator panel if it is hidden. Feedback?

Odd, thought I replied already. Looks good, programming in progress.

Yeah, I agree it isn't as good. Thanks for giving it a shot though.

I like the gradient effect. As a possibility, maybe do a double gradient? Often aircraft lights have two bulbs, so that if one burns out you can still see it come on (or simply because the annunciator is wide). Just a thought. Looking forward to seeing how the bezel turns out.

Yeah, I'm pretty happy with that layout. Maybe swap GEAR DN and BRAKES with PANELS DEP and LIGHTS. Actually, unsafe gear indications aren't uncommon, but they are generally in the gear handle itself and not any kind of warning/caution panel, so we're safe to leave them off. I'll have to look into getting at the UI's chute warning, hopefully won't be too much of a challenge. For ABORT, I'll probably just stick with exploded parts (shouldn't be too hard, but I haven't looked at that before), and LO FUEL is going to be total fuel, unless they have made it possible to access the state fuel percent from the UI. Wouldn't you want the OVER-G light to come on before all the crew died? I might just make it straight >15G, or cut those times in half-ish. I'll probably just let BATT DISCH flicker, these are steam gauges after all. Sounds would be traditional, but I'll probably just leave it with resettable master warning/caution lights for the first release. Maybe later on I'll include sounds.

The no chute light was an oversight, although I'm not sure how easy it would be to check for chute conditions. Otherwise, I mostly just stacked things vertically instead of in rows. And after further review, I would move the first column right two, so it would be two columns of propulsion, one of other warnings/cautions, and two columns of orbit and configuration. And yes, I'm not sure why I wasn't thinking of conditions on the gear up light. Does anyone else have an opinion?

That was more my thought. I removed the gear up light on the "dark cockpit" concept, where systems in their normal configuration don't light up. Thoughts?

I like them. Possibilities from a human factors perspective would be placing the red warning lights above the yellow cautions, along the top row if possible. Also, maybe move all the green information lights over to the right side, by the docking indicator. A possible addition would be a low altitude alert from the radar altimeter, maybe by squishing the dock light to half size.

KCAN requires remote direct downloading to function, which Curse does not support. Unfortunately, neither does my alternate host (OneDrive). So for now, it looks like KCAN is out. If I ever move this to GITHUB that might change. Oh, the other thing about the graphic is the red light is traditionally "WARNING." Otherwise I really like it, they look a lot like actual buttons. I'm looking forward to seeing what you come up with for the main panel. Don't worry about having an extra spot or so, most aircraft tried to leave a few openings for equipment added later on.

Thanks for the tech support assist, guys. I updated the first post with some links to the toolbar thread. I like the master annunciators, although I would consider leaving out the green annunciator. The green messages tend to be advisory, so if you want to know what is active you would just look.

I'll take a longer look at the KCAN specs, but it doesn't look like it would be too bad. That's not a bad annunciator panel. Although I'm not really sure when I would have the ABORT light come on. I think the reason I never did a panel was due to space reasons. I guess if you left it on you could just turn on the appropriate gauge when necessary. It shouldn't be too hard to code though, since I'm already checking everything there.

Glad you're enjoying it!