Giter Site home page Giter Site logo

Comments (13)

Mugen87 avatar Mugen87 commented on September 27, 2024 1

Besides, can you share a Chrome GPU report of one affected system by typing chrome://gpu/ in the address bar and hit "Donwload Report to File"?

from three.js.

csimlinger avatar csimlinger commented on September 27, 2024 1

Only happens in Chrome (currently everybody on version 125.0.6422.77).
Mac OS Versions:

12.6.6 - No issue
13.5 - Issue visible
14.3 - Issue visible
14.4.1 - Issue visible

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

I'm unable to reproduce on macOS 14.4.1 and Chrome 125.0.6422.77 and Firefox 126. This is how the scene looks with and without the red cube in Chrome.

image image

This issue might be device-related so please try to reproduce it on other systems.

from three.js.

csimlinger avatar csimlinger commented on September 27, 2024

I tried it on four different macs. The issue occurred on three of these four.

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

Have you tried different browsers as well? What happens in Firefox and Safari?

from three.js.

csimlinger avatar csimlinger commented on September 27, 2024

Here is the GPU Report: https://pastebin.com/cTeNs0m4

Strangely it worked for 10 minutes on another computer, without us changing anything.
Problem happens now again all the time on 3 of 4 computers.

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

Strangely it worked for 10 minutes on another computer, without us changing anything.

Do all affected macs use Intel+AMD? Can you also reproduce on a mac with M processor?

If the issue might temporarily disappear, I wonder if it makes a difference if the discrete AMD GPU is used or the integrated Intel graphics (in your case UHD Graphics 630).

I'm not sure this is works anymore but it was possible in the past to go in "System Preferences" - "Energy Saver" and disable "Automatic graphics switching". This should force the usage of the discrete GPU.

from three.js.

csimlinger avatar csimlinger commented on September 27, 2024

I was able to disable the "Automatic graphics switching", the problem still occurs.
Yes, all are Intel + AMD. Unfortunately we don't have any M1 Mac here right now...

EDIT: We just found out, that if you disable "Hardware Acceleration" in Chrome, it works. ๐Ÿคจ

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

It seems this is a GPU related issue. Unfortunately, there is nothing what we can do on our side. The problem should be reported to the Chromium bug tracker (https://issues.chromium.org/issues).

Please report the issue there including the live example, the GPU report as a txt file attachment and the findings from this discussion (the rendering issue happens exclusively with Chrome on macOS with Intel+AMD).

I could imagine that the live example is still too complex as a reproduction case for the Chromium team so I wonder if we can break it further down. Do you ass any rendering issues with examples from the official website? https://threejs.org/examples/

There are some font/text examples that might show glitches on your hardware similar to your fiddle. Besides, it would be interesting to know if affected devices have issues with non-text related examples as well.

from three.js.

csimlinger avatar csimlinger commented on September 27, 2024

Oh... thanks for the info, I will report it.

Regarding glitches of the examples, looked trough many of them and I encounter these (not 100% sure if they are supposed to look like that, but I guess they are supposed to look differently):

image image image image

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

The last two are definitely wrong. The logarithmic depth buffer demo shows glitches on the left side which is intended. The first one does not render its checkerboard pattern double-sided so the screenshot is as expected.

So there seems to be a more general GPU related issue on these devices. The root cause is not related to text rendering. It seems the 3MF demo (the one with the vehicle) could be a good reproduction test case since it does not involve font or text components.

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

Potentially related #27842.

from three.js.

Mugen87 avatar Mugen87 commented on September 27, 2024

Closing. This needs to be reported to the browser vendor.

from three.js.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.