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

iOS render issues not solved until it will at last support WebGL 2.0

Home › Forums › WebGL & WebXR Troubleshooting › iOS render issues not solved until it will at last support WebGL 2.0

Tagged: , , ,

Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • 2020-04-22 at 3:51 pm #26391
    illussimo
    Customer

    iOS and iPadOS still have some limitations in the number of lights and shaders one can use in WebGL projects. :negative:
    Also, antialiasing can give some problems.
    When using the Verge3D Outline feature, fine details don’t render smoothly on iOS devices and sometimes even look pixelated.
    It seems to have something to do with iOS having troubles with SSAA antialiasing.
    I found this post on the Epic Games forum. Also there it gives problems.
    https://forums.epicgames.com/udk/udk-development/ios-development/280332-how-to-enable-msaa-anti-aliasing-on-ios-for-ipad
    For one of my projects where it was very bad, I could make a workaround but hopefully, it will be solved when iOS will support WebGL 2.0. :unsure:

    2020-04-22 at 5:53 pm #26397
    jem
    Customer

    @illussimo, I wouldn’t hold my breath waiting for Apple to ship WebGL 2.0. Apple could have done this years ago, but choose not to do it. Apple has a history of poor support for open standard APIs. They have deprecated OpenGL and OpenCL on the desktop. They don’t support Vulkan. Apple has its own 3D low-level API called Metal. Based on what I have read, it seems that Apple wants to jump to WebGPU for 3D on the web. I would be happy to be wrong.

    Jeremy Wernick

    2020-04-23 at 6:49 am #26433
    Yuri Kovelenov
    Staff

    Agreed! At least Apple seems to be moving forward with WebXR https://github.com/web-platform-tests/wpt/pull/23031

    Chief 3D Verger | LinkedIn | Twitter

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