this is a rather insignificant issue due to how easy and inconsequential the workaround is, do not waste too much time on it :)

What i did / Steps to reproduce

generated/rendered as normal, set up webserver, all of the normal process

Expected result

The map to be shown

Actual result

black (no lighting)

Context

Version: 5.7
├ 8c74686
├ Implementation: paper
└ Minecraft: 1.21.5
Available Processors: 4
Available Memory: 4.0 GiB
paper-1.21.5-103.jar

Please note that D3D9 is from around 2002.... Windows XP era...
(https://en.wikipedia.org/wiki/DirectX)

IMO, if you're going to be messing with the GPU API backend manually, then it's also on you to realise that you really cannot expect something modern to work on something that old...
(Similarly to how you can't expect BlueMap to work on a Nokia 3310.)

yeah i know but there were some chrome bugs on nvidia with graphics flickering and d3d9 solved it
maybe you can add a
"Check that you are not using d3d9" to Q: I have a black map / a lot of the map is missing!
in faq?

BlueMap does simply not support D3D9, it requires WebGL2 to run.
This is a won't fix :)

BlueMap does simply not support D3D9, it requires WebGL2 to run. This is a won't fix :)

Can you add a disclaimer/warning somewhere? I spent 30 minutes thinking I messed up the setup before I found out D3D9 was the issue

How are you even (trying to) run BlueMap on D3D9?
Shouldn't Chrome translate the WebGL2 function calls to whatever best GPU API the device has?

Ah...

WebGL 2.0 requires hardware with OpenGL ES 3.0 support

(https://get.webgl.org/get-a-webgl-implementation/)

And ANGLE only supports OpenGL ES 2.0 on D3D9...
(https://github.com/google/angle)

D3D9 is not capable of supporting all WebGL 2 functionality, but D3D11 is.

(https://groups.google.com/g/webgl-dev-list/c/SzTfCzoB5Ss?pli=1)

It seems like your computer is just way way too old..?

Maybe you can get it to do software (CPU) rendering instead, somehow...? It'll be extremely slow (low FPS), but at least it'll work...

Ah...

WebGL 2.0 requires hardware with OpenGL ES 3.0 support

(https://get.webgl.org/get-a-webgl-implementation/)

And ANGLE only supports OpenGL ES 2.0 on D3D9... (https://github.com/google/angle)

D3D9 is not capable of supporting all WebGL 2 functionality, but D3D11 is.

(https://groups.google.com/g/webgl-dev-list/c/SzTfCzoB5Ss?pli=1)

It seems like your computer is just way way too old..?

Maybe you can get it to do software (CPU) rendering instead, somehow...? It'll be extremely slow (low FPS), but at least it'll work...

No bro it works perfectly i had set it to d3d9 for troubleshooting some other thing a while back, the plugin is actually fine, you should just add a reminder somewhere that d3d9 will cause issues and save people headaches :)
I have 1660ti and d3d11 works perfectly

I just pushed f2c6ae8 which will in future versions display this screen:

when WebGL2 isn't available .. i tested it with D3D9 and it will display that screen as well.