White semi-transparent PNGs are displayed in grey with krpano Player

[Chris-360x180]

Configuration

Wolvic version: 1.7 Wolvic build ID:

Hardware: Quest 3

Steps to Reproduce

1. open https://krpano.com/releases/1.21/viewer/krpano.html?xml=examples/depthmap/abu-simbel-tempel-tour/tour.xml
2. view the white hotspots that change transparency. They turn to grey.
3. compare white colour it with Oculus Browser. There it is displayed correctly

Current Behavior

Changing transparency of white UI elements in PNG format is quite common in virtual tours made with krpano. The transparency in Wolvic browser turns its white colour unexpectedly to grey. Correct behavior with Oculus Quest browser.

Expected Behavior

Possible Solution

Context

Error Logs and Stack Traces

``` ```

[svillar]

Thanks for the report!

[svillar]

This is Wolvic

and this is Meta Browser

The difference is very subtle. It does not affect user experience drastically, it'd be nice to fix but not a high priority bug

[Chris-360x180]

Hi Sergio, thanks for checking and pointing out. Though the UI example in the temple may not reveal a big difference, for me as a developer of virtual tours and panoramic photographer it’s very important that white stays white in transparent mode. Many UI elements I use for client projects are merely visible in Wolvic because of that grey above photo scenes. That's why I would stick to the Meta browser for now. In future I would really like to shift to Wolvic. Btw, FxR didn’t have this colour bug with krpano. Best regards, Chris

Am 30.08.2024 um 10:42 schrieb Sergio @.***>:

This is Wolvic com.igalia.wolvic.metastore-20240830-103719.jpg (view on web) https://github.com/user-attachments/assets/c2994550-59f3-48a2-b3e4-3cc56fd6a352 and this is Meta Browser com.oculus.browser-20240830-103644.jpg (view on web) https://github.com/user-attachments/assets/6ba2e40b-b022-4c5b-a784-30ffa43cd101 The difference is very subtle. It does not affect user experience drastically, it'd be nice to fix but not a high priority bug

— Reply to this email directly, view it on GitHub https://github.com/Igalia/wolvic/issues/1526#issuecomment-2320513178, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2I7VST7YXANMO5TUW4K32TZUAWA3AVCNFSM6AAAAABNL6VVPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGUYTGMJXHA. You are receiving this because you authored the thread.

[svillar]

That's interesting. It'd be great if you could come up with a very simple use case (the simpler the better) so that we could better understand what is affecting the rendering and causing that color shift.

Hi Sergio, thanks for checking and pointing out. Though the UI example in the temple may not reveal a big difference, for me as a developer of virtual tours and panoramic photographer it’s very important that white stays white in transparent mode. Many UI elements I use for client projects are merely visible in Wolvic because of that grey above photo scenes. That's why I would stick to the Meta browser for now. In future I would really like to shift to Wolvic. Btw, FxR didn’t have this colour bug with krpano. Best regards, Chris … Am 30.08.2024 um 10:42 schrieb Sergio @.***>: This is Wolvic com.igalia.wolvic.metastore-20240830-103719.jpg (view on web) https://github.com/user-attachments/assets/c2994550-59f3-48a2-b3e4-3cc56fd6a352 and this is Meta Browser com.oculus.browser-20240830-103644.jpg (view on web) https://github.com/user-attachments/assets/6ba2e40b-b022-4c5b-a784-30ffa43cd101 The difference is very subtle. It does not affect user experience drastically, it'd be nice to fix but not a high priority bug — Reply to this email directly, view it on GitHub <#1526 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2I7VST7YXANMO5TUW4K32TZUAWA3AVCNFSM6AAAAABNL6VVPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGUYTGMJXHA. You are receiving this because you authored the thread.

[Chris-360x180]

Please visit my krpano tour with Quest 3:

https://360.schnurstracks.de/panoramafotografie/duesseldorf/landtag-nrw-tour-19/

The floating menu to change scenes in the lower section should remain white in a semi-transparent mode. The grey rendered menu graphics on top of a grey carpet is hard to recognize (Großer Fraktionssaal Bereich D) ;-)

Am 30.08.2024 um 17:03 schrieb Sergio @.***>:

That's interesting. It'd be great if you could come up with a very simple use case (the simpler the better) so that we could better understand what is affecting the rendering and causing that color shift.

Hi Sergio, thanks for checking and pointing out. Though the UI example in the temple may not reveal a big difference, for me as a developer of virtual tours and panoramic photographer it’s very important that white stays white in transparent mode. Many UI elements I use for client projects are merely visible in Wolvic because of that grey above photo scenes. That's why I would stick to the Meta browser for now. In future I would really like to shift to Wolvic. Btw, FxR didn’t have this colour bug with krpano. Best regards, Chris … <x-msg://3/#> Am 30.08.2024 um 10:42 schrieb Sergio @.***>: This is Wolvic com.igalia.wolvic.metastore-20240830-103719.jpg (view on web) https://github.com/user-attachments/assets/c2994550-59f3-48a2-b3e4-3cc56fd6a352 and this is Meta Browser com.oculus.browser-20240830-103644.jpg (view on web) https://github.com/user-attachments/assets/6ba2e40b-b022-4c5b-a784-30ffa43cd101 The difference is very subtle. It does not affect user experience drastically, it'd be nice to fix but not a high priority bug — Reply to this email directly, view it on GitHub <#1526 (comment) https://github.com/Igalia/wolvic/issues/1526#issuecomment-2320513178>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2I7VST7YXANMO5TUW4K32TZUAWA3AVCNFSM6AAAAABNL6VVPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRQGUYTGMJXHA. You are receiving this because you authored the thread.

— Reply to this email directly, view it on GitHub https://github.com/Igalia/wolvic/issues/1526#issuecomment-2321542333, or unsubscribe https://github.com/notifications/unsubscribe-auth/A2I7VSXJMLKINLN5JKPG6ZLZUCCVNAVCNFSM6AAAAABNL6VVPGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRRGU2DEMZTGM. You are receiving this because you authored the thread.