Originally Posted by
PhantomTweak
I compared what you posted to what I have for the F-18 LEX Vapor effects. I can see a few glaring differences, that may or may not matter. I really think they do, though.
Here is the line from the Hornet's file:
(L:Vapor Calculator, number) 1 >
(A:SMOKE ENABLE:10, bool) ! and
(A:SMOKE ENABLE:11, bool) ! and
if{ 10 (>K:SMOKE_ON, enum) 11 (>K:SMOKE_ON, enum) } els{ }
and here is yours:
(A:SURFACE RELATIVE GROUND SPEED, knots) 5 > (A:SMOKE ENABLE, bool) ! and if{ (>K:SMOKE_TOGGLE) }
The L: var for the '18 is just the G force and ambient temperature requirements to enable the vapor. If the conditions are properly met, it returns a 1 to turn the smoke on. Then the section I posted turns on smoke entries 10 & 11. In yours, the surface relative ground speed is the triggering event, and turns on whichever smoke entry you're using. You don't specify which smoke entry in the aircraft.cfg [Smoke] Section is triggered, though: (A:SMOKE ENABLE:10, bool) vs (A:SMOKE ENABLE, bool). See the difference? You need to specify just what [smoke] section line entry you want to trigger, not just a [smoke] entry of some sort.
Then, the section triggered in yours isn't specified again in the K: Var entry.
if{ 10 (>K:SMOKE_ON, enum) vs if{ (>K:SMOKE_TOGGLE) }.
Also, I am not sure the K: var you're using is the right one. K:SMOKE_ON in the f-18 instead of K:SMOKE_TOGGLE in yours. Notice that in the F-18 one, the [Smoke] entry triggered is specified in the line, if{ 10 ... and in yours it's not, again.
Last, that I see, for what that's worth, in the F-18 line, the entry goes (>K:... but in yours it's just (>K:...
Do all these differences make a owl's hoot worth? I'm not, repeat NOT, an XML programmer, but all the things I pointed out, I believe, may be very significant.
No way will I even try to program your gauge, but maybe you can take a little look, and try making a few changes? Maybe see about making things match, or resemble would be a better word, a little more?
I hope all my babbling may be so some small assistance.
Pat☺
EDIT: I see now I am way too late in my post. I apologise if I insulted your gauge coding capabilities. I meant no disrespect. I was just trying to help, is all...
Bookmarks