Game:

Rendition (2007)

Duration: 0:00

65 views

7

Unlocked 16 MB of VRAM for DOS/Speedy3D apps has exposed how resolution support in Rendition games is largely controlled by the amount of available VRAM. vHexen 2 is unique in that it uses an RRedline API call to query available resolutions, but under Windows 10/11 struggles with the native resolution list.

Rendition Windows app (RRedline) can support up to 128 MB of VRAM, whereas Rendition DOS /Speedy3D apps top out at 16 MB (this has been recently unlocked, so vQuake can go as high as 1280x1024 internally (with instability at the moment)). Speedy3D can't support 128 MB because the games are tightly knit to the architecture of V1000/V2000 cards which only used 24 bit of address for the GPU framebuffer with the other 8 bits being used for metadata like byte ordering. Twenty-four bits can only address 16 MB of VRAM.

More tests will be done on physical hardware to see why vHexen 2 struggles with a modern resolution list, perhaps there's an internal buffer that's too small. Once again, thanks for the Rendition boards Vogon robertmo3.

The golems changing colour now works with up to 16 MB of VRAM with the resolution unlock hack.

There're two things wrong with this video:
1) The underwater resolution for 800x600 has been set to 1152x864, so the difference isn't as dramatic and
2) the loading progress bars are front buffer effects, so they can't be captured.

Other Statistics