Sinky

Thanks for the reply, looks like it would end up cheaper to just go for a whole new card when the next upgrade comes.

Welcome to having a grin on your face that you just can't shift.

Just wondering if it's possible to crossfire with my current motherboard. I'm currently using the Asus M4A785D-M Pro. Available slots are 1x PCIe x16, 1x PCIe x1 and 2x PCI. Now I can see I have two PCI Express slots but only one of them runs at x16 which worries me. If it would work, would it be worth it or would the x1 slot cripple the second card? Thanks.

Are you using SLI or Crossfire?

I've created a corrected HUD snap view for use with gun runs. Should do what you and Zorg are looking for. Here's the thread: http://forums.eagle.ru/showthread.php?t=72609

Before anyone flames me just let me say that I won't be buying the game on steam so the no UK sale doesn't bother me one bit. If I buy again it will be a boxed version. Well done ED, imagine adding UK sales onto that number. Could put it right near the top. Like I said above, this is not a dig at the developers.

I've corrected the default HUD snap view. I got tired of zooming on the HUD manually when making a strafing run, makes pulling out of the run more difficult whilst your trying to reset your view. The HUD in the tweaked view is no more cut off than the default cockpit position. Hopefully this will be of use to some people. Firstly please backup any file before you edit it. You can apply this change to either SnapViewsDefault.lua or SnapViews.lua both of which are located in your Config/View folder. You may have to edit the UseDefaultSnapViews in View.lua if you choose to use SnapViews.lua. The changes you will need to make are shown below. Snap[11][6] = {} Snap[11][6]["viewAngle"] = 28 Snap[11][6]["x_trans"] = 0.36 Snap[11][6]["hAngle"] = 0 Snap[11][6]["y_trans"] = -0.041336805555555564 Snap[11][6]["rollAngle"] = 0 Snap[11][6]["vAngle"] = -8.5 Snap[11][6]["z_trans"] = 0 Your mileage may vary on different resolutions. This is how it looks in my game.

The best thing we can do for now is setting noise1back = 50000.0 like Mustang said. I can live with the other problem it causes until we see a fix.

Setting it down to 25000.0 still has the same problem as before and it also brings back the blurry textures.

Hopefully setting the new value won't blur the textures again. I will give it a try later but I trust you've already tested and verified it working. In your Config/terrain folder you want to edit the line 'noise1back' to the value Mustang said. You would edit the file that corresponds to your current view distance setting. So if you run medium view distance you would edit Medium.lua. I hope so, I usually run medium view distance so all you would have to do is edit Medium.lua instead of High.lua. The textures were very sharp at 50k but it brought about the problem in my last post. I haven't tried the suggested 25k setting yet though.

I second this...Tweaking your axis curves is one of the best things you could do to increase your accuracy. Spend around half an hour tuning that and you should end up with nothing but smooth control input, none of this twitching that will make it seem as though your reticule and the target are both positive magnets. You may want to add a deadzone in also, if your control stick is a bit loose around the center.

It appears we have stumbled upon another problem which may or may not be caused by the tweak. It's not something I can explain so just take a look at the screen shots I took at different zoom levels.

Using high visibility distance it looks perfect. I think this is down to Mustang's tweak in the High.lua. I thought it was changing settings for the high scene setting so when testing I never set my visibility to high. This meant I never saw the changes. You could try applying his tweak to medium.lua if you use medium vis distance. Thanks Mustang, won't let me give you rep at the moment though.

I tried with HDR off when I was testing the flickering I had. I don't remember it fixing the blurry problem but I will test that and also the high vis distance when I next get a chance to jump on the sim.

Yeah it's more likely anisotropic filtering than anti-aliasing. I doubt that is the case in this instance though, seems to be a change made to the sim. It is strange how some are getting it and some aren't.

I will give that a try shortly. I've always ran with it at medium and never had any problems until lately.

Still appears to be no change, attached a few more screen shots including one of my options. Only the resolution and MSAA have been changed from the settings the sim suggested after the reinstall.

Just tried your tweak, changing the High.lua file inside the Config/terrain folder. I used the Black Sea Runway Start mission for testing. While I can see a massive difference in your screen shot, it appears just as bad on my end. I've attached a few screen shots. I appreciate the effort your putting in to try and fix this.

It's got me stumped, when I think about it I'm sure I saw this appear in patch .6, much less pronounced but it was there.

Thanks, the problem was UAC. If only there was a way to get around it while still having UAC active, without reinstalling or running steam as admin ( which it doesn't seem to like ).

I've attached a screen shot of the section you wanted to look at. I guess that rules out an ATI only issue.

Thanks, I've already tried this from the last thread you posted in and it didn't work. I currently have: Target: "C:\Program Files\Eagle Dynamics\DCS A-10C\bin\Launcher.exe" Start In: "C:\Program Files\Eagle Dynamics\DCS A-10C\" Nothing will come up on the screen after trying to start the game but it will briefly say that I'm now playing DCS A-10C for about 2 seconds.

Check this post for info on the steam version. http://forums.eagle.ru/showpost.php?p=1175835&postcount=7 I've yet to get the game to launch properly by adding it as a non-steam game.

What are your pc specifications? I tried a full reinstall of the new download yesterday and I'm still having the same problem. I've seen someone else with the problem here http://forums.eagle.ru/showthread.php?t=71789. As a side note, I did remember to clear out the DCS Warthog folder. I also left graphic settings untouched after the reinstall just in case.

I will try a full reinstall of the game in a day or two using the newly patched download, failing that I will mess with the drivers. Thanks for the reply's, +1 to you both.