@TKorho:
Aah. Thank you very much for the explanation! Good work!
Good solution(s)! I guess these are very useable for us. I am now placing orders for 1-2 FIPs and create the central pedestal instruments (HSI,alt,speed,RWR at least) out of them.
Wouldn’t it be simpler to use more of those extracted textures, and allow/pack them directly as instruments? Does a FIP page need much implementation per page?
At least standby attitude indiator, fuel cauge(s), HSI, altimeter, speedometer, (clock), trim panel, would be directly useable as FIP instrument information. Much like we use them as separate windows in MFDE itself. We just needed to have them (=that picture information) available as a page selection in the FIP. Is this possible?
Oh, I highly value your “natice” implementations as well.
Am I correct that your rudimentary cauges are generated from the shared data, and not using the extracted textures from the MFDE?
You’re correct, my rudimentary gauges are all generated from the shared data. There’s actually only a very limited set of shared textures available from BMS4 via MFD Extractor. The RWR in my second picture is another shared texture; for some reason, it doesn’t get the green circular background.
I’d love to find a way to get all of Lightning’s beautiful gauges available to the FIP, but F4TexSharedMem doesn’t seem to provide access to these. I think LightningGauges is what I need, but it has some .NET 4.0 dependencies, and I’m using VS 2008 because it supports IntelliSense for C++/CLI. Getting these to play nice together somehow is on my to-do list, but I’m not sure what the best way is yet.
@TKorho:
So the FIP input controls can change based on the page used? Is it hard to implement or hard to configure ourselves? (I have done extensive Cougar, Warthog and Cougar Pack programming, so I guess I could create those page-dependencies if they are user configurable.)
Yep! This is do-able. If you check the ReadMe under “binding keys to buttons”, you’ll find:
It’s also possible to bind events per-page, which overrides the global bind
while that page is active.
FIP example:
screen 1 bind “left_minus” “a”
screen 1 bind “left_plus” “b”
In that example, the left knob emulates the A and B keys when you’re viewing page 1. You could bind the knobs to do different things on each page. In the next version, I’ll make it so you could bind one of the knobs to next/prev page, and then you could have the S1-S6 buttons do something different on each page.