posted 03-15- 11:37 PM               

---

Whirlwind had a great paradigm shift in thinking about using obProb in the loadout files, and hopefully the mission editor too (don't think its been tried yet though). Well, it got me to wondering about other uses of obProb within the plane sm file itself.
Is there anything to stop us from using obProb to determine values that are set for the plane to start with? I'm thinking about things like Engine HoresPower and RPM, and maybe aircraft weight, and wingarea etc. Everybody knows that planes ran better or worse than their specs... wouldn't it be cool to have a plane with an Engine rated to 2000 HorsePower, but you're only getting 1950, because of some damn carburetor problem the mechanics couldn't fix that morning? Similarly, changing aircraft weight to account for different pilot/loadout weights, and airfoils' airArea to account for battle damage (maybe just modify the mainCYL airfoil to add drag for instance).

Would this stuff work?

charm

IP: Logged

posted 03-16- 09:45 AM               

---

How bout "obProb enemyExplode 100"

and "obProb meExplode 0"

Those are the two I want.

------------------
--jedi--

IP: Logged

posted 03-16- 09:50 AM               

---

Good one Jedi! Will you be here all week?

-Sv

IP: Logged

posted 03-16- 10:11 AM               

---

The Manc' is the prime target for engine power probability, since the engine that it used was notoriously stinky, that and most of the WWI plane engines...

There is a small chance the I'll give the mission file a go tonight.

IP: Logged