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.

Orbit cam autorotate webGL error and textures missing on iphone X

Home Forums WebGL & WebXR Troubleshooting Orbit cam autorotate webGL error and textures missing on iphone X

Viewing 15 posts - 1 through 15 (of 20 total)
  • Author
    Posts
  • #23772
    samuraijkm
    Customer

    Hi Devs,

    I’ve been updating my verge app with new features and there is a weird bug that was introduced where the textures don’t load on iphone X. My co-worker has iphone 11 and it works fine on his, but my phone turns every object black. I get no texture limit errors and it was working before just fine. :scratch:

    I’ve also got a an auto rotate camera error, I can’t get rid of. The camera switches from orbit to flying camera when clicking the expand button. I switch the auto rotate off before the camera switches but I’m still getting the webGL error, which starts iterating until you exit that view and go back to the orbit camera.

    Lastly, I am still getting a v3d. property binding: animated node error on the expansion icon I just added to the app even though the other animated node errors before are fixed via the latest prerelease update of verge3d. :wacko:

    Here is a link to my web page with the app – O2i verge app

    Any advice would be appreciated.

    Sincerely,
    Jason

    #23773
    samuraijkm
    Customer

    Here is a screen shot of the webGL errors for reference…

    #23824

    Hi samuraijkm,

    I get no texture limit errors and it was working before just fine.

    Unfortunately, we couldn’t reproduce this error so far. It can be possibly related to webgl texture limits. It would be helpful if you show us the webgl system report for that particular device by opening the following page https://www.soft8soft.com/webglreport/

    I’ve also got a an auto rotate camera error, I can’t get rid of. The camera switches from orbit to flying camera when clicking the expand button. I switch the auto rotate off before the camera switches but I’m still getting the webGL error, which starts iterating until you exit that view and go back to the orbit camera.

    I guess the cause of the issue is that the application automatically reenables autorotation after a while. I found that this is programmed in the reset_auto_rotation() procedure by creating a timer “myTimer”. So, the solution here is to disable that timer as well when you need turn off autorotation. You can do that by using the
    “remove timer” puzzle (https://www.soft8soft.com/docs/manual/en/puzzles/Time.html#remove_timer).

    Lastly, I am still getting a v3d. property binding: animated node error on the expansion icon I just added to the app even though the other animated node errors before are fixed via the latest prerelease update of verge3d.

    This is actually was bug in the engine itself and fixed it just now. So, thanks for bug reporting! The error should be gone in the upcoming verge3d preview/release update. I think you can just ignore it by now, since it shouldn’t break any existing animation.

    Co-founder and lead developer at Soft8Soft.

    #23834
    Branden Coker
    Customer

    Regarding the black model/missing environment: I’m able to reproduce it here on a second device. This one is an older iPad Air model MD787LL. Looking at this page:

    https://www.ifm.com/us/en/us/learn-more/temperature/tcc/tcc

    I get this result:

    black model

    There are no lights in this scene. The results look to me as though the environment image is not loading. The scene linked here only has a total of three textures. I’m attaching a screen grab of my WebGL report here as well.

    #23837
    Branden Coker
    Customer

    Well, I just posted an edited response to this, but I guess I got flagged as pending review. :unsure:

    #23851

    Thanks for posting this info. Today we are out of office due to public holiday. We’ll look at this tomorrow!

    Chief 3D Verger | LinkedIn | Twitter

    #23879

    Update: we managed to reproduce this on one of our device. Will try to fix this for the next preview build!

    Chief 3D Verger | LinkedIn | Twitter

    #23882
    Branden Coker
    Customer

    Sounds good, thanks Yuri!

    #24049

    Hi,

    can you check if pre3 works well on your iPhone X?

    Chief 3D Verger | LinkedIn | Twitter

    #24121
    Branden Coker
    Customer

    Hi Yuri, I’m having some strange issues with this application. When I attempted to update the app with pre3, I got the usual dialog to choose which documents should be updated. After clicking OK nothing appeared to be updated (same file modified dates).

    I then attempted to re-export the gLTF files, but I got a series of errors from Blender (2.82), and no file was written. Later I tried to update the files again in the application manager and I got an error stating “Missing app update information.”

    I’ve been using 2.82 and pre3 for most of last week on other projects, and everything seemed to be working fine.

    Here are the errors that Blender returned:

    V3D-WARNING: Object "incoming data" has a non-identity parent inverse matrix. Creating proxy nodes.
    V3D-WARNING: Object "outgoing data" has a non-identity parent inverse matrix. Creating proxy nodes.
    Traceback (most recent call last):
      File "C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons\verge3d\__init__.py", line 140, in execute
        return gltf2_export.save(self, context, exportSettings)
      File "C:\Users\uscokebr\AppData\Roaming\Blender Foundation\Blender\2.82\scripts\addons\verge3d\gltf2_export.py", line 134, in save
        sort_keys=True, ensure_ascii=False)
      File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\json\__init__.py", line 238, in dumps
        **kw).encode(obj)
      File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\json\encoder.py", line 199, in encode
        chunks = self.iterencode(o, _one_shot=True)
      File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\json\encoder.py", line 257, in iterencode
        return _iterencode(o, 0)
      File "C:\Program Files\Blender Foundation\Blender 2.82\2.82\python\lib\json\encoder.py", line 179, in default
        raise TypeError(f'Object of type {o.__class__.__name__} '
    TypeError: Object of type Object is not JSON serializable
    
    location: <unknown location>:-1
    
    location: <unknown location>:-1

    Update: I was able to get rid of the two warnings in lines 1 and 2. I just changed the parenting of those items (deleted two empties). The other errors remain.

    #24130
    Branden Coker
    Customer

    Another update: I was able to update the Verge application by creating a new application and replacing the models with the relevant files.

    The problem is now I’m getting a ton of node errors that all say to reexport the scene. Which takes us back to the problem I posted earlier; can’t export the scene currently from 2.82 using pre3.

    The good news is that all of the shaders are now appearing in older versions of iOS.

    http://localhost:8668/applications/TCC%20rev-2/hippo_test.html

    #24158

    Hi Branden,

    sorry to hear about those troubles. :-( Can you zip your entire project (or make a simpler example) and send it to the enterprise support email?

    Chief 3D Verger | LinkedIn | Twitter

    #24228
    Branden Coker
    Customer

    3.0.0pre3 does appear to fix the black model problem we were experiencing on older iOS versions. We’ve now tested this page successfully after updating it to pre3:

    https://www.ifm.com/us/en/us/learn-more/temperature/tcc/tcc

    We’re working on updating our other app now.

    As for the export errors I mentioned, this seems to be related to the texture input node when selecting an object as the input. I posted details on that issue here:

    Object output for Texture Coordinate node

    #24233

    We’ve now tested this page successfully after updating it to pre3

    excellent!

    As for the export errors I mentioned, this seems to be related to the texture input node

    Fixed that one!

    Chief 3D Verger | LinkedIn | Twitter

    #24305
    samuraijkm
    Customer

    Yuri and Ivan,

    Thanks for working on these bugs and being so responsive in development. As Branden had said, we were able to fix our texture issues and the removing the timer worked great for me as well. I can report that my verge app is now bug free and working on the iphone X! :yahoo:

    o2i verge app

    You guys rock! B-)

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