posted 12-07- 05:28 PM               

OK, thanks to Condor I'm working on an advanced engine DM, condors DM was the inspiration The information I desperatly need is this:

The pit dails qry things like eng temp, oil psi, coolant temp etc etc, OK, I know how to qry the data for the dials, but thats not what I need, I need to affect these readings, I need to raise the temp and lower the psi readings on the coolant, oils system and engine.

Can someone please tell me how I need to code this so that when a part takes damage I can call a function that will show a lowered oil PSI (for example) on the cockpit dials, this is a rather important part of my new DM so any help is really needed and very (as always) appreciated..

Thanks alot guys

~Nat~

posted 12-08- 12:01 AM               

I did this another way on the engine damage model for the Mustang. I added a dof to the needle of a gauge, and used an obExec/Func to call it. I could make a temp go higher and back down depending on what effect I wanted.

I can't remember why I didn't use the Max/Min, (maybe couldn't reset it?) but I do think it is the best way.

I hope that helps, I can't wait to see what you are cooking up for us.

posted 12-08- 12:13 PM               

You create an obFunc on the parent (fuselage) called, say, "Overtemp." The DOF for the 20-degree needle movement is activated by "cmdOvertemp" and the obFunc Overtemp in the main object is called by, say "onDmg 5" in the obDamage property for the engine. When your engine hits damage level 5, the carb heat guage will then go up 20 degrees, and stay there.

If you have a way to "fix the problem" (in the Corsair you open the oil cooler flaps--yes you can see them move now) then you make another DOF for the same guage, activated by "cmdCooldown" and another obFunc in the parent object "Cooldown." The Cooldown obFunc requires a breaking DOF to activate, and then triggers an "undoing" of some of the "bad stuff" that was happening due to the overtemp.

In the Corsair, your engine will "die" in a few minutes if you ignore the overtemp, but if you take "corrective action," it MIGHT run long enough to get you home. Or not

You can even define MULTIPLE guage readings off of the SAME obFunc, so you can make all the temperature guages react to the same damage using the same "cmdOvertemp" trigger.

In the Corsair, the guage movement was too "subtle" so I added a little "overheat warning light" that will come on when you get an oil leak, and go out if the engine "cools down." The engine still might fail though even with the cooler flaps open.

Anyway, that's an alternative to fiddling with the Min and Max values. You can create a separate DOF, and it will take the EXISTING position of the needle as "zero" and modify it from that point.