You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hey there! I'm experiencing an issue where, while dollycam is active, the camera will snap to a point (frequently below the field/play area) and flail the pitch and yaw wildly. I've looked through the Dollycam documentation as well as the open and closed issues on this repo and haven't found anything relevant, so I'm filing this issue.
I've attached a video of the phenomenon, with the BM console visible as I repeatedly spam dolly_cam_show to print the coordinates to the console.
Here's what I've tried/learned:
The phenomenon occurs only when the dollycam is active. If it is deactivated using dolly_deactivate, it stops on the current camera.
The phenomenon occurs whether the replay is paused or not, though it's noteworthy that sometimes during playback, it will snap out of it to one of the snapshot coordinates in the list and will continue playback correctly.
If you shift away from flycam, it will correctly adjust the camera to the player/camera mode, but will continue to fidget and squirm in an attempt to adjust the camera to these mystery coordinates. This can be used to escape from the flail-hell.
This may be connected to situations where there is no snapshot preceding the current frame (e.g. if the first snapshot in the list is on frame 5000 but playback is started at frame 4000).
The coordinates are not aligned with any of the existing snapshots.
The issue occurs in dolly_interpmode values 0 and 1 just the same.
Interpolation Mode Differences
The issue occurs in nearly all interpolation modes, with slight differences:
On linear interpolation (mode 0), the camera flails as seen in the video.
On nth bezier interpolation (mode 1), the camera starts by wobbling around more slowly before picking up speed over the course of a few seconds and beginning to flail as with linear.
On Catmull-Rom interpolation (mode 4) the coordinate itself is actually much different, tossing me far above and outside the field to (6812025.50, -3130587, 967385.94) before flailing similarly to linear interpolation mode.
On Spline interpolation (mode 5) the camera simply sticks me to the last snapshot in the sequence and does not move at all.
Please let me know if there's anything else I can do to help you reproduce the issue!
System Details:
VC Redist:14.28.29325 (Newest per BM wiki) Rocket League:201009.61933.295428 build 5663619 Injector:v2.1.3 BakkesMod:124 OS: Windows 10 Pro 1909
The text was updated successfully, but these errors were encountered:
Hey there! I'm experiencing an issue where, while dollycam is active, the camera will snap to a point (frequently below the field/play area) and flail the pitch and yaw wildly. I've looked through the Dollycam documentation as well as the open and closed issues on this repo and haven't found anything relevant, so I'm filing this issue.
I've attached a video of the phenomenon, with the BM console visible as I repeatedly spam
dolly_cam_show
to print the coordinates to the console.Here's what I've tried/learned:
dolly_deactivate
, it stops on the current camera.dolly_interpmode
values0
and1
just the same.Interpolation Mode Differences
The issue occurs in nearly all interpolation modes, with slight differences:
0
), the camera flails as seen in the video.1
), the camera starts by wobbling around more slowly before picking up speed over the course of a few seconds and beginning to flail as with linear.4
) the coordinate itself is actually much different, tossing me far above and outside the field to(6812025.50, -3130587, 967385.94)
before flailing similarly to linear interpolation mode.5
) the camera simply sticks me to the last snapshot in the sequence and does not move at all.Please let me know if there's anything else I can do to help you reproduce the issue!
System Details:
VC Redist:
14.28.29325
(Newest per BM wiki)Rocket League:
201009.61933.295428
build5663619
Injector:
v2.1.3
BakkesMod:
124
OS: Windows 10 Pro
1909
The text was updated successfully, but these errors were encountered: