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
If a character is positioned below the bottom edge of the screen (completely off-screen), then a speech overlay created by Say command (with Lucas-arts speech style) is not clamped to the visible screen bounds, and apparently is displayed off-screen as well.
This behavior contradicts to other cases, when the character is behind topmost, leftmost or rightmost screen edges, in which case the speech overlay is repositioned to the closest position which is still on screen.
EDIT: I did not test if there's a difference whether character is beyond room's bottom, screen's bottom (there's a case of scrolling room), or room viewport's bottom (in case of a smaller viewport).
AGS Version
Any 3.* version, at least since AGS 3.2.1.
Expected behavior
If character is off-screen, the speech should be consistently displayed at the closest on-screen position.
The text was updated successfully, but these errors were encountered:
Problem
If a character is positioned below the bottom edge of the screen (completely off-screen), then a speech overlay created by Say command (with Lucas-arts speech style) is not clamped to the visible screen bounds, and apparently is displayed off-screen as well.
This behavior contradicts to other cases, when the character is behind topmost, leftmost or rightmost screen edges, in which case the speech overlay is repositioned to the closest position which is still on screen.
EDIT: I did not test if there's a difference whether character is beyond room's bottom, screen's bottom (there's a case of scrolling room), or room viewport's bottom (in case of a smaller viewport).
AGS Version
Any 3.* version, at least since AGS 3.2.1.
Expected behavior
If character is off-screen, the speech should be consistently displayed at the closest on-screen position.
The text was updated successfully, but these errors were encountered: