The problem with The_Artifact is related somewhat as the bug with "doublevision": Image is showed upsidedown.

The same as the Grabber: When you twist in space objects, image is also downside.

Also the anims at the beginning of Resurrection of Devil and further: FPS go really down in particular instances (like being in front of a portal).

In normal D3 besides doublevision, when you go to Berserker mode all goes downhill.

The functions that add those effects are in PlayerView.cpp ( neo/game/ and neo/d3xp/ ):

Some code for other platforms out there have changes in those functions related to similar issues but still no luck applying it.

This problem was already present with the old tinygl.

Deja Vu. I think that already talked about it.







[ Edited by Cowcat 13.09.2022 - 08:37 ]

> Deja Vu. I think that already talked about it.

Indeed, comment #112.

What is current ProjectUAC MOS_progress?

Any chance of OS3 RTG Software render port, just as tech demo? :)))) Would try it on X13 V2 in lowest settings.

Quote:

https://github.com/Cowcat5150/dhewm3/releases

Quote:

Still ongoing. No updates on github doesn't mean I'm not testing things.

Wonder what is the state of shaders for this project: Besides the usual suspects, did someone checked SDL2TinyGL53 and recompile the whole stuff ?


Quote:

A software render port is out of question. An OS3 warpos minigl port ? Maybe:

- Bypass SDL2 code. Rebuild what is missing.
- Move out OpenAL stuff: Do an alternative.
- Bypass the missing opengl stuff in minigl (dare to remove all VBO code and use simple vertex arrays calls. Same with multitextures support, etc): See what happens.
- Use my MOS sources. Check old idq3 sources. Check other ports. Modify minigl. See my Ami Q3 engines. Modify code.
- Puke.
- Pay me some euros ending with 000. No guarantees.

Then:
- Find a big Amiga box with more than 512mg ram, a beffy gfx card and a souped-up PPC G4.

Result: A slideshown similar visually to the nowadays MOS port and a picture of me going to a Psycho Clinic.

Note: Actually I did a preliminary build of this project with no SDL at all.

Quote:

Tried. I managed to get the ARB2 route taken. It sadly explodes with various bad memtrashes at exit or on flight depending on where it trashes. That was a month ago or about. Didn't bothered to fix/tweak the guilty code, was busy with ShaderBoy.

Quote:

Ho. That's interesting. ^^ Hope you'll get to the end of that soon.

Quote:

How does it work? Is it much faster? You can show screenshot, video or preferably exe file.:)

The non-SDL port was one version I had when I started to build the project. Probably with mutated sources from some Q3 engine.

Pretty much it just loaded the menu screen and crashed down the line as it needed more work.

It is long buried in some forgotten dir now.

Question to my memory is if those versions (non-SDL vs SDL) were "different": At that time all I had were glitches at the first level and luck to start the game.

As experiment, one path to take is bypass opengl includes (that call SDL2 stubs) and inline the functions needed and see what happens "today". I did it time ago in some of the render code but didn't find anything special for performance.

I thought about a new non-sdl port just to isolate the shader problems in it besides what SDL2 does. Now it's a little more difficult as dhewm3 evolved but could be easier than an Amiga Warpos version :)

Appreciate the work CowCat!

Video of latest TinyGL and SDL / Project UAC r5.

I can't get r6 to load. It crashes with a keyboard error consistently.

https://youtu.be/NpgSbcThzog

Maybe porting Doom 3 wasn't the best option, because MorphOS and the computers we use are a bit inferior to the needs of the game.

@Templario: On the contrary, it seems a perfect match for top-notch MoprhOS hardware!

Doom 3 was released 2004 at a time where single core Pentium 4 was mainstream and 64bit CPUs for regular users still being a niche (Athlon 64, PowerPC G5). >1 Ghz G4 hardware was top notch, G5 was da new hot shit (no poor student could afford at that time ).

On the Windows side minimum system requirements were Pentium®IV 1.5 GHz or Athlon® XP 1500+, 384MB RAM, DirectX® 9.0b compatible card w. 64MB (Radeon 8500, 9x00 or GeForce 3/4/FX). It was even ported to the original Xbox which had a Pentium 3 733 Mhz CPU + 64 MB RAM + GeForce 3.

I played it extensively on my PC that time which was a bit above minimum specs (but not much) and it ran pretty well!

Quote:

@IKE I know about this issue with some gfx cards. Still don't know if it's about Dhewm3 or SDL2 upgrades. Have to update some code sources for the game and link all with new TGL and SDL2.

Quote:

@Templario. "Maybe" is a word I use quite often that I have to remind to change to "What if".

"Maybe" -> "If fails, back to what is known": Safe.
"What if" -> Dare to do things no matter the result. As we don't deal with brain surgery procedures, you're allowed to fail with no harm: Serendipity. Knowledge. Progress.

I see CowCat has a new release. Will download and try out this weekend. Haven't heard what progress has been made:

https://github.com/Cowcat5150/dhewm3/

Nice news!

Thanks Cowcat!

Just some git-master upgrades and minor things + linked with new SDL2 2.26.3.

I prefer to not change too many things until new tgl/system upgrades.

Quote:

And you can do something with a broken mouse, for me on two PowerBooks and one iMac G5 stopped working from version r_6. Thanks for your work!

Quote:

Same problem here, mouse is not supported (PowerMac G5)

Lots of questions....

https://www.youtube.com/watch?v=RlOZN-hrx3k

I see that r_usedrawinteraction0 0 fixes lighting issues, although ARB2 doesn't work with current release nor R2 release (checked as R2 is listed on window bar). Does it need any new release?

btw. in R2 release - mouse works and mainscreen gui doesn't have glitches

Quote:

According to https://www.amigans.net/modules/news/article.php?storyid=3116 the X5000 achieves 30+ frames in FullHD+ultra settings, so the MorhOS port could or should do the same results imho on an comparable setup with the newest TinyGL from https://tinygl.molsen.co.za/

Quote:

There's no "comparable setup", at least when it comes to gfx card. With Radeon X1950 being the fastest currently supported one we're quite far behind the RX560 used for AmigaOS 4 benchmark.

Quote:

Hoo. ARB2 rendering path worth the pain! Nice achievement. Congrats. :)



[ Edited by Tcheko 13.03.2023 - 08:15 ]

Quote:

Old ARB rendering is working since TexGen functions were fixed for 300+ a while ago.

r_usedrawinteraction0 was my workaround till those functions were sorted out....

... and I wondered why no one checked that, but whatever :)

So for 300+ gfx cards using latest TinyGL driver:

r_usedrawinteraction 0
r_skipFogLights 0
r_skipLightScale 0

Quote:

After version 5 something weird happened that affected some hardware out there.
I blame the issue since the upgrade of OpenAL library but could be anything in between.

The video is from a recompiled old r5 release with SDL2 link library from recent github and some changes here and there: For those daring to compile, now you have the clues.

BeWorld recent D3 source experiments help: It even work for any hardware (I have to investigate that).

Obviously shader support needs more work for this kind of game among other issues already exposed.

Thanks to Papiosaur, now I have access to this (problematic) hardware to continue my research.

Big applause to him.



[ Edited by Cowcat 13.03.2023 - 15:57 ]

Quote:

That's how this version looks on my machine (FullHD, Details set to Ultra, all advanced functions are on):

https://youtu.be/JlvsVvjY5wo

The game runs quite well (15-20 FPS) until there's some unsupported object in sight (like glass, or fire). Then the FPS gets down to about 1.