:bm1::bm2::bm3::bm4::bm5::bm6::bm7::bm8::bm9::bm0:

@bonkmaykr@canithesis.org

21 Male, Missouri, United States
Running Canithesis Interactive & Worlio LLC
Software engineer, newly an Amiga + Saturn nut

Currently working on a shmup game called "Time Falcon", my own game engine for it, and some other stuff. My posts can range anywhere from deep nerd thoughts to brainless shitposting.

Expert at run-on sentences

Give me liberty or give me death
XMPP/Jabberbonkmaykr@canithesis.org

59 following, 45 followers

0 ★ 1 ↺
xianc78 boosted

[?]:bm1::bm2::bm3::bm4::bm5::bm6::bm7::bm8::bm9::bm0: » 🌐
@bonkmaykr@canithesis.org

Hm, well, you guys were right. I was deriving the base classes wrong, using the public modifier fixed the compiler errors.

But the function calls going outside of their allowed memory is still happening.

What's weird is that it works totally fine on another objects, even with classes that are set up the same, but not on bullets.

CLion debugger (frontend for gdb) can see the object but only displays it's base o_worldObjectGeneric whereas it normally shows the entire hierarchy of inheritance. GDB CLI is so confused it literally crashes itself.

It might be an issue with the way I keep things inside vectors or add objects to the world mid-tick? I don't get why this is happening, I showed it to someone else and they couldn't fix it either. If I can't figure it out I might need to ditch inheritance somewhat and base all projectiles directly on a single class. It will make things harder to structure but I don't have a lot of other choices.

...

History