Do you mean the throttle animation is oscillating? Or is the thrust level also changing?
Throttle animation keep shaking inside the cockpit but also on the sensibility screen
Thrust level seems to be fine.
I didn’t experience any throttle shaking. Do you play in vr?
No. Maybe its something with he HOTAS 52 not the airplane.
Tried on other similar planes tha same thing happens.
On the sensibility screen shakes like crazy. no matter what i do.
Since im not used to this controller, kinda lost here.
If it’s shaking in the sensitivity screen, that would indicate that the hardware itself is noisy. Maybe try spraying some compressed air into the base, im not too familiar with that stick.
The X52 has this problem. I see it all the time in the Fenix and the FBW A320. Throttle is just noisy. Not a bug with the plane.
So its seems to not affect at all the thrust power. I guess ill leave like that.
I only use this for the F-22 / F-16 / T-45
Quick question, are you switching airport in Dev mode, or through the main menu?
That is an interesting bug… Volocopter, as far as we can tell, is the only Asobo default aircraft that uses wasm.
Yesterday I installed the Beta to see if it helped my issues with the F-22. It helped but did not fix it. However now I can just load into a Cessna or whatever and the controls will work and then I can go to the main menu and get back into the F-22 and it all works as intended. Hope in another plane first and load into the sim and then hop back out and get the F-22 and enjoy. They will get it sorted I am sure. But for now that is what I do.
So I checked my settings; no auto rudder and set the deadzone at 10% as well as the sensitivity down by 40% (-40%). I get the same behavior as when the deadzone is at 0% and the sensitivity is at 0%. I might be reading the wind indicator wrong, but the plane was turning into the wind.
Here is a short video, with control inputs being performed and with deadzone at 10% and sensitivity at -40% for both rudder axis as well as nose wheel steering axis (which have different inputs on my controllers):
Thinking the wind might have been pushing on the tail, I just tried again with the wind coming directly at the nose of the plane at 8 knots. The plane still veers left on the runway. Given that in the video it veered right (first time I’ve seen it do that - it’s always been to the left every other time), it seems to be tied to something, but it’s unclear what that would be.
I have the exact same problem
No assistance at all, sensibility at -50 and a 10% deadzone
The aircraft always go to the direction of the wind and it’s not possible to make it takeoff in line
PC Version - my experience with the addon
Darn, the Secondary Displays go blank when trying to use Logitech Multipanels. Oh well, it still flies as expected without secondary displays. Everything seems to work as intended if I don’t launch the Logitech Multipanel driver software. If I do forget and launch the Logitech software, I shut it down and restart the flight - then everything works as intended.
I didn’t experience nor observe any of the control issues experienced by several others (using the Thrustmaster Warthog and TPR), and the autopilot and gps navigation appear to be functioning as intended for me.
Since the systems and performance are classified, I can accept and appreciate the creative effort in the addons simulation. The “hidden” access to the G3000 panel is nonintrusive and appreciated, for the funtional use of the addon within the MSFS world.
I like this addon. It’s a solid release - at least for me.
Hi Guys!
To all with lockout issues, this fixed it for me for good!
Go watch this and enjoy the full-blown FBW model thereafter. Worked like a charm for me…take-off in line, flight dynamics and controls, thrust-vectoring simulation - all up to the mark.
Great job @Dakfly0219 and Top Mach Studios !!
thanks for the video, going to check this out.
What exactly is this “fix”, i cant find it.
Yeah, there was nothing in there about a fix. All he did was try the non-FBW version to see if his controls locked up on that version, which they didn’t.
All, we are working on a hotfix for the controls lockup issue. Testing is in progress. If we confirm that performance is improved and or the problem is resolved, this will be provided as an update via Justflight. Thank you for all of your support and patience.
Assistance menu options displaying Volocopter when Raptor loaded into a flight. This is confirmed due to a flag we use to prevent the assistance options menu from being used to enable assistances for the Raptor. This is done because they do not play nicely with the FBW system (like auto-rudder and other pilot assistances that affect aircraft controls). This was confirmed in two other aircraft where this flag was added for testing as well as in the IFE F-35, which also uses this flag for similar reasons. Asobo apparently overwrites the header field for each assistance menu item with “volocopter”, which is a strange bug, but appears harmless.
When in the main menu, can you please double check that all of your piloting assistance menu options are set to Off or Hard (whichever is removing an assistance) and then try again?