Jump to content

Nyghtfall

+MODDER
  • Content count

    612
  • Joined

  • Last visited

  • Days Won

    11

Nyghtfall last won the day on February 2

Nyghtfall had the most liked content!

Community Reputation

1,171 Excellent

About Nyghtfall

Profile Information

  • Gender
    Male
  • Location
    Schwenningen, Germany

Recent Profile Visitors

5,261 profile views
  1. Good to see you back in action!
  2. The TA-4-Model isn't getting any younger, but that's what we have...Getting there. TA-4H of TNI-AU (Indonesian Air Force).
  3. Size doesn't matter...something one could check without ANY effort. If the BMP works, than just use than one... Otherwise: Convert your BMP to a simple JPG, change the callout in the planes ini-file from BMP to JPG (not the data.ini) and it will also work...
  4. The only use of Alpha-Channels in SF2 I know of is for decals --> TGA-files. They are used to cover areas, that should not be seen on the decal (everything, except the number or whatever the decals shows). All other files (BMP, JPG) do not require or use Alpha-Channels. If I load the stock-loading-screen (blurred brownish F-4 picture) into Photoshop the file doesn't even have an Alpha-Channel...
  5. A quick last reply by me. Some of your questions are pointless, because with little effort you could find answers or at least another option for further trials. I think you said somewhere in your posts, that you are a fast-learner and have experience with modding for years...really? The picture you're drawing in your answer is of a total newbie, that just discovered SF2 and TW out of the blue... SF1 and SF2 are different for sure, no question about that, but still there are a lot of things similar...and that should not be a problem for a fast-learner, with your background. The boards are for helping people, yes. But excuse my ignorance...If someone wants help, everyone can expect at least a tiny bit of own effort, which IMHO you lack often enough... You ask a question, get an answer or at least a hint for further trial and all you do is ask more and more questions (and as spinners correctly mentioned...you ask tons of different questions one after the other in threads, that have nothing to do with it...if an answer is helpful, nobody will ever find it again in that mess), instead of just doing anything or test something. That's the picture I have of you. Your computer won't explode, if you just test something here and there. And excuse me again, maybe it's the language barrier (I'm also no native english-speaker), but for me your reaction to an answer is not always the nicest (I tried to sound as kind as possible here...). The "no one helps you with what you want to know"-bit is actually YOUR problem...Sorry to say that. Remember your gunsight-thread? There are posts after posts of people trying to help you...and in the end you had a total different problem than people thought the whole thread... So it was actually YOUR problem to not correctly describe your problem...and as people said already....make screenshots...you didn't... Don't blame people for your faults... People will help you in this community...they are just not always on your side when you snip a finger (actually a german quote...). This whole community-game-flight-sim-thing is a HOBBY of all of those people here... They relax while modding or playing the game. They are not here to answer your questions or do something for you... And yet they do! In the beginning my thoughts where exactly like yours...I asked and nobody was enthusiastic enough to help me out. Today I understand those! There are 2 options here...quit anything and be angry about all those egoistic people here or continue, learn stuff on your own, contribute to the community and be actually part of it. I chose the 2nd and it was the right decision. I learned Photoshop and Blender from scratch and although I still cannot build planes, I can make fakepilots for my favourite planes, which gives me more opitions to do more modding...an actual win for me! Be part of this community, try things out and learn stuff...
  6. Reinventing the wheel again and again and again and again... You could ask billions of questions and it still won't work, because you just ask question after question. Just try out stuff...experiment with stuff...check released stuff versus yours...make a MOD-folder just to try things out. If it doesn't work...then who cares...start again. That's how many people here did it and obviously it worked! If you have serious questions, ask and I'm sure people WILL help you out. You want much input...fair enough...we all want to...but the way you do it is not the best. ;) I like to help people out with my very limited knowledge of this game, but if I know from the beginning, that the answer to the actual question is of little interest, because the next bazillion questions are in the line already or you know it better anyways, then why care? If your custom loading screen doesn't work, then it is on your end. I am sure (absolutely, to be exactly), that there are tons of working examples found here on this site or in the download-section(*), that you could just download, try out and check those files versus yours to find the error. At the moment I'm looking for some pilot-model that I can use (and repaint) for one of my mods....guess what? I am downloading stuff and look for myself, rather than asking 5 milion questions... Sorry if I sound harsh, but checking the boards for news and only seeing tons of (often enough) pointless questions is a bit annoying. And yes, I am in a bad mood today, so sorry again :P Edit: added (*) --> You even have some mod already to check your loading-screen-error already....remember the Malaysian Skyhawks Mod from your other question lately? Have a look...it has loading and hangar-screens...and both are working! So don't just ask - do! ;)
  7. Indonesia LowVis Camo...TA-4H/J 2-Seaters are next.
  8. Just set the path of your SF2-Installation under "extras-->settings" in LOD-viewer. Otherwise it doesn't know where to find the CATs.
  9. Some more Asian Scooters...this time from Indonesia! Actually this was the first mod I release here a looong time ago (with the help of dtmdragon - Dan ) - Now it's time for an update!
  10. 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.
  11. 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?
  12. 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
  13. 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
  14. 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
  15. My A-4M- and OA-4M-mods are no dedicated models...the one is based on TWs A-4F/F_74-models, the other is based on Fractures TA-4-model. So you can use the templates available. I'll have a look for the templates of the fakepilot-stuff needed though.
×

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..