[BUG] Fade slope node behaves unexpectedly when dragging with CTRL pressed

FMOD Studio
1

Hi!

Apologies if this has been reported before. A search did not reveal similar issues.

Occurred in FMOD Studio 2.02.16, 64bit, Build #135072
Windows 10 Education 10.0.19045 Build 19045
Dual screen setup, (occurred with FMOD on both screens)

Steps to reproduce:

  1. Make a new event
  2. Add a timeline sheet
  3. On a timeline track add a new instrument (Reproduced with single, multi and scatter)
  4. Drag a fade-in on the instrument
  5. Drag the ‘curve node’ of the fade-in in a circular motion, note it behaves as expected
  6. Drag a fade-out on the instrument
  7. Drag the ‘curve node’ of the fade-out in a circular motion, note it behaves as expected
  8. Hold CTRL
  9. While holding CTRL, drag the ‘curve node’ of the fade-in in a circular motion,
    note that the fade-out node is moving together with the mouse translation (in both axis),
    ending up in a position it is not meant to be (not centered on the fade curve)
  10. Once this behaviour is present, either with or without hold CTRL, dragging any of the ‘curve nodes’ will end up displacing the opposite node in a similar fashion, until the instrument has been deselected or moved

As a new forum user I could not upload a video, but I added a screenshot of the behaviour:
FadeNodeBug

Greetings to the team.
Dries

2

That is a bizarre bug - and you’re the first person to notice it!

Thanks for bringing this issue to our attention. I’ll add it to our bug tracker to be fixed in an upcoming release of FMOD Studio.

1 Like