Jump to content

Fubar512

MODERATOR
  • Content count

    8,418
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by Fubar512

  1. In the immortal words of John Fogerty "Looks like were in for nasty weather..."
  2. You need a third-party app, such as FRAPS, to record in-game video in the SF series.
  3. If you watch the video, it's plainly obvious that my wingmen robbed me of a kill at least three times, and at one point, my wingman blew a MiG right off my tail.
  4. To get the full plane requires that you buy WoV. There was once a free addon F-4B at ThirdWire's site (it was meant for Strike Fighters), but they seemd to have removed it.
  5. Check this video out (not for 56K). http://forum.combatace.com/index.php?autom...si&img=3337 In it, you will see AI wingmen that engage (and hit their intended targets) , AI enemy aircraft that engage and fire SAHMs (at BVR) and IRMs, and avoid missiles, SAMs that track and engage you, etc. Perhaps I have that one in a million install....or (more likely), I have everything properly configured. Every time someone shows you how you might fix an issue, all you do is whine and pule that you cannot get it to work, it should have been incorporated in the initial release, or worse, reply with a sarcastic remark.
  6. Dogfight '87

    Wow, AI wingmen that engage, AI enemy aircraft that engage and avoid missiles, BVR missile shots, SAMs, etc. Perhaps I have that one in a million install....or (more likely), I have everything properly configured.
  7. Too bad the "damagedenginesoundname" parameter shares one thing in common with the "bombrelease" sound....neither of them have worked since day one.
  8. Eagle in the storm

  9. Here's a string of images showing a little project that I've been playing with. I took a satellite image of a Stratoculumus cloud layer, and set it in place of the default Thirdwire top cloud layer bitmaps. The model is the default '21MF with a skin that I released two years or so ago, utilizing Volksjagger's '21PFM panels by pasting them over the stock Soviet Silver texture set (and performing a few necessary edits).
  10. I beg to differ with you, but your 'SovietSilver2" is clearly based on work that I released, and you did not even extend me the courtesy of asking my permission, nor did you ask the same of Volksjagger, who's name I mentioned in the original readme.
  11. That's right Sukhoi=Su Mikoyan-Gurevich=MiG Tupolev=Tu Mil=Mi however, there is a bit of an exception: Yakovlev=Yak, insted of "Ya". I guess they thought that "Ya" would be too Rastafarian sounding, as in "I fly a Ya, mon!"
  12. The Su-27 (the 'u' is never captilized, as in 'Tu', 'Mi', etc.), is available at Marcelo's site, "Marcfighters": http://marcfighters.combatace.com/
  13. The following line needs to added to the data.ini of the (AI) aircraft you'd like to equip with an RWR, under the "Detect System" section: HasRWR=True To equip the aircraft with a player usable RWR system (aural only), involves modifying the avionics.ini file, something that's already been covered in detail by both Wrench & Myself.
  14. Better get 'er right, Zur...the "Osprey" is watching.....
  15. Nick, The issue you're experiencing can be rectified to a degree. Check PMs, I've sent you something to try out,
  16. Any 3rd party Crater.lod and Crater.tga files should reside in the Flight folder. The crater type association is called out in the Missileobject.ini. As to what file specifically determines the crater's .ini parameters, I suggest that you start perusing the various cat files, though I suspect that it may be hard coded.
  17. Flak in WOV

    http://forum.combatace.com/index.php?autom...si&img=2933
  18. There are updates more recent than that release. The latest weapons editor was updated and released in June of 2006 to work in conjunction with SP4, and may not work on earlier versions. Update your install to SP4: http://www.thirdwire.com/downloads_sfp1.htm
  19. Is C5 going the way of CA?

    Why, Indeed?
  20. Help for SFP1

    I'll bet that you have a corrupt weapondata.dat file (which is what the game actually "reads", not the weapondata.ini). First, make sure that you have a copy of the latest weapon editor. Then, go to the Objects/Weapons folder, find the weapondata.dat file, and delete it. Next, using the weapon editor, open your existing weapondata.ini (likewise located in the Objects/Weapons folder), and simply hit the save button on the weapon editor. This will generate a new weapondata.dat. and should resolve your problem.
  21. Again, that's something that's out of the qusetion with the present game engine.
×

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