Joby S4 - moving and crashing before clicking "Ready to fly"

ISSUE DESCRIPTION

The Joby S4, when starting a flight using the “On Ground - Ready for Take Off”-option, sometimes starts moving and crashing before you even click “Ready to fly”

FREQUENCY OF ISSUE

It doesn’t happen every time and unfortunately I can’t really see a pattern. I fly the Joby a lot and I estimate that the chance of this happening is about 15%. And, AFAIR, it only happens when I depart from either a helipad or a custom location. Can’t remember that it ever happened when departing from a runway, but I’m not 100% sure about that.

REPRODUCTION STEPS

Please list clear steps you took in order to help our test team reproduce the same issue:

  1. Set up a flight starting from a helipad or custom departure location.

  2. Click “Start Flight”

YOUR SETTINGS

If the issue still occurs with no mods and add-ons, please continue to report your issue. If not, please move this post to the User Support Hub.

No mods or add-ons (not available on PS5)

What peripherals are you using, if relevant:

Non, just the standard PS5 controller

MEDIA

Please add a screenshot or video of the issue occurring.

Your throttle should be at zero or as close to idle as possible. Please see the test case below. When I enter the cockpit, my Quadrant’s Throttle Axis is set to zero and you can see I’m completely stationary as the aircraft powers up automatically since there’s no way to start completely Cold & Dark on a helipad (known sim bug).

As I move my throttle using my hardware controls or with the mouse on the virtual cockpit controls - if I exceed the half-way point on the axis, that is enough for the Joby to start rolling since it doesn’t have wheel brakes. Otherwise it’s completely stationary as long as the throttle is closed.

I’m aware of the throttle issue and that you have to bring the dot to the middle position.

But this happened, as clearly visible in the video, before I clicked “Ready to fly” and therefore before I control the plane.

It might be that this is yet another Playstation specific issue that needs to be worked out. See my comments on your “experience” thread.

Yes, this could indeed be a PS5 specific bug.