CARTOK

Hi there, I got a VKB Gunfighter with MCG Pro grip. I understand the Njoy32 Blackbox can do some nifty stuff, however, the instructions aren't overly clear. Is it possible to switch the sensitivity of a physical or logical axis on-the-fly by the press of a button?

Thanks for that, good to know I'm not alone. Any indication of this being an item that is worked on?

That was quick, great work! Will play with this!

Anyone else experiencing incorrect input from the MCG buttons after computer restart, requiring one or multiple restarts of the Blackbox to get correct button readouts?

Perfect, appreciate the quick reply! :)

You got a new user onboard after briefly checking some videos about the software. Great work! A quick question regarding the addition of additional commands; I've added additional commands in the "Additional" category, is that where they have to be? Does it make a difference where they are placed? Awaiting the possible addition of pre-configured cockpit control commands, is it possible to configure a command to be specific for an aircraft type? I.e. if I say "gear down" while flying the A-10C, a specific keyboard input is executed, whereas if I fly the K50 and say "gear down" a keyboard input combination specific to that type is executed?

I noticed that the changelog had a lot of mentions of updating bindings to work properly, unfortunately the AFK joystick mapping is still not working as a toggle (whereas the keyboard shortcut does). Any hope for an update to this?

A separate question related to the introduction of the MCG line of joysticks: with the introduction of a brake lever, will it be possible to use the VKB rudders for differential braking in an intelligent/integrated/easy way?

Short or long stick? (Gladiator vs gunfighter) Really excited about the MCG PRO stick, got all the bells and whistles I'm looking for. However, I'm struggling to determine the better option for me with regards to the base; Currently have a CH Fighterstick which has served me well, but I've now reached the level where the center detente is affecting my flying in more pronounced ways. Hence, I'd like to improve precision. The longer Gunfighter stick would be the ultimate in precision, but I'm not sure of how much the difference is compared to the Gladiator. If anyone has experience going from short to long stick, or vice versa, I would appreciate it! On a sidenote, the number of extra buttons on the base of the Gladiator is definitely a plus in my book, although not a requirement. I'm flying at a desktop, no simpit or similar at the moment (although could consider an Obutto or simply a mount for a long stick).

I'm observing that AFK toggle is not possible when using the assigned joystick button, you can only enable AFK but not disable it. However, the assigned keyboard button works as expected i.e. AFK on/off every time the keyboard button is used. Don't think this is by design, maybe something to amend in a future update?

Actually, the dial just next to it has the same size numbers which are much more easily discernable. Might be a resolution/font issue with just the way point display.

Thanks, haven't had a chance to try this. Any word on an official fix for this? Of in not mistaken, there are other reports of other mappings exhibiting the same one way issues when mapped to joystick.

In short; the resolution of the little display that shows the active way point has such low resolution that it's hard to distinguish in 1080p, standard zoom/view. For instance, "M3" looks just like "M1". I'm comparison, the numbers on the dial just below are of the same size but easily distinguishable. Maybe something to fix?

+1 What's the story behind this, intended? +1 Very annoying, intended by design?

Don't think so as I don't touch any buttons on an on-runway-from-mission-start take-off. At least I haven't touched any buttons. As per my previous comment, I suspect it was local user (machine) error causing the issue for me, still no issues after plenty more take-offs (maybe I'm just getting better and not pushing things far off the norm to trigger any possible bugs... :joystick:). Thanks anyway! :thumbup:

I've been running with just a simple generated mission starting from the runway. Nothing special. Doing a few more runs now to see if I can re-create it in a sensible way. I've done another 10 take-offs now, I'm starting to suspect it is/was a controller input issue after all. Noticed odd/random drift possibly related to controller calibration, moving all input devices through their full axis just before take-off seems to have resolved it. My apologies for consuming your time. Will do another 10 runs to confirm. (Rudder is still super-twitchy on the runway though... :-))

Cheers, I'll see what I can do. Time is at a premium.

Tested again and experienced the same. Confirmed that it wasn't a joystick input commanded dive. I'm aware that as the landing gear comes up, the flaps are retracted and you could have a little dip. But this happens afterwards, when already at speed (550km/h) and engaging altitude hold. It sits perfect for a while, but after a couple of seconds (5-10s) it just starts diving without any other indication. It seems to happen soon after take-off; airborne, gear is up, speed stable around 550km/h and leveled off at 200-300 meters when engaging the altitude hold mode. For some reason it's not consistent, I get it sometimes - sometimes not. I even caught it once, disengaged altitude hold, leveled off manually and re-engaged. Same thing again. However, once having been airborne for a little longer, the problem doesn't occur. So it seems associated with the first minute or so after take-off. Is there any particular procedure here that I might have missed?

I've also experienced something along this. After take-off, get up to speed, engage altitude hold. After 3-4 seconds of horizontal flight the aircraft decides to pitch down at a rate of about 5 degrees per second, quickly leading to a fast dive. All while altitude hold stays engaged. Disclaimer: I haven't gone through the manual, there is a risk of user error on my part. Although not sure what it would be.

When mapping AFK activation/deactivation to a joystick button, the joystick button can only be used to activate AFK. However, the corresponding keyboard mapping ("J" by default) works as expected, i.e. toggles AFK on and off. The fast disconnect AFK/AA button does work correctly when mapped to joystick. I'm using a CH Fighterstick if it matters. A bug?

Experiencing the same stability issue. Using CH rudder pedals. Issue starts from about halfway to take off speed until take off.