Jump to content

FastCargo

+ADMINISTRATOR
  • Posts

    8,142
  • Joined

  • Last visited

  • Days Won

    16

Everything posted by FastCargo

  1. Okay, everyone stop right now. Iranianace, You need to stop what you are doing and start over. First, start here: http://combatace.com/forum/168-new-to-thirdwire-sims-sf-series-wov-woe-woi-first-eagles/ Specifically, here: http://combatace.com/topic/26293-basic-directory-structure-of-a-generation-1-thirdwire-sim/ You need to read ALL of this...because it explains what you should see and how you should see it. I'm temporarily closing this thread so I can write a more appropriate response. FC
  2. Piecemeal, what is F-15APit.LOD? If it's from any of the TW sims...pull it. FC
  3. Congrats! FC
  4. You have to make sure the aircraft have those animations in the first place. If they don't have them hardcoded in the LOD, you aren't going to be able to assign any. FC
  5. Not the first time this was noticed...included fixes to avoid nose/tail conflicts: http://combatace.com/topic/21978-weaponspack-oddities/page__view__findpost__p__97287 FC
  6. I suspect the weaponspack you downloaded is an outdated one. I would recommend starting with a clean SFP1 install, then downloading and installing a weapons pack dated Oct 2008 or later (and not any SF2 weapons pack). FC PS In fact, try this one: http://combatace.com/files/file/7791-weapons-pack-252-by-the-wosfp1-community/
  7. What are you talking about...you can post screenshots as just attachments or in the gallery. BUT, they should be in JPG format. FC
  8. If I remember correctly, the fuels are all done in kilos... FC
  9. Knowledge base section on adding weapons. Some of the data is slightly out of date, but most (including working with the weapondata.ini/dat files and the weapon editor) is still relevant. http://combatace.com/forum/189-adding-weapons/ A post getting into more detail on how the sim selects weapon racks. http://combatace.com/topic/52372-sf2e-wont-load-gbu-39b-or-gbu-40s-on-to-bru-61-racks/page__view__findpost__p__382415 In simple terms, an ini file is simply nothing more than a bunch of parameters. If you think logically, an ini file is very easy to read (well except for the FM parts), and it's very easy to figure out why something may or may not work. For weapon stations, note that some aircraft have parameters such as LoadLimit, DiameterLimit, LengthLimit. Note that for individual weapons (including racks) there are parameters for things like Mass, Diameter, Length. Note the similarities? So, thinking logically, it must mean that unless a weapon parameters (along with things like year of use, AttachmentType, WeaponClass) falls within the restrictions of the WeaponStation, that the weapon will not be selectable in the loadout screen (unless 'forced' using the aircrafts loadout.ini). FC
  10. If you can post here, you have all the skills already. Also, just find an example of a weapon with an ini file built. As from the stock AA-2.ini: That's it. FC
  11. If there is just one weapon LOD file, then the method you described will work (LODs and BMPs directly in the Weapons directory). However, if there are multiple LODs, then you will have to build a custom specific weapon.ini file that references the various LODs at various distances. Better yet, if you patched up to the Oct-08 level, then make a specific subdirectory for that weapon, put your custom weapon.ini, LODs and BMPs in the directory, and make your entry in the weapondata.ini and dat files in the Weapons directory. FC
  12. As far as why a particular rack did or did not exist at the time, that's something only the original modders can answer. Maybe they just didn't feel like making it. And since one of them is dead now, a great friend of the community who passed away unexpectedly, it's kind of hard to ask him. Deal with it. Now as far as why a particular rack is or is not used, remember that using a rack still has the same kind of limitations a weapon station can impart on it (diameter, mass, length, Attachment Type, Allowed Weapon Class etc). In addition, and this unfortunately is hard coded into the engine, the racks are searched for alphabetically (in SF2) or in the order they are listed in the weapondata.ini/dat. Which means the first time a rack meets all the qualifications, that is the rack that will be used, no matter if it's the right rack or not. In the Gen 1 sim, this was an easy (though somewhat tedious) fix. I grouped the racks by Attachment Type, then Allowed Weapon Class. Then, within those groups, I sorted the racks from smaller to bigger with very tight limits as to what it could carry. This way, say a twin Stinger rack may carry Stingers, but couldn't carry a Sidewinder, but unless you did a sort the way I described, you would see Stingers carried by twin Sidewinder racks...ridiculous looking at best. Anyway, after all this sorting in the weapondata.ini, I renumbered all the entries, then Saved. Works like a champ. And this can still be done for SF2, but you will have to build a custom weapondata.ini and weapondata.dat file...which sort of negates the ease of adding weapons in SF2 that didn't exist in SF1. Or you can just specify the RackType in the particular aircraft's loadout. FC
  13. There are a couple of ways to fix this: One, make a new weapon station that can only carry 2IR racks, and adjust it's position that way in the new weapon stations (making sure to delete the 2IR reference in the older stations) Two, if the 2IR rack is simply sitting too high or too low, adjust it's diameter in the weapondata.ini and save per normal. FC
  14. Well, you can still play it in high res now and on modern machines, it runs really smoooth... http://combatace.com/topic/20530-still-looking-for-strike-eagle-sim/page__st__15__p__89860#entry89860 FC
  15. Yea, that would be the understatement of the century... FC
  16. I noticed a big difference as well when I became a reservist, some crazy rules that take a little while to figure out. Loved it though, much better than active duty because you have much tighter control over your life. However, since I officially retired 17 days ago, I haven't noticed any more time available...seems like I'm just as busy as ever! FC
  17. Actually, none. I remembered incorrectly from when I did all the work on the F-15C cockpit improvements. There isn't a way to put the rounds remaining counter in the HUD. FC
  18. Note what you see in the RWR entry of any avionics.ini file of an aircraft that has an RWR: There are only 2 sounds, track and lock. There are no further sounds from the RWR to distinguish what type of weapon is being employed. FC
  19. Sure...just don't note the NodeName in the Weapon Station. FC
  20. 3 ways to do it: Avionics60, cockpit LOD has drum counters like older car odometers. Avionics70, cockpit LOD has digital counters. Avionics70, projected onto HUD. Only the third method allows you to set up something not set aside in the cockpit LOD. FC
  21. Not a fighter pilot, but done enough high speed low levels to make some observations. That depends on a ton of factors. Contrast (edge effects, coloration, silhouette, etc) ,line of sight movement, environmental (including things like atmospheric haze, sun position, shadows, ridgeline, etc), target study, scan pattern, time dedicated to scan, etc. Example: You're in a Hog, 5000 feet, 300 knots, sun behind you, looking for a green tank on a light tan background on a clear and a billion day and the tank is moving across your field of vision. You'll probably see it (admittedly, as a dot with a dirt plume) for tens of miles. On the other hand, now try this with the sun in front of you, hazy day, a tan tank on a light tan background (ie the desert), while he's not moving, and you're in a F-16 at 500 feet doing 480 knots. You'll be lucky if you see it outside of 2 miles. FC
  22. The answer is, why would you want to. Modern hex editors are fast, easy to use, and light programs. There is NO advantage in using Wordpad or Notepad...and in fact, it is MORE dangerous to use them vs a free hex editor. You have a file open in Notepad, Wordpad, and a modern hex editor. If you make NO changes at all to the file you are looking at, and you hit the SAVE button by accident, in Notepad or Wordpad, you have just destroyed that LOD file. In a modern hex editor, no changes have been made to the LOD. In addition, if later on you want to alter a LOD to use a different texture, you can do that in a modern hex editor. You cannot do that in Notepad or Wordpad. Do yourself a favor, download and use a modern hex editor instead of Notepad or Wordpad. It will pay off in the long run. FC
  23. Yes, the internal structure is exactly the same. I'm not on my laptop, so I can't tell you exactly how I laid it out, but it's pretty easy if I remember correctly. FC
  24. As far as I know, it should be possible. My mods are not in the Saved Games folder, I use a custom folder. Haven't tried it on a separate drive yet. FC
×
×
  • Create New...

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