tet5uo

Turns out it was because I had enabled a separate st_volume addon. I removed that one from my startup and it's working fine now.

Just wondering if anyone has encountered an issue where the STVolumeControl won't respond to the mousewheel? I can bring up the whisper/shout slider but when trying to adjust it with the mousewheel nothing happens.

And with the bonus shader bug that has been in the game since Alpha! http://feedback.arma3.com/view.php?id=436

lol are you people still giving each other "tricks" and "tips" to make this game run better? I hear voodoo dolls and prayer work well.

The real solution is to fix the shader.

They need to fix that shader to work properly with SLI I think. I also reported this issue in the early alpha. It's a common bug with shaders that use data from the previous frame not working nice with SLI.

Anyone reading this thread will find their IQ lowering just from close proximity to these posts.

Should the thread even still be open? Though I guess it's good to have one central place for this instead of new ones popping up all the time.

I play regularly with a couple of younger players in our group and they're more mature and less annoying than many of the supposedly "adult" players we have. So, no. I don't see why you'd limit the game based on a meaningless number.

So 133 pages later and the die-hards are still trying to convince us there is no performance problem?

Yeah i loved ACE's tracer mod.

What are you saying here?

What with the engine not handling multi-core CPU's very well, and instead preferring a very fast per/core clock instead, I don't think this game engine would lend itself to good performance on next-gen consoles. Even high-end PC's have issues with low FPS.

Arma3 Gymkhana map? lol!

You know you can probably get a card for free at this point that someone is throwing away that would be better than that thing :D

This is not even close to correct.

This is what you should do. You're contributing just as little to this thread trying to debunk the issue.

Try zooming in with num+ ? I also seemed to notice it only locks on when the thermal imaging is on.

Actually it's almost guaranteed to be the way that the shader is written that is causing the problems, not the NV drivers. When making a shader that uses data from previously rendered frames, you need to take into account for SLI or glitches like this will occur.

Ever heard of selection bias? Gamers are drama queens. There's companies that are actually costing people's lives, yet a gaming company is the most hated? Get real. I don't like EA much either, but i'm not about to go crazy about it like most people.

I think there's something in the game preventing this particular binding. I've tried it in A2 and A3 as well.

Perhaps try the -noPause switch in the shortcut?

They should have let them make Mirror's Edge 2 already. That game is screaming out for a re-make with the Frostbite tech. EA would probably make them put gun-play in it again and ruin the second one too though.

If I artificially increase the GPU load by doing something like 200% rendering quality, then you see the load across my 3 GPU's evenly. SLI is indeed functional.

Makes sense. I'm pretty sure IRL that NVG's don't limit one to 40 degrees of FOV like they do in game.