Quote:

The fact that we have loadshedding - which is our local term for rolling blackouts - is not new or unexpected. That's been going on for about 10 years now, what is new and unexpected is the extent of it. To quote Wikipedia: "By the end of September, 2022 had had more load shedding than all previous years combined." This year's loadshedding has been massive, relentless and unprecedented.

Appreciate the transparency...keep up the good work!

Living in the same country as BigFoot, I understand his pain.

Thanks for the great work you are doing! Hope fully I might be see you again one day soon

Thank you for the support, everyone! I appreciate it! :)

The sixth public TinyGL beta release is now out.

The main change in this update is the completion of project 1: Implement the fixed-function OpenGL pipeline as shaders. This change fixes a variety of rendering problems in various apps and games on hardware that currently supports shaders, meaning R300 and newer.

Unfortunately there are a couple of known regressions in this update as well, but at this point they've reached a number and severity that is low enough that I didn't want to hold off this update any longer before getting it out to you all.

The known problems all affect R300 and newer hardware and are:
- Virtual Grand Prix 2 runs noticeably slower than before, and the rear view mirrors no longer render correctly.
- FooBillard has rendering glitches it didn't have before. However this update also does fix some rendering issues that were previously broken, so this one is a mixed bag.
- Descent Freespace is completely broken.
- Reportedly there's an issue with the plasma blanker, but I'm not entirely sure of the details at this point.

I will probably release one more TinyGL update this year that hopefully addresses all of the above, plus any other regressions that might be reported by you.

I also want to say thank you to the usual suspects for testing the TinyGL changes for me! In particular beworld has supplied me with plenty of examples of things that didn't work for me to fix, as well as provided feedback on the changes I've made. jPV has also put in considerable effort doing regression testing for me this week, helping me put out a TinyGL update with much fewer regressions than it would have otherwise had. Also a thank you to cyfm for incessantly pestering me to fix regressions in Blender ;) And lastly a continued thank you to all of you for supporting this project!

[ Edited by bigfoot 16.12.2022 - 13:36 ]

Hey bigfoot,

I just installed the latest version on my FrankenMac, and now the Shader Test fails with :

A required OpenGL extension, "GL_ARB_shader_objects", is not supported

Clicking on GraphicsBoards, the driver says:

Driver: ATIRadeon 52.40 (5.8.2022)

^ The date looks "old" or is that correct?

Device: RV360 [Radeon 9600/X1050 Series] (0x4152)

p.s. Previous version of the beta didn't show this behavior.

Thanks

Quote:

Whoops. Well, it seems like this problem is in Shader Test itself, rather than the TinyGL update itself. If you try to run Shader Test from the previous update (with the current update installed), then I guess it works correctly?

Quote:

That is correct! The version shown there is that of the '2D' part of the driver.

Quote:

Confirmed, older Shader Test works

Quote:

I've updated the TinyGL update archive to include a working version of Shader Test now :D So anyone who downloads the update from now on should have that working.

Quote:


Glitchs fixed on Shader test here and dark colors fixed too on Neverput and neverball!

Thanks a lot bigfoot for this new update!

Continue testing...

There's some kind of issue with new includes (can't recompile D3):

For example:

Code:

And a good streamed amount of errors like that.

Probably some
Code:
is missing in some place ?

Opengl + SDL2 C programs like sm64x work ok.

@bigfoot My findings on the new update so far (G5 11,2. Radeon X1300/RV516):

Shardertest works, moving around the Shadertest window works but as soon as I resize the Shardertest window rendering breaks inside with various artefacts. Also the mouse pointer gets kinda jerky and the G5 lags (though not 100% CPU load). If I manage to get the mouse pointer over the close button of the Shadertest window and close it the machine is back to normal. Also Shadertest can be restarted with correct rendering in the beginning.

The colour issue in Virtual GP 2 i described in #204 is still there.

@cowcat, i try to rebuild SDL2 here and same error. I try to understand... i think problem seem in SDL opengl headers.

Problem seem here : https://github.com/BeWorld2018/SDL/blob/5e9a960fbf6f34465023b97194c4122e2eb3dde8/include/SDL_opengl.h#L40

PS: i think i find something :

https://github.com/BeWorld2018/SDL/commit/e2d8f21981c027cdd6c1f231b28bc10ed4cd5ffc

Now i can build SDL2 again but SDL2 SDK from old version is broken i think

[ Edité par beworld 17.12.2022 - 14:25 ]

[ Edité par beworld 17.12.2022 - 14:25 ]

@cowcat Other good new.... i will build your SM64 port with OpenGL 2 support (with shaders) and result... working

@beworld

Well, I thought that the issue was more towards SDL2 includes when C++ was in use, but not quite sure. Time to make another SDL2 lib ?

I saw your fork. Whats the visual difference with old sm64 version ?

If your SDL2 starts to allow GL2 support I see a good amount of upgrades, like scummvm (but only for r300+ users).

@cowcat...

SM64 visual difference.. i dont see any difference lol but shaders working..., (i can publish this bin with sdl2.library beta to test)

Make another SDL2 lib width new tinygl support... not sur, because :
1. new TinyGL.. is beta... and not finished
2. SDL2 can use shaders with opengl renderer but same as SM64, i dont see any difference (speed.. benefits etc...), i think FBOs support when available is more important with SDL2 (SDL_RENDERER_TARGETTEXTURE support for example)
3. I could only compile PrBoomPlus with shaders support, SM64...
ScummVM: i need to retry because it's more complex and not working with my last test.

@beworld

- SM64 - Yep, should be no visual difference with shaders but who knows :)

I think changing SDL_opengl.h (2.26.x) include with your finding is enough now. At least I can recompile my shit :)

ok,
I'm trying to see with bigfoot if it's good for him or if he modifies his SDK or I don't really know what

Quote:

No, it seems like that Dhewm3 depends on the OpenGL includes defining typedefs for function pointers to OpenGL functions, which MorphOS' current OpenGL includes don't have. I'll add them in the next update.

The reason it worked before was that MorphOS' OpenGL includes also didn't create the preprocessor definition for example named "GL_ARB_vertex_buffer_object". With this preprocessor definition missing, the SDL includes would inject its own typedefs for the function pointers. Now that MorphOS' includes have these preprocessor definitions, the typedefs are missing, and hence Dhewm3 doesn't build.

The easy fix for now is to edit gg:os-include/tgl/glstd.h and remove the block of #define statements from line 8 to line 93.

Quote:

Yep, there is indeed a problem with resizing shader-using applications in window mode. I'll get that fixed :)

Quote:

That's probably because of the same issue as discussed here. There'll be a fix for it, but probably not right away, unfortunately.

Quote:

I'll have to have a look at Virtual GP 2 soon to find out why the rear view mirrors broke, so hopefully I can find out what that texture problem is at the same time.

Quote:

I'll fix the include problems on my end for the next update :)

Quote:
I'm not sure if it's wrongly colored, or do you get different kind of colors on some older MorphOS/TinyGL version?

For me it just looks that Melbourne has certain areas of blue/red/yellow gravel, which probably was like that on the real life F1 circuit too. In your screenshot the green/yellowish area is lawn, but the blue area with stripes is plowed gravel.

I think it's looked like this always on VGP2... in original textures it's more colorful, but it's a bit lighter with the 3rd party HD textures.

[ Edited by jPV 18.12.2022 - 10:56 ]

Here's a photo of 2005 Australian GP and you can see blue ground there: link

And VGPHD texture set title picture shows the blue gravel too: link

[ Edited by jPV 18.12.2022 - 10:54 ]

A quick one question: Does Project1 fully applied to R200 driver ?

Seems that some of the upgraded functions still not working here.

Quote:
You are right! So this probably isn't a bug after all.

I only didn't play VGP2 that often as it had annoying graphical glitches before the OpenGL update. So I probably didn't know the courses that well.