RReady Alpha Release (26 October 2023) VH2 and SODA fixes. (Still undergoing testing)

https://1drv.ms/u/s!As-dKk-N73dSllRh1Y7y2dpix3FZ?e=debKRt
MD5:920187c675606f2bd799698d52c183d1

Adds: RRosetta SDK demo. This needs to be redownloaded: hit reset and automatically downloading in the alpha build or manually in the store release. Store rules prohibit bundleware, which is why the auto download is stripped.
Fixes:
SODA Offroad:
- Menus should show a copy of what used to be on the screen instead of a flat colour.
- Texture coordinate generation for this game now uses rounding to nearest pixels. Without this the revised code (requring repeating texture support/default no clamping) shows artifacts. Games like vQuake 2 and VH2 require precise coordinates. This is probably down to how textures are sampled on Verité as opposed to OpenGL.

VH2:
-World textures showing cracks fixed. vQuake 2 doesn't use repeating textures, generating fresh spans using <[0,1), [0,1]> as texture coordinates. vHexen does and this causes the cracks to appear. RReady's VL_QSpan implementation may be lacking or texture sampling is different with OpenGL compare to a Rendition board. The call's undocumented and probably needs more work. VH2 does not appear to change the clamping mode for QSpans and RReady guesses what sky textures (which do repeat) and world textures (which don't) and manually toggles the mode instead of honouring the RRedline setting. There may be issues with this method.
- 256 colour full screen palette effects are now implemented in a 16 bit mode. RReady uses the first colour to alter the screen colour. This does appear to work, though someone with a Verité board could probably comment on accuracy.
This should allow damage, power up collection and r_nomurk 0 to work. The toggle from r_nomurk 0 to 1 and back again does work. Not entirely convinced the colour's right.

sharangad wrote on 2023-10-26, 06:32:

RReady Alpha Release (26 October 2023) VH2 and SODA fixes. (Still undergoing testing) […]
Show full quote

RReady Alpha Release (26 October 2023) VH2 and SODA fixes. (Still undergoing testing)

https://1drv.ms/u/s!As-dKk-N73dSllPvgXyc9qti3qlp?e=A9jZI7
MD5: f098b514b0fdfb2d01c40d95d14c5c08

Adds: RRosetta SDK demo. This needs to be redownloaded: hit reset and automatically downloading in the alpha build or manually in the store release. Store rules prohibit bundleware, which is why the auto download is stripped.
Fixes:
SODA Offroad:
- Menus should show a copy of what used to be on the screen instead of a flat colour.
- Texture coordinate generation for this game now uses rounding to nearest pixels. Without this the revised code (requring repeating texture support/default no clamping) shows artifacts. Games like vQuake 2 and VH2 require precise coordinates. This is probably down to how textures are sampled on Verité as opposed to OpenGL.

VH2:
-World textures showing cracks fixed. vQuake 2 doesn't use repeating textures, generating fresh spans using <[0,1), [0,1]> as texture coordinates. vHexen does and this causes the cracks to appear. RReady's VL_QSpan implementation may be lacking or texture sampling is different with OpenGL compare to a Rendition board. The call's undocumented and probably needs more work. VH2 does not appear to change the clamping mode for QSpans and RReady guesses what sky textures (which do repeat) and world textures (which don't) and manually toggles the mode instead of honouring the RRedline setting. There may be issues with this method.
- 256 colour full screen palette effects are now implemented in a 16 bit mode. RReady uses the first colour to alter the screen colour. This does appear to work, though someone with a Verité board could probably comment on accuracy.
This should allow damage, power up collection and r_nomurk 0 to work. The toggle from r_nomurk 0 to 1 and back again does work. Not entirely convinced the colour's right.

I will test it again when I have time, but why did you implement 256 color full-screen palette effects in 16bit mode?

BEEN_Nath_58 wrote on 2023-10-26, 06:38:

I will test it again when I have time, but why did you implement 256 color full-screen palette effects in 16bit mode?

Because the game calls an API call to change 256 32-bit RGBA DAC colours. This should have no effect in a 16-bit mode, but it clearly does because the screen tints using these colours on an actual Verité board.

Tested Quake 2 with speedrun demos , it now goes further than with previous version, and crashed again , i assume with same error(s)

Tested SODA - wooow thank you very much its works awesome =0 woo, just wow )

P.S. HeXen II fixed , nice textures and flashes on pickups + nomurk works, for me it looks great as on original verite hardware.

RaVeN-05 wrote on 2023-10-26, 08:15:

Tested Quake 2 with speedrun demos , it now goes further than with previous version, and crashed again , i assume with same error(s)

Tested SODA - wooow thank you very much its works awesome =0 woo, just wow )

P.S. HeXen II fixed , nice textures and flashes on pickups + nomurk works, for me it looks great as on original verite hardware.

Glad those two are fixed. Working on a Quake 2 fix . Can you check RavDM4 to see if you see anything wrong?

Quake 2/VH2 Speedrun fix (Not tested against anything else, use at your own peril):

https://1drv.ms/u/s!As-dKk-N73dSllb7RHbQOoBpaOQr?e=h9AqLx
MD5: 33076420b258943b71cdb90751d6901f

Not the one below:
https://1drv.ms/u/s!As-dKk-N73dSllXrxQ_i1rQo_LV2?e=41JGDV
MD5: 7abb10f28377cd1df89552f15151f1f9
- When adding Quake 2 and VH2 mipscale 0 and +mlook added to autoexec.cfg file in baseq2.

Raven, can you give this a go?

[EDIT] Demos verified.

Tested: MD5: 33076420b258943b71cdb90751d6901f

Tested Quake2 trough playing speedrun, the whole game passed. Excellent, no crashes, that means long gameplays will be ok!

The only thing i spot (full screen, alt+enter or vid_fullscreen 1 ) will crash game. real hardware is ok here. So Quake 2 looks excellent only one thing different to real hardware.

i included log in case if its temporal fix and some other anomalities can be readed from log.

Next will be hexen2 , also will prepare demos that will show bugs.

SODA - Excellent.
Monster Track Mandness 2 - Excellent.

all sdk and contest demos - excellent .
other games judge by YT videos and what i run on real hardware - seems all excellent =)

RavDM4 is ok

RaVeN-05 wrote on 2023-10-26, 16:21:

Tested: MD5: 33076420b258943b71cdb90751d6901f […]
Show full quote

Tested: MD5: 33076420b258943b71cdb90751d6901f

Tested Quake2 trough playing speedrun, the whole game passed. Excellent, no crashes, that means long gameplays will be ok!

The only thing i spot (full screen, alt+enter or vid_fullscreen 1 ) will crash game. real hardware is ok here. So Quake 2 looks excellent only one thing different to real hardware.

i included log in case if its temporal fix and some other anomalities can be readed from log.

Next will be hexen2 , also will prepare demos that will show bugs.

SODA - Excellent.
Monster Track Mandness 2 - Excellent.

all sdk and contest demos - excellent .
other games judge by YT videos and what i run on real hardware - seems all excellent =)

RavDM4 is ok

Excellent! Thanks dude, it's good to know RReady can survive that.

The fullscreen res has to be forced from RRedline settings for vQuake 2. The force fullscreen option needs to be ticked in RReady config (Rendition.cfg forcefullscreen=max (or resolution of your choice 1920x1080x60)) and windowed mode must be set in baseq2\config.cfg (set vid_fullscreen "0").

It's a problem with vquake 2, vid_ref v1k can't go fullscreen on modern Windows. It fails without making any RRedline calls, so forcing fullscreen is the only option.

Were there any noticeable glitches/missing textures? There shouldn't be.

i spot no glitches in Q2 . There is two scenes in speedrun with flickering polygons, appears on real hardware too.
The other thing an idea, if its possible of course, the color conversions a v1k_surfacelookup or r_surfacelookup , while on 1 to make on videocard , its possible to make it truecolor or to use dithering as option to make color banding less noticeable , especially it noticed on shadows.

the hexen2 crashes couple times on various scenes.
last time i tried on win7

1Problem Event Name:	APPCRASH
2  Application Name:	VH2.exe
3  Application Version:	0.0.0.0
4  Application Timestamp:	346a08f1
5  Fault Module Name:	redline.dll
6  Fault Module Version:	1.0.1.46
7  Fault Module Timestamp:	653a5883
8  Exception Code:	c0000005
9  Exception Offset:	0004caa3
10  OS Version:	6.1.7601.2.1.0.256.1
11  Locale ID:	1033
12  Additional Information 1:	9818
13  Additional Information 2:	9818661a30c7a0589567783796653720
14  Additional Information 3:	175d
15  Additional Information 4:	175d7c2a0f13ea0bf876689840e5ca5d
16
17Read our privacy statement online:
18  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
19
20If the online privacy statement is not available, please read our privacy statement offline:
21  C:\Windows\system32\en-US\erofflps.txt

the hexen2 has some graphical glitches will show it soon

RaVeN-05 wrote on 2023-10-26, 16:21:

Tested: MD5: 33076420b258943b71cdb90751d6901f […]
Show full quote

Tested: MD5: 33076420b258943b71cdb90751d6901f

Tested Quake2 trough playing speedrun, the whole game passed. Excellent, no crashes, that means long gameplays will be ok!

The only thing i spot (full screen, alt+enter or vid_fullscreen 1 ) will crash game. real hardware is ok here. So Quake 2 looks excellent only one thing different to real hardware.

i included log in case if its temporal fix and some other anomalities can be readed from log.

Next will be hexen2 , also will prepare demos that will show bugs.

SODA - Excellent.
Monster Track Mandness 2 - Excellent.

all sdk and contest demos - excellent .
other games judge by YT videos and what i run on real hardware - seems all excellent =)

RavDM4 is ok

When you get a chance could you check final.exe (final version of ncubed) on actual hardware. I'm sure the paletted (4-bit 16 colour) section is wrong. Doesn't appear to be an issue with rready. Ncubed and final seem to be sending rready wrong palette data, at least on win 10/11 ).

RaVeN-05 wrote on 2023-10-26, 22:08:

i spot no glitches in Q2 . There is two scenes in speedrun with flickering polygons, appears on real hardware too. The other thi […]
Show full quote

i spot no glitches in Q2 . There is two scenes in speedrun with flickering polygons, appears on real hardware too.
The other thing an idea, if its possible of course, the color conversions a v1k_surfacelookup or r_surfacelookup , while on 1 to make on videocard , its possible to make it truecolor or to use dithering as option to make color banding less noticeable , especially it noticed on shadows.

the hexen2 crashes couple times on various scenes.
last time i tried on win7

Copy code to clipboard

1Problem Event Name:	APPCRASH
2  Application Name:	VH2.exe
3  Application Version:	0.0.0.0
4  Application Timestamp:	346a08f1
5  Fault Module Name:	redline.dll
6  Fault Module Version:	1.0.1.46
7  Fault Module Timestamp:	653a5883
8  Exception Code:	c0000005
9  Exception Offset:	0004caa3
10  OS Version:	6.1.7601.2.1.0.256.1
11  Locale ID:	1033
12  Additional Information 1:	9818
13  Additional Information 2:	9818661a30c7a0589567783796653720
14  Additional Information 3:	175d
15  Additional Information 4:	175d7c2a0f13ea0bf876689840e5ca5d
16
17Read our privacy statement online:
18  http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409
19
20If the online privacy statement is not available, please read our privacy statement offline:
21  C:\Windows\system32\en-US\erofflps.txt

the hexen2 has some graphical glitches will show it soon

Will check out the logs tomorrow. v1k_surfacelookup and its vh2 analogue can be set from rready under"app specific settings. " this will cause a hit to the framerate. You can also directly add them to autoexec.cfg or config. Cfg and it will work. I can't hit a solid 60 fps with it enabled and it won't give you better quality because the palette data is still 16 bit rgb565. Dithering isn't isn't implemented at the moment. I didn't know that this option had better image quality. Irrespective of the settings vquake 2 and vhexen 2 uses this call for console text (VL_Lookup is used for almost all texture loads with surface lookup 1).

This call has clearly specced behaviour. Rredline has a global dithering setting which at the moment does nothing. VL_Setditherenable 0/1. Opengl has a global dithering option which is enabled by default and does nothing on modern hardware or has undefined behaviour depending on vendor implementation.

I can look into implementing it in a future release.

@Raven, did vh2 crash while toggling resolutions in game?

If you are, you need to set rready's resolution to default and not maxxed or upscaled.

ok, will test ncube and final on real hw.

about dithering , dithering present as global on screen effect to simulate true color. And this dithering is ordered on real hw. While generally random/noise dithering produce better results but its not on real hardware.
The r_surfeclookup 0 produces better colors on shadows and highlights but no dithering here even if its 0 or 1. So what i ask is advanced feature, enhancement over original hardware , like you done with resolution upscale.
Dithering can be turned off/on in vQuake1 by d_dither 0/1.
vQuake2's v1k_surfacelookup 0/1 visually change nothing. only Quake1 and HeXen2 affected. 0 - is better colors , 1 - is colors allowed only from game palette.
vQuake2's v1k_surfacelookup 0/1 doenot matter colors will be used from quake2 palette. vQuake and HeXen II with r_surfacelookup 0 produce better results than Quake2

ok retested vh2 the way you told + i used windowed 800x600 resolution. Still crashed . I remember vhexen2 is also crashed on my real win98+rendition, so it could be a vh2 problem like beta patch?
In vh2 the maximum speedrun demos can reach is loading final level and crash. If i try to watch speedrun until it crash and next time continue watch where i left, it goes to end fully. So its already best results can be produced here.

RaVeN-05 wrote on 2023-10-27, 08:56:

ok, will test ncube and final on real hw. […]
Show full quote

ok, will test ncube and final on real hw.

about dithering , dithering present as global on screen effect to simulate true color. And this dithering is ordered on real hw. While generally random/noise dithering produce better results but its not on real hardware.
The r_surfeclookup 0 produces better colors on shadows and highlights but no dithering here even if its 0 or 1. So what i ask is advanced feature, enhancement over original hardware , like you done with resolution upscale.
Dithering can be turned off/on in vQuake1 by d_dither 0/1.
vQuake2's v1k_surfacelookup 0/1 visually change nothing. only Quake1 and HeXen2 affected. 0 - is better colors , 1 - is colors allowed only from game palette.
vQuake2's v1k_surfacelookup 0/1 doenot matter colors will be used from quake2 palette. vQuake and HeXen II with r_surfacelookup 0 produce better results than Quake2

ok retested vh2 the way you told + i used windowed 800x600 resolution. Still crashed . I remember vhexen2 is also crashed on my real win98+rendition, so it could be a vh2 problem like beta patch?
In vh2 the maximum speedrun demos can reach is loading final level and crash. If i try to watch speedrun until it crash and next time continue watch where i left, it goes to end fully. So its already best results can be produced here.

That crash is a good sign. I think I know what's wrong there.

I understand what you're saying about dithering, only vquake 1 and Hexen 2 is affected.

To test resolution changes in vhexen, set RReady's resolution to "default", not max nor 80xx600. This will match the physical resolution to the virtual resolution.

yes its tested as you said, the 800x600 windowed i set in game menu. The rlauncher used default

RaVeN-05 wrote on 2023-10-27, 10:06:

yes its tested as you said, the 800x600 windowed i set in game menu. The rlauncher used default

I think I only tested res change in fullscreen. Can't remember. Will add that to my test battery.

[EDIT] Actually there may be issues running VH2 in windowed mode. There's code to centre the Window in RReady when upscaling. It's needed because vhexen centres assuming an 800x600 full screen window. When the actual res is higher, the centering places most of the window offscreen. By how much depends on the upscaled resolution. There might be an actual test for fullscreen mode. Will check and fix once I fix the stability issue.

vHexen II Speed Run Crash logging

https://1drv.ms/u/s!As-dKk-N73dSllcHImRJZ1Wjn_q1?e=dy8a4M

MD5: f4eb0653384bce50b8b91855bcd44422

This version will still crash, but it will log the problematic call. So I'm sorry to hassle you with this @Raven-05, but this calls for another speedrun.

I tested the resolution switch and it works fine for me with Win 11, RReady at default, both Windowed and fullscreen. Just to be safe check that you have the corresponding full screen resolutions set up in nvidia control panel/AMD Catalyst control centre. Resolutions like 512x384, 400x300 and 320x240 aren't there anymore even if the monitor physically supports it. Modern WIndows is keen on dropping legacy compatibility.

no problem ) done

RaVeN-05 wrote on 2023-10-27, 12:37:

no problem ) done

Were you running in a window?

yes rready default, in game i choose 800x600 windowed

second demos run on win7 windowed 640x480 , rready default