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.

Verge 3.8 appInstance.renderer.setPixelRatio(..) downscaling picture?

Home Forums Bug Reports and Feature Requests Verge 3.8 appInstance.renderer.setPixelRatio(..) downscaling picture?

Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #45794
    precismo
    Customer

    Hi Verge,

    We have noticed that after update to Verge 3.8, our images become noticably more blurry on both Android na IOS mobile devices. Further investigation showed that same settings for appInstance.renderer.setPixelRatio(window.devicePixelRatio) works differently – please refere to screenshot for 3.8 from Android (IOS is experiencing same behavior).

    I would expect that setting pixel ratio to native device resolution would lead to very sharp image (+ slow performance) but it seems that 3.8 is doing further downsampling. This was not happening in previsous Verge versions where image was sharp.

    Im afraid that if we set pixel ratio artificially further up above window.devicePixelRatio, all our repositories on older engine versions will start crashing.

    May I ask how to solve this? Is this new feature of underlying Three.js?

    Thank you very much in advance,

    Petr from Precismo

    Attachments:
    You must be logged in to view attached files.
    #45796

    Hi,
    It’s possible you forgot to apply pixel ratio for postprocessing pass as well which is now required:

        // already have maximum pixel ratio in HiDPI mode
        if (!appInstance.useHiDPIRenderPass)
            appInstance.renderer.setPixelRatio(factor);
    
        if (appInstance.postprocessing)
            appInstance.postprocessing.composer.setPixelRatio(factor);
    
        // to update possible post-processing passes
        appInstance.onResize();

    Soft8Soft Tech Chief
    X | FB | LinkedIn

    #45852
    web
    Customer

    Sorry to hjack this thread. But does that change also affect the “app.enableSSAA(1);”. Because it doesnt seem to work anymore?

    #45854

    No, it should not affect SSAA rendering. BTW I’d suggest using app.enableSSAA(4) to improve quality, since 1 means using just 2 samples for AA.

    Soft8Soft Tech Chief
    X | FB | LinkedIn

    #45855

    In general, I’d suggest sticking to one of these – either increase sampling ratio or use super-sampler AA for your app. Not both.

    Soft8Soft Tech Chief
    X | FB | LinkedIn

    #45950
    precismo
    Customer

    Thank you very much Alexander, this fixed the issue!

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