Prospero 1 Posted July 16, 2002 Hi all, A quick message to ask if anyone knows whether the _apparently_ impotent CamSetDive and CamSetBank commands have been fixed yet (for v1.75) or perhaps stand a chance of being fixed in the future? A couple of things occured to me during the hours and hours of slaveishly trying to figure them out: 1) Changes appear only to be "committed" for vehicles with simulation-type "camera". That is, if, having issued these commands and Camcommit'ed them, one puts in a condition like -- @camcommitted _mycamera-- one will find that script execution is halted if you have used the commands on a vehicle with any other simulation-type. Of course, the commands don't work even with a vehicle of simulation-type "camera", but it's still worth pointing this out, I guess. 2) Using a SetDir on any object, including a camera-type, seems to set all three components of its attitude (yaw, pitch and roll) to zero - not just it's direction (yaw). I imagine this is why there are three separate attitude commands for setting camera attitude, including CamSetDir. Setdir would simply override the whole lot. Of course, it should be pointed out that CamSetDir doesn't work either... 3) Why am I bothering with this? That's a very good question. It's completely my own fault! You see, I am trying to implement something known as the "NASA Minimum Complexity Helicopter Maths Model" within OFP and "attach it" to a gamelogic, or better still, a custom vehicle of simulation-type "static" - as these have little physics associated with them. The idea is to develop a pretty realistic (yet fun!) UAV sim within OFP. I have already flown the maths model in OFP, and have developed a method to gain access to four axes of "simulated analog" keyboard input accessable via script. (You really do need four axes for a helicopter). Alternatively, one can have "proper analog" with a programmable joystick such as the TM Cougar. The one BIG thing missing is any way to assign the pitch and roll values generated by the maths model to either the heli UAV itself, or a camera placed "in" the UAV. Hence my interest in the CamSetDive and CamSetBank commands. If anyone knows something that might help, pls do get in touch. Indeed, I'd be most grateful if some kind soul at BIS could let me know whether these commands... a) Don't work b) Do work, and it's simply my own stupid fault. c) Will never work d) Might work in the future... (Tick one?) Best, Prospero Share this post Link to post Share on other sites
