Jump to content

Fubar512

MODERATOR
  • Content count

    8,418
  • Joined

  • Last visited

  • Days Won

    42

Everything posted by Fubar512

  1. RIP Alvin Lee

    http://www.cnn.com/2013/03/06/showbiz/obit-alvin-lee/index.html
  2. I've never noticed any difference in performance or compatibilty between ANSI and Unicode ini-files in SF2. I have noticed that some entries in both object and object_data ini-files are Verrrrrry picky in as far as being case-sensitive. But, even there, not consitantly so.....!
  3. What about good war films in general?

    I just picked up 9th Company on BluRay. It was very good, in fact, amazing in some respects, when one considers that it was done on a 9.5 million dollar budget.
  4. Initialization (ini) files being in Unicode or in ANSI makes absolutely no difference to the SF2 game engine. Just keep in mind that SF2 can read unicode, and SF1 cannot. And an .ini file is not a TXT file. TXT is a separate file format denoting text files. You obviously meant to say "textual". Just don't want to further muddy the waters and confuse any noobs that might be reading this.
  5. Hindenburg Mystery Solved?

    Sorry, but No, this is a recreation based on an eye witness account of what happened. The top of the Hidenburg was apparrently jumping with St. Elmo's fire. That, coupled with a defective hydrogen vent that allowed air to partially fill an outlet duct (thus creating the right lean air-fuel mixture necessary for combustion), is what caused the explosion. The Hindenburg disaster site is less than 20 miles from where I live.
  6. Hindenburg Mystery Solved?

    This was covered in a documentary on the History Channel about a year ago. They even performed an experiment with a scale model of the Hidenburg to determine the likelihood of such a scenario, I cannot recieve streaming video at work (network rules and all that), so I trust that this is the correct youtube video: http://www.youtube.com/watch?v=f7-RDwdTkfc
  7. Unfortunately, there is no provison for that feature in any Third Wire title.
  8. Perhaps that pilot believes that the other two (that are inside the aircraft) do not bathe as regularly as they should....
  9. Another film thread

    Here's a relatively unknown flick, that fits somewhat loosely into the genre, but is certainly worth watching: In Pursuit of Honor. It takes place during the same period as "The Professionals". http://www.imdb.com/title/tt0113399/
  10. That's caused by either a missing, or a corrupt, .tga-file. If that model is using a different afterburner effect, make sure that the effect .ini file and its associated tga file were placed in the effects folder. Refer to the SF2 knowledge base.
  11. I'll download your modified data, and take a look at the values.
  12. 2.67-2.9 kg/s is an R-29 burn rate. R-28 was capable of pushing the Yak-38 to Mach 0.988 at low level, So it was a powerful, and undoubtedly thirsty, powerplant. 15 minutes at 400 kts (a reasonable crusing speed at low altitude) = 100 nm = 185 km absolute range with zero reserve.
  13. That 50 km combat radius in Afghanistan was due to operation from hot, dusty airstrips at high elevations. In sea trials (that were probably conducted just south of the Arctic circle) Forger crews reported a 100 km radius, with just an A2A loadout.
  14. TSFC @ M0 is static fuel consumption at full military power (dry) TSFC @ M1 is fuel consumption in full military power (dry) at Mach 1.0 Both those values can usually be found for most powerplants by performing a google search. And, if it's any consolation, most of ThirdWire's values are close, if not spot on. Dave's explanation of your fuel consumption issues is mostly correct. BTW, the Yak-38 had horribly short legs in real life, and was lucky to have a 100 km combat radius at sea,
  15. I've just recieved a PM from Marcelo, and I'm sending him what I have (so far). So it may soon be available.
  16. Not really....... Windsound Flapsound Gearsound Landingsound AirBrakeSound *CrashSound* BreathingSound Stallsound Do not require separate entries in either 1st or 2nd gen series. * Not relevent to 1st series.
  17. It is stated that Eevee's post comes off as being quite rude, and that is something that we do not tolerate on our site...
  18. That may be the culprit, right there. The model itself is a newer one by Marcfighters (even though it's still 3-4 years old), and he may have changed it somewhat from the version that he released. It's still not perfect, as you can see the "ghost shadow" that I was referring to, in the second image. It's being cast by the right-hand side of the canopy bow, or "arco".
  19. I don't know what else to tell you, my friend, as it works fine for me...
  20. OK, in the Su-27_data.ini, add the following lines under the designated sections (you may have to adjust the coponent numbers to fit your existing sequence): [AircraftData] Component[012]=Hide1 Component[013]=Hide2 Component[014]=Hide3 Component[015]=Hide4 [Hide1] ParentComponentName=Fuselage ModelNodeName=arco DestroyedNodeName= ShowFromCockpit=FALSE HasAeroCoefficients=FALSE [Hide2] ParentComponentName=Fuselage ModelNodeName=Line07 DestroyedNodeName= ShowFromCockpit=FALSE HasAeroCoefficients=FALSE [Hide3] ParentComponentName=Fuselage ModelNodeName=Line08 DestroyedNodeName= ShowFromCockpit=FALSE HasAeroCoefficients=FALSE [Hide4] ParentComponentName=Fuselage ModelNodeName=Line27 DestroyedNodeName= ShowFromCockpit=FALSE HasAeroCoefficients=FALSE In the cockpit.ini: [CockpitSeat001] ModelName=SU-27-cockpit HideExternalNodeName=Canopy Position=0.0000,5.25,1.57 ViewAngles=0.0,-0.0,0.0 The only drawback is that the canopy frame shadows occasionally appear as faint "ghosts", depending on sun angle and the sun's relative position.
  21. Yes. You have to rotate out the canopy bow and the windshield frames. I will post the relevent statements when I get home this evening.
  22. The "smooth deployment" declaration does force any surface to stay open. What's causing your issue, is either improper control surface data tables, or (more likely) the ships data.ini being set to induce a flight deck pitching moment that's more appropriate to sailing into 7-meter waves, than the "flat" seas that the water shader would lead one to expect. That excessive pitch moment is allowing the FM to exceed the AoA or G-force settings of the slats and wing vortices. The fix is simple. Extract the data.ini for the effected ship model, and zero out the value on this declaration: SuspensionConstant=0.0
×

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