Jump to content

Wrench

ADMINISTRATOR
  • Content count

    26,943
  • Joined

  • Last visited

  • Days Won

    133

Everything posted by Wrench

  1. not at the same time, obviously.
  2. like I said, upload into the Utilities section; just like any other mod. zip it up, and upload it with a explination in the Announcment post
  3. and.. just as important, the relevant & matching ***.tga is in the terrain's folder
  4. wouldn't it be smarter to simply upload to the Utilities & Editors section of our SF2 downloads? Threads on forums tend to get lost and buried quite easily just saying...
  5. the CM dispensers are NOT weapons, and therefore do NOT require entries in the /Weapon section of the data ini, and definately don't need a "new" weapon for the /Weapons folder. They are SYSTEMS. they're system names would go in the Fuselage or Tail section (depending on their eject location. Then you, just have the statements for the CM dispensers. Below, from the stock 3W B-52D as an example: ==dispenser as located on model - [LeftWing] ParentComponentName=Fuselage ModelNodeName=Wing_L DestroyedNodeName=D1_Wing_L == -MAJOR SNIPPAGE- == HasVortexEmitter=FALSE SystemName[001]=LeftFlapInboard SystemName[002]=LeftWingFuelCell SystemName[003]=Engine2 SystemName[004]=Decoy1 == decoy dispenser statement -- (usually listed below the weapons station, along with any internal jammers) [Decoy1] SystemType=DECOY_DISPENSER EjectPosition=-11.78,-3.74,-0.04 EjectVelocity=-5.00,0.00,-10.00 NumChaff=120 NumFlare=30 Best examples, extract and study the data inis from the B-52D, A-6A, EA-6B, F-4J, and so forth
  6. JG52, eastern front. Staffel markings also are color coded (the numbers II/JG52 would have differing number colors from III/JG52, as well as Stab (think of that as the HQ flight) with the varying chevrons, lines, circles, dots, etc. LW markings is a whole seperate level of expertise; and there's a plethora of info availalbe. You just gotta dig deep ------------ required screenie: Sunset, and off to work
  7. insky it's not carried here, because it's a pirated model. be warned - people have reported many issue (viri, etc) when trying to download from there. People shouldn't be making mods for things that can't be had. Bazillius, looking at you
  8. Mue's lod viewer. Mind you, 99.9% of all that work has already been done by your's truly, on various terrains. Even some cheats for multiple stacks
  9. yes, one must edit BOTH the aircraft's data ini AND loadout ini. As long as you remain within the allowed 6 groups, you can have as many stations as you like. Of course, mounting positions WILL differ yes, you can have a 7th station, if you want something permantently loaded. Can't remember what plane we used it on, but it did work iirc.
  10. indeed, sounds like something's very broken; like not all the pieces are there. delete the mods folder completly. Don't save anything. create a new, clean, untouched SF2V mods folder. Start the game and see if all the "usual suspects" show up; all the player flyables, the maps, etc. DO NOT ADD ANYTHING!!! Now the important question: where did you get the game from?
  11. both versions are here: what you want to use, is the later version, the "WoE TE". Has slightly better functionality
  12. one of the reasons that learning and using, even with it's flaws and (sometimes) difficulty in use, is the stock 3W terrain editor. Not only allows the quick and easy addition of new tiles, but automatically generates the necessary TFD, HFD and _data inis. Then, it's a simple matter to copy/paste the newly added tiles statements to the data ini, and TFD & HFDs into the terrain under construction. BE ADVISED: back up the original _data. ini, and the TFD and HFD before doing anything!! There's no automatic save in the TE or the TFD tool. You make a mistake, you eat it. I find the TFD tool less than useful for creating and modifying full terrains. Oh, its good for viewing, and maybe carving a river valley through a mountain, but overall ... to the questions: not all terraformers included all the tile necessary for their terrains, especially the very early 1stGen versions. That's because they reference them from one of the main terrain cats. (one of the reasons I include ALL tiles in ALL my terrains. Then you only have to worry about terrain objects. Also referenced from "main cats") all tiles from all the 3W games are in bmp and tga formats (we won't discuss the format changes right now), and are stored within the varying terrain cat files (ie: wwiverdun.cat). You will one of the cat extractors, and just pull everything out of the cat. Store it someplace (relatively safe) You will need the data ini, as you need that to add the new tiles too. Unfortunately, you'll also need the textruelist.ini for the terrain you're working on. Odds are, there won't be one. Which means you need to create one using that function in the TE, and following the numeric listing from the data ini. If you're trying to make a "swampy" or party flooded region, with patchy water or patchy dry land, you'll have to make tga's for those. The best example, visually, are those I created for the Everglades on the Cuba OTC map. So, more questions, ask and I'll try to answer.
  13. 1) locate x/y/z position of top of smoke stack 2) open _types ini, locate or add factory to be smoking 3) add statements to create effect type and location of smoke discharge example below: stock 3W Generator building
  14. maybe you guys should delete some of the p0rn??? (that's what I had to do, even with a 1TB drive)
  15. probably not the best idea. the core files must be installed to the comps HD
  16. ABSOLUTELY!!! those cockpits are the bomb!!
  17. This pack contains new data ini for Wolf257's ETO used Mustang Family. It includes both RAF and USAAF versions. I've included his P-51D-30, simply for historical reason. If anyone feels the need, I'll be happy to upload the ENTIRE set of Wolf's Pony; they are and should be still available in the SF/Wo* WW2 Aircraft/Allied Fighters downloads section Aircraft are: Allison Powered -- Mustang I Mustang IA ** (**please note, while equipped with 4 20mm cannon, there are NO barrels extending from the wings. If a 3d guy wants to build them, I'll attach them via fake pilot) Merlin Powered: P-51B/C (standard canopy) P-51B/C (Malcom Hood) Mustang III (Malcom Hood) P-51D-30 (bubble top) AvHistory Allison and Merlin sounds are included. FM for the B/C/D are based off the 3W P-51D from the Expansion Pack. While not perfect, they are better than they were. eto_ww2_wolf_mustangs.7z
  18. While, eventually, each aircraft package WILL be getting the newer inis (hit box adjustment, armor upgrades, loadout adjustments, etc), this thread will be storing them for now
  19. This is for 2 of Wolf257's P-38 Lightnings, again for ETO usage P-38H P-38J a reminder, these are exceedingly OLD models (dated 2004); they have a number of flaws, like no moving surfaces, mapping issues and various other things. But, until if and when (also not likely) we get new Lightning variants, these are what we have. Finally added are the long missing outer wing fuel tanks. eto_ww2_wolf_lightnings.7z
  20. no, the "core files" must be installed to the C drive
  21. This pack is for the RAF heavy bombers Halifax B2 Halifax B3 Lancaster Mk.1 Stirling Mk.1 Hudson Mk.1 please note, I've given the Lanc an "ASV" style radar, but I"m not positive the mk.1 had it, as there's no ASV scanner on the lower fuselage. to remove it, you'll have to remove the radar statements from the avionics ini (which has the Crusader bomb sight mod -- so don't remove that section!!). As I got dumb and forgot to create a backup copy. You may wish to backup the original avionics ini, if you're so inclined. I've also included my Lanc "Box Art" hangar and loading screens; didn't remember if the original upload had these. The Hudson could use some new skins, as I'm not sure the colors are correct. When I get around to the PTO RAAF version, I plan on redoing the skin, and making proper, historical serial numbers. But for now... <gr> ww2_v2k_raf_heavies_tweeks.7z
  22. the model looks pretty good! Keep going!
  23. This set is for MontyCZ's Avia S-99 (Bf-109G), and the 3 WW2 variants we have been using it for.. Bf-109F4 Bf-109G6-AS Bf-109G10 I do not remember if there have been any FM improvements. You'll have to test fly for yourselves (If there are other made from Monty's S-99.lod, please PM me with a link, and I'll give them a go.) These data ini adjustments can also be used on the Czech (real) S-99 as well. I have the S-199 'Mule' for CzAF and Israeli use done, too. Just not sure where to upload them ww2_eto_mcz_109_series.7z
×

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..