As i said, it doesn't wait for them to load every time, you're getting confused. Check chrome://cache and you'll see the model files are kept there too. They're cached but the cache is only used while online (at least in chrome) to speed up the page load significantly. The reason for this i presume is so that it can check it's cache is up to date before using it (or else it could be using out of date files without knowing). This is why the first time you load the game it takes a long time, but after that the models load relatively quickly (theres still a short access/check time, but it's only a second or two). I'm talking specifically about "work offline" which is something chrome doesn't automatically do anyway unless you tell it or use a plugin.
Also, the game starts if the textures/models haven't loaded yet because that's how you set up the project. Q3D supports async downloading of all the models flawlessly, but you can make a loading bar which shows the download progress relatively easily with like 3 events.
There are a few ways you can make a loading bar:
on a different layout with Q3D Master, or on the main layout, whatever you want (this depends where you want the bar to show, and when) Run the actions that starts downloading all the necessary models
-> Q3D Master actions: "--> load model" this action downloads the specified model and parses it, then saves it to memory for the rest of the project duration.
you can call this action multiple times for different files one after another, and it makes a stack, loading the first file first, second second, etc. until it's done.
you can get the progress of the download from Q3D Master expressions in the "Loading" section:
the 4 values you can currently get for the loading process are:
loaded items: the number of items that have been loaded so far.
loaded filename: the filename of the file currently being downloaded.
load status: the state of the load.
load total: the total number of items that have been loaded into the project so far.
Note that when Q3D Models automatically download files they're added to this queue as if the "load model" action was called from Q3D Master, it just conveniently does everything for the user if "autoload : yes" is specified, which is the default. You can also have a loading bar that shows even if you never use the Q3D Master load actions (i.e. it can just work using the models auto-load feature themselves if you dont feel like making a layout to call load model on all the project files a bunch of times)