Slayer

You guys are kind of confused on Vsync.... Vsync on = sync to the monitors vertical refresh rate. Turning it off allows the higher framerates because its not locked to the vertical refresh rate. By default almost every application or game has vsync turned on. In Vista MS made it a WHQL requirement at the driver level that vsync is turned on. It can only be switched off in an application or game that is coded to have a setting to allow it to be turned on or off. The setting you see on the Nvidia performance page only pertains to OpenGL ( it even says this if you select the option and look at the help text below) As far as I understand it BS is not an OpenGl application and there is no setting from within the game to enable or disable Vsync...so unless you have some kind of hack like nhancer or rivatuner there is no way to turn it off for BS. [ATTACH]26044[/ATTACH]

Wow you guys are brutal. He just needs some coaching. @Herguy: There are lots of people willing to help you and give pointers, it just takes some getting used to. If you could master this game in 1 day you'd be bored of it in a week and quit playing. I would suggest joining in on a multiplayer server and getting teamspeak or ventrilo and joining in one of the practice servers out there. I recieved lots of good advice from some people on there before....ironically I think it was the 159th's server...

Ok..not being able to use the right shift is a known issue of the older SST software. This bug is gone in the newer SST beta software. Here is the link on their forums. No new drivers are needed it just updates your magic mouse and the SST. http://www.saitekforum.com/showthread.php?t=16643

to use the clutch button as programable you need tu turn off the clutch function in the joystick control panel. Right click the joystick icon on your windows taskbar and pick control panel. It is sort of hidden under the MFD page tab...., uncheck the "Enable Clutch mode. In regards to maping multiple keystrokes to a key binding it is reverse of what it shows in the game config file. so if it says " A+rshift+alt " you need to set it as alt+rshift+A in your profile.

The rotaries are treated as axis. The only way you can utilise these is under the axis page in DCS or map it in SST In the game they are: joy_ry joy_rx You need to move the rotaries quite a bit to get detected in the axis page.

I would like something along the lines of the Falon4.0 manual

Even my old socket 754 Athalon 64 could run 64 bit.....I used to run Xp64 on it so it's not like this is some new tech that everyone needs to upgrade to. That old system is ......what 6 years old now? It's a safe bet to say that most systems support it (dependant upon if a 64bit OS is installed) If your computer is so old that it can't run a 64 bit app or game then odds are it doesnt have enough horsepower to run DCS.

http://www.microsoft.com/windows/windows-vista/features/superfetch.aspx

I never put a stopwatch to it but DCS:BS does seem to load faster in Vista compared to XP. I use never turned off the SuperFetch. I also use ReadyBoost. Try it with Superfetch on and off and see if you notice any improvement.

Yes, you must open the profile in the profile editor, the test only works on a profile you are working on in the profile editor, it ignores what is loaded in the stick. Right click the joystick icon in the corner of your taskbar and pick profile editor, open the profile you want to test and then press the little scope icon in the upper right corner of the editor. Test away.

I upgraded for SLI 8800 GTX 768 MB's to a GTX 295 and only get a few FPS better if any. I wish they would do more to push this game towards GPU processing instead of being so heavily CPU dependant :/ If you play other games though then don't base your purchasing decisions on just this game at it's current state. You will definately get better FPS in other games an they are working on updrading this games engine so who knows what the next few years may bring..

64 bit allows you to move larger chunks of data more efficiently, thats why so many database solutions moved to 64 bit years ago. It's not just a memory limitation that x64 will address. Another thing that many people forget is that out current processors (C2D etc) native mode is 64 bit. If I remember right they are running in some kind of compatibility mode when operating in 32 bit, so I'm betting that we should see some performance gains on a 64 bit executable. Being as this sim seems so CPU bound it will probably deliver more bang for the buck than a DX10 implementation. Not only that DX11 is coming with Windows 7, so why waste time on DX10?

The newest saitek beta programing software supports the X45 now. All you have to do is grab someones x52 or x52 pro profile and load it up in the editor. After you load it just click the dropdown at the top, select your x45. Then to reuse the commands all you do is right click on the slot your programing and select the preprogramed function. This way you can reuse all the commands and save yourself hours of typing. I do this with my X52pro and then used the same file to program the macro keys on my cyborg keyboard, huge timesaver. Just do a search of this forum for profiles, theres some people have uploaded a bit back in this forum. I know you were hoping for a full X45 profile but many people don't use it anymore :/

You have 3 devices capable of sending text input to the game. I would try to work through those first. Could be some conflict between the programing software for your different devices? I'd start with the N52 first.

You should just leave the file renamed and then work on troubleshooting what the other causes are for you to crash. If it is it renamed or deleted it cannot cause the game to crash because it isn't loaded. It sounds to me as if you may have multiple problems. Try to be more specific on what the actual crashes are after removing the file and maybee we can figure out what your other problem is.

Yes it does the same thing here. Your doing it without a profile open in the editor. You must have the profile you want to test loaded in the editor and when you use the test function it temporarily overrides anything that may be loaded on your stick.

The reason you probably didn't get the crash earlier is possibly because you were maping the buttons in the game interface instead of using the programing software. When I initially got the Russian version I only used the game to program the stick, it didn't crash alot until I made a SD6 profile. ED Rik said in another thread they are fixing the bug in the patch, so lets keep our fingers crossed this will be gone soon :)

The functionality has always been there to program it. If your a programmer you need to get the DirectOutput SDK. the LUA functions in the game I'm guessing allow you to read values in the game so that you can send them to the display with DirectOutput. At this point in time it doesn't really do anything in the game other than send a "Rulllez Saitek" message to your display. Looks like they toyed with the idea but ran short on time so it never really got implemented to do anything. Would be cool if they do though :)

Thanks I hadn't seen that post before {obviously} :P

We can have gameplay like this in DCS, just turn on arcade mode :P

Good to hear :) Thanks for letting us know.

I just saw this article about a new FFB stick being worked on. It's definately something to keep an eye on. Hopefully they have a retail product soon. http://www.guru3d.com/article/paccus-fluid-head-force-feedback-hawk-joystick-interview/ This would be great for BS as well as WWI and WWII sims.

Kind of late reply , but anyways the fix to your problem is to go into the C:\Eagle Dynamics\Ka-50\bin\stable(or whereever you have it installed) folder and remove or rename the file called "lua-direct_output.dll" This will fix the random crashes you are having. There is a related thread on this for Saitek X52 Joysticks so I won't go into the details of why. Just get rid of that and you will play with no crashes. There are a few users reporting problems with Realtek onboard sound but those don't crash the game.

Stick/collective/pedals for $400.00 isn't too bad to swallow then. Now if they just would add FFB :)

The reason it's faster is because its doing something called SLI AA, It doesn't show this as a seprate "mode" with the nvidia control panel but at some point it turns on. In Nhancer you can see this hidden functionality. Don't stop until you hit 21K :P