A new, non-bricked device!
Mar. 9th, 2023 09:03 pm![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
carlfoxmartenI don't know if it was just due to good customer service, or the fact that I'd backed the project, but the person I was dealing with sent me a replacement Xtron Pro device, no charge. And it arrived today.
I immediately plugged it into my computer, uploaded the latest firmware file, then added the latest version of my project that I had on hand. Which crashed the device, but nowhere near as badly as last time. This time, I was able to restart it back into the menu program instead. So I was able to properly delete the old file, then generate a new file from my project and drop that onto the device, where it's been working perfectly ever since.
It's finished charging now, too, so I'll be able to fiddle around with it as much as I want. Though I'll need to remember to properly delete the old files whenever I add a newer version of my project. I don't want a rehash of this incident to happen again...
Now, I get to fiddle with how the whole game feels. For example, the time it takes to lower the falling block one row is a bit fast. Which is something I never thought I'd say. Either it's not taking enough time to move, or it's waiting too long between each rendered frame.
It's all a balancing act, now. Though I still haven't done anything with regards to scoring...
I immediately plugged it into my computer, uploaded the latest firmware file, then added the latest version of my project that I had on hand. Which crashed the device, but nowhere near as badly as last time. This time, I was able to restart it back into the menu program instead. So I was able to properly delete the old file, then generate a new file from my project and drop that onto the device, where it's been working perfectly ever since.
It's finished charging now, too, so I'll be able to fiddle around with it as much as I want. Though I'll need to remember to properly delete the old files whenever I add a newer version of my project. I don't want a rehash of this incident to happen again...
Now, I get to fiddle with how the whole game feels. For example, the time it takes to lower the falling block one row is a bit fast. Which is something I never thought I'd say. Either it's not taking enough time to move, or it's waiting too long between each rendered frame.
It's all a balancing act, now. Though I still haven't done anything with regards to scoring...
