Greco

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

Dmut...glad to do my tiny bit....you are very welcome.

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

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

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

All my observations are with 1.12a.....

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 the waypoints (ie the OSA is stationary)!! Bottom line is this: give your OSA only one waypoint and it'll function properly. Expect wierd behaviour if you assign more than one waypoint to your OSA.

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: give your OSA only one waypoint and it'll function properly. Expect wierd behaviour if you assign your OSA more than one waypoint.

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.

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 detonation. Anybody know what's going on in with the OSA in 1.12a?? Cheers, Greco

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

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

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

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.

Ironhand, Once again, thanks for your efforts....is there anything about LOMAC you don't know??...... Keep the great info coming, Greco

Thanks for this EXCELLENT intro to the Su-25T.

Thanks for your prompt reply. No, I don't speak or write Russian....but a lot of the letters do look very similar to Greek....so I guess I can fake it. Cheers, Greco

The user's manual doesn't explain how to read the Su-25T fuel gauge. What do the Roman numerals I and II signify? How can I tell if my fuel pods are empty? How can I tell if my fuel tanks are full, half-full, etc., etc... Thanks for your help, Greco

BBQ....You need to set VISIB RANGE in the GRAPHICS options to MED or HIGH. I get the exact same graphical anomalies as you if I set VISIB RANGE to LOW. Hope this help you, Greco P.S. I am using the Cat 5.4 drivers. I saw the graphical glitches that you posted using the Cat 5.1 and Cat 4.12 drivers. Solution always was to set VISIB RANGE to MED or HIGH.

Toronto, Ontario CANADA....eh

Folks: I mostly play FPS and Flight Sims. I am looking for a 19" LCD to replace my (aging) CRT. Any suggestions? What about the Dell Ultrasharp 1905FP?? Thanks.... P.S. My hardcore FPS gaming buddies are begging me to stay away from LCD's. They say to stick with CRT's.

Thanks to all for your replies. My mistake for thinking that I had to destroy all enemy units for the mission to be a success. (I suppose I am playing way too many FPS games where you shoot everything in sight.) Fly in...destroy what you can at a safe distance...and then get out of dodge. Cheers, Greco

Guys: I'm enjoying the demo quite a bit. I was wandering if there was any way to (automatically) target the AAA and SAM units in the demo A-10 mission. Ideally, I'd like to take these units out with the Mavericks from a distance. What happens is that I end up destroying the wrong units with the Mav's, and then get so close for a rocket/bomb kill that the AAA and SAMs chew me (and my wingman) to bits. (Just curious....in a real world situation would A-10 drivers risk going after a column of tanks/trucks that is supported by AAA and SAM units???? That's looking for trouble if you ask me.) Thanks, Greco

Thanks for the reply Dmut.....but I have to ask you: where in the documentation does it say that ALT-HOLD and joystick-wheel trimming is not implemented in the Su-25?

Folks: I just flew the Su-25 in the 1.1 Demo, and I encountered a couple of problems: 1) I could not enable the ALT-HOLD command. Pressing the "H" key did nothing 2) I also could not trim the Su-25 using my X-45 rotary wheels. All the joystick mappings are correct in the options screen. I can only trim using the keyboard. Note: the ALT-HOLD and joystick trim works fine for the A-10 in the 1.1 Demo Has anyone else encountered these problems? Cheers, Greco