robertmo3 wrote on 2024-06-16, 13:48:

if you press F6 then + and - is not crushing

Hmm. Need to see what's happening with F6 as well. It's a bit hard to debug because dosbox and rready don't indicate some thing's wrong. Something dosbox r does causes the game to meltdown.

[EDIT] tomorrow will be a rebel moon day. [/EDIT]

robertmo3 wrote on 2024-06-16, 13:48:

if you press F6 then + and - is not crushing

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash..

This might be a game bug.

Also the resolution change is weird at 640x400 (at startup)

the framebuffers are 0xE000, 0xE00 + (640x400*2)

At pretty much every other resolution the framebuffers are at the same addresses, which makes no sense because at 640x480 buffer 0 will spill over into buffer [EDIT]1 (not 0)[/EDIT].

Until someone with a Rendition card and a copy of Rebel Moon can confirm that all the issues with Rebel Moon do in fact work properly , I'm putting all work on Rebel Moon on hold.

sharangad wrote on 2024-06-17, 11:56:

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash.. […]
Show full quote

robertmo3 wrote on 2024-06-16, 13:48:

if you press F6 then + and - is not crushing

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash..

This might be a game bug.

Also the resolution change is weird at 640x400 (at startup)

the framebuffers are 0xE000, 0xE00 + (640x400*2)

At pretty much every other resolution the framebuffers are at the same addresses, which makes no sense because at 640x480 buffer 0 will spill over into buffer 0.

Until someone with a Rendition card and a copy of Rebel Moon can confirm that all the issues with Rebel Moon do in fact work properly , I'm putting all work on Rebel Moon on hold.

I have tried on original game bundled with 3D Blaster PCI, run it with Verite mode and
F7 crushes
F6 garbaged screen
+ freezes
- freezes
I have also tested these in CGL mode and none of them have any effect.

Gona wrote on 2024-06-17, 20:20:

I have tried on original game bundled with 3D Blaster PCI, run it with Verite mode and F7 crushes F6 garbaged screen + freezes - […]
Show full quote

sharangad wrote on 2024-06-17, 11:56:

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash.. […]
Show full quote

robertmo3 wrote on 2024-06-16, 13:48:

if you press F6 then + and - is not crushing

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash..

This might be a game bug.

Also the resolution change is weird at 640x400 (at startup)

the framebuffers are 0xE000, 0xE00 + (640x400*2)

At pretty much every other resolution the framebuffers are at the same addresses, which makes no sense because at 640x480 buffer 0 will spill over into buffer 0.

Until someone with a Rendition card and a copy of Rebel Moon can confirm that all the issues with Rebel Moon do in fact work properly , I'm putting all work on Rebel Moon on hold.

I have tried on original game bundled with 3D Blaster PCI, run it with Verite mode and
F7 crushes
F6 garbaged screen
+ freezes
- freezes
I have also tested these in CGL mode and none of them have any effect.

Oh wow! Thanks Gona!

Does the level 06 switch save crash if you jump down the precipice behind you (download/file.php?id=195373)?

Oh BTW, the PM system is very slow, sometimes it takes over a week to send a message, not sure whether it's because the recipient's inbox is full.

sharangad wrote on 2024-06-18, 03:32:

Oh BTW, the PM system is very slow, sometimes it takes over a week to send a message, not sure whether it's because the recipient's inbox is full.

this only means if someone has actually read the message or not.

Two more FIFO tests:

FIFO2 is interactive and should dump stuff to the console.

FIFO3 will take twice as long. It too dumps to the console, but because it's a graphical app you won't see anything.

For some reason the previous FIFO test locked up while querying a mode and the modes it was querying weren't on the list.

If these two crash in the same way I've got a memory corruption problem (all of these run in dosbox-rendition just fine).

https://nirvtek.com/downloads/Fifo.20240618.004.zip (two exes inside)
MD5: 32f15ef9483b798024082667853e7712

Gona do + and - work after pressing F6?

Gona wrote on 2024-06-17, 20:20:

I have tried on original game bundled with 3D Blaster PCI, run it with Verite mode and F7 crushes F6 garbaged screen + freezes - […]
Show full quote

sharangad wrote on 2024-06-17, 11:56:

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash.. […]
Show full quote

robertmo3 wrote on 2024-06-16, 13:48:

if you press F6 then + and - is not crushing

If you start a game and hit '+' (at the default resolution 640x400) the game doesn't crash..

This might be a game bug.

Also the resolution change is weird at 640x400 (at startup)

the framebuffers are 0xE000, 0xE00 + (640x400*2)

At pretty much every other resolution the framebuffers are at the same addresses, which makes no sense because at 640x480 buffer 0 will spill over into buffer 0.

Until someone with a Rendition card and a copy of Rebel Moon can confirm that all the issues with Rebel Moon do in fact work properly , I'm putting all work on Rebel Moon on hold.

I have tried on original game bundled with 3D Blaster PCI, run it with Verite mode and
F7 crushes
F6 garbaged screen
+ freezes
- freezes
I have also tested these in CGL mode and none of them have any effect.

The other thing I've noticed is that f6/F7 switch to 15 bit modes which isn't normal. Rredline and all the speedy 3d games which work with rready default to 16 bit modes. This includes rebel moon, at least until you hit f6/F7.

F6/f7 cycle between 640x480/15-640x400/15-320x200/15. 640x480 works with rready with some corruption but 320x200 produces a black screen. The game doesn't crash, you can cycle between them.

640x480/15 works with rready because internally all framebuffer modes are treated as rgb565 (/16). Videos are rendered in 15 bit colour and rready converts them to rgb 565.

robertmo3 wrote on 2024-06-18, 03:48:

sharangad wrote on 2024-06-18, 03:32:

Oh BTW, the PM system is very slow, sometimes it takes over a week to send a message, not sure whether it's because the recipient's inbox is full.

this only means if someone has actually read the message or not.

Oh and I thought this worked like a mailbox.

it works differently than you describe:
game starts in 640x400
F6 switches to 640x480 (only to 640x480)
F7 switches to 320x200 (only to 320x200)
F7 sometimes often works but you need to press it twice (and don't look at the wall) (maybe high fps prevents it from working)
Start new game, move back till you start to see walls of a tunnel and move forward till you stop seeing them, press F7 twice. If it didn't work: press F6, wait, press F7 twice.

Rendition BIOS info:

[EDIT] to detect board
Int 10h AX=0x158D (Detect if Rendition BIOS is present)
On exit CX and DX contain entry point BIOS address and BIOS segment (CX depends on BIOS and DX is 0xC000)

Int 1A AX=0xB101 Query PCI version.
See here:
https://www.delorie.com/djgpp/doc/rbinter/id/81/23.html

(For vQuake and so far only for vQuake, EDI needs to return a 32 bit address to call to run Int 1A queries from protected mode.)

Int 1Ah AX=0xb101, CX=0x01, DX=0x1163 (Query PCI device by ID)
(CX=1 for V1000 and CX=2000 for V2000, DX is the PCI manufacturer ID 0x1163).
return bus num in BH and dev num in BL. The call is described here:https://www.delorie.com/djgpp/doc/rbinter/id/82/23.html

Int 1Ah AX=0xb108, CX=((BusNum<<8)|devNum), DI = <reg num> (Query PCI device by ID)
Read PCI device register (These are not GPU registers, but PCI interface controls like interrupts.) The PCI register list can be found in the v2200 spec(http://vogonsdrivers.com/getfile.php?fileid=324&menustate=0) on page [EDIT]39[/EDIT].

The int call is described here:https://www.delorie.com/djgpp/doc/rbinter/id/85/23.html

Int 10h AX=0x1582, All regs 0
Called to possibly stop the currently running microcode program [EDIT[(RISCReset)[/EDIT]

Between these calls the microcode has to be copied over to VRAM,.

Int 10h AX=0x1583, CX=<board relative address of firmware> all other regs 0
runs the microcode at GPU address stored in register CX. (Usually 0x1000).

[EDIT] After this and before running actual handing out commands:
Int 10h AX=0x1584 (all regs 0)

Int 10h AX=0x1587, BX =0x10 (all others 0) (Possibly run subroutine at program start(0x1000 + register BX)

Int 10h AX=0x1580 (all regs 0)

Issue commands

To shutdown do an Int 10 h setmode mode 3 (text).

edited previous post

robertmo3 wrote on 2024-06-18, 07:51:

it works differently than you describe: game starts in 640x400 F6 switches to 640x480 (only to 640x480) F7 switches to 320x200 ( […]
Show full quote

it works differently than you describe:
game starts in 640x400
F6 switches to 640x480 (only to 640x480)
F7 switches to 320x200 (only to 320x200)
F7 sometimes works but you need to press it twice from a F6 mode (you need to press F6,F7,F7) (and don't look at the wall) (maybe high fps prevents it from working)

You're absolutely right. I was wondering why the cycling wasn't working properly.

So is there no way to switch back to 640x400?

not that i know of, but i wonder: "-vga" mode starts in 640x480
maybe verite should start in 640x480 too

you quoted my post before it was edited - it has a mistake

robertmo3 wrote on 2024-06-18, 08:02:

you quoted my post before it was edited - it has a mistake

It's ok, I re-read it.

On actual hardware the game starts up at 640x400.

So I should be able to knock up a working test app now.

when i say F7 works i mean that you can play it - cause you said it is black screen for you
for me it either:
1 freezes picture in 320x200
2 freezes picture with black screen with few green dots
3 works ok, with blinking screen and some textures blinking black too

for point 1 i have to press F6 to unfreeze
for point 2 you can immediately press F7 and it may move to point 3 (if you press F7 too late, than you have to press F6)

robertmo3 wrote on 2024-06-18, 08:56:

when i say F7 works i mean that you can play it - cause you said it is black screen for you for me it either: 1 freezes picture […]
Show full quote

when i say F7 works i mean that you can play it - cause you said it is black screen for you
for me it either:
1 freezes picture in 320x200
2 freezes picture with black screen with few green dots
3 works ok, with blinking screen and some textures blinking black too

for point 1 i have to press F6 to unfreeze
for point 2 you can immediately press F7 and it may move to point 3 (if you press F7 too late, than you have to press F6)

Yes that's what I see too.

Could someone with a Verité board run this and see if it produces a red square and then shuts down after 5 seconds. Dosbox-Rendition users may have to press [ENTER] after 5 s.

https://nirvtek.com/downloads/Square.20240618.001.zip
MD5: ecfa4f9ffb153d27f90fa9c57ed0fcb9

(You will need the included UC file).