Pavespawn

A slick 53 would be a lot easier to produce as well. No IDAS system, TF/TA, hover coupler, etc. Of course all of those things are what make a Pave Low so much fun! Pave Low by definition was the TF/TA ability in 0/0 visibility.

As much as I would like to plug the MH-53M Pave Low, it did take all 6 of us to fly it. It could be done with snap views to see the FE panel I suppose. Really I think the practical choice is the H-60. Variants would be easier to produce like the HH or DAPS or even the SH. Mission sets are so varied that there would be plenty of room for differences. Just my opinion.

That looks great. How many screens are you running on your front panel? Looks like 5? Plus your three displays, how does all that connect? I am admittedly ignorant on a lot of this.

Thanks! I think Helios is going to be the answer for now. I was able to get that working in about 6 to 9 minutes.

Hey guys, new around here and I am trying to figure out this GP-Wiz thing. First off, hi, my name is Gary. I've been in the Air Force for about 21 years now and currently I teach at the Weapons School here at Nellis. I am attempting to simply get my Electrical Power panel to do what I want. Right now when I flip say my APU Gen switch it turns it on but when I turn it off nothing happens. So I read about editing the .lua for the GP-Wiz but the problem is all I can find is the .diff.lua file with the differences of the controller. Is this the file to change or should I have another one? For switches that don't have off commands can you put OFF after the iCommand and make it work? I notice that the numbers don't appear like they used too in the beginning of this tutorial. Thanks in advance. Oh if this is covered elsewhere please point me in that direction instead of repeating yourself. Apparently I don't know what to search for.