Jump to content

Wrench

ADMINISTRATOR
  • Content count

    27,022
  • Joined

  • Last visited

  • Days Won

    134

Everything posted by Wrench

  1. sorry, I don't recognize them, although I'e had the rear gunner for years. btw, here's the statement for the manual animated canopy: [Canopy] SystemType=ANIMATION InputName=ANIMATION_10 AnimationTime=3.0 AnimationID=5 replace the other statements with that watch out for the shadows ... it's OK (sorta) until you open the bombbay, then you get the MASSIVE tractorbeam line. Looks like a glitched mesh in the bay doors. wrench kevin stein
  2. Create a new folder on C/ Call it "Cat Extractor". Put all of Gerwin's stuff in there. Copy/paste the cat to be extracted INTO the folder. Drag/drop the cat OVER the CatPack.exe all the files in the cat will be extracted to a sub-folder inside with the cat's name. Then, just delete the cat, since the original is safe in the /ThirdWire folders. just like it says in the included readme. btw, the F-4D stuff is in ObjectData003.cat, for a full-4 merged install wrench kevin stein
  3. can ONLY be done with the original MAX files. However.... there is a way to cheat that ... look at my F-79 Manta, and the HP Perigrine flying wing fighters. 2 (or 4 on the Peregrine) seperate pylons, added as 'fake pilot' seats. The fun part is dailing in their locations, and weapons mounting The downside is, they're permanant fixtures. wrench kevin stein
  4. the tail wheel could come up just a hair, but it's not worth messing with. But the mains a close ... looks like they're underinflated a bit, and have a good deal of weight on them. Again, fiddling with 3rd decimal places get tire-some!! (pun intended!!! ) wrench kevin stein
  5. This is your problem: Program Files/Strategy First/Strike Fighters/Objects/Aircraft put it in the ROOT of C/ C:/StrategyFirst/StrikeFighters 7 don't let you change thing in either the ProgramFiles folders (found this out the hard way, EVEN with admin priviliges) move it OUT, like in my screenie Also, WW2 installs, or ANY at 06 patch level WILL CRASH unless you comment OUT the shader lines in the various terrain's data inis. This is the same issue we had with Vista and the shaders. ONLY the 08 patch levels have working shaders in Vista/Win7. wrench kevin stein
  6. you mean an uncontrolled ROLL to the left. That's completly different than 'torque steer'!! I've never flown HARD, so I don't experience it. Maybe checking the values =and WHICH ones I haven't a clue!!!= for the wing's, ailerons, lift statements?? Check for extra spaces, negative values that should be positive (YMac?), etc EDIT-- left and right YMac valuse are the same; one should be positive, one negative. Check the PropHead Forum, 1stGen; I made a note about it in the "Tweeks and Tricks" section (meaning: I can't remember which is supposed to be which!) wrench kevin stein
  7. screenshot might help!! Please!!! is this the bug where the cockpit is BELOW the aircraft/pilot sightline and then JUMPS up into proper position after takeoff?? wrench kevin stein
  8. THAT would have been my next suggestion ... a ship=load of these old aircraft DON'T have the MaxDecalLod= statement, and it needs to be added. wrench kevin stein
  9. check the engine torque value...(ThrustPosition) Oddly, the left/right number IS set to 0.0, so it shouldn't "pull" ???? ??? Unless the left/right sides of the LOD are perfectly matched?? also, try these for RollingRadius: [TailGear] RollingRadius=0.17 [LeftMainGear] RollingRadius=0.55 [RightMainGear] RollingRadius=0.55 EVERY aircraft brought over to NextGens (and sometimes to 08 levels) needs them adjusted wrench kevin stein
  10. GREAT shot of the landing light positioning!!! (yah, you all know I love adding them!) wrench kevin stein
  11. welllll....if he DOES give us Iran/Irag, I guess I can stop work on revamping the old map, huh?? The IsraelME tileset would be very good for that terrain wrench kevin stein
  12. simple ini edits, and copy/paste can create the -25 variant (how do you think I created the F and M???) My FM that I created is, at best, a hack job. Mostly all I did was make 1 elevator and 2 rudders. wrench kevin stein
  13. my Spanish is VERY limited, but you covered the basics! The only thing missing is the renaming of the skin bitmap, and the hex editing of the LOD, and "saving as..." to create a new pilot . Let's say you've repainted the HGU-26AW (the plane white helmet) to how you like it. Now, it's important to SAVE that skin bmp with a unique name, that is a MAXIMUM 8 digits long (not counting the extension -> .bmp) For exampling, we'll call the pilot Wrench01 (note the length - 8 digits). The number MUST be exacly the same as the original skin's name length -this is VERY critical!!! If the name you choose has less than the exact number, you can fill the empty spots with 0 or the dash (-). That's why I used the 01, to fill the length. So, you have a newly repainted and renamed skin bmp, you've chosen a LOD to edit, and have an ini to edit. The ini is the easiset and simplest ... most pilots use 2 lods, as you can see below (again, the HGU-26AW) [LOD001] Filename=HGU26AW.lod Distance=40 [LOD002] Filename=HGU26AW_lod002.lod Distance=200 So, we edit the names of the lods we're going to use in the HGU-26AW.ini... [LOD001] Filename=Wrench01.lod Distance=40 [LOD002] Filename=Wrench01_lod002.lod Distance=200 Now, do a "save as..." on the ini to match the name: Wrench01.ini And now, that's taken care of. The fun part begins now ... the hex editing. I use XVI32; it's freeware and pretty easy to use. As the existing pilot lods are NOT in unicode, it works fine (it'll also open unicode lods,if you tell it to) So, with XVI32 installed, and it's properties set (ie: open LOD with this program), double click on the HGU-26AW.lod. You'll see something like the image below (but that's a later shot). Open the SEARCH tab, and FIND... you'll have a blank space, and type bmp into it. Make sure "Text String" is checked. Then, "OK". You'll find there are 3 instances of 'bmp' in BOTH lods (LOD and _lod002.lod) and you'll need to change all of them to match the NEW skin bmps name. After changing the all the bmp names, you'll have to "SAVE AS..." the lod, with your new name. And that's pretty much it. Getting your new pilot in game, is exactly as desriped by Sony above. You'll also find more information at my site .. follow the link below in my signature; there's 2 pages of pilot figures there. wrench kevin stein
  14. That IS Hysterical!!!! One of the funniest, most honest things I've ever read on any board, EVER!! Eric, I'll be glad to share my template, if you want to get the rivets/panel/fabric lines on rudder of the AeroNaval version. Just say the word! So, it's as simple as increasing the MaxSteeringAngle ????? I been fighting with that for 3 years!!! If that's all it needs, and many more aircraft have the same symptioms -- we can start moving the WW2 stuff over to SF2 now (given that every single aircraft, regardless of WHO made it, needs new FMs....but, it's a START!!) wrench kevin stein
  15. revamped for SF2, both skins (only 830 Suez shown here) ... just need to check with my KAW teammates (expecailly Dels) on an early release of the Skyraider cockpit. wrench kevin stein
  16. well, they WILL show up on the ramp, as game-generated statics. I'd think it'd be WAY cool to see more civie stuff, even if only parked. wrench kevin stein
  17. why not just repaint a pre-exsiting one? We've plenty of modern western pilot skins ... the hardest part is the internal hex editing of the PilotXXX.lod to rename the bmp to match your 'new' skin. I'd reccomend any of Old Diego's skins, as they're fairly large, and easy to work with. there's a tutorial I wrote a looooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooooong time ago on creating new pilots; it may have disappeared in one or another of the upgrades; if you need help, shout out. The hex editing, literally, only takes a few seconds wrench kevin stein
  18. at Geo's website, http://www.geos-aircraft.com/ you'll probably want to pick up the rest of the WW2 items you'll be needing, from there too. I thought I'd put his URL in all my WW2 terrain mods readmes ...???? Mayhap, I'd forgotten it on 1 or 2... wrench kevin stein
  19. is it just my perverted old mind, or did Lexx's explaniation sound just a little dirty???? "reduce your emission rate". note self ... cut down on p0rn!! wrench kevin stein
  20. where are you putting them?? EDIT: this link might help a little (I hopes!!) http://combatace.com/topic/44026-converting-older-planes-to-work-in-sf2-a-basic-guide-by-migbuster/ wrench kevin stein
  21. for the Son-9s, Ed?? or ??? or just 'generic' EWRs?? I like it though!! wrench kevin stein
  22. well, I don't know much about MAX, so can't answer the 'walking' thing, but it would use the 'vheicle dust emmitter', like tanks or trucks. thinking about surface-to-surface reflex rockets for the Gerwalk tank-Vals, maybe a laser guided (ala TOW), with a low percentage hit probability (50%???) I do remember seeing some kind of MLRS used in some sequecnes, early and late in the series. One could even make Z battlecruisers as carriers, cargo ships, etc, and place them in/on the terrains like they landed there. Lot's of possibilities!! wrench kevin stein
  23. Actually, we DON'T have enough of "proper" EW-Radars for the SAMs we have; we're missing Long Track for one, and a bunch of others that are associated (ie: newtworked) with various Search/Track/etc SAM radars. Pity the game can't/dosen't handle the 'hand-off' from long range search to tracking to targeting to etc. wrench kevin stein
  24. next on the list is Russo's Lightning Mk.6 ... although I may have to do a 'nationalized' Saudi version, cause of the above-wing Matra pods. Still need to figure out a underwing pylon for the Saudi variant... wrench kevin stein
  25. 1) extract ALL data inis for ALL ground objects from the Objects.cat, place in EACH of their respecive GroundObject folder; 2) removed whatever effect is called for in the DestroyedEffect= line (ie: after the = sign, leave it blank) example: from Zil-157 truck... [GroundObjectData] DamagedModel= DestroyedModel=Truck_destroyed.LOD DestroyedEffect= <--note removed effect callout EmptyMass=8900.00 Component[001]=Chassis Component[002]=Turret 3) extract all _Types.inis from ALL terrains, leave in EACH terrain folder; for add on Terrains, they'll be in the terrain folder already 4) find all callouts for ground vehicles in _Types inis, erase the DestroyedEffect= called for, and ALL effects called for in SecondaryEffect=; conversley, you can can change SecondaryEffect= to 0 (zero) Example: the generic AAA callout in all _Types.ini: [TargetType059] Name=AAA FullName=AAA TargetType=AAA UseGroundObject=TRUE ActiveYear=0 TargetValue=50 RepairRate=3.22 StartDetectChance=50 StartIdentifiedChance=10 IncreaseDetectChanceKey=10 MaxVisibleDist=8000.0 DestroyedEffect=SmallRocketGroundExplosion <--remove or change SecondaryEffect=VehicleFireEffect <--remove SecondaryChance=100 <-- set to 0 that should make for a nice, clean, higher-frame rate mission, albeit a bit boring without all the nice burning Bad Guy ™ targets. wrench kevin stein
×

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