Edges shown when they should be hidden by other objects

[CabeDigicorp]

Describe the bug 📝

This is a sample model with PostProductionAspect set to "COLOR":

And this is the same model with PostProductionAspect set to "COLOR_PEN":

As you can see, a bunch of edges that should be hidden by other structures are visible.

This is my configuration for PostProduction:

world.renderer = new OBCF.PostproductionRenderer(components, viewerDiv);
    
world.renderer.postproduction.enabled = true;
world.renderer.postproduction.style = OBCF.PostproductionAspect.COLOR; //or COLOR_PEN
world.renderer.postproduction.outlinesEnabled = true;
world.renderer.postproduction.smaaEnabled = true;

world.renderer.postproduction.edgesPass.width = 1;
world.renderer.postproduction.edgesPass.mode = OBCF.EdgeDetectionPassMode.DEFAULT;
world.renderer.postproduction.edgesPass.color.set("#343a40");

Reproduction ▶️

No response

Steps to reproduce 🔢

No response

System Info 💻

System:
    OS: Windows 11 10.0.26200
    CPU: (16) x64 AMD Ryzen 9 6900HX with Radeon Graphics
    Memory: 14.89 GB / 31.24 GB
  Binaries:
    Node: 22.12.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.21 - C:\Program Files\nodejs\yarn.CMD
    npm: 10.9.0 - C:\Program Files\nodejs\npm.CMD
    pnpm: 9.12.1 - C:\Program Files\nodejs\pnpm.CMD
  Browsers:
    Chrome: 146.0.7680.165
    Edge: Chromium (146.0.3856.62)
    Firefox: 149.0 - C:\Program Files\Mozilla Firefox\firefox.exe
    Internet Explorer: 11.0.26100.7309

Used Package Manager 📦

npm

Error Trace/Logs 📃

No response

Validations ✅

• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Make sure this is a repository issue and not a framework-specific issue. For example, if it's a THREE.js related bug, it should likely be reported to mrdoob/threejs instead.
• Check that this is a concrete bug. For Q&A join our Community.
• The provided reproduction is a minimal reproducible example of the bug.

[agviegas]

Hey @CabeDigicorp can you send this model to antonio@thatopen.com? Happy to sign an NDA if needed!

[agviegas]

The problem is that his model seems to have coplanar surfaces, and there's no global way to know which ones you want to represent on top. If the surfaces are not coplanar and it's an engine error, let me know. That said, there are ways to get rid of the z fighting so that you don't have that flicker effect. Example attached. Let me know how this goes!

index.zip

[CabeDigicorp]

Some surfaces may be coplanar, but not all of them. Have a look at the following (same model):

Note that the whole structure of the door is visible (which should not be the case, as it's well behind the front wall).

However, if I move the camera towards the door (no zoom, just dolly):

The back side of the door has disappeared. It seems that edges are shown only whithin a certain distance (inversely proportional to the camera distance) behind the surface that should be hiding them.

[CabeDigicorp]

Seems better (still not OK, however) with Components 3.4.5.