Raylib-CsLo VS tinyraycaster

I wonder if it would be worth a try to use Raylib-CsLo. That would for sure confirm a binding issue.

Long time [Raylib_CsLo](https://github.com/NotNotTech/Raylib-CsLo) user, first time C user.

I'm under the impression that Unity builds have a good deal of overhead. Plus, in many cases, something like raygui (C# bindings) will actually be quicker to develop with. Nothing wrong with Unity, though. The best tool is the one you know how to use, in my opinion.

I'm a big fan of Raylib-cslo.

Regardless, the C# binding I'm using is Raylib-CsLo which autogenerates the binding around the original C library, at least as far as I understand it. Maybe you could reach out to the developer (via Discord/Github) and ask him how it's done.

I wrote a C# binding for Raylib, which I am going to try building up into a kid-friendly framework: https://github.com/NotNotTech/Raylib-CsLo

That sounds like a fun challenge. If you're constraining yourself to use as few libraries as possible, I'd go with OBJ [1] for the 3d mesh and PPM [2] for writing images. It's easy to implement a bare bones reader/writer and some OSes (like macOS) can show them in the file browser. Raytracing in One Weekend goes over PPM. There are a bunch of header-only libraries that handle different file formats like stb_image [3]. I usually end up using those when I start dealing with textures or UI elements. I don't use Windows so I haven't used their APIs for projects like this. I'd usually go for imgui or SDL (like you mentioned). tinyracaster, a sibling project of tinyrenderer, touches on those [4]. I liked LazyFoo's SDL tutorial [5]. Good luck!

[1] https://en.wikipedia.org/wiki/Wavefront_.obj_file

[2] https://en.wikipedia.org/wiki/Netpbm#PPM_example

[3] https://github.com/nothings/stb

[4] https://github.com/ssloy/tinyraycaster/wiki/Part-4:-SDL

[5] https://lazyfoo.net/tutorials/SDL/index.php

I haven’t followed this one but I did follow another of his tutorials and that was good, here is ssloy’s tinyraycaster: https://github.com/ssloy/tinyraycaster/wiki

Don't just jump into the source file , read the make file first, from there you'll know how main file is dependent on other files , and start with the .h(header files as they'll give a basic idea what their corresponding .cpp file do and yeah start with small Repos first as they are easier to understand like this one.

I believe this wiki page can walk you through a retro style raycaster engine: https://github.com/ssloy/tinyraycaster/wiki