Jump to content

Greco

Members
  • Content Count

    25
  • Joined

  • Last visited

About Greco

  • Rank
    Junior Member
  1. Turning on the EOS on the Su-25T (pressing '7' and the 'O') causes a large drop in FPS, making the simulation appear to stutter and jerk. Increasing the zoom from 1X to 8X restores the FPS to normal and motion is fluid once again. Any Su-25T drivers notice this issue, or is this a problem specific to my rig/drivers? Thanks
  2. Dmut...glad to do my tiny bit....you are very welcome.
  3. GGTharos.....Here you go......Six launches from the OSA along with six early detonations. Actually, this track shows a couple of the SAM's climbing more than a few meters above the launcher before detonating. OSA SAM Example.zip
  4. Dusty, Sorry...I meant to say a "FRESH" install of 1.12a (1.0 to 1.1 to 1.12a) was used to create and observe mission.... Greco
  5. Dusty, All missions were set up using 1.12a. All observations (obviously) were made on 1.12a. Missile Effectiveness slider was set at default position of 50% (As an aside, I did the exact same test using version 1.1 to build the mission and observe it and found that the number of waypoints did not affect SAM performance. So, obviously, something was changed in 1.12a to cause this dependancy of SAM behaviour on the number of waypoints.) Cheers, Greco
  6. I posted this reply in the BUGS Section as well................. OK, here's what I found is happening. If I assign just one waypoint to the OSA (for example Waypoint 0), then everything functions fine: the OSA launches and there is no early detonation of the SAM's. If I assign more than one waypoint to the OSA (for example, the FBP assigns two waypoints by default, WAYPOINT 0 and WAYPOINT 1), then the SAM's behave as per my original post: they launch, travel a few meters away from the launcher and detonate. This early detonation of the SAMS happens even if I set the speed to zero between th
  7. OK, here's what I found is happening. If I assign just one waypoint to the OSA (for example Waypoint 0), then everything functions fine: the OSA launches and there is no early detonation of the SAM's. If I assign more than one waypoint to the OSA (for example, the FBP assigns two waypoints by default, WAYPOINT 0 and WAYPOINT 1), then the SAM's behave as per my original post: they launch, travel a few meters away from the launcher and detonate. This early detonation of the SAMS happens even if I set the speed to zero between the waypoints (ie the OSA is stationary)!! Bottom line is this: giv
  8. Dusty....fresh install here...1.0 to 1.1 to 1.12......and I still get the OSA (and TOR and other SAM's) self detonating shortly after launch.
  9. Folks: I set up a mission (with the FBP and 1.12a) having an Su-25T going up against a lone OSA-9A33 SAM unit. Here's the problem: the OSA launches its SAM salvo as one would expect once I get into range, but each one of the six SAM's that gets launched travel a few metres above the launcher and explode (or self detonate) for no reason. None of the launched SAM's ever make it near my plane. I do not turn on ECM or launch any chaff/flares. Repeating this exact same scenario in Version 1.1 had the OSA seemed to work fine during each test run, launching its salvo without the early detona
  10. Folks: I set up a mission (with the FBP and 1.12a) having an Su-25T going up against a lone OSA-9A33 SAM unit. Here's the problem: the OSA launches its SAM salvo as one would expect once I get into range, but each one of the six SAM's that gets launched travel a few metres above the launcher and explode (or self detonate) for no reason. None of the launched SAM's ever make it near my plane. I do not turn on ECM or launch any chaff/flares. Anybody know what's going on here?? Cheers, Greco
  11. Greco

    ATI Bugs

    I'll keep an eye open for this bug. But, so far, I haven't noticed it nor any second-or-two freezes.
  12. Greco

    ATI Bugs

    Thomas: What ATI driver are you using? Maybe the bug is driver specific. I have an x800xt (PCI-e) with the CAT 5.11 and I don't see any graphics bugs during explosions. Cheers, Greco
  13. I was browsing through my Lock On sub directory and noticed it contains a folder named Backup_1.1. Is it safe to delete this file? On another note, in my Lock On folder there is a batch file named "deleteobsoletefiles." What does it do? Thanks P.S. ED, I appreciate all your efforts on the 1.11 patch.
  14. Ironhand, Once again, thanks for your efforts....is there anything about LOMAC you don't know??...... Keep the great info coming, Greco
×
×
  • Create New...