fly/fgdata
1
0
Fork 0
Code Activity
fgdata/Aircraft/tsr2-yasim-set.xml

85 lines
1.9 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
<?xml version="1.0"?>
<!--
************************************************************************
BAC TSR2 simulation config.
2002-10-26 Lee Elliott leee-fgfs@spatial.freeserve.co.uk
************************************************************************
-->
<PropertyList>
<sim>
<flight-model>yasim</flight-model>
<aero>tsr2-yasim</aero>
<fuel-fraction>1.0</fuel-fraction>
<sound>
<audible>true</audible>
<path>Aircraft/a4/a4-sound.xml</path>
</sound>
<panel>
Lee Elliott: Here are some more updates, and bits and pieces. The tsr2 is mostly a re-write, with more reasonable figures for the wing and hstab. I've also tried to reduce the poly count on the model whilst adding the airbrakes and canopies. Finally, I've set up some panels, based on the c310 vfr and mini panels. The vfr panels have a lot of additional instruments on them but impose quite a high frame-rate hit on my system. The mini panels also have some additional instruments but seem to work without noticable penalty here. I've set these panels as the defaults for these aircraft but I'm not sure it's a good idea to have the vfr panels by default due to the performance hit. Using them as default will should give some feedback though;) To go with the new panels are a number of rough and ready instruments I hacked, mostly out of one of the rpm gauges, but I've adapted the throttle quadrent (jet-throttle-quadrant) to funstion for throttle, flaps and reheat. All the gauge faces were based on an existing ffgfs instrument texture, so there's no problem with copyright there. All the other bits that I've done may be distributed under the same conditions as fgfs.
2003-01-19 03:50:13 +00:00
<path>Aircraft/tsr2/tsr2-vfr-panel.xml</path>
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
</panel>
<panel_2>
Lee Elliott: Here are some more updates, and bits and pieces. The tsr2 is mostly a re-write, with more reasonable figures for the wing and hstab. I've also tried to reduce the poly count on the model whilst adding the airbrakes and canopies. Finally, I've set up some panels, based on the c310 vfr and mini panels. The vfr panels have a lot of additional instruments on them but impose quite a high frame-rate hit on my system. The mini panels also have some additional instruments but seem to work without noticable penalty here. I've set these panels as the defaults for these aircraft but I'm not sure it's a good idea to have the vfr panels by default due to the performance hit. Using them as default will should give some feedback though;) To go with the new panels are a number of rough and ready instruments I hacked, mostly out of one of the rpm gauges, but I've adapted the throttle quadrent (jet-throttle-quadrant) to funstion for throttle, flaps and reheat. All the gauge faces were based on an existing ffgfs instrument texture, so there's no problem with copyright there. All the other bits that I've done may be distributed under the same conditions as fgfs.
2003-01-19 03:50:13 +00:00
<path>Aircraft/tsr2/tsr2-mini-panel.xml</path>
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
</panel_2>
<hud>
<path>Huds/Default/default.xml</path>
<visibility>true</visibility>
</hud>
<model>
<path>Aircraft/tsr2/tsr2-model.xml</path>
</model>
<view n="1">
<config>
Lee Elliott: Here're a couple of updates. Well, one's an update - the tsr2 and this now has reasonable wing and hstab values. The roll rate was very high and I figured that as it was going to be a hack anyway, due to the all moving tailplanes, I just made them very ineffective and linked them top the tailplanes in the model file. I think I may have over factored them a bit too much but it's interesting watch them in chase view. If the autopilot roll-out-deg is dropped to about two it'll start oscillating, and from behind it looks like it's paddling:)
2003-01-09 14:54:53 +00:00
<z-offset-m type="double" archive="y">-50.0</z-offset-m>
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
</config>
</view>
</sim>
<controls>
Use new magnetos property.
2003-04-05 15:15:40 +00:00
<engines>
<engine n="0">
<magnetos>3</magnetos>
</engine>
<engine n="1">
<magnetos>3</magnetos>
</engine>
</engines>
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
</controls>
<autopilot>
<config>
<min-climb-speed-kt type="float">150.0</min-climb-speed-kt>
Lee Elliott: Here're a couple of updates. Well, one's an update - the tsr2 and this now has reasonable wing and hstab values. The roll rate was very high and I figured that as it was going to be a hack anyway, due to the all moving tailplanes, I just made them very ineffective and linked them top the tailplanes in the model file. I think I may have over factored them a bit too much but it's interesting watch them in chase view. If the autopilot roll-out-deg is dropped to about two it'll start oscillating, and from behind it looks like it's paddling:)
2003-01-09 14:54:53 +00:00
<best-climb-speed-kt type="float">650.0</best-climb-speed-kt>
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
Lee Elliott: Here're a couple of updates. Well, one's an update - the tsr2 and this now has reasonable wing and hstab values. The roll rate was very high and I figured that as it was going to be a hack anyway, due to the all moving tailplanes, I just made them very ineffective and linked them top the tailplanes in the model file. I think I may have over factored them a bit too much but it's interesting watch them in chase view. If the autopilot roll-out-deg is dropped to about two it'll start oscillating, and from behind it looks like it's paddling:)
2003-01-09 14:54:53 +00:00
<target-climb-rate-fpm type="float">12000.0</target-climb-rate-fpm>
<target-descent-rate-fpm type="float">8000.0</target-descent-rate-fpm>
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
Lee Elliott: Here are some more updates, and bits and pieces. The tsr2 is mostly a re-write, with more reasonable figures for the wing and hstab. I've also tried to reduce the poly count on the model whilst adding the airbrakes and canopies. Finally, I've set up some panels, based on the c310 vfr and mini panels. The vfr panels have a lot of additional instruments on them but impose quite a high frame-rate hit on my system. The mini panels also have some additional instruments but seem to work without noticable penalty here. I've set these panels as the defaults for these aircraft but I'm not sure it's a good idea to have the vfr panels by default due to the performance hit. Using them as default will should give some feedback though;) To go with the new panels are a number of rough and ready instruments I hacked, mostly out of one of the rpm gauges, but I've adapted the throttle quadrent (jet-throttle-quadrant) to funstion for throttle, flaps and reheat. All the gauge faces were based on an existing ffgfs instrument texture, so there's no problem with copyright there. All the other bits that I've done may be distributed under the same conditions as fgfs.
2003-01-19 03:50:13 +00:00
<elevator-adj-factor type="float">800.0</elevator-adj-factor>
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
<integral-contribution type="float">0.005</integral-contribution>
Lee Elliott: Here are some more updates, and bits and pieces. The tsr2 is mostly a re-write, with more reasonable figures for the wing and hstab. I've also tried to reduce the poly count on the model whilst adding the airbrakes and canopies. Finally, I've set up some panels, based on the c310 vfr and mini panels. The vfr panels have a lot of additional instruments on them but impose quite a high frame-rate hit on my system. The mini panels also have some additional instruments but seem to work without noticable penalty here. I've set these panels as the defaults for these aircraft but I'm not sure it's a good idea to have the vfr panels by default due to the performance hit. Using them as default will should give some feedback though;) To go with the new panels are a number of rough and ready instruments I hacked, mostly out of one of the rpm gauges, but I've adapted the throttle quadrent (jet-throttle-quadrant) to funstion for throttle, flaps and reheat. All the gauge faces were based on an existing ffgfs instrument texture, so there's no problem with copyright there. All the other bits that I've done may be distributed under the same conditions as fgfs.
2003-01-19 03:50:13 +00:00
<max-aileron type="float">0.5</max-aileron>
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
<max-roll-deg type="float">60.0</max-roll-deg>
Lee Elliott: Here are some more updates, and bits and pieces. The tsr2 is mostly a re-write, with more reasonable figures for the wing and hstab. I've also tried to reduce the poly count on the model whilst adding the airbrakes and canopies. Finally, I've set up some panels, based on the c310 vfr and mini panels. The vfr panels have a lot of additional instruments on them but impose quite a high frame-rate hit on my system. The mini panels also have some additional instruments but seem to work without noticable penalty here. I've set these panels as the defaults for these aircraft but I'm not sure it's a good idea to have the vfr panels by default due to the performance hit. Using them as default will should give some feedback though;) To go with the new panels are a number of rough and ready instruments I hacked, mostly out of one of the rpm gauges, but I've adapted the throttle quadrent (jet-throttle-quadrant) to funstion for throttle, flaps and reheat. All the gauge faces were based on an existing ffgfs instrument texture, so there's no problem with copyright there. All the other bits that I've done may be distributed under the same conditions as fgfs.
2003-01-19 03:50:13 +00:00
<roll-out-deg type="float">4.0</roll-out-deg>
<roll-out-smooth-deg type="float">20.0</roll-out-smooth-deg>
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
<zero-pitch-throttle type="float">0.5</zero-pitch-throttle>
<zero-pitch-trim-full-throttle type="float">0.001</zero-pitch-trim-full-throttle>
</config>
</autopilot>
</PropertyList>
Copy permalink