SneakyBastd

Holy crap! Has anyone else been able to replicate this? I'll definitely try this tonight with my 1080Ti. How can it just suddenly start utilising the GPU like that lmao?!?!? And if you run WITHOUT steamvr, how is the head tracking? I just assumed it would be crap without it??? Edit: Nevermind, apparently you can still have lighthouse tracking without steamvr running. I didn't even know that!

I just upgraded to a Pimax 5k+, and the sky instantly redraws after exiting F10 map view. It just goes straight back to cockpit view instantly, perfectly rendered, as you would expect. It just works, and is obviously a nice bonus to have. But on the Vive the sky would take a second or two to redraw after exiting F10 every time. So this could be due to the headset you use for some reason.

Thanks for that Voight. I've read about people trying different render resolutions, like 0.5 in pitool and 200% in steamvr. Is this still recommended for... reasons? If it's a little more efficient one way or the other, I'll happily take it.

I'm using 1.0.1.129_212 atm. The installer seems broken though, because I ran pitool after installation and one of the screens said I only had a partial install! I couldn't get the headset to work. So I uninstalled it, put on 1.0.1.91, and then installed 1.0.1.129_212 over the top of it again. It updated my firmware to 2.1.255.212. It works well in DCS (which is my only real concern). But some games like Everest won't work. It comes up double vision. I enable Parallel Projections, and the screen is just blank. TheBlue won't work at all, even though the mirror to 2D screen DOES come up, the headset is again, blank. Welcome to pimax software I guess? lol. Other games, like The Lab, run perfectly.

Hi all. Just got my 5k+ and tried it for the first time on DCS. I was concerned about getting a playable framerate, but it's running quite well! I'm getting over 40fps on our multiplayer server. Usually 45-50 if higher up. This is with no real experimentation yet for more fps. Normal fov, 100% in pitool and steamvr. So I'm happily surprised! The fov really is damn nice to have, and everything is a little crisper and clearer than my vive. So if you're worried you don't have a 2080Ti, it's definitely not a required piece of kit. 7700K@5ghz, 16GB 3600mhz, 1080Ti.

I have a MCG Pro on GF Pro, v0.87.05 and firmware v1.94.9. I've been having an issue in DCS the last couple of days where the pitch and roll axis stop responding for a few seconds. The buttons still work, as does the brake axis and mini stick. Mostly it comes back after a few seconds, but once it went full back and left deflection and it needed a restart to fix it. I spun in to the deck that time. When it happens, VKBDevCfg test shows the axis is definitely NOT moving.So it's likely something going on in the stick itself. It doesn't seem to matter if it's plugged directly into a mobo usb, or a usb hub. Sometimes it's good for an hour or two, sometimes it glitches a few times in a minute. Has anyone else had this or have some suggestions? I don't know if it's a firmware issue, hardware or whatever. Thanks. Update: I just had the first stage of the trigger completely fail on me! I can pull to second stage and that works fine, but first stage is broken. Lodged a support ticket.

The default setup is very light and will flop around all over the place, especially if you have the extension. If you want to keep the throw nice and light, try the other cams. It gives you a better sense of centre.

Thanks all, that gives me a much better idea of what to expect, and watch out for. And backstab, I hope you get your issue sorted quickly. You don't want that sort of rubbish happening on such a premium item. But from everything I've read, Virpil seem to be on the ball. GL!

I do not have their throttle yet, I'm still waiting for an analog ministick version. But I'm curious: 1. How does the throttle axis work in DCS with the detents? When you push forward to full mil, and then want afterburner, is it simply a case of finding that magic spot where DCS engages afterburner and setting the detent at that point? If so, that seems easy enough. But.... 2. How do you set it up so that pushing the throttles from fully back to the idle detent will start an engine, but will not move the throttle above 0%? It seems like you need to program a button to fire as you progress to the idle detent, but have no throttle axis progression until you push further forward from idle. A deadzone in effect, up to where you have set your idle detent, but a deadzone in which a button fires? 3. Are all fast jets with burner using the same axis points for selecting idle/AB, etc? Or do you need to load a profile each time you switch airframe? ELI5 please ;) Thankyou.

Thank you Snacko and Rrohde. That's very helpful, and I'll try it out tonight when I get home. :) Update: OK, I seem to have gotten everything going. Lots of trial and error but it's doing everything I want. MasterMode is an 8 way hat. Gate Cont is a 4 way hat. Brake lever has a button press at almost full squeeze. And the folding trigger fires momentarily on fold up and down! Thanks again for your help, it put me on the right path.

Can you explain how you configure the stick and bind that in DCS? Because when you flip the folding trigger down to the "armed" position (middle) it constantly presses a button for me. That can obviously be bound to master arm ON. When you flip it UP back to the safe position, the button stops being pressed. But it does NOT press another button. There is no way to bind that action in DCS to master arm OFF is there? The folding trigger when fully depressed is fine, it fires a button ofc. I have v0.87.05 and v1.94B. "Enable MCG PRO Trigger", "Safe", "Armed" and "Fire1" are checked. What am I missing here? Thanks!

So I just realised I've had my GFPro and MCG Pro for 1 year now. While I love it, I have still seen nothing that helps me with the folding trigger. Is it still impossible to get a momentary button press to fire when folding up/down? The folding trigger is supposed to be a feature of the grip, yet I barely find a use for it with its current behaviour. :(

Thanks, but I don't think I have any duplicate axes. Not since I checked a couple of days ago anyway, and it was happening then also. But I'll check again tonight.

I'm using the Beta branch, and sometimes while flying the throttle axis will move all on its own. If I drop to idle power (throttle), sometimes it stays at mil (game). Sometimes it will drop to idle as it should, then I look back a few seconds later and its wandered back up to mil again! Very annoying when you are in the break, and you wonder why the hell you aren't slowing down, even though you pulled the throttle all the way back, but the game controls show you are still at mil power. Sometimes it is just out by a bit, say 80% throttle instead of being at mil where it should be. And then at other times it is perfectly fine for over an hour or more. I can't nail down what will make it happen. Happens in both F18 and F15, which I fly the most. I'm using a CH Pro throttle, but I am certain the throttle is good. I soldered the pot contacts, and it does not do this in the calibration utility or in other games. Playing in VR (vive). It only happens in DCS, both single and multiplayer. Anyone else seeing this, or have an idea of how to fix it? Thanks.

Cool setup!

The CH Pro Throttle axis was jittery for me also. It would move on its own, sometimes considerably. After taking it apart I noticed the 3 wires attach to the potentiometer tabs with loosely fitted crimp connectors. I soldered them on, and the axis has been rock solid ever since. A very easy fix if you can solder. And even if you can't it's a dead simple solder for even your first attempt. If you just can't solder, try crimping them on more tightly.

So I just saw this - new firmware for GFPro with MCG/MCGPro: https://vkbcontrollers.com/?p=16623 It's been out for several days. Why no announcement from vkb or changelog? Hoping it fixes the buttons on issue at startup and adds folding trigger options... will try it tonight. Been waiting over 6 months for this, hope it ticks all the boxes.

I set up Gate Cont as a 4 way hat with push by using this guide: http://forum.vkb-sim.pro/viewtopic.php?p=28475#p28475 Hope it helps.

Good news Rrohde. Do you happen to know if the firmware also includes the extra options for the folding trigger? Momentary button presses on folding up/down would be brilliant. I really love my GFPro/MCGPro, and that is all it needs imho to complete it.

You don't use sensor control switch to slew the cursor. Sensor castle is on the stick. You use the throttle mini stick to control the TDC. In axis (maybe hotas?) section it's called something like "throttle designated cursor/controller".

dburne: You will not have "phantom" button presses in game - if you restart the joystick before playing. This is very easy, but it is a little annoying. As soon as I boot up, I run VKBDevCfg. Sometimes a few buttons are on, sometimes not. Sometimes nearly a third of the buttons are on! Press restart, sometimes it takes a few attempts, and that fixes it. Easy enough. But hoping VKB gets this fixed in an official update soon! If I don't reset, I find that certain buttons will not work in game. But I don't have phantom presses activating anything randomly. Note that when I start SteamVR for my Vive, it also screws up the buttons on the MCGPro. Even if it was properly reset beforehand. Something about SteamVR booting up must affect the usb. So I just do my joystick restart once VR is running and I don't have any issues after that.

I've given up waiting for VKB to respond. It's been weeks.... So, is the current beta firmware with improved folding trigger support good enough to use right now? Or does it have problems that make it not worth bothering with? Thanks.

There's lots of ways to handle this. Some people get desk clamps. I decided to homebrew this up, it's just 90mm pvc tubing bolted to a sheet of mdf, with tube caps on each end. I ended up adding two brackets for a little bit extra support, which I found I needed with a couple springs on each axis. It's very stable, and with your feet on the pedals it's not going anywhere. It's cheap, easy to make and does the job for me. https://imgur.com/RRdPC5D

Is there any word on when the next firmware will be released? It's been a long time since the last official update, and I'd really like to get the folding trigger sorted out!

VKB acknowledged this is a bug and next firmware should sort it out. Until then just go into VKBDevCfg and click Reset. Should fix it.