I've decided to re-install Quake again, to check it with the new Warp3D drivers on my R9 270 gfx card, but while it's fully playable it gives me graphical glitches. I'm using Quake 2.40 (Frank Wille's port). Any ideas?

_________________

@Phantom

What kind of glitches? What machine? GLQuake ?

On my X1k the *software* version of quake glitches oddly with whole walls disappearing / going grey. This is ofcourse nothjing todo with teh warp3d drivers but I'm not sure that Frank Quake is GL based....

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

On X1000 of course, but I remember that I didn't have this problem before (at least with Wazp3D). Yes, exactly the same effects, walls disappearing or going grey.

I tried FuhQuake but it crashed on startup.

_________________

@Phantom

Well whatever causes it . it's not Warp or Wazp 3D as Quake is software rendered.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@Phantom

If you were using a different video card before then here is the probable answer.

http://www.amiga.org/forums/showpost.php?p=788660&postcount=3

@Rob

That's not remotely the issue. The colours are fine, what we see is missing sections of graphics, it's a calculation issue *not* graphics issue, as the rendering is software based. Smething odd goes on with the culling of polygons, but strangely on on the x1k. Some very subtle processor incomptablity.

Last edited by broadblues on 02-May-2015 at 04:31 AM.

_________________
BroadBlues On Blues BroadBlues On Amiga Walker Broad

@broadblues

Ok.

@Rob

Yes, correct, it's software rendering only.

About fuhquake, it's missing a libpng14.so.14, nowhere to be found. Anyone have it want to share it here? And yes, renaming another libpng15.so.15 or libpng16.so.16 doesn't work.

_________________

Quote:

broadblues wrote: That's not remotely the issue. The colours are fine, what we see is missing sections of graphics, it's a calculation issue *not* graphics issue, as the rendering is software based. Smething odd goes on with the culling of polygons, but strangely on on the x1k. Some very subtle processor incomptablity.

Maybe a floating point precision or rounding problem? Frank's publically available Quake PPC executable (from his web site) is likelly compiled with an older version of vbcc. I think there is a newer version of the source code in some SVN somewhere also. The problem may go away by obtaining the newest sources and compiling with the newest version of vbcc (or GCC). The PPC assembler soures can be disabled when building to see if that is a problem also. I have not observed any gfx gliches (or instability) in the 68k version of his Quake compiled with GCC or vbcc although the 68k FPU initialization was fixed in the newer version of vbcc and I fixed a minor bug or 2 in the Quake 68k assembler sources which didn't seem to be causing problems. Frank and I use his software rendered version of Quake to test for floating point problems in vbcc. I expect he would be interested to hear from anyone about problems. GLQuake/BlitzQuake would be better for testing Warp3D though ;).

@Phantom

Try this:

https://dl.dropboxusercontent.com/u/26599983/libpng-1.4.16.7z

I just quickly cross-compiled it so it is completely untested.

@salass00

Thanks, but it gives a grey screen and nothing else. Maybe somebody else wants to give it a try?

_________________