lowenz

About necrothreads.....STEAM RELEASE?

nbohr1more, he's trolling.

It's not a "command", it's a VARIABLE. You know nothing about ID3Tech engine, LOL, Mr "I am an experienced tester" Are you a friend of Shadowhide?

He's trolling.

In trolling?

It shows that the AMD driver is compliant when the Nvidia one (or MESA) needs extensions override mechanism to run IDTech 2 based engines.

https://postimg.cc/Pp41sQDt

I know but the implementation of AMD enable some kinds of automatic extension compatibility, 'cause ID2 Tech based games need manual extension override control on Nvidia GPU systems. MESA too needs to set it manually (via environment variables)

To wrap up the behaviour: r_glCoreProfile "0" -> 3.3 compatibility profile context r_glCoreProfile "2" -> 3.3 core profile forward-compatible context Either way r_useBindlessTextures is not working (so maybe it's a bug and not a compatibility issue)

r_glCoreProfile "0" Here's the screenshot (with r_glCoreProfile "2" - 3.3 core profile - I *CAN'T* take a screenshot, the screenshot is all black! ) https://postimg.cc/fJ767nhV Performance is pretty the same, still BindlessTextures NOT working right (if set to 1). No need to vid_restart, just setting it to 0 solves the issue directly in game.

It gives me "3.3" and with GL_ARB_COMPATIBILITY Green! No more red!

OK, but the problem now is if "Bindless Textures" are 3.3 compliant in AMD implementation. There's a RED cross in the console extensions list when you start TDM, about "GL_ARB_COMPATIBILITY", just right after "Bindless Texture" (GREEN CHECK!)

So maybe TDM is running in 3.3 mode but 3.3 mode is NOT compatible with BindlessTextures (only 4.x?)

Example in ioQuake3 Classic Renderer (Opengl 1.x?) https://i.postimg.cc/jq62xw0d/0.jpg New Renderer https://i.postimg.cc/xCDjYY6z/1.jpg

AMD uses its own "compatibility profiling" (for the driver) to avoid/solve problems with OpenGL extensions. It's why you can run '90s OpenGL games (example: SiN) with no tweaking needed.