Dels

FYI, the General Dynamics FSW proposal based on the F-16 was nicknamed the "Saberbat". During testing, the X-29 picked up the unofficial nickname of "Polecat." Not sure about that one.

Ok, it seems that one thing is for sure...we can't agree on anything. Thanks to everyone for their continued input an support of this thread. Please continue to make suggestions as we might come up with a name that really fits. Just for stamps, here's a little info regarding the X-29 and it's relationship to other aircraft: The nose section is off an F-5E. The main landing gear and control surface actuators come off an F-16 and the engine is the F404-GE-400 out of the F-18A/B. The rest of the aircraft was purpose built. For my F-29A I've decided on the F404-GE-402 out of the F-18C/D because it's the same size but more powerful.

Ok, well at this stage I'm leaning toward Warhawk II, but what do people think of Rapier?

I agree about Razor. If I included Hellcat II in the poll would people prefer that to Warhawk II? Or am I

Geez, I really stirred up a sh*t storm here didn't I? Do we need a new poll, or should I just decide on a name myself?

Just a preliminary pic of the X-29 model so far.

Only just!

Here's a pic from Max of the gun port.

Sure, I'm not at my computer at the moment, but I'll upload a pic later.

About the cannon, no. I have replaced them with a M61 in the lower right side of the nose. Let me take the time now to make this disclaimer: As this aircraft never went into service and consequently was never fitted with weapons etc. I have taken some artistic licence. If anyone is overly miffed by this, I'm happy to discuss.

I also don't have a problem with it.

While we're on the topic. AFAIK the X-29 was never given an official name other than FSW (Forward Swept Wing). This is pretty lame. So, could everyone come up with some suggestions for names and we'll do a poll to see which one wins. Grumman F-29A "????????" Sound like a good idea? Dels

You'll need to set up a heirarchy in 3dsmax based on what needs to move and how. If we use this B-2 for example, this is what I'd expect the heirarchy to look like (minus all the other meshes): Fuselage Left_Wing Left_Aileron <-----------------------(this is a dummy mesh) Left_Airbrake_Top <-------------(this is a dummy mesh) Left_Rudder_Top <------------(this is the actual visible control surface) Left_Airbrake_Bottom <---------(this is a dummy mesh) Left_Rudder_Bottom <--------(this is the actual visible control surface) You will need to animate the airbrakes splitting in 3dsmax but the rest will move from the entries in the Control Surface section in the _DATA.ini.

Mate, You can see the copilot in "mid-air" because the mesh that the pilot's are linked to is set as ShowFromCockpit=TRUE in the _DATA.ini. To fix the height/position of the pit, you will need to go into the _COCKPIT.ini file and change the OffsetPosition=x.xx,y.yy,z.zz. This is the position of the virtual cockpit reference the external model (and consequently eveything you can see from inside the cockpit). You can change this to the pilot's position from the _DATA.ini and work from there. Dels

Dude, You're correct about the FM. You will have to set up a standard rudder which will act as the aerodynamic rudder in the game. As for the animation, you will need to create a set of dummy/helper meshes to animate the split ailerons. These control surfaces will have no aerodynamic values and will be purely cosmetic. If you need some help, have a look at the _DATA.ini of the F-23A I built. I had to do pretty much the same thing (except the split ailerons). Good luck. Dels

G'Day again, I thought I'd ask before I get shot down again, but is anyone in the middle of building the X-29? If not, it will be my next project, hopefully beginning work next week.

Eraser, I'm still on board with the FA stuff and I can give you a hand with the X-32 when you like. Jedi Master, I'll be planning on having a similar armament to what the X-29 had in Fighter's Anthology.

That's good news. Might have to go back and change some of my pits.

You're right there! A well aimed RPG or S-5 rocket will do heaps more damage than a SA-7/14/16 that has not been defeated by flares/DIRCM.

I guess you could give the "Item number" a try and see if it works for internal fuel tanks. I've never thought about that. However, I don't think you could apply the same to the external tanks. So I think that you might be stuck there. Let us know how you get on.

Once again I have been blown out of the water. The SR-71 etc. is already in the works. But that's good news, because it means it's closer to release than if I were to start one from scratch!

File Name: C-130E Version 1.0 File Submitter: Dels File Submitted: 17 Feb 2008 File Category: Multi Engined Aircraft File Version: 1.00 Website: No Information C-130E As flown by 37 Squadron Royal Australian Air Force from 1966 to 1999. Read the Readme.txt Click here to download this file

Recently, while I was doing the final testing on my C-130E I found that some of the landing light positions on all my Hercs were incorrect. To fix it, do this: Open you C-130*_DATA.ini file and go to the very bottom section where the light positions are. Make the following changes: [inboardTaxiLight1] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=-2.650,0.125,-1.124 <------Change to -2.650,1.15,-1.124 LightSrcOffset=2.43,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE [inboardTaxiLight2] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=2.775,0.125,-1.124 <------Change to 2.775,1.15,-1.124 LightSrcOffset=-2.43,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE and, [LandingLight1] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=-7.400,0.50,1.825 <------Change to -7.408,0.50,1.825 LightSrcOffset=1.0,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE [LandingLight2] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=7.705,0.50,1.825 <------Change to 7.54,0.50,1.825 LightSrcOffset=-1.0,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE

File Name: C-130J-30 Version 2.0 File Submitter: Dels File Submitted: 19 Sep 2007 File Category: Multi Engined Aircraft C-130J-30 As flown by 37 Squadron Royal Australian Air Force. VERSION 2.0 NOTES ----------------- This updated version of my original C-130J-30 has some changes to the model as well as the inclusion of a virtual cockpit. The main changes/additions to the model in Ver 2.0 were: - Added all the antennas and aerials to the top and bottom. - Added pitot probes either side of the nose - Moved the landing gear pods forward. (The old model didn't look "stretched" because the pods were too far back.) - Reshaped the tail and dorsal fin. (Also didn't look right) - Cleaned up the Wing/Fuselage interface. - Fixed the landing gear shock animation and made it so the rudder will turn the nose wheel on the ground. - Extended the cargo compartment inside the aircraft and added two new pallet and three vehicle positions. At this stage, the only vehicle you can load is the M38 jeep included in the game (so sorry, no chute animation). - Modelled the MAWS sensors on the nose and tail. - Modelled the damaged outer wing section. - Fixed the flight model to more accurately resemble that of a Herc. - Added two external hardpoints for external fuel tanks. - Fixed the texture mapping on the control surfaces. - New Hangar and Loading screen. Read the Readme.txt Click here to download this file

Recently, while I was doing the final testing on my C-130E I found that the landing light positions on all my Hercs were incorrect. To fix it, do this: Open you C-130J-30_DATA.ini file and go to the very bottom section where the light positions are. Make the following changes: [inboardTaxiLight1] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=-2.650,0.125,-1.124 <------Change to -2.650,1.15,-1.124 LightSrcOffset=2.43,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE [inboardTaxiLight2] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=2.775,0.125,-1.124 <------Change to 2.775,1.15,-1.124 LightSrcOffset=-2.43,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE and, [LandingLight1] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=-7.400,0.50,1.825 <------Change to -7.408,0.50,1.825 LightSrcOffset=1.0,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE [LandingLight2] SystemType=LIGHT Color=0.88,0.88,0.88 Brightness=0.10 Position=7.705,0.50,1.825 <------Change to 7.54,0.50,1.825 LightSrcOffset=-1.0,80.0,3.0 LightSrcRange=90 LightRange=45.0 CanFlash=FALSE LightNodeName=LandingLight IsLandingLight=TRUE