BakaNi

Another 2560x request. At this resolution it's possible to pull the zoom all the way back inside the cockpit and still read all the tiny writing. However, the game LOD drops detail when pulled back that far and ruins the image :( Anyway to force a high detail LOD inside the cockpit?

Interesting, details please. I experience corruption using both AFR and AFR with compatibility tweaks, on vista 64 with the latest nvidia WHQLs 180.48. In my testing, sli produces nothing but a net loss in fps, no matter the resolution or anti-aliasing. Assuming it does work for some people, then fantastic, but you've got to be running a pretty weak graphics card for it to be the limiting factor in black shark. The game is so badly cpu limited that even at very low resolutions and all the graphics turned to low, on a modern overclocked c2d, you can end up with ~ 10fps Could you run a little test for me? Run the first black shark tutorial mission, where the camera pans in and out the cockpit and outside and benchmark it and then turn off sli and do the same. Maybe we can find out where sli works and where it doesn't, your system specs and ingame settings would help also :)

There is no nVidia profile for DCS - Black Shark, by default SLi won't be used. Creating one for blackshark is pretty pointless as all you'll achieve is graphics corruption and probably worse performance. Even at 2560x1600 with 16x AA, one card out performed two. The game seems to be incredibly cpu limited, you'd have to be using two very poor graphics cards for sli to make any difference. This is one to be left to the nvidia driver team, if they care, they might beable to pull something out of the hat.

Anything that's not a cold start, has trim issues. Mission one of the campaign starts on the ground from a helipad, but as the k80 is powered up, it is untrimable. Maybe... ship me your joystick? :joystick: EDIT: It seems that the chopper completely untrimable, regardless of state, so long as ffb is enabled :(.

*Excuse the wall of text, I can't see include any formatting :(* Argh, so that explains why the trim wasn't acting very enthusiastically, it wasn't working at all! Trim works fine when I disable FF ingame, unfortunately this disables FF, which I've grown to know and love, my copter feels lifeless without it. How did you set this variable? I only have one forcefeed back device on my pc and that's my joystick, I'd look to check something else hasn't installed itself, on the off chance. I hope this bug can be fixed soon! Random little story, I managed to press a few too many switches and ended up with left and right engine overspeed, before I even took off, unable to kill said warning messages, I just ignored them ;) About 5 minutes in the flight, a huge bang goes off from my left rear speaker and the joystick violent lurches down and right, catching me completely by surprise and spilling my cup of tea over my trousers. After the initial 'wtf' moment, I cut to outside view to see huge chucks of something blasted out of the back of my left engine and the copter death spiralling towards the ground. So in the interests of laps everywhere, FF and trim must learn to live in harmony together.