@BinoX

Have you installed the latest OS update #4. I had this problem before with Heretic II demo but one of the OS updates fixed this (Radeon 7000).

@salass00

Yeah.. I'm usuing update 4... I didn't install heretic 2 until I had update 4.. heh

_________________
Back to action!

@Hans

Quote:

Yes but there are always system differences that get in the way. For example, a serial class for windows that I was using started to really crawl ( 0.5 seconds to send a 10 character string) once I switched to Visual Studio 2005 express. This was due to a difference in the way that Visual Studio handles BOOL -> bool conversions. After "porting" the class to VS2005, performance was back where is should be.

Typically, BOOL is an "int". It generates performance warnings in VC++ 7.1/VS .NET 2003) during BOOL-bool conversions.

Last edited by Hammer on 13-Jul-2006 at 11:52 AM.
Last edited by Hammer on 13-Jul-2006 at 11:51 AM.
Last edited by Hammer on 13-Jul-2006 at 11:49 AM.
Last edited by Hammer on 13-Jul-2006 at 11:46 AM.

_________________
Ryzen 9 7900X, DDR5-6000 64 GB RAM, GeForce RTX 4080 16 GB
Amiga 1200 (Rev 1D1, KS 3.2, PiStorm32lite/RPi 4B 4GB/Emu68)
Amiga 500 (Rev 6A, KS 3.2, PiStorm/RPi 3a/Emu68)

@Hans

Quake 3 Arena 1.30+ is said to be optimized for PPC G4 (MacOS)…

Last edited by Hammer on 13-Jul-2006 at 12:12 PM.

_________________
Ryzen 9 7900X, DDR5-6000 64 GB RAM, GeForce RTX 4080 16 GB
Amiga 1200 (Rev 1D1, KS 3.2, PiStorm32lite/RPi 4B 4GB/Emu68)
Amiga 500 (Rev 6A, KS 3.2, PiStorm/RPi 3a/Emu68)

With the same config and prefs i have 30 fps with the AmigaOS4 final.
2 frames more than with update4.

_________________
AmigaOne X1000 1,8 Ghz/2 GB Ram + Radeon 6670 2 GB + AmigaOS4.1
A4000T CyberstormPPC 604e-200Mhz/060/128MB+CybervisionPPC 8MB + AmigaOS4
and anymore other Amigas...

@AmigaPapst

There's a good performance table @ppcnux

_________________
Indigo 3D Lounge, my second home.
The Illusion of Choice | Am*ga

@zErec

Quote:

When starting Q3 Arena I notice an uncorrect display of the mirror effect

It's a bug in the user cliplane code within MiniGL.

@itix

Yes, they use the same code, basically (at least the time critical code is the same, i.e. rendering etc).

The problem with 3d speed is two-fold:

For one, the screen switching takes an enormous amount of time, roughly 30-40 % of the time is taken up by screen switching alone (run the MiniGL gears demo, which will show you the time spent rendering the frame, and switching the buffers). On the Radeon, this is even worse if no interrupts are enabled.

The second problem is the non-existent integration of 3D and 2D drivers. One is always in the way of the other, so the 3D driver practically has to initialize for every frame it draws, adding to the overhead (around 40 % of the computing time are used in setup and cleanup operations).

As stated earlier, this is the reason why we didn't go for a full OpenGL support yet, since the effort would basically be wasted without a new graphics subsystem.

This will be addressed in later OS4.x versions.

As such, speed comparisons between MorphOS and AmigaOS are not really of much use, not to mention that comparisons would only be valid between them if they'd run on exactly the same hardware.

Edit: Oh, just realized how old this thread is

Last edited by EntilZha on 24-Jan-2007 at 03:03 PM.

_________________
Thomas, the kernel guy

"I don't have a frigging clue. I'm norwegian" -- Ole-Egil

All opinions expressed are my own and do not necessarily represent those of Hyperion Entertainment

@EntilZha

Quote:

EntilZha wrote: The problem with 3d speed is two-fold: For one, the screen switching takes an enormous amount of time, roughly 30-40 % of the time is taken up by screen switching alone (run the MiniGL gears demo, which will show you the time spent rendering the frame, and switching the buffers). On the Radeon, this is even worse if no interrupts are enabled. The second problem is the non-existent integration of 3D and 2D drivers. One is always in the way of the other, so the 3D driver practically has to initialize for every frame it draws, adding to the overhead (around 40 % of the computing time are used in setup and cleanup operations). As stated earlier, this is the reason why we didn't go for a full OpenGL support yet, since the effort would basically be wasted without a new graphics subsystem. This will be addressed in later OS4.x versions.

Do you mean that Picasso96 will be replaced, or will it be a rework of the internals? Also, any idea how long development of a new graphics subsystem will take? I'm asking because I use OpenGL and full OpenGL support is something that I'm waiting for. While I'm not counting on it coming any time soon, shader support and GLSL are important for the kind of stuff that I do.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

@Hans

The plan is to replace everything that is attached to "graphics". This includes the original graphics library, Picasso96, and everything else. The idea is to build a foundation that is based on Porter/Duff IC, and stupports native lowest-level OpenGL to allow the graphics foundation to make use of it for the IC, supports native multiheading, Xinerama-style multi-desktops, things like that.

It is unknown how long that will take. We will also need to build a compatibility system that can be used to run old apps. Currently we're in early planning for this.

_________________
Seriously, if you want to contact me do not bother sending me a PM here. Write me a mail

@Rogue

So you're ripping the old system out and providing a compatibility layer. Sounds like quite a task. But it will result in a much higher performance graphics system. Those overheads that EntilZha talked about sound really big. Guess I'll have to stick to development on PCs for now when it comes to graphics.

Hans

_________________
http://hdrlab.org.nz/ - Amiga OS 4 projects, programming articles and more. Home of the RadeonHD driver for Amiga OS 4.x project.
https://keasigmadelta.com/ - More of my work.

My speed on Q3 is great once I am in the game, but it is horrible durring the disk access.

When it goes into the setup screen I have to wait for each action. Loading each item into the game takes about half a minute. On the PC it just flies through this stuff and you hardly notice.

I had a thought that it might be due to the no DMA problem. I have since loaded a Sil0680 card and it still seems slow. However, I have had a little problem with configuring it, so I am not sure if it is using DMA or not.

I have a SX with a G4 processor. I don't really care if it has a high frame rate. It plays smooth once things are loaded, but the disk access is a killer for me.

@Rogue

I think this bit odd what you’re saying because, I see there have been updates to Warp3D drivers, (don’t you think it’s better to spend time on OpenGL?)

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@EntilZha

Quote:

The second problem is the non-existent integration of 3D and 2D drivers. One is always in the way of the other, so the 3D driver practically has to initialize for every frame it draws, adding to the overhead (around 40 % of the computing time are used in setup and cleanup operations).

So how much work do you think it is to rewrite code 3d driver to become a plug-in for the 2D driver? Hook interface of some sort?

_________________
http://lifeofliveforit.blogspot.no/
Facebook::LiveForIt Software for AmigaOS

@K-L

Quote:

I have not managed to make it work. I get either a DSI Error 800003 or a 800004 error or I get only a grey screen (even if I launch WarpView or GLQuake before, those two working perfectly).

Yes! Exactly the same happens to me too! How do they make it work??! Where are, and what does their configs look like?? No one knows.. Do they all have the retail version or do some play the demo..? It's a complete mystery that I seem completely unable to figure out. Either it doesn't start at all (this happens when I don't have "demota/default.cfg" created) or it crashes on startup in the R_FindShader() function

_________________
- Don't get fooled by my avatar, I'm not like that (anymore, mostly... maybe only sometimes)
> Amiga Classic and OS4 developer for OnyxSoft.