Customers who*** already bought the BOXED VERSION *** will be able to download the AmigaOS 4.1 Final Edition version *** FREE *** of charge after registration of their copy.
@kas1e If libtxc_dxtn was a false alarm, then I definitely recommend it over S2TC, since it produces much better looking textures. It should be well tested, since it's part of Mesa. (Technically it was an external library because of licensing issues, but you get the idea).
This is just like television, only you can see much further.
@All I made thread about Shogo, so we can continue there about minigl only :)
@BSzili At least from tests i do, libtxc_dxtn version for sure works now.
Probably before you/daniel think about unstability is just via testing quake3 (with enabled extensions) and it failed (as issues with extensions come up) and as result false alarm
@kas1e I updated the mgl.zip one my homepage on last time (crossing fingers ). The new dtx-lib is inside. I also re-enabled the replacements for the deprecated CreateIO functions etc. Yesterday I disabled those when searching for the crash-culprit. Please try that one again! Would certainly be best if we'd use the modern functions. http://www.goldencode.de/tmp/mgl.zip
@Daniel That version also fine. I doing that way: reboot with that new libraries, and:
1). run 5 instances of "testgl" , and exit from 2). few run/exit from "cube" and on last one played a bit 3). run q1-darkplace, play a bit, exit 4). run sdl2 version of q3, timedemo on it, exit 5). run sdl1 version of q3, timedemo on it, exit 6). for sake of messing the memory a bit run gl4es version of q3, timedemo on it, exit 7). run Blender, move a bit in all directions, exit 8). run RCTW, played for about 10 minutes, exit 9). run Smoking Guns (damn how horrible slow is it even on x5k, need to made gl4es port for sure) 10). run LodePaint, paint a little for minute, exit 11). fire up odyssey to download some stuff from os4depot (and to mess memory more), download from there some minigl crap, run it as well one by one, all works.
At this point exit, and write that post. So, probably all still fine and good. At least i can't see any problems. Expectually if i run those mosnters like RCTW, q3 all different versions, odyssey on top of it. If it still didn't crash, i'd say go for that one :)
@kas1e @samo79 I now asume the lib is the most stable MGL version ever and that samo79's issue is nothing new or unrelated
@Capehill Yes, right, you just found another package of MGL bugs (almost exactly 14 years old bugs) And I just fixed it. Not yet comitted, but the lib on my homepage has been updated accordingly, please check it out.
However, please, report bugs in the usual way. This whole story here is about making sure that the upcoming 2.23 with its current feature list can safely replace any former lib. Let's bring this to an end for now. I at least don't want to spent more time with this right now, I got my own projects to care for
Retested Shogo and found that problem in reality was related to AHI, Units need to be set the same as in AHI's prefs and in game prefs, in this case Unit 0 for both, otherwise game seems crashing at exit
@Daniel Tried last version too, yeah, all fine. May i also suggest a bit change readme too ? On top we have now:
Quote:
MiniGL is a 3D API which is compatible to OpenGL(tm). It implements a subset of that API and was designed for speed, therefore it directly interfaces with Warp3D. This also means that there is currently no software mode.
This release is the second release of MiniGL as a set of shared libraries: minigl.library, which is the GL part, and mglut.library, which implements (partially) the GLUT API.
The new shared library interface drops a lot of the original functions (mgl*) in favor of GLUT. Unfortunately, no documentation exists yet. Refer to the glut source code and src/context.c to get an idea on how it works.
Imho today it will be better to just be like:
Quote:
MiniGL is a 3D API which is compatible to OpenGL 1.x. It implements a subset of that API and directly interfaces with Warp3D. There is also no software mode.
MiniGL reliased as a set of shared libraries. There are two such libraries: minigl.library, which is the GL part, and mglut.library, which implements some of the GLUT API.
The new shared library interface drops a lot of the original functions (mgl*) in favor of GLUT. Unfortunately, no documentation exists yet. Refer to the glut source code and src/context.c to get an idea on how it works.
Maybe even worht to delete 3st block at all about dropping of *mgl fucntions in favor of glut and no documentation.
@all I just bumped minigl and mglut to version 2.23, committed everything to the repo, incl. an updated 7z of precompiled binaries.
@kas1e The very latest temporary mgl.zip from 5 minutes ago on my homepage has the same structure as Hans' old 2015 minigl-archive on os4depot. Please check it out!
@BSzili Haha :) Not big deal to touch readme anyway , maybe later someday :)
@Daniel Yeah, all looks fine, and like you use that mkrelease script , which have only one problem : icons didn't sorted visually correctly (expectually those ones in the Demos). If you doesn't mind, i can sort it all (so visually when any user will unpack it, all will fits nicely in wb windowses, etc).
But if not want to bother anymore, then yeah, that mgl.zip exactly like one we have on os4depot, just much better :)
The only issue i can notice now, is that seems "data" of demos directory somehow changes a bit. At least, and by size of some files, and , by visuall look for example of "warp" demo.
It uses stars.ppm and flare.ppm.
In 2.20 archive, sizes are :
stars.ppm: 49.190 flare.ppm: 49.167
In 2.23 archive, sizes are :
stars.ppm: 49.452 flare.ppm: 50.390
As result, with new data files "warp" demo looks a bit strange. Instead of some circle in the middle its now has rectangle, which didn't fits in.
Probabaly data files somehow was regenerated or something ?
And that for sure datafiles, not minigl itself, as i tried demo and from 2.20 and from 2.23 archives on old datafiles they both fine, on new datafiles, they both looks wrong.
See:
old datafiles:
new datafiles:
See there some rectangle now.
In worse case, we can just recopy data files from 2.20 to new archive so all will be fine, but through it probably interesting to know why and when they changes.