Rendering Artifacts in the VSG Builder Example #1389
-
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
That's quite bizarre, first time I've seen an artifact like that. The VSG should be sending the same data to each of the drivers/hardware, so it's likely a bug in the driver or what the desktop compositor is doing that is messing things up. Have a look at your drivers and desktop settings to see if this helps. |
Beta Was this translation helpful? Give feedback.
-
It'd be easier to diagnose if the screenshots weren't scaled down. You should be able to upload images to GitHub without any scaling. A couple of things I'd suggest would be enabling validation layers and running the example through RenderDoc. If there's been a regression caused by any changes made recently, they might be able to identify the problem. |
Beta Was this translation helpful? Give feedback.
The fact that the sample count affects the artifact suggests it's something happening with the driver/hardware side rather than the VSG.
How are you setting the sampler count? The vsgbuilder example doesn't have an option for it. Is this your own example?
To test the sampling on my Kubuntu 24.04 + Geforce 1650 system I've run vsgbuilder outputting a test.vsgt model then loading it into vsgviewer with has the --samples command line option for controlling the sample count:
I don't see any issues with a sample count of 2, edges look as expected.