-
Notifications
You must be signed in to change notification settings - Fork 62
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
Is it possible to support automatic reload? #163
Comments
It should already do this. Does it not do it for you? |
I had thought that this would already be enabled, but as far as I can tell, it is not. Here's the setup:
One thing to note. I am overwriting the file. I am not updating the contents of the glTF file. I did the same test, but after regenerating the glTF, I just clicked on one of the other engine buttons without closing and re-opening the 3D preview. In this case, when the new engine's display came up, the updated results were visible. Switching engines loads the latest. But the current engine does not update its visualization when the file is overwritten. |
Gotcha. I've submitted a fix. |
Version 2.2.6 is published. |
One more data point here. When I first loaded the update, it didn't seem like the fix worked. Then I realized that the changes I made to the gltf were changes that would only change the |
Yeah, I don't think this one is easy to fix. The bin file isn't loaded by VSCode and thus it doesn't know that the file has changed. |
We could use fs.watchFile after collecting all the uris in the glTF. |
Hmm, good idea. I'll try it out in a bit. |
This extension is fantastic, and has become an indispensable part of my glTF development kit. The one piece that I’d be interested to know whether it is possible to develop is automatic reload. When I’m viewing a glTF file, it would be ideal to have the extension’s view reload when that file changes on disk.
Apologies if this has already been suggested or already works. I’d be happy to contribute if there is a straightforward path for how to do it.
The text was updated successfully, but these errors were encountered: