Nyghtfall

Then you should probably have a look at the planes avionics.ini. If it has a HUD (many data shown, ususally in green), than there are several entries that are named "HUD_...". Something like that should be it. If it's just a simple Gunsight (usually no other data shown), maybe you can change the depression-values in cockpit.ini under [GunsightFront]...I guess "DefaultDepression=" is the value you have to change. Just try for yourself.

I don't seem to get, what you're after... Maybe a screenshot would help? I thought, you wanted to move the Gunsight in the cockpit... If I read this above, than you actually want to move the display-mark, your nose is pointing, that is shown on the HUD itself?

As for the above axample: The following is from the stock A-4F-cockpit...the only thing for "Radar-Altimeter" in there: [RadarAltimeter] Type=RADAR_ALTIMETER NodeName=needle_radaralt MovementType=ROTATION_Y ValueUnit=FEET Set[01].Position=-180.00 Set[01].Value=0.0 Set[02].Position=-139.90 Set[02].Value=50.0 Set[03].Position=-100.30 Set[03].Value=100.0 Set[04].Position=-57.40 Set[04].Value=200.0 Set[05].Position=-16.30 Set[05].Value=400.0 Set[06].Position=8.6 Set[06].Value=600.0 Set[07].Position=39.9 Set[07].Value=1000.0 Set[08].Position=60.50 Set[08].Value=1500.0 Set[09].Position=81.60 Set[09].Value=2000.0 Set[10].Position=106.20 Set[10].Value=3000.0 Set[11].Position=137.50 Set[11].Value=5000.0 And that's from the A-4PTM-cockpit.ini -> as you can see, there are 2 more things for the RadarAltimeter: First one is the same as above. [RadarAltimeter] Type=RADAR_ALTIMETER NodeName=needle_radaralt MovementType=ROTATION_Y ValueUnit=FEET Set[01].Position=-180.00 Set[01].Value=0.0 Set[02].Position=-139.90 Set[02].Value=50.0 Set[03].Position=-100.30 Set[03].Value=100.0 Set[04].Position=-57.40 Set[04].Value=200.0 Set[05].Position=-16.30 Set[05].Value=400.0 Set[06].Position=8.6 Set[06].Value=600.0 Set[07].Position=39.9 Set[07].Value=1000.0 Set[08].Position=60.50 Set[08].Value=1500.0 Set[09].Position=81.60 Set[09].Value=2000.0 Set[10].Position=106.20 Set[10].Value=3000.0 Set[11].Position=137.50 Set[11].Value=5000.0 The next 2 are to actually move the Instrument on the X-axis and 2nd on z-axis...as you can only move in 1 direction at a time. The "type" should be of a type, you don't actually use or have in that cockpit, otherwise you can get strange results I guess. Nozzle_position_indicator here, because the Skyhawk doesn't have a nozzle to change. The values are for on and off, that's why there are 2 values...but they are the same, so just use it that way and it will work. The position-stuff is what you have to find out...trial and error here...a lot. It's very time-consuming, as you have to fire up SF every time you change something to check. LOD-viewer won't work here. Also X-,Y- and Z-axis may differ from item to item...you just have to find out. Usually it's +X moves to the right, -X moves to the left, +Y moves to the front, -Y moves to aft, +Z moves up, -Z moves down. In the example I moved the Radar-Altimeter-Casing(*) a bit to the left and a small bit down: (*) = Always use the parent-node of an instrument to move (usually the case_...), to include all child-nodes in the move - you will find out about the structure in LOD-viewer. [MOVE_CaseRadarAlt_X] Type=NOZZLE_POSITION_INDICATOR NodeName=case_radaralt MovementType=POSITION_X Set[01].Position=-0.22 Set[01].Value=0.0 Set[02].Position=-0.22 Set[02].Value=1.0 [MOVE_CaseRadarAlt_Z] Type=NOZZLE_POSITION_INDICATOR NodeName=case_radaralt MovementType=POSITION_Z Set[01].Position=-0.005 Set[01].Value=0.0 Set[02].Position=-0.005 Set[02].Value=1.0

You just should open the A-4PTM-cockpit.ini and a stock A-4F-cockpit.ini and see the difference. You will notice, that this is not just a repainting of stuff...instead it can be a solution for your problem. You decide. Maybe this helps with you understanding the workings. Just look at the pic. It's the same LOD (A-4F-pit.lod). I just moved stuff around with changing things in the cockpit.ini of the plane. I recommend making a new "plane"...make a copy of a plane and change the name in the according plane's ini to use the ...-pit.lod instead the planes lod....that way you can load the Cockpit into LOD-viewer, wich will help you getting the mesh-names to move around and a first guess on distances. An example (You just need to change the green bits, all other entries are of no interest at all.) - the plane-folder is called "_TA-4J Cockpit": [AircraftData] AircraftFullName=_TA-4J Cockpit --> thats the Name of the "Plane" and it's folder. AircraftShortName=A-4 AircraftDataFile=A-4G_data.ini LoadoutFile=A-4G_loadout.ini CockpitDataFile=TA-4J_cockpit.ini LoadoutImage=A-4G_loadout.tga UserList=A-4G_UserList.ini HangarScreen=A-4G_hangar.jpg LoadingScreen=A-4G_Loading.bmp AvionicsDLL=Avionics60.dll AvionicsDataFilename=A-4G_avionics.ini [LOD001] Filename=A-4B_pit.lod --> change to the Cockpit-lod you want to use. Distance=100 [Shadow] CastShadow=TRUE ShadowCastDist=10000 MaxVisibleDistance=800 [DamageTexture] DamagedPostFix=_Holes.DDS

Have a look at my A-4PTM mod. I've used it a lot to mod the cockpit the way it is. There are also hints in the naming, on what axis it affects. You actually can move stuff only in one direction at a time, so if you need all 3 axis to move, than just add the mesh 3 times and move them one after the other. The "REMOVE_..."-bits in the cockpit.ini do not work in SF1 afaik, as the "Type=inactive" isn't available here...you have to move those just out of sight for SF1. The mod is for SF2, but I guess the moving stuff works for SF1 too. Malaysian Skyhawks

Thanks! Never seen them before...I thought this was a joke. P.S. And sorry for hijacking the thread!

I'm really interested, what type of planes Mordor is currently flying.

For safe and easy use thats correct. But it's not really needed, as the length actually _can_ differ. You just have to watch carefully, how the characters etc. are coded. The pattern in the picture is character, followed by "00" (the dots in the right column). Add those "dots" on the left side by typing 00....if you hit the "dot-key", you will get the hex-value of the actual dot, which is not "00". Follow this pattern and don't overwrite stuff other than "00" and it will work with longer or shorter names too.

Some more Air-Defense Skyhawks from ASW-Carriers 2 of the 4 shady Girls of H&MS-15 on USS Hornet in 1965/66 Fanny Hill... and Polly Adler.

You should look for a place to land right after takeoff or have a personal refueler on the way to your targets. ;)

Only 1 goal for this year for me - get enough motivation to do some useful SF2-modding again...

Another way is to look for a photo of good resolution without to much sun, pick the colors from there and adjust them here and there to get a good result.

All A-4E-based Cockpits are repainted and have updated inis (all E, F, G, H, K). A-4A to C and L are still missing. I started work on the B though.

Looks good, thanks!

FRONT and BACK are correct.

There are several similar pics on the net. If someone landed on the wrong carrier, the plane was "decorated" in special ways. ;)

I don't know if SF2 alone is enough - trial and error here I guess. I just reinstall all games, delete the clean stuff in the directories and copy the old modded stuff in those directories. You only need options.ini and versions.ini in the users-directory at c:, everything else therein can be deleted, if you move the mod-folder to another location.

You can do a clean install of all SF2 games to a directory you want, start them once after that to let them create the files in the user-folder. Then change the options.ini to your needs. All other stuff (except versions.ini) in the users-dir can be deleted then. Then copy your modded stuff then to the directory you named in the options.ini.

nice work! you've got a spelling error on the mentioned sticker - greather - get rid of the "h" and another 2 in the second to last one - befor --> before, and separaded --> separated sorry for nitpicking

The Sticker says: "WARNING HERMETICALLY SEALED UNIT DO NOT SUBJECT TO PRESSURE DIFFERENTIAL GREATER THAN 15 PSI" Here's the template for the old Walleye model I once did. Maybe it helps a bit. Template_WalleyeI_NF.7z

Here you go, repainted LAU-7-Rail Have Fun! LAU-7_A4K.7z

VFA-127, Double Nuts, 1986

Your tga seems to be fine. It works perfectly as a decal on a plane - only the tower is visible. Pure guesswork here: Maybe tgas (or transperency of tgas) do not work as texture-file on a 3d-model?

A quick look in some stock plane inis showed that loading-screens are always referenced for stock planes as <name of plane>_loading.jpg (<name of plane> is the same as the foldername of the plane). TW just didn't put a separate picture in there. So if you put a picture in the plane's mainfolder, it should work.