robertmo3 wrote on 2024-05-08, 15:25:

sharangad wrote on 2024-05-08, 15:12:

robertmo3 wrote on 2024-05-08, 14:58:

dma=0 cycles=45% intro 60-130fps game at start with cycles=105% 20fps when focus on game 40fps when focus on dosbox […]
Show full quote

dma=0
cycles=45%
intro 60-130fps
game at start with cycles=105%
20fps when focus on game
40fps when focus on dosbox

dma=1
cycles=105%
intro 100-200fps
game at start with cycles=105%
40fps when focus on game
80fps when focus on dosbox

Drat! You don't get 60fps with dma.

fix the mirror first 😉

Mirror? In Whiplash?

switch views with f3-f4 one is mirror there one is a camera on opponent

sharangad wrote on 2024-05-08, 14:34:

robertmo3 wrote on 2024-05-08, 14:19:

asdf53 tested rebel moon rising on rebel moon engine on v1000 and it has same artifacts as in the wrapper

Well that's a relief. Unfortunate, but a relief, for me at least.

it works properly in -vga mode so it looks like buggy verite. still worth fixing if possible. it is a verite 4k exclusive after all 😀
btw on rm engine rmr allows higher angles when looking up/down.
cgl version of rebel moon may be harder as it crushes even in -vga mode
btw ef2000 is verite 4k exclusive too as it is statically linked for 3dfx 😀

robertmo3 wrote on 2024-05-08, 15:44:

it works properly in -vga mode so it looks like buggy verite. still worth fixing if possible. it is a verite 4k exclusive after […]
Show full quote

sharangad wrote on 2024-05-08, 14:34:

robertmo3 wrote on 2024-05-08, 14:19:

asdf53 tested rebel moon rising on rebel moon engine on v1000 and it has same artifacts as in the wrapper

Well that's a relief. Unfortunate, but a relief, for me at least.

it works properly in -vga mode so it looks like buggy verite. still worth fixing if possible. it is a verite 4k exclusive after all 😀
btw on rm engine rmr allows higher angles when looking up/down.
cgl version of rebel moon may be harder as it crushes even in -vga mode
btw ef2000 is verite 4k exclusive too as it is statically linked for 3dfx 😀

Ef2000 doesn't run at the mo. I have a few more tests for Verité board owners to test. Will knock them up tomorrow.

Verité 4k exclusive!(tm). Sounds nice.

The spdy3d stuff is statically linked as well.

isn't speedy stored in the SPD3D.uc? just like glide in glide2x.ovl?

No the uc file contains the 3d command interpreter for gpu. Rredline apps rely on uc microcode as well. It's like an implementation of direct3d or opengl for the gpu.

Verité boards can't render anything until the microcode's loaded. It's like the os/3d rendering bios for the gpu.

Speedy3D apps don't have redline.dll or verite. Dll or equivalent. Ovl files. These are statically embedded inside the games dos4gw implementation. All of the equivalent high level calls are hidden from rready and an element of experimentation is required to get games to run. In fact, that's why Whiplash's mirrors don't work and tomb raider has broken menus. Other things will just work.

Also there're some new commands which don't exist in rredline and no documentation to go with them. So a lot of playing around is needed. Nascar has a ridiculous number of these. Some of them have equivalents but appear to be different. A lot of them are virtually identical.

RReady ignores microcode and implements variations depending on the game.

[edit]
Sorry for editing this, but it's hard to type on my phone.

RReady can handle resolution scaling because the apps use a bios call to change resolution with a vesa or rendition internal mode number. These I've got from running tests on @whitmagicraven and @agentofthebsod's cards.

The framebuffer address which is where in gpu memory the display output is stored changes from game to game. A little playing around is necessary. I don't know whether vquake uses a fixed address or changes it depending on resolution. That's a bridge to cross another day.

@robertmo3, can you see if you can get Scorched planet running. A fixed clock rate of 40000 didn't seem to help.

it only helps in vga mode not in verite mode

mirror works in whiplash with different .uc (the one from cr_n2_sp_d2 and rm and quake)

robertmo3 wrote on 2024-05-08, 17:07:

mirror works in whiplash with different .uc (the one from cr_n2_sp_d2 and rm and quake)

With rready/Dr?

yes, also fixes performance a lot - works almost perfectly with cycles 105%

robertmo3 wrote on 2024-05-08, 17:20:

yes, also fixes performance a lot - works almost perfectly with cycles 105%

:0. How? The uc file isn't used by rready. It's usually loaded on to the Verité board, which in this case doesn't exist.

i mean intro audo jerkyness slowdowns with dma=0,

and this is how cart and nascar menus and rebel hud looks when using .uc from wl_tr_ef

robertmo3 wrote on 2024-05-08, 18:04:

and this is how cart and nascar menus and rebel hud looks when using .uc from wl_tr_ef

Holy..!

I wasn't doubting you. I just don't understand how this is happening.

I was under the impression that framebuffer addresses were generated by c based libraries in dos4gw. Your image implies the uc file has something to do with it.

Oh, I do. It's not the uc file, it's the size of the uc file. The framebuffer starts after the uc's loaded into ram. A bigger uc changes the framebuffer address.

Could you post the 2 uc file sizes? I guess this means the framebuffer address I generated for whiplash with the original firmware is wrong.

I don't have pc access right now.

robertmo3 wrote on 2024-05-08, 18:04:

and this is how cart and nascar menus and rebel hud looks when using .uc from wl_tr_ef

What you're seeing here is data meant for part of the front buffer being split because the start address is wrong.

I'll have to work out the framebuffer address based on the firmware size.

Do tomb raider's menus render properly with the cr_quake firmware?

tr menu background is either solid black or solid pink 😉

robertmo3 wrote on 2024-05-08, 18:40:

tr menu is either solid black or solid pink 😉

If you go into a game and hit escape, does the menu background render correctly? Game in background instead of black.