From: Jim W. <ji...@ke...> - 2001-07-10 23:34:32
|
Hi, Well not much done yet with pilot-offset parameters (been busy pretending to be on vacataion) but I have been thinking about it. Haven't seen enough of the code to know yet: How much mem and cpu resource are we talking about for a 3rd view? I'm thinking that adding an overhead-view would be helpful. Take a look at the xml down below, I'm not necessarily talking about adding support for creating x number of views in xml (not yet anyway...as Norman mentioned the view code will need real work at some point). But rather would use xml props to enable or disable two variations of the lookat view. One being the chase-view that we have now, and the other the new overhead-view. This would allow cycling through the three views using the v key (or whatever binding). Also we'd be able to add parameters such as a default pilot-offset for each view. Let me know if this sounds useful before I make the code changes (which should be *fairly minor*). Any suggestions would be most welcome. BTW if you haven't tried the taxiway scenery files yet, check them out. They look really cool. I even spent about 20 minutes cruising around all the ones at SFO. Kinda fun going down those long ones 50mph with the wheels on the ground. Didn't even get a speeding ticket. Best, Jim <sim> .. <views> <chase-view> <enabled>1</enabled> <pilot-offset> <X>25.00</X> <Y>0.01</Y> <Z>0.01</Z> </pilot-offset> </chase-view> <overhead-view> <enabled>1</enabled> <pilot-offset> <X>40.0</X> <Y>0.01</Y> <Z>25.0</Z> </pilot-offset> </overhead-view> </views> </sim> |