Nope, it doesn't work. The interpolation table doesn't seem to handle the small values necessary for texture translation. For instance, you would think an input value of 29.90 into the following table would give you an output value of 0. No dice. You get .9 no matter what the input value is. So it looks like I'm back to scripting to get this to work for the 3D display. Here's what I want to do:
Write a script that adds a node to the property tree that contains the mbar value. I only want the script to run when the T6 Texan II is loaded. From what I've looked at, it seems the best place for the script is under the nasal directory? Sorry for all of the questions, but we're building a high fidelity cockpit for the T6 Texan II and I want to get as much as possible working. -Vance <animation> <type>textranslate</type> <object-name>mb_digit_3</object-name> <property>/instrumentation/altimeter/setting-inhg</property> <interpolation> <entry> <ind>29.50</ind> <dep>0.9</dep> </entry> <entry> <ind>29.90</ind> <dep>0.0</dep> </entry> </interpolation> <!--<factor>0.001</factor>--> <step>100</step> <!--<scroll>20</scroll>--> <axis> <x>0</x> <y>1</y> <z>0</z> </axis> </animation> -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vance Souders Sent: Friday, November 19, 2004 10:19 AM To: 'FlightGear developers discussions' Subject: RE: [Flightgear-devel] Nasal Vivian, The interpolation table did the trick. Thanks for the heads-up. -Vance -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Vivian Meazza Sent: Thursday, November 18, 2004 12:07 PM To: 'FlightGear developers discussions' Subject: RE: [Flightgear-devel] Nasal Roy Vegard Ovesen wrote: > On Thursday 18 November 2004 16:53, Vance Souders wrote: > > Here's a snippet of code to convert the inhg property value to mbar and > > then use this to rotate the left-most digit on the mbar display. The > code > > doesn't seem to work; Is this the correct usage of the <scale> tag? I > > can't find an example of its use for a 3D cockpit. > > > > <animation> > > <type>textranslate</type> > > <object-name>mb_digit_4</object-name> > > <property>/instrumentation/altimeter/setting-inhg</property> > > <scale>33.86</scale> > > <factor>.0001</factor> > > <step>1000</step> > > <!--<scroll>20</scroll>--> > > <axis> > > <x>0</x> > > <y>1</y> > > <z>0</z> > > </axis> > > </animation> > > > > Thanks again, > > Vance > > Hmmm... I guess that the factor tag does the same for 3d as the scale tag > does > for 2d, so you should put 33.86 inside the factor tag, and remove the > scale > tag completely. But I'm not sure about this. > > I wish I had a clue about how to add text chunks to the 3d animation code > :-| > Here's another way of doing it: data/Aircraft/Spitfire/Models/boost.xml. The data between the <interpolate> and </interpolate> tags converts inHg to psi and changes the output from absolute to gauge. You need to work out the factors involved by hand though. Regards, Vivian _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d _______________________________________________ Flightgear-devel mailing list [EMAIL PROTECTED] http://mail.flightgear.org/mailman/listinfo/flightgear-devel 2f585eeea02e2c79d7b1d8c4963bae2d
