PlayBASIC Devlog – Primitive Drawing Tests, Collision Updates & Documentation
Welcome back, PlayBASIC coders!
In this devlog, we're continuing the gradual process of replacing parts of the original PlayBASIC command sets with newer implementations from the PlayBASIC 2 development work. This time, we're looking at primitive drawing functions, comparing performance against the built-in commands, testing some replacement world collision code, and working through the ongoing documentation updates.
The early benchmarks are interesting. Some of the replacement drawing commands are already showing performance improvements, with dot drawing running almost twice as fast in certain tests. Interestingly, the actual drawing code hasn't changed in those cases — the difference comes from how the runtime dispatches commands and calls the underlying functions.
We also take a look at sticky collision testing, comparing the existing implementation with the replacement code while thousands of objects bounce around a test world. There are still some collision quirks to iron out, but the replacement is showing improvements.
On the documentation front, I'm filling in missing command descriptions, adding examples, updating tutorials, and removing references to obsolete technologies. It's not the most glamorous part of development, but it's necessary work if we're going to get the next free edition of PlayBASIC out the door.
There's also a closer look at how the original runtime handles command calls, why some small built-in functions can actually be slower than their replacements, and how these findings feed into the design of the next-generation runtime.
Progress isn't always about adding new features. Sometimes it's about pulling apart the old machinery, understanding where the overhead comes from, and making the next version a little better.
Thanks for watching, and I'll see you in the next devlog!
#PlayBASIC #GameDevelopment #BASIC #Programming #IndieDev #PlayBASIC2
Welcome back, PlayBASIC coders!
In this devlog, we're continuing the gradual process of replacing parts of the original PlayBASIC command sets with newer implementations from the PlayBASIC 2 development work. This time, we're looking at primitive drawing functions, comparing performance against the built-in commands, testing some replacement world collision code, and working through the ongoing documentation updates.
The early benchmarks are interesting. Some of the replacement drawing commands are already showing performance improvements, with dot drawing running almost twice as fast in certain tests. Interestingly, the actual drawing code hasn't changed in those cases — the difference comes from how the runtime dispatches commands and calls the underlying functions.
We also take a look at sticky collision testing, comparing the existing implementation with the replacement code while thousands of objects bounce around a test world. There are still some collision quirks to iron out, but the replacement is showing improvements.
On the documentation front, I'm filling in missing command descriptions, adding examples, updating tutorials, and removing references to obsolete technologies. It's not the most glamorous part of development, but it's necessary work if we're going to get the next free edition of PlayBASIC out the door.
There's also a closer look at how the original runtime handles command calls, why some small built-in functions can actually be slower than their replacements, and how these findings feed into the design of the next-generation runtime.
Progress isn't always about adding new features. Sometimes it's about pulling apart the old machinery, understanding where the overhead comes from, and making the next version a little better.
Thanks for watching, and I'll see you in the next devlog!
#PlayBASIC #GameDevelopment #BASIC #Programming #IndieDev #PlayBASIC2