OptiCode 0x0003 - Failing to work with my clunky CPC Wolfenstein engine code remnants

My initial goal in this video was to debug a new improved raycasting algorithm replacing the old one in my CPC Wolfenstein engine that I might be working and abandoning since almost 10 years back. It ended up failing horribly.

First I was talking too much explaining the whole framework (SDCC or PC SDL, compile for CPC or run a simulated CPC vram for fast debugging of the algorithms on PC) which is ok, but it took over an hour describing things, then realizing that for some reason it crashed on CPC (at least when I change a define to enable the old fast engine).

And what was it that I wasted time? The code growing so much that it overflowed the data again. And yes, yes, I know I should change the way I work, right now some things are very clunky and very bad from programming perspective. Anyway..

I guess you've seen now my engine and the dual framework, the way I don't let SDCC build a binary, but only spit out the assembly and pass through a lot of other mechanisms like a goldberg machine (extremely clunky stuff). Everything automated though so I even forget what I was doing.

I guess in my next video (will see, unless I scrap it) I will start what I wanted to do, work on fixing the new raycasting algorithm, now that the framework and memory issues are figured out.

Видео OptiCode 0x0003 - Failing to work with my clunky CPC Wolfenstein engine code remnants канала Optimus6128