With a DLL you could load a mesh in a separate thread.
1. Call a dllfunction that starts loading a mesh into memory using a separate thread.
2. In your "while loading" loop, call the dll and check if the fileloading has finished.
3. When the loading has finished, start reconstructing (using blitzcommands) the mesh using meshdata from memory.
If the mesh is large you may have to do the reconstruction in small pieces a time,(to let blitz do some rendering and stuff in between)
This is just a theory, but I believe it could be done.
At least for meshes and textures/images.
Sounds will be harder, as you can't create sounds using code in blitz.
The question is if it's worth all the work.
[Edit]
Sorry Almo!
I saw your post after I posted mine. :)
1. Call a dllfunction that starts loading a mesh into memory using a separate thread.
2. In your "while loading" loop, call the dll and check if the fileloading has finished.
3. When the loading has finished, start reconstructing (using blitzcommands) the mesh using meshdata from memory.
If the mesh is large you may have to do the reconstruction in small pieces a time,(to let blitz do some rendering and stuff in between)
This is just a theory, but I believe it could be done.
At least for meshes and textures/images.
Sounds will be harder, as you can't create sounds using code in blitz.
The question is if it's worth all the work.
[Edit]
Sorry Almo!
I saw your post after I posted mine. :)