yakarov79

Nope. or you can add lights via effect emitter. In this case, the effect is quite cool but it does not really give illumination ahead...rather than glowing bulb ...but looks better than those tgas shaped into light cones. (or maybe someone can work on emitter effect that will give proper light effect) I am using one of the aircraft carriers emitter effects. during the day... and night...

better to use symmetry. make a wheel , resetxform, uvmapp, set pivot point to X=0, apply symmetry on x axis. then again symmetry on y axis. You have 4 wheels. fast and easy.

Nope. It is already in the freezer. Not gonna bother me now...one day perhaps.

must be part of model...no animation, only movement via pitch and yaw of mesh... no as far as i know...it drift left or right but no steering as we know it... only animation for a ground object is reload animation I think...(not even sure if it works) Nope. You can add 'tga lights' like me or killerbee added to flightline objects...but the thing is it will appear 24h .....so no point really.

does not matter. assign a different material to wheels only. if you clone and then mirror etc...and then resetXform..you have to flip polys.

did you try to assign different material for wheels ? wheels are editable poly or mesh?

exactly. was about to say the same thing. SF1 ini

I am lost .. those are just normal pilots from a pilot folder? the maybe create new aircraft component in data ini [AircraftData] EmptyMass=10900.0 EmptyInertia=197413.39,30260.70,203674.09 ReferenceArea=38.00 ReferenceSpan=11.10 ReferenceChord=3.71 ReferenceLength=17.32 CGPosition=0.00,-1.20,0.15 UseMetricUnit=TRUE Component[001]=Fuselage Component[002]=Nose Component[003]=LeftWing Component[004]=RightWing Component[005]=LeftStab Component[006]=RightStab Component[007]=LeftVertTail Component[008]=RightVertTail Component[009]=LeftOuterWing Component[010]=RightOuterWing Component[011]=placeforpilots then that component... [placefor pilots] ModelNodeName= ShowFromCockpit=FALSE MassFraction= HasAeroCoefficients=FALSE CLa=0 DamageRating=DISABLED SystemName[001]=pilot SystemName[002]=copilot

yes and for example 4 dig counter in cokcpit ini. [RadarAltimeter] Type=RADAR_ALTIMETER CounterNodeFormat=RADalt_dig%d MovementType=ANALOG_COUNTER ValueUnit=FEET represent those 4 nodes linked to one parent mesh. Altimeter_box [144 polys, 160 verts] '03' RADalt_dig1 [20 polys, 40 verts] '21b- Default' RADalt_dig2 [20 polys, 40 verts] '21b- Default' RADalt_dig3 [20 polys, 40 verts] '21b- Default' RADalt_dig4 [20 polys, 40 verts] '21b- Default' important is meshes should have names ended by dig1, dig2 dig3, dig4 last number on counter is dig1 where a higher dig(4/5/6) is the first number on the counter

good idea... It all also depends on the damage model of particular aircraft.

One of the most common missiles launched at me. Somehow easy to avoid if you are fast...but if few appear in area...It is getting harder. Very effective against slower aircraft. The only issue is that often fires at targets at maximum range...so effective shots decrease as it is easy to avoid.

yap F-100F uses Tank335-F100C and Tank335_F100C (silver and camo) both should be included in yap set. Each bitmap skin should be in the weapon folder not in aircraft skin folder (tank is not a part of airframe) look for errors in aircraft.ini loadout.ini etc. maybe there is a misspell or something.

I think you just need to launch the game...for all ini entry to be updated.. Quit program and LOD viewer will see all skin sets.

Do not get me wrong. I am aware of read_me. But still, i did a shitload of work to convert stary's tiles to your terrain. including adding more than 60 new tiles. few things are not finished (and perhaps never will be..but for home use, this terrain now is quite a prefect)

Bored with flyers... so moved back to targets...just Labour Day laziness... to add to my SA-3 system... 5P73, 5W27, and PR-14A

you need to map. Like anything else.. So if you want 'reflection' of pilot on canopy top left-right front..you have to map those positions on a bitmap. Reflection actually, in my opinion, is quite a fuzz in SF2. It is still image....so despite your position and position of the sun...reflection is always the same.... That is why I am not sure if some detailed reflection is good on gauges..etc...just my personal preference. despite the environment, you will have 'reflection' there Could be better to do just glass with some cool glossiness.

You can put Stary's tiles on Wrench/Gepard terrain. Lots of work. But. Works for me.

Super Jolly Green Giant

oh? how about BUFF and Albert ...not really younglings.

little below 7Mb. switch to a position via hook indicator (or any of the empty/unused /not important indicator) and one animation in 3dmax. In fact you are not switching position in the cockpit - you are moving the whole cockpit to a different position as a point of view is defined in cockpit ini. my way in my two-position cockpits (Cobra, Loach, TAV-8) Type=ARRESTING_HOOK_INDICATOR MovementType=ANIMATION AnimationID=10 AnimationTime=1.0 Set[01].Position=0.0 Set[01].Value=0 Set[02].Position=1.0 Set[02].Value=1 but can be also (if you have an empty animation slot in the external model) by adding and animating some hidden mesh in an external model. Then cockpit animation can be done as tornado-guuruu way [Co_pilot] Type=EXTERNAL_ANIMATION_LINK NodeName=whatever you are moving -top mesh in a hierarchy. MovementType=ANIMATION AnimationID=1 ? ItemNumber=4 ?

In my twin-seat harrier after transferring to back seat - cockpit ini moves whole front panel (and some other nodes that are not really visible from the back seat) to the back behind back seat - so generally it is not in point of view from 2nd seat. This is still a prototype mambo jambo..but in fact form back seat you are not seeing front panels...so move them out of POV.