Slayer

With all due respect: Regarding the rudder axis on my G940 I said I "suspect" it was a hall sensor, even if it is a resistance pot it is hyper sensitive. Your using Saitek pedals and a TM stick so your hardware is different I was simply pointing out the problem I see on my machine. I have been flying this also since the Russian version came out so I'm not a noob. Just because you have NEVER seen this problem doesnt mean that there isn't a problem between the game and another hardware configuration. I'll post a trackfile of it happening when I get some spare time.

It happens if you hold down the trim button. Holding trim while manovering is about the only way you can move in close combat situations at all (unless you switch to FD mode). A lot of real chopper pilots fly this way. When enroute you make small corrections and press trim each time, but when you have to bank hard because you came around the corner face to face with an Apache or a jet then what? How long will you survive doing adjust-trim-adjust-trim ad nausem? You can't, you have to press and hold the trim button down, complete your manover then release when you are where you want to be.. That is the other outstanding issue with the G940 is that in the real world when you hold the trim down it releases pressure from the stick. With the G940 it doesn't. You have to push against the FFB then trim, it doesnt release tension from the stick like it should. When you release the button the stick holds in position. It's in the manual and been discussed in the forums before. I haven't been able to try it on say a MSFFB2 or anything but it is my understanding that it does work properly on that old stick. That is why some people have the problem with the rudder worse than others. It's just a bug that ED haven't delved into yet because not everyone manovers by holding trim. Some gave up and just use FD mode to cheat it. Others use the Z X trick or trim reset....

PCIE 3.0 level hardware should start hitting shortly after the game releases. It's going to be rough to hold out on DX11 hardware considering I have a GTX295....

Is porting a version to DX11 going to push release into 2011?

DX11 has a trickle down effect even for those without a DX11 graphics card because all the librarys etc were supposedly retooled by MS to use multicore/multithreaded processors. THis should provide a small boost for everyone with a dual/quadcore compared to a DX9 or DX10 version because it puts those unused cores to use, even in single threaded apps. Time will tell on this.. Direct compute might have something to offer too but I havent heard of a game using that yet.

There are certain situations where you trim and center the pedals but the in game pedals (what you see in the cockpit) continue to travel in the last direction you pushed until they hit the virtual "stop" This results in uncontrolled spin. Pressing X or Z stops this ghost pedals movement. Also trim reset will correct it BUT from what I see in game if I only do a short press of the trim reset button the peddals do NOT move back to the neutral position, you need to press and hold the trim reset then the pedals will slowly move back to neutral position. In my case I suspect the G940 rudder pedals use a very sensitive hall sensor and even the slightest movement while pressing trim will cause this problem( think of it in the same way as trimming then not returning stick to center and its the same effect if you don't have a FFB stick) In the game specific settings for Blackshark in my G940 profiler I added an 8% deadzone and it seems to help but it is not a 100% solution. rudder and trim issues have been beat to death in the input section of the forum. Do a search there for more info.

Does your G940 work in any other FFB enabled games? In the joystick control pannel do you have forces on the joystick test page?

Great thread. Was trying to figure out how to do exactly this the other night. Even if it doesn't take you back to a shkval lock it will get you in the area. Especially useful when there are targets near or in the forrest and they are hard to see(evil mission designers like to hide manpads in the forrest).

Any chance you can make this a modman pack? Much easier to remove/reinstall when you release newer versions.

That checkbox doesnt work. I think after the 1.02 patch it resets some control settings.

Are you using DT or DH mode for your autopilots? (Desired track/Desired Heading) Sounds to me like you are in the DT mode to me... its the switch on the autopilots panel. Edit : DH/DT switch defaults to a neutral position . Also you can try auto turn on target it works with the APs in all modes including enroute.

This is the thread for the G940 LED program. I will only work in single player as just about every server considers it "cheating" to have lua export enabled so you cant even join most servers with it: http://forums.eagle.ru/showthread.php?t=45895 As far as stick settings go: my advice: Ignore most of those threads. Many are based on old firmware and/or software. In the end its all down to personal prefrence on how it feels to you. I do not recommend tampering with stick curves or FFB settings within the game at all because many are duplicated within the stick software. I've seen several posts where people are turning 1 setting down in the profiler then turning it back up in the game settings. Deadzones etc are duplicated between both although they are not named the same the net effect is the same and you will only confuse yourself for hours on end sorting it out. Tune the overall force in the profiler if you thing the stick force is too strong for you. The first post of this thread is good info but some of it is outdated: http://forums.eagle.ru/showthread.php?t=45695 First unless you feel like totally reprogramming the stick or wondering why the included DCS:BS profile doesnt work: The .exe location for the game is changed between the original game and the 1.02 version so you must choose the proper location for the exe so that you can use the Blackshark profile that is included with the G940. Open the profiler. Pick "select game" pick DCS:BS. Now hit the "edit" menu at the top and pick properties. The new location should be similar to this: C:\Program Files (x86)\Eagle Dynamics\Ka-50\bin\x86\stable\simulator.exe Note: I am on W7 x 64 if you are 32 bit it will just be program files... Now you can alter the default profile to your liking without spending hours typing in commands. If you are a pilot that that does press and hold on the trimmer while manouvering like I do, here is a tip that will somewhat remove the trimmer force when you depress and hold the trim button ( as in the real KA-50) Again its personal prefrence, some people prefer to constantly make small trim adjustments and just trim -adjust -trim-adjust etc. I find this way to be cumbersome and hard to do when in combat and you need to manuver quickly. http://forums.eagle.ru/showthread.php?t=55303 The biggest problem I had with switching to the FFB is that even though the stick is now FFB your rudder peddals will not be. So what you need to learn is after you release the trim button is to remove pressure off the rudder or you will spin uncontrollably intil you trim reset, hit a rudder key like z or press rudder in the opposite direction. Eventually you will want to fine tune it but do not get overzealous with changing settings, only try one at a time and see what it does for you. Dont get too confused about the slop discussion. It's not about slop in the stick being read by the game but a small slop in that there is play in the actual force feedback IE if you are using the tape over the deadman sensor and remove your hand you can jiggle the stick around its trimmed postition. Being as the stick is using hall sensors and can sense the tinyest of movements the helicopter can sometimes wander from a perfect hover state because of the small FFB slop not holding it exactly where you left it. It doesn't hold it perfectly tight like the old Microsoft FFB sticks. No ammount of tweaking or fiddling with settings can correct this because it is a hardware issue.

Hopefully all you need to do is have a version of BS upgraded to 1.02 to stay compatible with FC2 then it allows you to install a 2nd copy to bring it in line with the A10 version of DCS. Not sure how the copy protection will work in this scheme though? Would you have to deactivate one install to play the other? Who knows maybee it'll never happen because it's a lot of code to rewrite but I'll be the first to pay for a DCS:BS 1.5 or some such to allow multiplayer with both modules. I'd venture a guess that people will be busy with A10C for quite a while once it hits the market but even so FC2+BS takes it to a whole nother level. I play BS more now then I did in the past for that reason alone. Heck look at how many servers there are....

I was refering to the original poster of the thread. To me it sounded like he was speaking of traditional navaids that you would find on any civillian chart(VOR/DME). TACAN of course is Tactical Air Navigation and the sole domain of the military but these also are fixed navaids. What you're talking about sounds more like FAC stuff (ED is modeling this also)

When I was in the USAF we got to see a declassified video of the Apache taking out an Iraqi chopper in the first gulf war, he used a hellfire. Wish I had that movie but it was before DVD and we all had to watch it in the base theater...

I highly doubt there will be a TACAN or VOR/DME available to use over enemy teritory. Maybee in the training map but anywhere else would make no sense at all...

You might have to mod that stick to get it to work. In that case I would reccomend one of these boards. http://www.leobodnar.com/

Every stick has it's ups and downs. I have owned every major brand of stick and I can tell you the G940 is ok. It's more of a personal prefrence though if you want FFB there really is no other choice. I will still probably get a TM A-10 stick but I will never fly the Blackshark again without FFB. I don't regret buying it for a second.

In related news: http://photoblog.msnbc.msn.com/_news/2010/07/23/4739027-pilot-ejects-an-instant-before-fighterjet-crashes

At the dropdown of the configuration box make sure you are picking "axis commands" otherwise the they dont show up under the button configs. You must do this setup for each aircraft.

add a slight delay in your digital commands, it sounds like the release is happening too fast and not being processed, try recording it with delays on and see if this helps. Also check to make sure that your keys are releasing in reverse order of being pressed otherwise it gets mixd up too. I've had that problem on saitek and logitech hardware also( the programming software for both sticks appears to be made by some of the same people and works almost the same.....) With the analogue hat all I had to do was put in a 8% dead band on both axis in the game and drifting was solved for that...

Wow man...F117 goes down in flames and all announcer dude can say is "buy more pepsi product for your kids"...No wonder it was the last airshow in Maryland

I'm also a fairly new owner of the G940. I tried some setting but what I have learned is that you do not want to touch the range setting. This setting at anything less than 100% is affecting the force feedback. At 80% you can feel when you hit the 80% in the range of the stick because the trimmer will not hold it past 80% of the movement of the stick. It also seems to break the method I use to take pressure off the stick when I hold in the trim button( I don't do a bunch of trim presses, I press-hold-manouver-then release) I posted it it in the input section if your interested: http://forums.eagle.ru/showthread.php?t=55303 On the other hand I like your settings of 30% on the X and Y axis so I'm using those now. I definately love this stick for DCS:BS it adds a whole new dimension to the game.

You should set water to normal in the game if its not, thats a huge FPS killer. If you are having problems with shadows I'd try the setting in game for "all planar" It's hard to tell from your post exactly what you are seeing as far as shadows and such so a screenshot might help. Also helpfull if we know what resolution you are running at. There are a couple of issues with the DCS:BS graphics engine that cannot be fixed with driver updates and settings tweaks no matter how hard you try or what settings you change. The game is mostly CPU bound so you are only going to get so far.

You should turn on some anti aliasing too it gets rid of the jagged lines on your MFD. for it to work in LOFC2 or DCS:BS you need to "override any application setting" in the nvidia control panel. [ATTACH]40671[/ATTACH]