COBRA wrote: So it seems to be a problem with opening either lowlevel.library or utility.library there. Are you sure you have an OS4.0 final system with all the updates correctly installed that were available?
7.WoRkBeNcH:> version utility.library full utility.library 52.1 (2006-12-04)
7.WoRkBeNcH:> version lowlevel.library full lowlevel.library 51.6 (2005-11-06)
Is this the correct versions for an os4.0 system with the july update?
I get also a grimreaper immediately after choosing the screen resolution (so right before quake starts).
I gnoring it makes it possible to play Quake ..
The great addOn Malice also works fine with this quake version (but also only with grimreaper).
Increasing the stack doesnt solve the problem.
GLQuake would be even more fun How about a gl version of quake? The one availabe doesn't work with Malice! And there are some cool levels in Malice which only can be found/entered and played with GL-Extension
greetings, nexus
Sorry, forgot the most important thing: I tested it on Sam440ep with AOS4.1
For those who are interested, there's a new version of Quake available on OS4Depot which fixes some nasty bugs, has some optimizations, triplebuffering, and now works perfectly on Sam440 too.
It must be for SAM only; totally unusable here -- A1-XE/G4 and Rad-9250. It kind of resembles TV's sync lock problem. ? The old version always worked fine with PowerColor7000 and 9250.
It must be for SAM only; totally unusable here -- A1-XE/G4 and Rad-9250. It kind of resembles TV's sync lock problem. ? The old version always worked fine with PowerColor7000 and 9250.
Heh, no it's not Sam-only, and it was tested to run fine on an A1-XE/G4@933 and a Radeon 9250SE, as well as on a Pegasos2 with Radeon 8500. Works fine in all cases. I deliberately did not compile it with the latest SDK, but the one before it which was well proven.
Is it possible that you either:
1. Run with too low stack 2. Don't have INTERRUPT=Yes set in your Devs:Monitors/Radeon tooltypes?
What exactly happens? What if you run it with the -notriplebuffer option?
I don't have an AmigaOS 4.0 installation anymore to check. However I do recommend you to set up a second boot partition and do a fresh install of AmigaOS 4.0 on it. I'm sure quake ran fine on my AmigaOS 4.0 system, and I did not make any changes to the startup code where it crashes for you.
What wide resolution was that? The rendering routine of Quake processes 32 pixels in a loop, and does not handle the case when the width is not a multiple of 32, in which case you might get a smear kind of an effect (with each line offset some pixels horizontally), is that what you have experienced?
Yes, but the opengl version on os4depot isn't so smooth as the software render.. i think could help if someone could recompile it with the new sdk and maybe have a look at the source code.. i am talking about how does it runs on the SamEP440
Does this version of Quake support CD AUDIO ?, if yes how do i enable it ?
Good question, according to the History text, there is some untested one, but all I did was to take the original sources from Frank, made some fixes, and released a fixed version, so I don't know anything more than what is in the included text. There should be some kind of a Readme file, but there wasn't one in the original 2.20 archive that was on OS4Depot.net.
Something interesting: I did some benchmarks (with -notriplebuffer doing a 'timedemo demo1'), and on the Sam440-667 it is 35fps, while on the Pegasos2-G4-1Ghz, it is 50fps. I find this very surprising, because this means it's only 42% faster on the Peg2 than on the Sam, even though the clock speed of the Pegasos2 is 50% higher, and there is also an L2 cache on the Pegasos2, which the 440EP does not have. And this is pure CPU rendering, so it is very surprising that it performs so well on the Sam.