1
0
Fork 0
fgdata/Aircraft-yasim/tsr2-yasim.xml

134 lines
5.7 KiB
XML
Raw Normal View History

Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<!-- TSR2 yasim config. This is a hack and not an authentic
representation of the aircraft. Having said that, the
numbers, where I could find them, roughly match those of
the original aircraft. Lee Elliott.
The ailerons are a hack on this fdm - the real aircraft
use all moving tail planes for roll and this model had a
very high roll rate so they've been made relatively
ineffective and in the model/anim file the aileron surface
positions actually operate on the tailplanes.
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
-->
<airplane mass="54750">
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<!-- Approach configuration -->
<approach speed="130" aoa="10.0">
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-setting axis="/controls/throttle[0]" value="0.2"/>
<control-setting axis="/controls/throttle[1]" value="0.2"/>
<control-setting axis="/controls/flaps" value="1.0"/>
<control-setting axis="/controls/spoiler" value="0.2"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-setting axis="/controls/gear-down" value="1"/>
</approach>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<!-- Cruise configuration -->
<!-- <cruise speed="500" alt="35000"> -->
<cruise speed="550" alt="35000"> -->
<control-setting axis="/controls/throttle[0]" value="0.5"/>
<control-setting axis="/controls/throttle[1]" value="0.5"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-setting axis="/controls/flaps" value="0.0"/>
<control-setting axis="/controls/gear-down" value="0"/>
</cruise>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<cockpit x="8.5" y="0.0" z="1.0"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<fuselage ax="13.0" ay="0" az="0" bx="-14.13" by="0" bz=".64"
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
width="2.0" taper="0.5" midpoint="0.3"/>
<wing x="-3.0" y="1.5" z="1.7" taper="0.25"
length="5.0" chord="6.0" sweep="50" dihedral="-1.0" camber="0.003">
<stall aoa="35.0" width="3" peak="1.3"/>
<flap0 start="0.0" end="0.9" lift="1.4" drag="1.2"/>
<flap1 start="0.0" end="0.4" lift="1.05" drag="1.2"/>
<spoiler start="0.54" end="0.86" lift="0.0" drag="20.0"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-input axis="/controls/flaps" control="FLAP0"/>
<control-input axis="/controls/aileron" control="FLAP1" split="true"/>
<control-input axis="/controls/aileron-trim" control="FLAP1" split="true"/>
<control-input axis="/controls/spoilers" control="SPOILER"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-output control="FLAP0" prop="/surface-positions/flap-pos-norm"/>
<control-output control="FLAP1" side="left"
prop="/surface-positions/left-aileron-pos-norm"/>
<control-output control="FLAP1" side="right"
prop="/surface-positions/right-aileron-pos-norm"/>
<control-output control="SPOILER" side="left"
prop="/surface-positions/left-spoiler-pos-norm"/>
<control-output control="SPOILER" side="right"
prop="/surface-positions/right-spoiler-pos-norm"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-speed control="FLAP0" transition-time="5"/>
<control-speed control="SPOILER" transition-time="0.5"/>
</wing>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<hstab x="-10.0" y="1.0" z="0.5" taper=".2" effectiveness="2.0"
length="3.0" chord="4.0" sweep="55" dihedral="0.0">
<stall aoa="35.0" width="3" peak="1.5"/>
<flap0 start="0" end="1" lift="1.26" drag="1.3"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-input axis="/controls/elevator" control="FLAP0"/>
<control-input axis="/controls/elevator-trim" control="FLAP0"/>
<control-output control="FLAP0" prop="/surface-positions/elevator-pos-norm"/>
</hstab>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<vstab x="-10.0" y="0" z="1.38" taper=".176" effectiveness="1.0"
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
length="4.5" chord="4.0" sweep="50">
<stall aoa="28.0" width="3" peak="1.5"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<flap0 start="0" end="1" lift="1.15" drag="1.3"/>
<control-input axis="/controls/rudder" control="FLAP0" invert="true"/>
<control-output control="FLAP0" prop="/surface-positions/rudder-pos-norm"/>
</vstab>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<!-- nose -->
<gear x="3.0" y="0" z="-2.0" retract-time="7" compression="0.8">
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-input axis="/controls/rudder" control="STEER" square="true"/>
<control-input axis="/controls/gear-down" control="EXTEND"/>
<control-speed control="EXTEND" transition-time="7"/>
<control-output control="EXTEND" prop="/gear/gear/position-norm"/>
</gear>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<!-- left main -->
<gear x="-4.0" y="2.5" z="-2.0" retract-time="7" compression="0.8">
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-input axis="/controls/brakes[0]" control="BRAKE"/>
<control-input axis="/controls/gear-down" control="EXTEND"/>
<control-speed control="EXTEND" transition-time="7"/>
<control-output control="EXTEND" prop="/gear/gear[0]/position-norm"/>
</gear>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<!-- right main -->
<gear x="-4.0" y="-2.5" z="-2.0" retract-time="7" compression="0.8">
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<control-input axis="/controls/brakes[1]" control="BRAKE"/>
<control-input axis="/controls/gear-down" control="EXTEND"/>
<control-speed control="EXTEND" transition-time="7"/>
<control-output control="EXTEND" prop="/gear/gear[1]/position-norm"/>
</gear>
<!-- Canopy -->
<gear x="3.0" y="0.0" z="0.6" retract-time="7" compression="0.6">
<control-input axis="/controls/parking-brake" control="EXTEND"/>
<control-speed control="EXTEND" transition-time="10"/>
<control-output control="EXTEND" prop="/canopy/position-norm"/>
</gear>
<jet x="-8.0" y="-1.0" z="0.4" mass="4000" thrust="16600" afterburner="30600">
<!-- <jet x="-22.0" y="-1.0" z=".44" mass="4000" thrust="30600"> -->
<control-input axis="/controls/throttle[0]" control="THROTTLE"/>
<control-input axis="/controls/afterburner[0]" control="REHEAT"/>
</jet>
<jet x="-8.0" y="1.0" z="0.4" mass="4000" thrust="16600" afterburner="30600">
<!-- <jet x="-22.0" y="1.0" z=".44" mass="4000" thrust="30600"> -->
<control-input axis="/controls/throttle[1]" control="THROTTLE"/>
<control-input axis="/controls/afterburner[1]" control="REHEAT"/>
</jet>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<tank x="-2.0" y="0.0" z="0.5" jet="true" capacity="13000"/>
<tank x="-3.0" y="2.5" z="1.7" jet="true" capacity="11000"/>
<tank x="-3.0" y="-2.5" z="1.7" jet="true" capacity="11000"/>
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
<ballast x="8.5" y="0" z="0" mass="3000"/> <!-- Cockpit -->
<ballast x="4.0" y="0" z="0" mass="3000"/> <!-- avionics -->
<ballast x="-6.0" y="0" z="0" mass="100"/> <!-- Trim ballast -->
Lee Elliott: I've taken the liberty of attaching a .tar.gz file containing a .3ds model of a BAC-TSR2, a yasim config file based on the correct figures (where I could find them) and the -set.xml and model.xml files to fly it. I'm primarily a 3d'er and originally did the TSR2 for a picture I'm working on but when I got fgfs running (Debian Linux) I couldn't resist loading it in and trying to get it to fly. The model was created in Realsoft3D and exported as .3ds. I've been able to tag the various sub-objects, to animate them but the export process appears to 'flatten' any object hierarchy I set up and I'm guessing this is necessary for sequential animations - I couldn't set up the correct sequential rotations to properly bring the main u/c in. Also, in real life, there are several other u/c doors that should open and close in sequence to get the gear in and apparently the sequence was quite complex. On the ground though, it is as shown (so I didn't need to model the extra doors for my picture anyway;) It could do with some airbrakes too, both for the model and for the fdm. As with the extra u/c doors, I didn't need them for the picture and they haven't been modelled. As well as not being able to preserve object hierarchies when I export from Realsoft3D's native object format to .3ds, I'm not able to preserve textures or colour-mapping either, so the aircraft appears all white. Hopefully, someone might like to add the extra doors and airbrakes, which shouldn't be too difficult, and put some texturing on it - mostly white anyway, for the prototypes, or a contemporary RAF scheme if someone wants to pretend that it entered service. The yasim fdm model, as said, cannot be regarded as accurate. However, while it is based on the specs for the real aircraft, where I could find them, the measurments are probably only accurate to about 1 metre. That's assuming I was measuring the right things in the first place;) Other bits that I wasn't sure about i.e. flaps, ailerons etc. have been hacked out of the a4 or the 747. It could do with some 'refinment' by people who know what they're doing, but it seems to fly about right, or rather, as I'd imagine:) (me want a forward-looking ski-toe terrain avoidance radar:) Anyway, I'm happy for the whole lot to be released under the same licence and conditions as the rest of the fgfs stuff, either as a part of fgfs or by anyone else who will also follow those same licence and condition terms. I've also got a reasonable yasim b52 flying but no moveable bits on the model yet, a vulcan with a similar simple 3d model using a grossly hacked c310 jbsim fdm (right numbers where I could find them but powered by a couple of XLRs) and a Saunders-Roe SR45 Princess flying boat model and yasim fdm (can't get it into the air with propellors but substituting equivilent jets (2.5x factor) got it flying. I've started on a EE/BAC Lighting FMk6 model but I'll probably be doing a Fairchild A-10 and an Antonov An-225 first. I figure this is the best way I can contribute to the fgfs project, and l'd like to be able to offer something.
2002-11-27 21:35:06 +00:00
</airplane>