Snaut

Let's be clear that the looping sound of gun when supersonic is a bug of the game engine, not anything realistic.

I can confirm also. F-15 after 1.2.9 gets into fast yaw oscillations in supersonic flight. In external view substantial oscillating rudder deflections can be seen.

Blue screen of death would indicate some driver or hardware problem. You shouldn't get it just from running the game.

Onboard sound here, no stutters firing cannon in DCS. Also, I'm getting awesome 1 ms latency using ASIO in Ableton Live :)

I would get a CPU with stronger single-core performance and a stronger GPU with lots of video memory. SSD will not improve your fps.

Make sure your aa method setting for the radeon is multisampling. Vis range medium should give you noticeable improvement. How much memory does your Radeon have? With textures on high you will max out 1GB quickly. What fps are you getting with this setup?

If you don't have TM Warthog don't get discouraged. It's not hard to do it with a less precise stick (Saitek Cyborg here) The throttle inputs translate into speed changes with some delay, so it's more about anticipating that changes. It doesn't need to be super fast or super precise, but the timing matters. It's akin to keeping neutral buoyancy with breaths while diving and the rhythm is similar. Add some throttle if you see/anticipate the boom extend, reduce back before it goes back in the green, giving it time to slow down. Keep the tanker with stick inputs more or less on the same spot of your canopy and concentrate on the throttle. Don't worry about keeping the position as much as the distance. If you don't exceed the boom angle, the boom operator will manage.

I'll try to join. It's 1.2.7, I presume?

If you want to control the overall volume, a keyboard with volume keys works great. In cockpit there are working volume knobs for radios, stall warning, rwr, tacan etc. You can assign key shortcuts to them.

I can confirm it doesn't work. The tanker should slow down on fuel request and it doesn't.

Setting shadows to low removes self shadows and cockpit shadow - these can be taxing for a weaker PC. I doubt the remaining simple boxy shadows that are subject to LOD impact fps at all.

I think you can disable shadows in options.

The mod is awesome, but I have a weird problem: If I save my own snapviews the mod no longer works the next time I load the game. EDIT Correction, it just doesn't work with an older saved mission.

From my observations the smoke bug manifests with crashed A-10 destroyed civilian traffic (set the traffic to high and strafe a highway or a train = slideshow)

Is there any way to reduce or turn off the smoke effects until there is a patch for this?

+1 Would be great if moving map wasn't affected by the texture setting.

i3 is not the strongest CPU but the real problem is that you seem to be using the graphics integrated with the CPU. You need a reasonably powerful dedicated graphics card to run this sim.

If you contact the tanker with 'intent to refuel' they will turn the lights on and tell you the altitude. Maybe it's my screen but I can see the brighter outline of the tanker over the black sky, no NVG needed.

Is precise trimming that important when refuelling? There are always some oscillations when you throttle up or down during refuelling that you'll need to constantly compensate with stick inputs. I generally match the speed of the tanker and then only roughly trim the plane for level flight in precontact. I think it is the throttle that is much harder to 'feel' and more important.

The point is, everybody is experiencing worse fps and it's not because everyone's PC suddenly developed overfilled temp folders or faulty hard drives. Let's not muddy the waters. The problem is in the code and is very real and I for one would love to see it getting some developers' attention.

I can't see how on earth any of the magic placebo moves proposed above are supposed to improve fps. Clear windows temp? Seriously? Immel noticed FPS decrease on the same machine, same system, same hardware. How is it that temp files hadn't affected 1.0.0.8 but now they're a problem? Honestly I don't think any of these fixes are relevant when the real problem is in the code.

The mouse cursor bug finally fixed, I can fly A-10 again! New tracers look more faint in daylight, but seem more realistic and easier on the GPU.

I hope it's not. Makes no sense from the usability standpoint. How am I supposed to hit anything clickable when I have no cursor?

Mouse cursor doesn't show up after enabling it(Alt-C). It takes few seconds of vigorous movements. The same problem, still not fixed.

Same problem, mouse cursor doesn't appear immediately when enabled with a key combination. Maybe it's not fatal with TIR but it's unplayable with mouselook where you switch the cursor on and off a lot.