Drawing and Loading: One of it in a thread; Possible?

[Tenry]

I am currently working on some code which should show something on the screen (animated) while resources are loaded.
To have a clear animation which is not interrupted by loading resources (which might take some ms per resource) I do one of the two tasks in a separate thread.

Now I'd like to know how I should manage it. I tried to let the main program create the window, start the thread and load resources whereas the thread draws a sprite on the screen, but I get some OpenGL error in the console:

Code: [Select]

An internal OpenGL call failed in Drawable.cpp (399) : GL_INVALID_OPERATION, the specefied operation is not allowed in the current state
I suggest I must draw in the same thread where I created the window, but the same thread must be responsible on loading images I suggest...

Any solutions / tips on this?

[Kingdom of Fish]

All drawing has to be made from the same thread, set the worker thread to load data instead.... there are texts about it on the wiki.

[Tenry]

All drawing has to be made from the same thread, set the worker thread to load data instead.... there are texts about it on the wiki.

Oops, I haven't taken a careful look in the wiki  :roll:
Thanks ^^

[Laurent]

This is not true, drawing can be done from other threads. The only thing to care about is to deactivate (SetActive(false)) the window in the thread where it is active, before activating it in another thread.

But however, it is simpler to load images in a thread and leave the rendering in the main thread.

[Kingdom of Fish]

Oh, sorry  :oops:

[Tenry]

This is not true, drawing can be done from other threads. The only thing to care about is to deactivate (SetActive(false)) the window in the thread where it is active, before activating it in another thread.

But however, it is simpler to load images in a thread and leave the rendering in the main thread.

Okay, but I have it already changed that the thread loads the stuff while the main program draws on screen.

By the way, I found an old post:

I first thought it was not a good idea, but then I realized that it could easily be done without altering the public interface, nor requiring extra calls from the user.

I modified the code so that internal OpenGL textures are now not created right after loading, but rather on first use. So that loading can be done anywhere with no restriction.

Thanks for the idea

Does that have any effect (e.g. some ms delay) when first drawing it on screen? Or does the texture creation happen when I assign an image to a sprite? Or jas something changed since then?