-
Notifications
You must be signed in to change notification settings - Fork 0
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
Add new landmarks renderers #218
Conversation
0326f48
to
b3cac8b
Compare
src/main/kotlin/solve/rendering/engine/core/batch/RenderBatch.kt
Outdated
Show resolved
Hide resolved
src/main/kotlin/solve/rendering/engine/core/input/PointLayerClickHandler.kt
Outdated
Show resolved
Hide resolved
} | ||
|
||
fun initializeFramesRenderer() { | ||
CoroutineScope(Dispatchers.Default).launch { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
can it be canceled?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a problem with rendering process. The FramesRenderer
needs to initialize a textures array on a GPU side before it can render frames, and it requires some time. The problem is that if we try to execute PlanesLayerRenderer
(which also works with textures) at that time, the textures array of FramesRenderer
doesn't initialize correctly, and we get "black" frames. I spent a lot of time on this bug, but still haven't figured it out.
fun initializeFramesRenderer() { | ||
CoroutineScope(Dispatchers.Default).launch { | ||
isFramesRendererInitializing = true | ||
delay(FrameRendererInitializationDelayMillis) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
where is the real init process?
59ad3c2
to
d997fe9
Compare
2024-04-10.00-17-56.mp4