Hyperion Entertainment Message Boards

samo79 wrote:Yes maybe .. instead is there any hope about the freeze problems ?

Apart WipeOut that is a WarpOS game with all their in-famous issue involved, still bad freeze also in Quake 3 (as i said in my previews post) but also in some old games like Enforce 68k .. i really hope that soon or later a fix can be found for them

Thanks a lot Karlos, updates and fix are always apprecied !

Was Enforce ever even released? I seem to recall it being just an engine demo.
http://aminet.net/package/game/demo/Enforce_demo01

^ According to this, it doesn't work on Picasso96 at all.

Karlos wrote:Was Enforce ever even released? I seem to recall it being just an engine demo.
http://aminet.net/package/game/demo/Enforce_demo01

Yes sadly it's a demo engine only, not a full game

Karlos wrote:^ According to this, it doesn't work on Picasso96 at all.

First version 0.1 does not work, instead you should download the latest version 0.2 availible here:

http://aminet.net/game/demo/Enforce_demo02.lha

This one will start fine using the default settings, just download, extract it and start
Once the engine start you will be able to move yourself into the labirinth for atleast a couple of seconds, then the machine will freeze

samo79 wrote:This one will start fine using the default settings, just download, extract it and start
Once the engine start you will be able to move yourself into the labirinth for atleast a couple of seconds, then the machine will freeze

I tried it in 4.1 on my classic, which should have improved compatibility since at the time it was written, the Permedia was one of the few cards that could run it. There are a very very large number of illegal memory accesses (enough to overflow the debug buffer) being made that were nothing to do with Warp3D. Suppressing these DSI, I got as far as a black screen and that was it. The CPU was maxed out, however.

I would't hold this demo up as an example of the problems you are encountering. It probably freezes for other reasons.

Despite not having a working radeon system for a while, with the help of a couple of testers, I think the bug reported here could well be fixed.

Karlos wrote:I would't hold this demo up as an example of the problems you are encountering. It probably freezes for other reasons.

Note to self, happened to test this the other day in OS3.9 with Warp3D 4.2, CGX 4.2 and it does run, it also tends to bomb randomly.

Karlos wrote:Despite not having a working radeon system for a while, with the help of a couple of testers, I think the bug reported here could well be fixed.

Good i hope it will be possible, that engine is a nice attemp

Karlos wrote:Note to self, happened to test this the other day in OS3.9 with Warp3D 4.2, CGX 4.2 and it does run, it also tends to bomb randomly.

Many of that old games/demos are surely not so compliant in general so i'm not surprised that they can have problems even under classic machines .. not to mention that there are games that seems to work (more or less) under cartain OS4 hardware (AmigaOne for example) but still fail on others --> Sam440 expecially SamFlex with a different GFX, or higher clock

Also for that reason i opened a compatibility list thread at: http://forum.hyperion-entertainment.biz ... f=14&t=404
and WipeOut is a very interesting example even if not the only one .. a proper testing for all that games/programs would be hard and time consuming i fear ..

samo79 wrote:Good i hope it will be possible, that engine is a nice attemp

The issue this thread is about is nothing to do with the Enforce engine. FWIW, given that the latter also randomly crashes on a real 68K running OS3.9 with CGX then I wouldn't hold a lot of hope for it.

Ok understand .. and the others ? can we do somethings for them ?

For example FxPaint, Nightlong or PuzzleBOBS

.. not to mentions the in-famous WipeOut (i start to hate it)

@samo79
As far as i know FxPaint do not use warp3d.

And anyway, all those old warpos based programms/games will never works normally, until (and if) someone will create a new version of warpos.library , or get a sources from Joerg and improve them. In most cases with all that games problem is warpos emulation, not warp3d. Karlos there can do nothing with only warp3d improvements.

kas1e wrote:In most cases with all that games problem is warpos emulation, not warp3d. Karlos there can do nothing with only warp3d improvements.

That's definitely true for WipeOut at least. I was able to play it without any issue for hours with both R100 and R200 cards in my A1 and the Permedia2 in my A1200. The stack trace from the crashlog Samo send from his machine indicated the problem was somewhere in the powerpc.library, though it isn't possible to figure out what exactly.

sure it's a problem in warpos emulation, on Sam460 it has never worked, some time ago i asked a version for these kind of CPUs (AMCC460) but probably anyone has no interest in it