Great work so far! Very smooth on PowerMac G5 2.0 DP (Radeon 9650/256MB). Worked thru the first two objectives despite the missing shaders. Seemed to avg 30-40 FPS when running.

Wasn’t able to compile, aborts at ~35% complaining ‘undefined reference to main’ (during d3xp.so linking)

Noticed ‘timedemo demo1’ doesn’t run on the console and causes program to shut down.

Keep up the good work, I’ll try it out some more once I load it on my MacMini 1.5 and PowerBook 1.67!

@IKE

Thanks. I hope it will be better.

dx3.so needs the same treatment as base.so: Just add dllglue.c code to it. Other stuff inside dx3 needed to be done I don't know if it works because I didn't work on it.

I tried to compile with dlfcntl.h include but so far only works for main executable (as other versions compilers do) but it fails with "main" needed for the ".so". So the dll library I left there is needed.

And no, timedemo fails here too.

I didn't use the cmake way to compile BTW: Barebones single makefile for me.

[ Edited by Cowcat 06.01.2021 - 08:34 ]

And thanks to Waldiamiga for being the betatester. He found that the only way to run the game "almost always" was from an icon with stack.

Different options added are in my Github: People should go through the code to see what is done. No README for now.

So far:

Two bugs (and a half?). One is related to "brightness" of the scenes and the other the failure of representing the models.

- You can dim the lights with r_skipLightScale.
- Models rendering can be seen somewhat with r_skipUpdates (heads still shake).

The other half bug happens in the first scene in the hangar: In my system is basically all red with some spots till entering the labs. In other systems with more vram or other gfx cards is a triangle/texture dance.

Still shims of black triangles and quads here and there, probably related to models and scene render.

My workaround for the scenes to be viewed implied leaving out a couple of binding textures and keeping the one that has all colours.

Did some tests and concluded that texture mapping fails in the driver (glTexGenfv).
Got a couple of simple glut programs that also fail to work with that function (probably more are involved).

Not much can be done for now till this is resolved by the morphos team developers.

Some bugfixes for mirrors and cleanup for draw_arb soon.





[ Edited by Cowcat 14.01.2021 - 12:19 ]

Great work! Can't wait to test the bugfixes. Keep up the good work.

Very nice news i wait !

I hope MorphOS Team could correct that soon! Maybe a fix ?

Damn...It seems I have a bad Doom3 version . It fails to load with this error:
ERROR: LoadTGA( textures/sfx/monitor_glass2.tga ): Only type 2 (RGB), 3 (gray), and10 (RGB) TGA images supported

Will try with another version :/


EDIT: I have used the latest patch version of DOOM3 and now it runs. It goes at 20 fps +- with a lot of gfx glitches but it is a really good start!

[ Editado por tolkien 16.01.2021 - 01:37 ]

Did someone realize that in my latest "Project UAC" video the first scene kinda works?

I got a theory that lights, textures and entities that go beyond some boundaries are the cause of the render errors all the way.

In the testing video two functions that check a certain situation exceeding > 1024, I make it return from those instead of continuing the drawing that normally the engine does.

And that happens all over the place: The debug option "r_checkBounds" spits a whole bunch of problems in the original game but it does nothing about it. (tr_light.cpp).

The bypassed option test I did is where "r_showUpdates" is called in tr_lightrun.cpp (and more): In the first scene (the hangar) the problems are more apparent.

The missing model bodies, the shaking model heads and general gfx glitches here and there have probably a root cause in those referenced boundaries.

I checked a whole bunch of source code ports for different systems and no apparent problems are in those versions.

Morphos gfx drivers allergic to this engine? All is theory.

And no response from MOS developers about why texture mapping fails to do its thing.

Quote:

I've been discussing this with bigfoot lately and we came to the conclusion that various things related to glTexGenfv most likely don't work as required or the required infrastructure to make it work correctly isn't available in TinyGL. So no easy solution to it as of now.

Thanks for the explanation.

The Texgen bug is not exclusive of Doom3 but game works ok with the morphos workaround I did running on another system. It is what it is now.

The other part about boundaries surpassed hopefully will be discussed in dhewm3 Github.

[ Edited by Cowcat 24.01.2021 - 13:20 ]

Update:

> First release: https://github.com/Cowcat5150/dhewm3/releases

2nd release from a week ago.

Nice news!

Thanks Cowcat and Adreas_Wolf


[ Edité par Papiosaur 16.04.2021 - 22:00 ]

I have to do another release (r3).

What is known now:

-The problems with the first level in the Hangar were due to the fog functions that use Texgen (bugged) so that made crazy textures dancing or covered most of the screen in "red".

-To my understanding, the crucial part that renders basically all is located in VertexCache.cpp that makes use of the VBO functions at massive scale. The shaking models/heads appears to be a symptom of the render driver trying to update newer textures while older ones still waiting to be removed. And of course, lag and glitches when too many cache allocations happen in a frame.

Some of the upgrades in VertexCache.cpp are from different doom3 ports/mods. Yep I'm aware of all of them but none of them talk about those issues other than RADEON/AMD cards have a different way of doing things and new code tries to (partially) fix that.

I don't know about other MOS programs that use VBO functions so I don't know if they are working as expected.

Thanks for your work so we are waiting for the r3 version.

Thanks for the update! Appreciate the work!

So with LogTool enabled (no TGLDEBUG option)...

Code:

Any of my versions....

And that explains a lot.

Updated to r3.

I modded "r_showTangents" debug function and other parts to bypass most of the VBO rendering when is in use. Kinda no glitches so far when is called with "2" but no GUI and nothing more: Pure silly colored view, but you can get an idea of how the game works and "play" around.

Compiled with 2.0.14 SDK.

Now time to someone else to fix what is needed to be fixed.

Thanks Cowcat for this new release!

I hope MorphOS Team could correct that.

[EDIT] Must wait more 10 seconds to switch Window mode to Fullscreen mode and have the picture...normal ?

[ Edité par Papiosaur 19.04.2021 - 22:25 ]

If I understand you, yes: Some values return to default (off?) when switching video modes.

I must point out that for some cvars I changed get "saved" like r_skipLightScale and r_skipFogLights that should be used for this particular version.

Other way of doing it is by using the cfg that is in the package that sets some values for low end machines, etc.

I see new recent release on GitHub
ProjectUAC_r3.lha
https://github.com/Cowcat5150/dhewm3/releases

> I see new recent release on GitHub
> ProjectUAC_r3.lha

See comment #67.

…and video: https://www.youtube.com/watch?v=dTU4xfNiZYI

I tested out the LAN multiplayer functionality today and didn't run into any issues. It connected, reconnected, changed maps, etc to the local server without any problems.

@IKE

I just simple made the thing compile and didn't care too much. For compiling with new SDK some function in network has to be disabled because is not found. Whatever.

Oh, by the way..... https://www.youtube.com/watch?v=M-DrfK5ZJ2Y

[ Edited by Cowcat 13.05.2021 - 11:30 ]

Thanks for the info and updated video. Progressing very well!

Checked latest (r4) build yesterday: initially I tried a ripped / prepatched Doom 3 pack I found on the net and although dhewm3 PC version worked on it, MorphOS's port didn't. So I proceeded the hard route, installed original Doom 3, patched it, copied base paks and port worked. It was a magical moment seeing Doom 3 intro on MorphOS. However, it seems to be quite unstable in my system, got 2 out of 3 times *Application is Meditating* which freeze my system completely and had to hard reboot. Also, I am getting a DLL Output that Doom is not an executable, which beats me what means. Regarding performance, I was getting from 7 fps on wide scenes (opening scene) to 25-30 on close range but given I am on an old AGP 2x I am quite happy tbh. Has anyone tried any supporting mod? Or does it require a different build or .so? Especially Hard Corps which was released recently is quite impressive that I checked on the PC.