Jesse

No problem. The old threads are buried and a new one is needed anyways. 1. Without force feedback enabled, the stick must be used like a non forcefeedback stick. You must return the stick to the center after each press of the trim button. The problem is, without ffb enabled, the tightness that you feel in the center with ffb enabled can't be found. The center of the sticks range feels extremely sloppy unless force feedback is enabled. Basically the tightness can only be turned on when a game sends spring holding forces, not when using the profiler to turn on centering spring mode or whatever. 2. The problem you're experiencing here is the tiny bit of slop with the force feedback motors. The motors can't hold it perfectly still. If you've done the firmware upgrade you've surely noticed how much that was improved last year. If you have any curves set up in the game to make the center movement more precise, the curves will not move with the trimmed position of the stick, meaning that if you trim hard stick forward, your stick is now very imprecise because you're on the wrong side of the curve. The solution to this (that ED could absolutely implement) is a moving response curve for ffb users. This means that if you're trimmed far to the left, the curve is reapplied after you trim to diminish any movement of the stick in it's new position. 3. The profiler is a nice tool that has some purpose, but for modern games like DCS it not necessary or useful to use it to map your controls. You should map everything you can inside the game, and use the profiler only for doing things you can't, such as mapping the ministick to do the trim in the A10C by making it send key presses to the game. Other than special uses like that, never use it to map your complete hotas. DCS can read input straight from your device so using a third party tool to have your device send keystrokes to the game is dumb, and screws some stuff up such as SOI selection etc in DCSA10 where you must hold the hotas button. I have a profile for every game in the profiler (for the axis adjustments), but what I do is apply that profile as a persistent profile using the 'Options>Global Profiler Settings...' window before I play. I don't bother launching the game with the profiler or having the profiler autodetect my current game. That's just me though.

Again, everything you are doing to make the G940 hotas work with this game is simply a bad workaround trying to fix a broken ffb implementation. Control Panel\Hardware and Sound\Devices and Printers Sadly I haven't overlooked anything. I've owned the G940 since 2009 and followed this issue closely for years waiting for a fix. This issue is well known and exists in every G940. Thankfully the forcefeedback is fine in other games and DCSA10C. Yeah save your 20 bucks. I knew this wasn't going to be fixed but I had to try it myself.

Yes. In theory you should be able to have your force settings at 100%, the stick should be unmovable until you hold the trim button, at which point the stick becomes slack. Then you move the cyclic wherever you want it and release the trim button, which turns on the forces again and makes the stick immovable. Since the G940 release, this has never worked correctly. Currently you must set the force level on the stick low enough to be able to move it around without tiring yourself, but still high enough to keep the stick steady when you reposition the stick and trim. This is not right. It's only a bad workaround that leaves a lot to be desired if you know any better. Also upon releasing the trim in a new position, the stick is very briefly slack until the force feedback motors work to center the stick in the new position. Since you're constantly fighting the force feedback (using your muscles to pull the stick to the new position against the sticks will), when it releases it for that very brief moment and you're not prepared for it, you will keep trying to pull the stick in that direction and the loss of force will make you jerk the stick slightly. All the firmware update for the G940 did was decrease the amount of slack in the center of the stick when the motors are holding it in place. It just made the stick feel tighter when the force feedback is on. It does nothing to address the fact that the G940 is and always has been broken when it comes to the Black Shark trimming system.

I've got 1.0.2 and 2.0 installed. I'm flying them back to back. The g940 behaves the same. It's jerky when you let off the trim. If you've any pressure on the stick and spam the trimmer, it walks in that direction. There is always pressure on the stick regardless of the trimmer button being held down or not. I haven't changed any settings in either game except for video and the basic hotas controls. They are fresh installs on a fresh Win7 install. The joystick is at 50% power or so. I remember it doing this the last time I tried to play Black Shark. The force feedback has always been screwed up. Yeah I'm sure we're all aware that the FFB2 is the ideal stick to have for Black Shark but this has nothing to do with the G940. The G940 has always been bad. There are no workarounds for the problem, only ways to make it less obvious and annoying. The G940 will not under any circumstances work like your FFB2 will in this game.

Force feedback for this game on the G940 just does not work well. The jerking forward you're feeling happens exactly the same way in 1.0. The force feedback is exactly the same as 1.0. The problem is that the spring force applied to the joystick to keep it in its current position is not disabled when you hold the trim button like its supposed to. As far as I know ED hasn't said anything about this and we'll never get this fixed. If I remember correctly, Logitech has stated that it can be fixed with some extra programming. It's obvious that this is not on their priority list. It's been two years since the stick was released. It's never going to happen and you're better off with another hotas for this game. If you feel ripped off by both companies than come join the club.

If an application is going to write to the program files directory in windows vista or 7, it needs elevated privileges. Run notepad++ as admin.

Wait, you guys are talking about multiplayer UI when there isn't even dedicated server software??? :huh:

I 100% completely understand that the marks will be overwritten. What do I do if I have all 25 marks filled and I have a bunch of targets I need to mark for a JDAM run. If I have forgotten which mark was next in line to be overwritten or maybe I accidentally hit the mark button an extra time or two, it seems I am screwed because I don't know what mark I'm saving to. So simplified: Is there any indication as to what mark (abc) the plane will save to next? EDIT: found it New problem: It seems that the system is stopping at Y and not continuing to A like it says in the manual and as you've explained. Is this a bug or am I wrong about that letter in the CDU being the indicator for the next mark save?

Yes I know, but is there zero indication of exactly what point is going to be overwritten?

How do I clear offset markpoints? If I can't, how do I know which markpoint will be overwritten the next time I create one?

Sorry if I wasn't clear. I just started up the game to confirm this: When the game has just started and it says 'press pause/break to start', you should be able to use your TrackIR to skew the view around the cockpit even while its paused. You should also be able to hit escape and close the game through the 'mission pause / interrupt' menu. So I would start up trackIR, bind the pause function ingame to Z or X, start the game and try to do all of these. If you cannot do any of these things, then it seems your game is actually frozen and I've no idea where to go from there except reinstall. I think the devs and people in the beta forum might be able to help you better.

Well that's the only thing I've experienced as far as pause bugs go. Here is what I would do: -Check pause binding in options -Check to make sure another application such as trackir is not capturing the pause key press and not repeating it You could also try binding something else to pause in options to make sure that it's not just your key presses failing to reach the sim.

Is the pause/exit popup still there after you press your pause key? If it isn't, try pressing pause again.

I bought a 99 cent app for this very reason. Search for 'GoodReader' on the app store. There are quite a few ways to download the PDF into the app. I used google docs. It's quite an amazing value for such a cheap app. It can but the apple reader sucks ass.

Consoles and bad games are ruining PC gaming. Steam is an online service that allows you to optionally purchase and download games and keep them conveniently ready to download and autoupdate at any time. I put the key word in bold for you. Can somebody explain why we're not getting a simultaneous steam release? What logic is there to explain that? Most people who are going to buy DCS:A10 are probably going to buy it at or near release. If my preference is Steam then my only choice is to wait a year for it to release finally or buy the game twice. What exactly is there to investigate? It seems to me that it's not that you guys can't do a simultaneous steam release, you've just decided against it. Care to explain?