Thanks a lot Koszer for this new video showing the true about Doom3 port on MorphOS

This is the way

Uploaded a new release with shaders enabled.

Two executables this time: The "_alt" version is for those with gfx issues (never enable EAX sound with it).

I would not go too crazy with a 64mg vram: 640x480 and low settings preferable.

For a "normal" game now better set r_renderer ARB as shaders still not there for this game among other issues. You can enable r_useTripleTextureARB for bumpmapping/specular that kinda works with it (of course no r_usedrawinteraction0 enabled -> just for R200 gfx for now).

Doom3 ProjectUAC_r6_4 "alt version"
https://youtu.be/Igxpvdx4Y94

PowerMac G5 DC 2.3GHz, Radeon X1950Pro 256MB Pci-e

The "normal version" works well, but without mlook.

Try :

r_skipPostProcess 1

I try that and magical .... no more FPS at 1

Dont known if we lost detail GFX with this option



Quote:

Quote:

The details are lacking one way or another. But with this option we certainly gain some visual effects that would otherwise be a black blob and some speed too.
Here is how the timedemo works with and without r_skipPostProcess 1:

WITHOUT (watch out, painful to watch):

https://youtu.be/qqe8RDWBCtU

WITH (typed during the first seconds of the video):

https://youtu.be/EI7g7KULroY

What was the rendering resolution?

Quote:

This comes down to an issue I asked many moons ago but seems to be a forgotten email....

And for what I check now, it "could" be also related when effects as
doublevision/berseker/grabber, etc are applied (probably others).

r_skippostprocess is checked in draw_common.cpp/RB_STD_DrawShaderPasses. After that if renderer is ARB2, copyframebuffer is called.

That function ("copyframebuffer") is in image_load.cpp.

At image_load/copyframebuffer, opengl functions (readbuffer, copyteximage2d, etc) are called: Something's going on with those.

Ok. What it has to do with doublevision/grabber and so ?

Well, at game/PlayerView.cpp, those visual effects call "capturerendertoimage".

At rendersystemsystem.cpp is were capturerendertoimage is located and what it does is flag commandId with "RC_COPY_RENDER".

Further down the line the check for commanId is at tr_backend.cpp/RC_ExecuteBackEndPrograms.

When "RC_COPY_RENDER" is checked in the loop, it calls RB_CopyRender. And RC_CopyRender calls "copyframebuffer".

So now we have two places were copyframebuffer does "wrong" whatever ARB render is in use.

Edit: Postprocess also affects all renders.

[ Edited by Cowcat 11.04.2023 - 13:37 ]

Quote:

1920x1080

Details set to: Ultra.

Advanced options:

High Quality Special Effects - Yes
Enable Shadows - Yes
Enable Specular - Yes
Enable Bump Maps - Yes
Vertical Sync - Yes
Antialiasing - 16x

Quote:

Ha. Maximum stress settings.

How much FPS at 800x600 (about 4x less pixels) or 1024x768 (about 3x less pixels)?

15 fps is barely enjoyable for playing imo.

here i have 800x600 20-60 FPS

For those trying D3 with new MOS 3.18 and have issues with mouse/menu/gfx the fix is not really there:

As I suspected from and old debug beta done from someone with a beta 3.18 SDK, game recompiled with new SDK works now for supposedly all machines that were problematic.

And I don't really know why the f new SDK fixes that :)

Anyway working on for another release.

PS: Does game now looks better with shader render with new MOS upgrade ???

Quote:

Here's a video of timedemo1 on the latest dhewm3 version (and gfx card drivers public release 9):

https://youtu.be/97T2iJ0rRE0

I can see some new effects (like sparks). Some slowdowns are gone, but I believe some new were found :)
The starting screen acts weird (with discoloration problems on buttons, and the incoming Mars seems to be missing us by a fair margin).

@koszer
And latest r6_5 ? Only one binary. It should fix almost all problems witn menu/intro mars: On some machines forward button + fire gets "nulled", but rest kinda works.

Quote:

Please what machine is used?
Is it yours Powermac G5 Quad + Radeon X1950GT ?

Quote:

Yep, that's my QUAD.

Quote:

From what I've checked the menu glitches are gone. But I've managed to run the r6_5 only after a few failed attempts. I'll do some more testing soon.