Quake 060 performance

[NovaCoder]

Originally Posted by litwarski

I just checked and I got an average 13.9 FPS from timedemo demo1. The demo seemed to slow down when there were flashes from the weapons, and when there were multiple enemies. When I watched the demo a sceond time, the FPS jumped to 15.9.

When I play the game myself, the slowdowns appear when the room I'm in is big. If I look at a nearby wall, the game looks smooth enough.

Oxypatcher doesn't help with AmiQuake, you need HSMATHSLIBS.

What file system are you using, if you are using FFS it will probably slow it down quite a bit. I recommend PFS3 060 version.

[litwarski]

I use PFS3, didn't know of an 060 version of it though.

I did manage now to get to 14.9 FPS by using the FastPatchQuake and a demo version of HSMathLibs.

[phx]

Depending on the Quake version being played I cannot believe that patching math libraries does make much of a difference. Most versions use hand optimized assembler code for the most important routines, which certainly avoid instructions which have to be emulated. The rest is compiled with fpu=68060 settings, which should avoid these instructions as well (depending on the compiler used).

Also note that the graphics card makes a big difference. I think nobody mentioned that yet. I remember that for Zorro3 the CV64 always allowed the fastest frame buffer write speeds. I doubt that the ZZ9000 is much better.

[Thomas Richter]

Ditto. These libs only make a difference if the source is stupid enough to use the FFP format for floating point *and* call into any math library in first place - and I really doubt this. It potentially could use the IEEE math libraries, which are the recommended math libraries anyhow, and for them, it does not matter which version you take. It's only one FPU instruction per library entry anyhow.

This being said, I doubt it even uses math libraries. If it requires the FPU, and it is speed critical, it would rather use the FPU directly instead of going through the Os math model.

[Marce]

none of such math libraries makes any difference in framerate in quake
either oxypatcher or similar program does not make any difference
just urban Amiga myths

Today to play quake at a reasonable speed in a real Amiga you need yo use some unofficial quake port and a PPC
even the slowest PPC in the blizzards which is at 160 mhz makes a big difference

[tom256]

Originally Posted by Daedalus

That's a 486 at 100MHz, not a Pentium. The 200MHz Pentium manages around 45FPS, so all other things being equal you might expect around 22FPS from a 100MHz Pentium.

Pentium 75:
17.5fps

[ Show youtube player ]

Pentium 60:
14.4fps

[ Show youtube player ]

All are 320x240. I think Amiga version runs 320x256.

[trixster]

Both clickboom quake and AmiQuake can be set to render 320x240

[tom256]

Originally Posted by Marce

Quake uses fpu
that's why is faster on a pentium 100 than a 486/100
because the fpu in the pentium is 2x faster

the 060 fpu is something around the 486 fpu speed

on the Amiga + overclocked 060 you can expect 12-13 fps at 300x200 not 16
there is nothing else that can be done to speed up this game
personally I prefer to be jailed instead play a 3d game at 12-13 fps

technically the game Quake should never have been made for the Amiga
because the Amiga does not have enough power to run that game at descent speed
it was a simple matter of business

That is not true. MC68040 has more effcient FPU than 486, and is more faster clock to clock.
Problem with MC68060 and it FPU is more complex. Clock to clock MC68060 has faster ALU than early Pentiums. Performance problems staring to apear when you are using FPU, due one shared pipeline with FPU. So to simplify you can use 2 ALU unit at once, or one ALU and one FPU.
This was designed to keep with transistor limit in CPU.

[Marce]

Originally Posted by tom256

That is not true. MC68040 has more effcient FPU than 486, and is more faster clock to clock.
Problem with MC68060 and it FPU is more complex. Clock to clock MC68060 has faster ALU than early Pentiums. Performance problems staring to apear when you are using FPU, due one shared pipeline with FPU. So to simplify you can use 2 ALU unit at once, or one ALU and one FPU.
This was designed to keep with transistor limit in CPU.

yes 040 and 060 fpus are a bit faster than the 486 and 586 but just a bit
but not as fast as earliest pentiums clock by clock
in fact u uploaded a video where a pentium 75mhz did 17 fps in quake,
while OP computer is 80mhz and he said does 13.9 fps

[neocdtv2]

Hardware:
A4000TX, BFG9060 with 68060@100Mhz, Cybervision 64/3D
Software:
AmigaOS 3.1, CyberGraphX V4, Warp3D 4.2a, mmulib
GLQuake 320x200x15bit - 12,3FPS - [ Show youtube player ] - you can tweak it up to 14.5 kommen
Clickboom Quake CGXv4 320x200x8bit - [ Show youtube player ] - 21,27FPS
Clickboom Quake CGXv4 320x200x15bit - [ Show youtube player ] - 17,7FPS
Clickboom Quake AGA NTSC 320x200x8bit - [ Show youtube player ] - 20,25FPS
NovaCoder AmiQuake AGA NTSC 320x200x8bit - [ Show youtube player ] - 17,9FPS

Hardware:
A4000TX, BFG9060 with 68060@100Mhz, Cybervision 64
Software:
AmigaOS 3.1, CyberGraphX V4, Warp3D 4.2a, mmulib
Clickboom Quake P96 3.2.x 320x200x8bit - [ Show youtube player ] - 23,45FPS
Clickboom Quake P96 3.2.x 512x342x8bit - [ Show youtube player ] - 15,33FPS (non-Fullscreen)
Clickboom Quake AGA NTSC 640x200x8bit - [ Show youtube player ] - 14FPS (non-Fullscreen)

[Estrayk]

Hardware:
A1200, Trinity 1260 with 68060@100Mhz, AGA
Software:
AmigaOS 3.2.1, AGA, mmulib, MuRedoX, copymemaio, blazewcp.
Clickboom Quake AGA 320x256x8bit - [ Show youtube player ] - 14,27FPS

[neocdtv2]

Originally Posted by Estrayk

Hardware:
A1200, Trinity 1260 with 68060@100Mhz, AGA
Software:
AmigaOS 3.2.1, AGA, mmulib, MuRedoX, copymemaio, blazewcp.
Clickboom Quake AGA 320x256x8bit - [ Show youtube player ] - 14,27FPS

Can you make a Video in NTSC?
Does copymemaio, blazewcp have impact on the performance?

[Estrayk]

Originally Posted by neocdtv2

Can you make a Video in NTSC?

17,54 FPS in 320x200

Does copymemaio, blazewcp have impact on the performance?

I dont know, let me check it...