@Tanuki legible yeah but what do all the numbers mean? ;)
@Tanuki
Im not sure how to make sdl fast but im glad its not a problem with my core haha
for get color i think yes. Its called for each pixel 320 times per hblank times 240 per vblank times 60 frames per second iirc
@QuestForTori you need to know what reference is bad and handle it in the code specifically. Does it say what referenced the script in the log?
@QuestForTori you need to know what reference is bad and handle it in the code specifically. Does it say what referenced the script in the log?
@QuestForTori i can when i get home. I use windbg so i need to have vs in front of me to help
@QuestForTori it should have a ~className func thats always there even if you didnt create it that calls Destroy().
No time like the present to learn the debugger! ;) if you learn it this stuff takes 5 min to fix. If not you go mad trying :/
@QuestForTori the script object itself should have a destructor which is named ~script (or whatever the classname is) which calls a function Destroy().
Set a breakpoint on that ~script function and run in debugger. it will be called in a place you dont expect it to be. Then check the stack trace in debugger and it will show you what function caused its destruction.
I expect its changing the script and that change makes a new one and destroys the old and theres an old ref
@QuestForTori can you break on the destructor and check the stack trace? Are script objects like immutable?
@angrboda too real
@angrboda bottle caps??
@Tanuki thank youuuuuuuuu
@Tanuki I added two issues.
Instruction bug which I should probably handle, and the fact that we're slow as snuts which I dont know how to handle.
@mawr *out of
@mawr I dont know what you mean by "never look back", but I'm also fucks to give about version control today ;)
@mawr I mean... SVN is pretty straightforward...
@mawr its about 800 million x more complicated and obnoxious to use than it ever needed to be
Mixie trash
- she / her -