MagnumHB

I had it reset before, but I tried it with the Windows calibration, then the TM calibration, and the range of motion at least seems to be corrected, but the input sticks to one side or the other, especially with small movements. Still though, the raw values you can see on this test page are definitely skewed to the right and don't center out properly.

Well, I've had mine installed for a while, but I'm finally getting around to trying to calibrate it, and I just can't get it to work correctly in the X axis. After running the calibration tool many times, the range of motion left of center is almost nothing, and the input tends to stick at max deflection when the stick is moved to the right. Has anyone seen something like this?

Awesome, just grabbed one. Looking forward to it.

I've had the mixed fortune to find this thread now, right after the X/Y portion of my slew control died (the button press still works) after replacing the main right throttle cable for the second time. I'll certainly be jumping on the next batch for a replacement instead of springing for an entirely new throttle just to get the cheapest part on the whole thing functioning again. Should be able to order again in a few weeks, yes?

Still broken as of 1.5.8 open beta. Very annoying.

Really on the ball. Much appreciated.

Another possible related bug (or maybe just a symptom of the hack): I edited the joystick lua just to test out the functionality (just copied the relevant lines from the keyboard file), and it mostly worked, but with one small hitch. The normal switch sounds did not play when moving the mode selector with my new joystick binds. The sounds do play when moving it with the mouse however. The weapons selector was fine either way. In all cases, the mode switched properly, just with missing sounds on the mode selector when using the joystick.

Great update. I am wondering if there are plans to add additional keybindings to the Viggen for things like mode selector and weapons selector left/right, and the toggles addressed in this mod.

Nice work, I'll be using this for sure. I do hope that at least some of this gets officially implemented by LNS though.

It sure would be nice if ED could find a way to allow third party developers to release their own patches in a timely manner. It's unfortunate that Viggen fixes are ready to go, and we have to wait another week (at least!?) to enjoy them. Perhaps the modules, should be, you know, modular, and be versioned and updated independently of the core game.

That could certainly be argued to be a more sensible release policy, but it wouldn't be a proper ED patch release if it didn't introduce new bugs, now would it?

If you publicly add support for a new module to an existing version, then it's not really the same version anymore.

I think the simplest explanation is that the Viggen just isn't ready yet. A video posted a week ago has minor but obvious bugs, and a screenshot posted in the same thread several days later is described as a WIP. LNS has stated that their goal is to release in such a way as to minimize the amount of required bug fixes afterwards. ED, even if they know a potential target release date, can't really say much until LNS has a firm idea of when they'll be ready.

Ah, I was wondering what was up with that.

Thanks for that. Not trying to be adversarial, just hadn't seen those tidbits buried on the Russian side.