HVSCMAZE

[nicolaspersijn]

Some important code in this rom that doesn't exists anywhere else, apparently.

 

Have at it, guys!

HVSCMAZE.rom

[+CyranoJ]

If you are talking about the gpu compiler then no. None of that will be in the rom just the output from it.

[TXG/MNX]

yep this is what's known about this demo, written by Scott Corley

 

 

This is a direct translation of a Dr. Dobbs Journal raycasting demo.
It runs entirely on the GPU. The 68000 is stopped while this demo
is running. (If you stop the stub in the debugger and trace over a
few 68000 instructions, you'll notice the GPU wakes up and runs the
demo even though the 68000 is still running the debugger stub).


The changes that were made from the Dr. Dobbs version are:
Reading graphics from ROM instead of from files
Using blitter to copy pixels instead of CPU
Adding work-around to fix compiler comparison bug


Compilation:
The C code was compiled with GCC for GPU version 2.6.
The code was post processed with GCCGPUM (HVS tool).
No hand-tweaking was required.
No 4k segments were required.
No function grouping was required.
In other words, it went pretty smoothly.
The overall size of the code running is larger than 4k.
The HVS GPUMGR is used to handle virtualization of the
GPU cache.


The frame rate is 30FPS. None of the code is hand optimized
assembly, it is all C. Screen copy and vertical line drawing are
done with the blitter (set up from C).



Scott

 

This demo was build with the AGPU 2.6 GCC compiler from the Atari Jaguar Dev-kit. HVS was the only company we know that got this compiler working.

The did compile it with the compiler and ran a program GCCGPUM (HVS tool) and this would fix all bugs/issues that could exist in the output code of the gcc compiler.

This program is still lost, maybe it will be found someday.

 

But the fact is that they had the compiler working and have used this HVS GPUMGR in several projects, one of them would be Ruiner Pinball but some other releases later then Ruiner should use it aswell.

 

We suspect TRF and Dactyl Joust did use it also.

[Clint Thompson]

Looks to be only 1MB of real data, most of which are graphics.

 

Howdy! GPU Routine table is corrupt. GPU BSS Seg table is corrupt.

MAPS (plural) but probably doesn't mean they exist.

[KidGameR186496]

I'm impressed that they managed to cap 30fps on the Jaguar,That's a miracle. Many Thanks to you Nick for posting this

Edited November 21, 2016 by KidGameR186496

[JagChris]

I don't think the GPU manager was mature enough to be used until sometime after NBA Jam.

[JagChris]

Looks to be only 1MB of real data, most of which are graphics.

 

Howdy! GPU Routine table is corrupt. GPU BSS Seg table is corrupt.

 

MAPS (plural) but probably doesn't mean they exist.

You have a copy of the ROM?

[neo_rg]

I love it when people read stuff but don't notice stuff that's right in front of them. Look at the first post again....

[JagChris]

OK thanks just woke up lol

[JagChris]

Someone post a video. Prefer vimeo

[Fredifredo]

ok .. it's a rom created with something lost and no chance to be find now...

any real interest ?

[JagChris]

ok .. it's a rom created with something lost and no chance to be find now...

any real interest ?

Judging by the downloads, yes!

 

The GPU manager is buried in their somewhere running the show.

[+CyranoJ]

Howdy! GPU Routine table is corrupt. GPU BSS Seg table is corrupt.

 

 

I love it when people read stuff but don't notice stuff that's right in front of them. Look at the first post again....

 

 

Judging by the downloads, yes!

 

The GPU manager is buried in their somewhere running the show.

[JagChris]

I dunno. Haven't had a chance to try it myself.

 

As for the error message as usual it is posted without context. And no one else has corroborated yet. Is it via bjl? Alpine? Skunk? No one knows because not enough info was given.

 

However it obviously runs and works. People are posting pics of it in action.

 

Non sequitur anyways. Interest generated is still high. Can't be helped.

[VladR]

Is there, somewhere, a description of full functionality of their GPU Manager ?

 

Granted, I haven't written a GPU code just yet, but I read my fair share of GPU code and once you blit the code into the cache using Blitter, there's really not much else you want to be doing 'managing' that code, other than swapping of the pieces that do not fit in (e.g. a simple list of code blocks).

 

Usually, there's a dispatcher switch..case block a the start (to choose between various small routines that all fit into the cache), so really the only meaningful functionality of GPU MGR seems to be blitting the blocks of code from some list of code blocks (to work around the 4KB limit).

 

Anything else useful that the GPU MGR might be doing ?

[JagChris]

Yes see the link I posted a couple replies up. The author talks about it in depth

[JagChris]

Wrong thread. Here, and actually read it. Because I know you don't like reading docs and if you show up 6 months from now wondering what a GPU manager is am gonna throw stuff at you.

 

http://www.3do.cdinteractive.co.uk/viewtopic.php?f=35&t=3492

Edited November 21, 2016 by JagChris

[VladR]

Wrong thread. Here, and actually read it. Because I know you don't like reading docs and if you show up 6 months from now wondering what a GPU manager is am gonna throw stuff at you.

 

http://www.3do.cdinteractive.co.uk/viewtopic.php?f=35&t=3492

For some reason, the link keeps disappearing, but when I quote it, it's actually there. Weird. Browser bug ?

 

From the link it looks like there are 2 main additional features:

- LRU caching

- Address remapping

 

Still not convinced not to rather write them from scratch, if desired ...

Edited November 21, 2016 by VladR

[skip]

Someone post a video. Prefer vimeo

A video would be great and appreciated. It loads but does nothing in Virtual Jaguar on the Mac.

[Beta Phase Games]

Nice to finally get the opportunity to play a couple Thea Realm of Fighters builds.

 

Recently got a capture card for another project so here's a video:

 

[JagChris]

Thank you. This was on actual hardware? Bjl? Alpine? Skunk?

 

Did you run into any corruption messages or other errors?

[TXG/MNX]

It runs on skunk and you can scale the walls within the view smaller or taler.

 

I think at one time the code freezes but I think its more random than on a specific place/time.

 

Its funny it runs on a real Jaguar but not on Virtual Jaguar I tryed all options.

[adriano gt]

It runs on skunk and you can scale the walls within the view smaller or taler.

 

I think at one time the code freezes but I think its more random than on a specific place/time.

 

Its funny it runs on a real Jaguar but not on Virtual Jaguar I tryed all options.

 

A friend helped me run this in dosjag - THANK YOU, DXWHO

But it has no purpose, this labyrinth.

Or did anyone find something?

[TXG/MNX]

Hi read the 3th post on the beginning of this thread. This demo was made by a coder of High-Voltage Software. The demo was build with the GCC compiler from the devkit. Both the 68k and gpu/dsp code was done in C. High-Voltage was the only company we know that used the Risc GPU/DSP C compiler and used it. This demo showed it did work. Later they did more titles in C like Ruiner Pinball.

 

Sent from UMI hammer with Tapatalk