HDRIs (Lookdev) in 2.8 - EEVEE not working #59200

New Issue

Djeb · 2018-12-11T18:37:14+01:00

Djeb commented

2018-12-11 18:37:14 +01:00

System Information
Operating system: Windows 10
Graphics card: Nvidia Quadro FX 1800

No matter what i tried (even with factory settings), its impossible to preview materials in the lookdev thing.

as seen here: https://gyazo.com/fe4f11f93fb4332bda7cf1b480db30ea

Might be because of my opengl or directx versions (3 and 10)
it is the only thing that blocks me from using 2.8, and its really annoying, because of that tiny error i'm still stuck in 2.79 :(

**System Information** Operating system: Windows 10 Graphics card: Nvidia Quadro FX 1800 No matter what i tried (even with factory settings), its impossible to preview materials in the lookdev thing. as seen here: https://gyazo.com/fe4f11f93fb4332bda7cf1b480db30ea Might be because of my opengl or directx versions (3 and 10) it is the only thing that blocks me from using 2.8, and its really annoying, because of that tiny error i'm still stuck in 2.79 :(

Djeb commented

2018-12-11 18:37:14 +01:00

Added subscriber: @Djeb

Jacques Lucke commented

2018-12-12 16:44:40 +01:00

Added subscribers: @JacquesLucke, @fclem

Clément Foucault commented

2018-12-12 17:36:45 +01:00

Can you try running blender in a console and using the --debug-gpu-force-workarounds option and copy the output to a text file that you can attach here.

Also try that with the --debug and --debug-gpu options.

Thanks.

Can you try running blender in a console and using the `--debug-gpu-force-workarounds` option and copy the output to a text file that you can attach here. Also try that with the `--debug` and `--debug-gpu` options. Thanks.

Djeb commented

2018-12-12 21:52:08 +01:00

Hello

I haven't figured out how to copy the results to a .txt file so i took screenshots instead;

Here are the results for "--debug-gpu-force-workarounds"
https://gyazo.com/b29d7bddbb2ca24f2ea8201b92c0c7cb

Here it is for "--debug"
https://gyazo.com/ca3c96611760d56022a27a35ad651efc

And here for "--debug-gpu" (This one kept updating and getting longer so there isnt everything in that, but i think the useful info is at the beginning)
https://gyazo.com/0b1e8aedb7c64f368b7310c71f787419

Let me know if i'm doing anything wrong, still a noob with coding and this type of stuff

Hello I haven't figured out how to copy the results to a .txt file so i took screenshots instead; Here are the results for "--debug-gpu-force-workarounds" https://gyazo.com/b29d7bddbb2ca24f2ea8201b92c0c7cb Here it is for "--debug" https://gyazo.com/ca3c96611760d56022a27a35ad651efc And here for "--debug-gpu" (This one kept updating and getting longer so there isnt everything in that, but i think the useful info is at the beginning) https://gyazo.com/0b1e8aedb7c64f368b7310c71f787419 Let me know if i'm doing anything wrong, still a noob with coding and this type of stuff

Clément Foucault commented

2018-12-12 22:41:58 +01:00

You can copy the content of the console by click dragging to highlight the text you want and just right click to copy to clipboard (selection disappear if copy worked).

The Texture 0 is base level inconsistent is worrisome.

Did you try to play with the render settings options? (AO, SSR, Bloom, etc)

You can copy the content of the console by click dragging to highlight the text you want and just right click to copy to clipboard (selection disappear if copy worked). The `Texture 0 is base level inconsistent` is worrisome. Did you try to play with the render settings options? (AO, SSR, Bloom, etc)

Djeb commented

2018-12-13 19:54:01 +01:00

Nope, at least not the eevee checkboxes