Weird 3D Artifacts

[fooxeh]

Hello dear Sweet Home 3D Forum members,

i've been working with version 6.6 for a couple months now and recently upgraded to 7.0.

Everything was working fine until today, the Planning view and the 3D view both only show artifacts for the 3D objects.

3D View:
https://imgur.com/Ui6Btum

Planner View:
https://imgur.com/A5r7sMT

I tried reverting to 6.6, same issue.
I created a new plan, and used an old version, both still have the same artifacts.
Also reinstalled the Graphics Card drivers, no change.

Does anyone have an idea? [:(]
I can install an older Graphics Card driver if that might be the issue, using an AMD Vega.

[hansmex]

Maybe not all walls have the same height? In that case strange triangles appear where a ceiling is expected.

H

[fooxeh]

Yes, I saw those before too.
This is not the same however, if you look at the 3D View, it is totally broken.

And even with a new project, by default the ground is dark-grey.
If i place any object, it becomes a giant black cluster

[hansmex]

Withoutt acces to the original *.sh3d file it's hard to see what's happening...

[bartjansen]

Same issue here, and for me it was an issue with the latest AMD adrenaline drivers (22.7.1). When I reverted back to 22.5.1 everything started working again.

[Puybaret]

Thanks for your feedback. Be sure to report this issue to AMD so they fix it in a future update.

[fooxeh]

Yes, I now also downgraded to 22.5.1 and the Artifacts are gone

I reported the issue via the AMD Bug reporter, hope they can fix it

[[email protected]]

I have installed versione 22.8.1 and have same problem. I have notified AMD of the bug, I have little confidence that they will correct anything.

[anhmax]

I have the exact problem. I use AMD with Adrenaline driver 22.8.2, and it cannot show the 3D window. Hope AMD fix it soon

[cyphorage]

Just confirming that this is still an issue with latest Adrenaline driver (22.9.1) released yesterday (2022-09-21)

https://www.amd.com/en/support/kb/relea ... win-22-9-1

Does anyone know the exact crux of the issue so that we can report it directly to AMD?