We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Ok, I Agree

getting tons of deprecation errors and super slow load times

Home › Forums › Graphics / Blender › getting tons of deprecation errors and super slow load times

Viewing 8 posts - 1 through 8 (of 8 total)
  • Author
    Posts
  • 2023-08-05 at 7:07 pm #65794
    swatchyb
    Customer

    Hi,
    I have a configurator that I never would have been able to do without Verge (thanks!) and it has been working great until my upgrade from 4.1 to 4.3 and now getting tons of deprecation errors and super slow load times. (10secs vs 2).
    I think I followed the instructions of the 4.0 migration guide properly, and re-exported the primary scene (room) and several product sub components (as gltfs loaded from html – I have >100 glft files for product sub components).
    Anyway, do the below errors give any hint where the problem might be?
    With thanks!

    ps. errors and slow load are in all browsers/ and iOS, but not Android which loads a complex product (12 gltfs) in <3secs. Also, all materials are external to the app.

    Attachments:
    You must be logged in to view attached files.
    2023-08-05 at 8:51 pm #65796
    swatchyb
    Customer

    Just saw and tried BennyHase post re using FXAA and loading time dropped to normal.
    Still get the deprecation alerts though, so help with that would be great. Likely there is more going on.
    Thanks!

    BennyHase

    bennyhase wrote:

    I´ve found another issue with new chrome: If i switch Anti-Aliasing from “Auto” to “FXAA” the loading time (with the actual chrome version M116) the loading time is a lot faster. From 30 seconds to 4 seconds.

    With the old chrome version the loading time was with Anti-Aliasing set to “Auto” also 4 seconds.

    2023-08-05 at 9:21 pm #65797
    kdv
    Participant
    swatchyb wrote:

    Still get the deprecation alerts though,

    That’s because your app is still using old gltf/bin. Maybe you re-exported your files somewhere but your app sees only old files…

    One more possible reason: you didn’t update Verge3D add-on and it exports with old extensions.

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

    2023-08-05 at 10:22 pm #65801
    swatchyb
    Customer

    thanks for the quick reply and suggestion kdv.

    I double checked and the re-exports are being ftp’d to the correct server folder, and I run the browser with Disable Cache checked.
    I also deleted the primary gltf and bin off of the server, refreshed the page to make sure I got a 404 file not found, then re-uploaded the new files and refreshed with same deprecation errors.
    , so pretty sure it should only be seeing the new gltf/bins.

    2023-08-05 at 10:25 pm #65802
    kdv
    Participant

    Share one of your scenes (gltf + bin). The smallest one.

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

    2023-08-05 at 10:34 pm #65803
    swatchyb
    Customer

    sure, these are the primary scene, and the smallest by far.
    thanks!

    2023-08-05 at 10:55 pm #65804
    kdv
    Participant

    Files over 4Mb won’t be attached here. So use Google Drive or some other cloud service and share the link.

    Puzzles and JS coding. Fast and expensive.

    If you don’t see the meaning in something it primarily means that you just don’t see it but not the absence of the meaning at all.

    2023-08-05 at 11:04 pm #65805
    swatchyb
    Customer

    Those should be 28k and 72k respectively. But I can send a link when I am back at my computer thanks

  • Author
    Posts
Viewing 8 posts - 1 through 8 (of 8 total)
  • You must be logged in to reply to this topic.