sh0v0r

I had a look through the default.lua file and found this: {combos = {{key = 'JOY_SLIDER1'}}, action = iCommandPlaneCollective, name = 'Flight Control Collective'}, What does the Ministick map too with respect to its Axis name, based on what I'm experiencing its 'JOY_SLIDER1' and... -- View {combos = {{key = 'JOY_BTN_POV1_L'}}, pressed = iCommandViewLeftSlow, up = iCommandViewStopSlow, name = 'View Left slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_R'}}, pressed = iCommandViewRightSlow, up = iCommandViewStopSlow, name = 'View Right slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_U'}}, pressed = iCommandViewUpSlow, up = iCommandViewStopSlow, name = 'View Up slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_D'}}, pressed = iCommandViewDownSlow, up = iCommandViewStopSlow, name = 'View Down slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_UR'}}, pressed = iCommandViewUpRightSlow, up = iCommandViewStopSlow, name = 'View Up Right slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_DR'}}, pressed = iCommandViewDownRightSlow, up = iCommandViewStopSlow, name = 'View Down Right slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_DL'}}, pressed = iCommandViewDownLeftSlow, up = iCommandViewStopSlow, name = 'View Down Left slow', category = 'View'}, {combos = {{key = 'JOY_BTN_POV1_UL'}}, pressed = iCommandViewUpLeftSlow, up = iCommandViewStopSlow, name = 'View Up Left slow', category = 'View'}, {combos = {{key = 'JOY_BTN5'}}, pressed = iCommandViewCenter, name = 'Center View', category = 'View'}, I'm guessing that's the source of my troubles?

I should add that I think this is the source of my warnings I keep getting on engine startup as the ministick is setting the collective to 50% on startup and once everything is running I have to grab the throttle and shift it forward then back to overide it. On a side note I've also noticed the Rudder Pedals are not being reset and I need to do a full left to right on it to make BS recognise the centre calibration and stop the heli from yawing.

Hi all, I've noticed something odd with my setup. When I push up and down on the Mini Stick it effects the collective. The only reason I can think of is that the axis it uses is normally assigned to a throttle lever on a joystick and BS is auto assigning those inputs. I've looked through both the Profiler settings and inside the Control Options in BS and it is not bound to anything in either. In addition to this it seems the D-Pad hat on the joystick is also defaulting to camera view controls. Anyone else experiencing this? I have gone through all the Assignments in the Profiler and unbound them, choosing to assign them through BS to avoid conflicts. I have all the latest Software/Firmware.

Thanks for letting us all know. I spent some time today looking into importing a copy and happened across this thread this afternoon. I quickly went off to the site and placed an order.

Thats interesting, perhaps its some other software that starts up with windows that prevents it from working correctly. Are you running in Fullscreen mode?

Yeah they're unchecked.

Thanks for the reply Nate! Yeah I'm feeling the same, there are times when I love my card, but the amount of issues like this just leave a bad taste in your mouth. I'm going back to Nvidia next card. When it does work it looks very very good, the combination of 8x AA and 16 AF create such a sharp crisp image you can spot details a long way out. It looks incredible.

Bringing this up again. I have spent allot of time trying to get this to work with only a little success and have noticed a few other things of note. I read that Alt-Tabing out and enabling it in CCC once the game is running works. This method is very unreliable. When I did get it to work I noticed a big jump in my frame rate by almost double. 20 - 30 upto 40 - 50 in the winter demo. This I suspect was because the game was only running on one core and enabling the AA some how activated both GPU cores. I also tried using ATI Tray Tools but this didn't work either. I was able to turn it on and off consistently when running in windowed mode but the 4870X2 only runs on one core in this mode. The fact that the game uses two seperate executables (launcher & DCS) means I cannot force the settings on startup because you cannot launch DCS.exe directly. It's quite disheartening knowing that my machine is capable of running the game at max settings 1920x1200 8x Edge Detect AA(24) 16xAF with 40 -50 FPS but I have to prey to the gods that I can get the damn thing to actually get into this mode. I hope in the forthcoming patch this might be something that can be looked at. It might actually be a driver issue and the ball is in ATI's court. My System: CPU: Q9550 Vid: 4870X2 (Cat 9.6) RAM: 4GB OS: Win XP32 Pro SP3 SND: X-FI