Sunday, April 20, 2025
spot_img

What’s the trigger of those pixel artifacts and the way do I forestall it?


I am getting these unusual picture artifacts after I try a low-res 3D orthographic scene in Godot 4.4:

artifact_example

Here is my steps to breed:

  1. In MagicaVoxel, export the built-in "fort" instance to *.obj format.

  2. In Godot 4, begin a brand new challenge and arrange a primary 3D scene (floor mesh, digicam, directional mild).

  3. Drag-and-drop the fort obj file into the scene, and create a primary BoxMesh3D as nicely for comparability.

  4. I am going for a faux-2D orthographic look, so I observe the preliminary setup really helpful on this video:

    • Set the challenge Viewport to 1080p.
    • Put my primary 3D scene beneath a SubViewport, and put this SubViewport inside a SubViewportContainer
    • Configure the SubViewportContainer to stretch to suit the canvas, and lift "Stretch Shrink" to 2 or larger to approximate a pixelated look.
    • Activate "Nearest" texture filtering on the SubViewportContainer.
  5. Already the preview rendering exhibits the artifacts famous above; operating the scene continues to indicate the rendering artifacts.

  6. Some assorted hypotheses I’ve had and issues I’ve tried:

    • The Show > Window > "Stretch mode" challenge setting doesn’t seem to have an effect on this downside come what may (at the very least the disabled and viewport states).
    • The banding seen on the fort additionally impacts the native Godot mesh in sure viewport resolutions–not seen within the screenshow above, however belief me :).
  7. As a final strive, I attempted switching the renderer from "Ahead+" to "Compatibility" mode. Alas, that appeared to repair the difficulty, albeit with a brand new lighting difficulty:

enter image description here

So I am left with loads of questions:

  • Why is my debug run nonetheless showing to run at 1080p or a decision increased than the shrunken 540p or 360p? Is that this an anti-aliasing setting that I must disable someplace? Is anti-aliasing the offender?
  • Is that this a identified difficulty with the Ahead+ renderer?
  • Is there another configurations I might strive (e.g. select a driver) to attempt to mitigate this difficulty? I might like to make use of the Ahead+ renderer if attainable.

Thanks prematurely for any assist or recommendation in any respect!

Related Articles

LEAVE A REPLY

Please enter your comment!
Please enter your name here

- Advertisement -spot_img

Latest Articles