The current bookmark system catastrophically overrides all viewports in multi-viewport scenarios. Example：
Pressing 1 in Viewport 3 (after setting Bookmark 1 in Viewport 1) should only reposition Viewport 3
Actual Behavior: All viewports (even top-down Viewport 2) are forcibly overwritten by Bookmark 1
Critical Consequence: Original positions of other viewports are permanently lost with no undo option
Requested Improvement:
Rebuild the bookmark logic to support “active viewport-exclusive response” —— shortcuts should only affect the viewport where activated, preserving all other viewports’ states.
Thank you for raising this. From what I can tell, this is expected behavior based on the current implementation in BookMarkTypeActions.h and it hasn’t changed since the introduction of UE5. The default logic applies the bookmark to all level editor viewports, regardless of which one is active.
That said, if you’d like to localize the behavior so that the bookmark only affects the focused viewport you can customize the JumpToBookmark method like this:
virtual void JumpToBookmark(UBookmarkBase* InBookmark, const TSharedPtr<struct FBookmarkBaseJumpToSettings> InSettings, FEditorViewportClient& InViewportClient) override { if (UBookMark* Bookmark = Cast<UBookMark>(InBookmark)) { // Set all level editing cameras to this bookmark for (FLevelEditorViewportClient* LevelVC : GEditor->GetLevelViewportClients()) { bool bIsCurrentViewport = LevelVC == &InViewportClient; if (bIsCurrentViewport) { // If the viewport is focused, apply the bookmark to it ApplyBookmarkToViewportClient(Bookmark, LevelVC); } } } }With this change in place, only the active viewport is repositioned when invoking a bookmark and the others remain unchanged.
Thank you, the code has been verified to be highly effective, and it works equally well for the quad view (three orthographic views plus perspective view) within the same viewport.
However, I sincerely urge you to consider implementing this modification in the official engine. Please experience firsthand how frustrating it is when switching bookmarks across two viewports working collaboratively——as demonstrated in the video (20250610_1007.mp4). I believe there is virtually no practical need for this forced synchronization. If required, users could simply press the bookmark hotkey in another viewport—a process taking merely one second. Without this code fix, all views display only one bookmark result, which completely undermines the concept of multiple viewports.
Thank you again for the feedback and for highlighting the value of this improvement.
I’ve passed your request along to Epic for internal review. Please note that feature requests like this can take time to be evaluated and may or may not be prioritized for future engine updates. If I receive any updates or confirmations from Epic regarding this suggestion, I’ll make sure to follow up here in the thread.