Forum Replies Created
-
AuthorPosts
-
shantiscriptCustomerHi, i just tried the update and for one of my scenes the loading time increased dramatically. From 13 seconds with verge3d 3.2 to 26 seconds with the new version, which is not really acceptable. I tried another scene and similar performance decrease. But then for another scene the loading time went down by 5 seconds.
This is a somewhat unpleasant outcome.
For the teapot header and the scooter the load time went down by 6 to 7 seconds.For all scenes tested I get a warning in the browser console. (I tried this with Brave browser and the newest version of google chrome as well as Safari, and get the same warning in all browsers)
The warning is:
v3d.js:1 v3d.WebGLRenderer: KHR_parallel_shader_compile extension not supported.
Chromes version:
Version 84.0.4147.89 (Official Build) (64-bit)(this is the newest version of chrome on osx, the other browser are allso all up to date).
I am running on a macbook with intel i7 from 2013first screenshot below is a wrong screenshot. I can’t remove the old one when editing but attached the right screenshot.
Any insights on this? Is there something in the update that could cause these kind of load differences? Like big texture maps or similar?
I can upload and share the scenes if needed.shantiscriptCustomerHi Alexander,
at the moment i don’t need anything specific from the newer versions. I just wanted to figure out if you keep the base up to date so we can make an informed choice for our dev stack. Its good news for us that you do!!!!!Thanks and best regards
SebastianshantiscriptCustomerYou included a new template for vue.js and react.js
The template is called embeddable, here is a screen shot from your 3.1 release anouncement. The template is in the template folder but doesn’t show up in the app manager?shantiscriptCustomerHi i just updated to verge 3.1
After updating the new Embedabble Template doesn’t show up in the app manger? Is this supposed to be like that or should the template show up by default.shantiscriptCustomerOk i figured out what the problem is. I am using Brave browser which blocks device recognition that somehow causes this error:
https://github.com/mrdoob/three.js/issues/16904
When following the advice in the github issue it works!!
shantiscriptCustomerBy the way I just went through the process of setting up the vue.js example of the template you created. Its working just fine!!!…really don’t know why just running the examples straight through a simple node server is breaking? Maybe need to use web-pack and babel for es6 compatibility?
But embedding the iframe from the VergeNetwork into a simple an html file thats served through a local sever should work no matter of the setup of the local server?
Also tried to use a python flask server to serve a simple html file and embedd the vergeApp…same errorshantiscriptCustomerHi Thanks for the quick reply..very appreciated!!!
I ran both tests without error. And i attached the exact error as screen shot. It seems to be exactly the same error you created deliberately ??
I did find a way which should make it easy for you to reproduce the error, unless this is a problem with my local machine.
If you use live-serverhttps://www.npmjs.com/package/live-server
if you install it globally with
npm install -g live-serveryou can just navigate to the verge3d installation folder and launch one of the examples from inside the application folder
`live-server teapot_heater’
i am running node version v13.8.0
…by the way verge3d is awesome. We just discovered it recently and are exited about the potential it opens up
shantiscriptCustomerOne adition. I uploaded the test app to the verge3D network. Created an embedd section in a static html file. If I load that file statically by just opening it in a browser all works fine.
But if i serve that file locally through my node.js express server i get the same error again and the scene won’t load which is really strange??? -
AuthorPosts