obsproject / obsproject/obs-studio

Undo/Ctrl + Z and Redo/Ctrl + Shift + Z completely broke the scene layout and don't respect the history or the things to undo/redo

Open
#10,120 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
76.4k
Forks
10.2k
Avg merge
4d 23h
Merged PRs (30d)
12

Description

Operating System Info

Windows 11

Other OS

No response

OBS Studio Version

30.0.2

OBS Studio Version (Other)

No response

OBS Studio Log URL

https://obsproject.com/logs/XARI8wOo1un5ORMi

OBS Studio Crash Log URL

No response

Expected Behavior

When undoing a change, that the change is undone. When redoing a change, that the change is redone.

Current Behavior

It is completly messed up. Things are not undone in order, some changes are never undone, some never redone, some redone but incorrectly...

Steps to Reproduce
  1. Move an object
  2. Move another object
  3. Undo 2x
  4. Redo 2x
Anything else we should know?

I cannot reproduce it on a blank new scene, but I can every time on another.
Please have a look at https://youtu.be/G0OB2JKy9cs
This fuc*ed up my whole scene with ~20 objects precisely placed, two times. The first time when I added a new source, moved it, then pressed Ctrl + Z. Everything broke. I then carefully replaced every thing at its original place, but during the process had to undo a change, and it messed up EVERYTHING for the second time. That is REALLY ANNOYING.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the provided OBS Studio log and video, then reproduce the issue in the affected existing scene rather than a blank scene. Follow the listed sequence of moving two objects, undoing twice, and redoing twice. Done means undo and redo follow history in order and preserve the scene layout.

Written by the indexing model from the issue text.

Assessment

Tech stack
c
Domain
desktop
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.