This bug re-appeared when installing 1.5.3. It disappeared without any specific reason after multiple launch.
Still happening for me on 1.5.3.0.
I was still not able to reproduce it today. Maybe I should tell, what I am doing at every (!) Beta Update.
- Wipe SceneryIndexes
- Wipe StreamedPackages
- Wipe WASM caches from all Addons (only WASM, not work folder)
- Wipe LocalState/Cache folder
- Wipe Rolling Cache
- Wipe DXCache
- Wipe D3DSCache
Maybe that makes the difference.
So far I havenāt been able to reproduce the problem with the current SU3 beta build 1.5.3.0.
Launched the sim multiple times, spawned at different airports, switched to drone mode via the binding on my Alpha yoke - no problem. On the previous build I could trigger it 100%. Letās hope the fix sticks.
Iāve definitely experienced it on 1.5.3.0 with an empty Community folder so not sure where the inconsistencies are. Unfortunately that always makes it tougher for devs to fix, but Iāll keep trying in future builds.
I had this happen while I was testing something else at the weekend. Like before, if you use the UI controls in the top menu it never does it, and the keyboard shortcut will work fine after that.
But if you go for the keyboard option straight away you are sent to water world. Oddly though its not every flight, I think. And also its not really the drone camera proper as you cannot move or cast you view about like you can in the drone camera mode.
My drone also goes weird not every flight but intermittent itās miles away out at sea and looks like itās between the sea and the sky.
Specifically it is at latitude/longitude 1.0000,1.0000
On Xbox Series X 1.5.3.0, I was able to trigger the Lat 0 / Lon 0 jump by activating the showcase camera whenever I used an aircraft or scenery I havenāt used before - it also happens when I activate the showcase camera for the first time via the drowpdown menu instead of the shortcut key.
In my example:
- Loaded A330 in into default LSZH for the first time since updating, using hotkey = teleport
- Next time loading in A330 into default LSZH, using hotkey = no teleport
- deactivated default LSZH, activated FSDreamteam LSZH
- Loaded A330 into FSD LSZH = 0/0 teleport, regardless of hotkey or drowpdown menu activation of showcase camera
- reloading flight = no more teleport
Is someone able to reproduce these steps as well?
Yes, I posted before that it always happens for me when using an aircraft for the first time. If I want to reproduce it, I just pick a random aircraft I never flew before and enable the drone view with a joystick shortcut and always get the bug, so itās easy for them to reproduce it.
Iāve never had it happen via the top menu, and Iāve had it in planes Iāve flown hundreds of times.
The only way I have found to stop it from ever happening is to use the top menu first, then the keyboard shortcut works as expected.
Is still happening for people after todayās new SU3 Beta build?
Yes, still happening. Looks like none of the important bugs were fixed.
For me, the problem is no longer reproducible since version 1.5.3.0. Previously I had it on almost every flight. Since then, not at all.
Still present in 1.5.4.0.
Just updated the sim and loaded into the default Max at the default KDFW. Shftt-X did NOT trigger the drone cam bug.
So I ended that test and decided to try the same at Flightbeam KSFO. Sim CTDād as soon as I loaded in right as the yellow button was about to appear.
(I believe this CTD issue is something unique to my system and involves GSX, as it does not occur at every airport or aircraft, but does occur frequently with the MAX, but only so long as I have GSX installed).
I havenāt had any issues with the Drone Camera before, and I still donāt experience any problems after updating to SU3 1.5.4.0
Iāve tested it using keybinds assigned to both
āToggle Drone Cameraā
āToggle drone"
and I havenāt encountered any issues on my end.
The team so far has been unable to reproduce this issue - here are the locations and aircraft we tried it in:
Airports:
- KSEA
- KJFK
- LHBP (with the associated marketplace item installed)
- LFMN
Aircraft
- C172
- Draco X
- C400
- H125
If you are running into this issue in the newest Beta Builds, weād love to see if you could provide as much detail as possible on where it happens: Coordinates, aircraft, weather, peripherals, etc.
2 Likes
Iāll test and see if I still get this bug in the latest build.
Loaded in at KCID in the 777F, pressed the drone toggle keybind and the bug didnāt happen, so I exited out of the flight.
I then reloaded at KCID in the 737 Max, and pressed the drone toggle keybind, and the bug did happen.
Here is what I see after pressing drone toggle. Iāve had this happen during the daytime where it just shows me over water. This screenshot is at nighttime with that orange horizon line over water.
I am using the drone toggle keybind, not clicking the camera button in the toolbar.
