Hi Guys, anyone bought a VelocityOne Flightdeck yet? If so what are your thoughts?
David.
Yes, and was unpleasantly surprised to find it didn’t come with any kind of config for MSFS, nothing. You have to map every button and control yourself. That’s great for down the line when I want to do that, but without that, I doubt i will be keeping mine unless they release some very, very soon, (even with the nice fit and finish it has.)
Has anyone independantly released any configs?
Even my Honeycomb Alpha and Bravo came with great configs…
came looking for flight deck setup info. No joy, back to control mapping hell, how can setting up a simple throttle be this hard…
1 Like
Thank you for replies. They came alittle late as I decided to pull the trigger before your comments came out.
After using it for a week now I can say that Im over joyed with it. It feels very comfortable in hand and have more buttons and axis to cover all my needs. I agree it would have been better to have at least one profile to use in MSFS but honestly it was ok, it gave me a fresh start to get it how I wanted to use it. I know Turtle Beach get a fair bit of grief over their products but I now have the yoke and this HOTAS and im very happy upto now with the quality and options.
David
1 Like
Presets are basically the job of Asobo - and that is going to be added on SU15 (already currently in beta):
However thing is that anyway the layout won’t fit every aircraft so manual mapping on so many buttons is just not avoidable. While I started from the preset I changed most to everything by now after receiving mine on Friday. I already discovered that mapping on the autopilot buttons is wrong on the preset comparing to the Turtle Beach logic. Think I gonna report that one.
While I in general like the functionalities of the flight deck I’d love to be able to disable the virtual buttons on the lowest and uppermost sections of the throttle. Especially the lowest ones are troublesome if you bind keys for reversers. On the uppermost buttons of the scale I added the afterburner toggle which actually works great on the default F/A18E.
I’d wish Turtle Beach will update their software to be able to also read variables from MSFS/P3D/FSX to make landing gear indications and usage on the screens. Otherwise some mods could make that possible at some point.
Has anyone used this with the Fenix? I’m curious about the throttle haptics on the detents.
Picked one up last week. As of this date, there are bindings for it - don’t know if that’s as part of the next beta or not, though.
I like the build quality more than I thought I would, and the stick doesn’t feel quite as stiff as the standalone Flight Stick product. The heavier base also makes it unlikely you’ll tip it over.
I don’t really care for the throttle axis being 0-65535 as opposed to -32767-32767. It’s HIGHLY resistant to approaches like setting a neutral point to establish a reverse/beta “axis”. SPAD.next was very useful on that front - just set it up with as an axis with reverser and off you go - but it would be nice to not need a third party product.
Speaking of SPAD.next (and I’m assuming that AAO and FSUIPC might be similarly affected) - the virtual buttons you can define on the touchpad do not manifest there, so you can’t add custom actions - you have to set that up in MSFS - so you can’t do things like control the G1000NXi user interface with it, at least not easily.
Finally, dials - they work, but only if you deliberately turn it so each detent stop is neatly hit - if you crank the dial like you’re trying to set altitude, heading, vertical speed, etc., you will find that it “eats” all of the motion and emits a single click event. So, using the dials for such purposes will take time. Lots of time.
Annoying, to be sure, but I do think that these are all things that could be fixed in software. Already have tickets open for it. I think there’s some polish missing but there is a ton of potential. More to follow…
1 Like
Additional thoughts after about 6 weeks with the thing. First, the dial issue, it affects the center dial on the throttle only. The upper (inner/outer ring combined) dial, and the lower dial seem to send (nearly?) all clicks through. The center dial (B-29/30) eats extra dial clicks if you turn the dial quickly. As a result, I won’t map that button until TB get their act together with a firmware update.
The virtual buttons - they manifest as keyboard keys (“Q”, “Y”, etc), so there’s a high likelihood you will conflict with existing keyboard settings. SPAD.next, sadly, does not yet handle this (and I don’t really blame them, because who does this)?
So, what I have here is something of a hybrid setup - my MSFS device configs are created from empty, not based on default. I use SPAD.next for two things - configuring the axis to have a reverser range (which is super easy), and the inner/outer dial on the throttle to G1000Nxi’s FMS dial. Everything else gets mapped in MSFS.
I enjoy it, but it’s annoying in some ways. I see the vision for it but it’s not fully thought through or implemented. We’ll see.
I just got the flightdeck and it is a nightmare to setup… I started a new profile from scratch in MSFS… Assigning both throttles to 0-100% axis (selecting the axis in the drop list as they are not even recognized in MSFS…).
Just tested in PMDG 777 and even though there are no other buttons/axis set, moving the throttles axis would engage the reverse thrust in the 777… this is crazy !
When I’m back on that box I will take some screenshots of my settings. The throttle is working correctly in general, but I stopped trying to map the reverser axis for the 777, rather I’m using the F2 decrease thrust trick.
Now, when I originally purchased this, TB hadn’t released their profiles for the throttle and stick, so I had cobbled together a combo wtih spad.next and a scratch profile - but I found limitations there as well - the soft buttons on the throttle display are encoded as letter keys, but not on the keyboard, so spad has no idea what to do with them.
Since then, TB came out with a default profile and things have been working somewhat better.
For me, my biggest issue is that the rotary encoders on the throttle are inconsistent - when you crank the middle one, it emits continuous click events, when you crank the upper and lower ones, it eats all the extra motion and emits a single click.
You are wrong there are default bindings and you even get the default profiles in MSFS. Ok i hate the default bindings so i remapped them. But others dont. You even get a sheet that has them all on.
1 Like
W.r.t. the difficulties setting up controllers, such as this comment:
Have a look at this post:
and in particular, listen to what Mr Martial Bossard has to say in the livestream about the new functionality in 2024, and the ability to save the configurations in “packages”, which can be shared both by manufacturers of hardware & between users! 
On the 777, I managed to get it worked using Fsuipc… But on the Fenix A320, when throttles are on idle, it shows 50% on the MCDU while calibrating… and on idle, the reverse are slightly engaged… gosh, this thing is getting me crazy.
Ahhh my apologise 
Has anyone managed to setup the throttle to work with the FENIX A320 without using reverse throttles ? (I prefer to assign buttons to engage the reverse thrust).
Thank you.
Not looking to hijack the thread, but this was worth a response - layered settings is something I’d hoped for in 2020 for a long time - now I’m really looking forward to 2024!
Even though the Turtlebeach software shows 0-100% on the axis, when I calibrate them in the Fenix A320, I get 50% when I have the physical throttles on idle…
Now that MSFS24 is out, has anyone mapped out any bindings? I just bought the Flight Deck. My initial thoughts about it are great, but it does look to be a nightmare to map out everything for certain aircraft.
1 Like
I haven’t really, yet. I’m getting used to the SIM and then figuring out what I’d like to set up differently. The basic functionality (control axes, camera controls, etc) seem fine. There are a number of controls (switches on the flight stick base, dials on the throttle base) that are currently unmapped, and I’ll sort that out soon.