Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Strange transition behavior on the second replay #108

Closed
Morgerion opened this issue Jan 31, 2024 · 5 comments
Closed

Strange transition behavior on the second replay #108

Morgerion opened this issue Jan 31, 2024 · 5 comments

Comments

@Morgerion
Copy link

Situation: there is a project in which transitions between windows are made through black. To make the implementation work as convenient as possible, it is done through the third window "black", which simply contains a full-screen black node.
Everything works correctly, but in one case a strange thing happens - when you reopen the window, its contents start to be displayed after the transition is complete.

test1.mp4
test2.mp4

This is strange, because the log file shows that window initialization occurs at the moment of transition start, and a dozen frames pass before transition completion. But during these frames the window is not on the screen. But after the transition is completed, it appears suddenly.

test3.mp4

The conclusion I made after studying this situation is that the window is processed correctly when restarted, before the transition starts, but REALLY appears on the screen only after the transition is completed.
It is not clear where the window is during the transition - but it is not on the screen, that's a fact.

I have already encountered this behavior of monarch in another project of mine.
General conclusions:

  1. this behavior occurs only if "*.script" and GO-objects are present in the collection.
  2. if the collection contains only GUIs, there are no problems with transitions.

P.S.
I apologize for the google translation in video, my English is not good enough to explain it clearly.

@Morgerion
Copy link
Author

Morgerion commented Jan 31, 2024

I can send access to the project on github, I need your email for that.

@britzl
Copy link
Owner

britzl commented Mar 9, 2024

I have already encountered this behavior of monarch in another project of mine. General conclusions:

  1. this behavior occurs only if "*.script" and GO-objects are present in the collection.
  2. if the collection contains only GUIs, there are no problems with transitions.

Very strange. I don't quite understand what the script files have to do about anything, unless perhaps there's some code in the script that blocks the main thread or something?

I can send access to the project on github, I need your email for that.

I would prefer if it is possible to reproduce in a minimal project of some kind. Can you reproduce it in a test project?

@Morgerion
Copy link
Author

I have a project where everything is working correctly.
It has a direct launch: "lobby" -> "black" -> "gameplay".
There everything works correctly always.

But everything is different in the project, the video from which is demonstrated here. Here the launch of transition to "gameplay" happens from "popup". That is, the "popup" closes first, and then the transition to "black" starts. This is probably the only significant difference.

I have some ideas, I'll think about it and post here.
And also I will put together a minimal example of the project.

@Morgerion
Copy link
Author

I've managed to overcome this problem.
The problem turned out to be project-specific (because the same solution works stably in another project).
The solution was strange, but the main thing is that it works.

@britzl
Copy link
Owner

britzl commented Jun 11, 2024

Good to hear that you managed to solve it. I'll close this bug report.

@britzl britzl closed this as not planned Won't fix, can't repro, duplicate, stale Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants