Wrench

yes, it's the single sheet skin texture. The good thing is, if I make an Army or whatever version, simple hex editing and renaming the MAIN skin (fuselag1, fuselag2, etc) and renaming the lod to match (HRS -seen above, CH-19 for USArmy, etc), all the interior bits remain the same. I don't know why this is true, but the H-19 is my favorite helicopter. Maybe from all those old movies (and don't forget, they used to get Prof. Challenger to the plateau to discover his dinosaurs!!) or my Dad used to take me to the western end of Santa Monica Airport as a kid (1960s) to watch the US Mail chopper pick up it's load of letter.

oh, hell yes this is getting pinned!! DONE!!

I"m sure it's one of the many (myriad?) things that got fucked over the years with the various patches. I don't think it works in SF2 anymore. Maybe something missing from a dll??? Menrva might know??? Sad, because I liked the 1stGen hangar noises

yes, when each unique one is placed WITHIN that skin sub-folder. Been there, done that! Got the t-shirt!!!

for statics, you've NO idea how hard it is to find a good one!!! And dopey me dosen' t have them all extracted from the pre-lock object cats. Most, but not all

well, something's wrong. I, and others, have been doing it that way since 2003. It's never failed and yes ... [AircraftData] AircraftFullName=F-15A Eagle (3W) AircraftShortName=F-15 AircraftDataFile=F-15A_data.ini LoadoutFile=F-15A_loadout.ini UserList=F-15A_UserList.ini CockpitDataFile=F-15A_cockpit.ini LoadoutImage=F-15A_loadout.TGA HangarScreen=F-15A_hangar.JPG <<<---------THIS LINE LoadingScreen=F-15A_Loading.JPG <<<-------and this line AvionicsDLL=Avionics70.dll AvionicsDataFilename=F-15A_avionics.ini

I"d trust Frenchie with ANYTHING for RCN/RCAF/CF stuff! He's knows his stuff!! -- Did a little personal renaming; with different named lods and renamed skin and then a quick hex edit... for the static version (extended rotors), give me options for the various services. It's very over-mapped; meaning all the parts for the Player Flyable (tm) are used on this. Not a bit deal, as the file sizes are fairly small. I placed 2 at MCAS Kanehoe, and they look really good!! Of course, have to use the "inactiveyear=" switch on the _targets ini, but that's NO big deal (for me!! <gr>) could use a silver Air Force skin, but no big deal! looking good Russ!! Thanks!!

Drop all your graphic setting to as low as possible, turn off mirrors, turn off shadows. It'll look like shit, but it might be playable. Good luck with your treatments!!!

you just name it what you want, place the jpg/bmp INSIDE the aircraft folder, and do a rename in the aircraft's main ini. Remember how the game engine LOOKS for files --- folders, then cats. Folder always takes precedence. You've NEVER ever had to use a whole pathway -- all the back to 2003. Believe me, I know. I cut my teeth making hangar and loading screens in the early 2000s. That's how I got started modding these games Hangar and loading screens are the easiest things to do in this game.

Those of us the know, already know how. but, it would look like this: called it "Suk100" , as we have an Su-100 tank for a long time. This removes ANY possibility of confusing the game engine (which is fucked up enough in places) the destroyed model is a 'best fit'; unfortunately, you'd need to extract the destroyed lod from the object cat, and place it into the terrain folder to make sure it works. Just referencing it, sometimes don't work.

they're a nightmare to build -- the seaplane ramps aren't that hard, just use the large concrete slabs. It's the lack of proper sized hangers (REALLY LARGE) to place nearby. I know, I've tried!!!

Awesome! and they sit levei on the ground?? But I"ll check 'em out for sure!! thanks Russ!!

View File SF2 F-86D Sabre Dog Revamp Pack SF2 F-86D Sarbre Dog Revamp Pack 5/19/2020 "Quarantine Approved - Essential Mods" = For SF2 (Any & All) = This package is designed to replace the original F-86D/L pack available from the folowing URL: https://combatace.com/files/file/10286-sf2-f-86dl-v10/ by suhjake from 2009 It is NOT necessary to have the original mod pack, as this WILL replace it in total. Everything reusable from that pack will be included with this. On a side note, the F-86L "Lima" Sabre will be covered in a a seperate release. Even though the folder is named "F-86D-45" it represents =ALL= production blocks of the Sabre Dog, for those users included in the mod package. The following units are depicted herein: 101st Hikotai (56-68) - JASDF 16th FIS (51-59) - PACAF, Misawa Japan 37th FIS (53-58) - Ethan Allen AFB, VT 97th FIS (51-55) - Wright-Patterson AFB, OH 431st FIS "Red Devils" (55-58) - Wheelus AFB, Lybia 469th FIS (53-58) - McGhee Tyson AFB, TN 520th FIS (54-55) - Geiger Field, Spokane WA 146th FIS Pa ANG (57-60) -they used the F-86L congruently with the F-86D and a USAF Silver (Generic) -a blank skin for other skinners to use. All of the Original Skins have been completely redone, although they remain in bmp format. Several of the orignal decals have been reused, but modified from level 2 to level 0 (tail squadron markings). 26 all new serial and buzz numbers have been created. The 101 Hikotai and the 97th FIS & 431st do NOT use this same pool of numbers. They needed they're own for reasons that will become apparent during game play. The 431st is the ONLY unit in the pack that is listed on the stick squadronlist ini, and is tagged accordingly. Most marking are decals; in some cases wing and squadron marking had to be painted on due to mesh issues (tail). Decal randomization is TRUE for all skins. On the individual number lists, any number marked with a star (*) is 100% correct for that unit. All weapons, pilots, etc are included. A backup copy of the original Data ini is already provided, as the new one has many modifications and adjustments. As always, fairly easy to follow, detailed install instructions are included. So, please read them .... they can be accessed after unzipperizing. Please follow the 'usual instructions' Happy Landing! Wrench Kevin Stein Submitter Wrench Submitted 06/08/2020 Category F-86  

so...the nickname would be Wedgie??? ducks and runs...............................................................................

and they don't show enough of the LW airfields in the 1969 movie to be of any use. (which might be too modern at any rate!)

Yes, it really DOES need a better tile set. Also a better elevation map (HFD). I just wish the game supported the way the Canal actually is, instead of the cheat I had to use. The terrain engine is sooooooooo limited .....

For personal use only, I hope, and not for release. I have a very strict policy about others modding my terrains.

Them's the rules --- THERE MUST BE A READ ME IN THE ZIP SO DOWNLOADERS (END USERS) KNOW WHAT THEY'RE SUPPOSED TO DO. Never assume that said end user knows how to install a mod. Make sure that they do. This is covered in GREAT Detail in the pinned post at the very top of the forum. To all that don't follow these rules, which, btw, ARE site policy, your uploads will be deleted until they comply with our stated policy and standards and practices. Just in case you can't find it, here's a link

definately good for post-war!

it's kinda stupid, but stupid in a funny way. Malkovitch STEALS the show!

Well, when in doubt, you can always consult this guy.... ------- not so much a 'cruise missile', but adding the nuke warhead is just a simple text edit.

The Rocinante doesn't seem to have any issues with it's rail guns. Or missiles. "spurt bombs", maybe? Ala "Footfall" (small nukes for the emission of x-rays/gamma rays) I think the addition of a 'service module' for the weapons bays, while breaking the look of Dragon, might be something to consider

Rule #1: You never fuck with the targets ini Rule#2: You never fuck with the types ini. THIS especially! Unless you're a pro at terraforming, best course is to change nothing. When we build terrains, we do things as historically correct as possible, even to the point of placing specific units in EXACT locations. Although, TK has screwed us over by breaking the 'direct called" units. Doing so makes them go 'stealty' and they won't show on the RWR. Especially TEWS. So, by using the random tags (AAA, SAM_RADAR, SAM_Launcher, EWR) one is left hope the userlist (for SAM/Radar) will keep them associated with their own networked units. The same goes for networked AAA units. The level (amount) of air defense units can be changed on your screen. While I'm sure this may only effect single missions, i'm sure there's a line somewhere in the campaign ini that allows you to change the % level of AD units. Messing with the targets ini is the last thing one should do.

well, somebody's not keeping up with current events ...