-
Posts
691 -
Joined
-
Last visited
-
Days Won
27
Content Type
Profiles
Forums
Gallery
Downloads
Store
Everything posted by Dels
-
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
-
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.
-
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.
-
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!
-
G'Day all, I'm in the middle of a project at the moment, but I was considering doing an SR-71 as my next project. Is anyone interested? Also, if I did make a recon SR-71, would anyone be interested in a fictional strike version with internal weapons bays?
-
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
-
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_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
-
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-130H_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
-
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
-
-
View File C-130E Photoshop templates Ver 1.0 These are the Photoshop templates for my C-130E Ver 1.0, so that others can make skins for it. Enjoy! Submitter Dels Submitted 02/17/2008 Category Skin Templates / Decal Sets
-
-
View File C-130E Version 1.0 C-130E As flown by 37 Squadron Royal Australian Air Force from 1966 to 1999. Read the Readme.txt Submitter Dels Submitted 02/17/2008 Category Multi Engined Aircraft
-
G'day everyone, Just thought I'd post to say that a C-130E will be inbound very soon. No pics to post at this stage, but you won't have to wait long. Maybe two weeks, maybe less... Dels
-
Marcello is already a fair way into building a B-2.
-
But of course if you want to put the decal on the doors also, you'll need to create a separate entry for them.
-
Yeah, I attached the landing gear pods to the fuselage. So the mesh is "Fuselage". Any time.
