The desktop screen looks bad, and the image results are incorrect

Hello again!!! Version 2.11 is running terribly on my computer.
The desktop screen looks bad, and the image results are incorrect.
First, I uploaded the desktop screen images and the results to version 2.10, and then to version 2.11.

Before installing the new version, I deleted everything previously installed.
I deleted all traces of D5 render from the PC.
I also re-created the files from scratch for each version.
I did this to make sure there was no possibility of inheriting any problems from previous versions.

And 2.11 doesn’t work properly.

Version 2.10


Version 2:11


Hi @germanvallverdu

I apologize for the inconvenience.

  • This happens to all of your Files right?
  • Does disabling any of these settings (Super Resolution, FSR Frame Generation, and FPS Booster for Complex Geometry) alleviate this issue?
    image

Please send us this specific file and generate a log file for us.

Hi, Clov

In version 2.11 of my D5 Render, the menu doesn’t exist (FPS Booster for Complex Geometry).
I just reinstalled everything.
My menu looks like this.

After reinstalling everything, the image on the desktop screen still looks this bad.

I’ll send you everything you asked for in another message.

Best regards

What kind of GPU do you have?

Hi @germanvallverdu

Alright, thanks for the additional information. Looking forward to the sent Log and Scenefiles.

Hi, Clov
AMD Radeon RX 7800 XT 16GB ASUS

I am not from the d5 crew. But will answer already maybe that clears things up

Quote from d5 crew LeahLi: “For AMD graphics card, after comprehensive evaluation, Path Tracing is no longer available for AMD users in this version due to performance issues. Thank you for your understanding.”

Hope that @Clov also cam help you further

Hi @germanvallverdu

As expected, no replication on my end. Can you share to me which AMD Drivers you are currently using?

Hi, Clov
The drivers I have installed right now are 32.0.21013.9005
But I tried others, and from what I understand, it’s a program limitation for AMD cards in the current version 2.11.

Thanks anyway.

Hi @germanvallverdu

Thanks for the information. I’m attempting to replicate this on my end (with an AMD device). Can you tell me which drivers you’ve tried and still got the same result (except for the one that you have already mentioned) ?

Update: I’ve successfully replicated this issue, and it has been escalated for further troubleshooting.

1 Like