An example of shader code for shadows (although pretty bare) is included in OpenB3D Plus add on

Regarding the chunk world system. have also a look at built in octrees (blocks cannot cast shadows, but meshes inside octrees can, I think)

I have a question for the developers: since I have added the headers to the source code of FreeBasic, is there a way to add the libraries to the DOS distribution, to have it able to work out of the box?

Shadows are not children of a mesh, they are managed aside. From the screenshot I cannot tell for sure what happens, although I can make a hypothesis: the algorithm used by OpenB3D is called Stencil Shadows, and it basically work by creating a mesh that is not visible, and is shaped like the shadow ...

Now, going to that “ADLIBEMU.C” program in your link that you just showed me, I am DEFINITELY looking into it, for if my memory serves, that code can be adapted for use to replicate a true-quality emulation of the OPL2 chip in both Windows and Linux... but there is one problem though. This will cre...

The OPL2 chip can be emulated via software on systems that don't have it:
viewtopic.php?p=192395#p192395

I found this shader, and I ported it to FreeBasic/OpenB3D: https://www.shadertoy.com/view/lssGDj The BASIC code (it requires the library OpenB3D) #include "openb3d.bi" screenres 800,600, 32, , &h10002 Graphics3d 800,600,32,1,1 var camera=createcamera(0) cameraclscolor camera,0,0,255 'c...

I remember it, it was mentioned on PetesQBSite years ago, I intervened too: http://www.petesqbsite.com/phpBB3/viewtopic.php?p=39070#p39070 It is an open source program, written in javascript (with some WASM and TypeScript). It can be downloaded for free here: https://github.com/IshikawaMasashi/QBasi...

I managed to integrate a basic interpreter inside FreeBasic programs:

viewtopic.php?t=29109

But that interpreter is not FreeBasic, it is a different basic dialect

I think worth investigating because I'm not sure at the moment; the compiler sometimes uses constructions internally involving`*(@(expression))` where it's probably expected that it doesn't immediately convert types. Another approach would be to at least warn (or even error) about things that certa...

I have a simple suggestion: wouldn't be possible to return the address of a fixed length string not as a string pointer (it wouldn't work, since it would not contain the terminator, nor the string descriptor), but as an Unsigned Byte pointer? After all, a fixed length string with no zero at the end ...

I wonder, will the update fix this bug too?
viewtopic.php?t=31753

This doesn't affect me so whatever, but I'm gonna be honest: Well, that's the point: finding out whom would be affected... or if anyone would ever be affected. potentially throwing your entire current user base under the bus and changing the ABI for some potential future code or mythical people who...

I must also add another consideration: like I said before, the change might introduce incompatibilities in case an UDT containing fixed length strings is saved in a file, and then such file is read by the same program, compiled with the newer version. But the same incompatibility currently exists if...

A string is not just for printing. It can also be used to store other kinds of data (think about the strings used to control the DRAW command). Also, in regular strings the CHR(0) is allowed, and so it was in original QBASIC (where CHR$(0) was also used for special commands, like cursor keys) I thin...