Summary
I’ve created a Fortnite map that uses the RR_Vehicle device (so I’m NOT making a Rocket Racing map, this is a Fortnite experience) that was close to release, and the vehicle no longer works as expected as it completely ignores all set parameters of the RR device (top speed, acceleration, drift, braking, etc).
It obviously worked before while I was creating the map and testing it in Edit mode.
Now, when playing it in Edit mode, the vehicle settings are ignored.
I’ve recorded a video demonstrating the issue in my map, where I state the various ways I tried to resolve the bug. There is a second bug mentioned but I’ll make another bug report for that (perhaps a bit later so I’m not flooding the forum with just my issues). But I do think this second issue may give a clue as to how to fix this bug on Epic’s end. The second bug is demonstrated at the end of the video.
Please select what you are reporting on:
Unreal Editor for Fortnite
What Type of Bug are you experiencing?
Assets
Steps to Reproduce
In a pre-existing map where you’ve implemented custom RR Vehicle behaviour, run the map in Edit mode and note that it may no longer obey the custom parameters for the vehicle.
Expected Result
The expected result is that the custom parameters (like top speed set to 0.2 instead of 1.0) would result in a car with a lower top speed when playing.
Observed Result
The observed result (as demonstrated in the video) is that the custom parameters are ignored.
Platform(s)
Tested on PC and Xbox Series X
Video
Additional Notes
The second bug (in which if the vehicle is destroyed, the player disappears and the camera is fixed in the same spot the camera disappears and is in first person mode and locked) persists across play sessions. When that bug appears, and I redeploy the project again, Fortnite resumes from that exact same position with the exact same bug. Perhaps this may be a clue as to what the problem is?