Spetz

I've got an AMD HD 7950 3 Gb coupled with a 3930k processor. Everything maxed and using sweetfx I get over 60 FPS On the ground, never drop below 35 in the air and haven't noticed any FPS hits using rockets. So far combination has been better than anything I have had before, including nVidia cards.

Serial #16762 Vancouver Island, Canada

So did I. To the nearest cover anyway.

Looks good. Thanks!

Pack where you spawn at and all will be fine.

Reading "A10's over Kosovo", seems a lot of the time they would carry only 4 x Mk 82's, full cannon. That's about it.

Easy versus sim settings?

Air brakes deployed? IFAIK PAC doesn't work when deployed. Just wondering...

Looks good..this combined with multiplayer stability and we might see a return of LOCERF or the like..

Well, if altitudes are not dependent on pressure levels, how does one set a ALTITUDE HIGHER THAN 3045(m) and have it trigger on the altitude displayed on you HUD? From every test I've done, it triggers it on the altitude displayed in the F2 view, not the HUD, which can be several 100 feet different? Mission attached.. Altitude triggers are at STPT 1 and 2. EDIT*** Figured it out. Mission editor uses 29.92 Hg for all altitudes on the triggers. Just have to set 29.92 after take-off to reach same altitude as what I set the ME to. Not the most realistic I guess, but works. Don't know why it didn't work before..

Think I figured it out. When you are on the airfield, ATC gives you QFE, which is different at each airfield. You set that into your altimeter (shoudl read Zero height) and take-off. Once you are airborne, that QFE is useless, you have to redo your altimeter to the pressure levels in the area, which unless you have an ATIS report for everywhere you are flying, it's impossibe to get. Once above 18,000 feet, you set it to 29.92..all is good.. But is seems the ME takes into effect all the differing pressure areas. You can test this out easily. In the A10, level out and use ALT/BRG hold at 5000 indicated on the HUD. Your altimeter should read the same despite whatever setting you have. Switch to F2, and you can see you actual height MSL, which can vary by hundreds of feet. By moving your altimeter knob up and down you can level out the F2 altitude and the indicated altitude. Once they read the same, that is the altimeter setting for that exact spot.. My issue was that STPT 1 was only 4nm from the airfield, so the QFE worked just fine on that trigger zone because it was so close. But once I fly to STPT 2 and 5000 feet higher, the altimeter was way off, even using 29.92 at 10,000 feet was several hundred feet difference, almost 800 IIRC. So basically, unless you can get an accurate reading and equal reading, it is rather hard to make a higher than / lower than trigger, especially using dynamic weather.. Anyway, this is what I'm thinking... Sounds right to me..

In installed beta 6 last night and after an hour of flying I had no flickers or anything on my HD 7950.. Much better than the last 12.? driver..

That second one sounds like a blast. That's for posting!

I've been trying to get a trigger working for mission but its giving me grief. I want a trigger based on an altitude of anything higher than 3045 meters ( roughly 10,000 feet). I have it working at 5000 feet but it will not work at the higher level. This is what I have.. ONCE > UNITS ALTITUDE HIGHER THAN (test pilot,3045) > MESSAGE TO ALL .......... UNIT INSIDE ZONE (test pilot, Mvr message) It's the exact same at the lower altitude except the altitude obviously and a different zone, and it works. Does pressure altitude come into effect with this type of trigger? I've set it to 29.82 as ATC directed on the ground. I did notice when I air start its set at 29.92, 200 foot difference. All other triggers in the mission work fine. No trigger zones are touching each other to be safe. Any ideas? Oops, wrong area..can a mod move this for me. Thanks

As well, switching to manual mode often helps. Sometimes you can be all lined up with no launch authorization. Go manual and fire, very easy

Place into the Missions folder and they will be available in game.

Doubt it. It was never added in FC 1/2 so probably won't be added in FC3. I made the toes on my Saitek rudders into bands and then set the bottom (depressed 75%+) to the W key. At least it works as brakes but you have no modulation, only full on of off.

Pretty good idea!

Very nice.

GPU = Graphics Processing Unit (Video Card).. Here's what I've accomplished now, pretty happy with the settings..

I believe the newest one from AMD's site.. Are you 100% it's 1.1.1.0? When I changed to the preview version, I used Revo Uninstaller to d uninstall, took out all the Reg keys too, maybe try that.. If you are using 1.1.1.0, you have to have it there... Are you using an AMD GPU?

Strange.. Here's some pics, might help..

I think only 32bit for now..

Check out Guru3d. It does work for nvidia, but from what I read, you have to place the files into the game directories.. http://www.guru3d.com/files_details/sweetfx_shader_suite_download.html

I'm messing around with vibrance (.50), LumaSharpen (1.60), CinemaGP? and something else. the HDR option is a big FPS hit through RP I noticed, cut my FPS by half (usually 50+ maxed out with HDR on normal in game). Another thing I noticed is the side by side screenshot comparison mode messes with the settings. For example, I set the option to 3 (diagonal mode) and the left side became very over saturated and dark, the right side fine. At the time the only option I had activated was splitscreen, so I think it's a bug (still beta). 2 last points - 1. Thanks to GregP, I sorted this out -- If for some reason the program stops working (I noticed because the FPS counter failed to show up after loading), go to overall settings and check "Disable 64 bit support" and save, then uncheck and save again. It kick started RP back into action and has worked 100% afterwards. 2. In the readme, it mentions you can Alt-tab out of game, change settings in the settings.txt file, save them and then alt-tab back into game and they will work right away. This did not work at all in DCS, and I had to continually quit, change settings, reload, toggle Ctrl-S (turn off/on SweetFx) to see the differences. Hope this helps