Omnimaga
Calculator Community => TI Calculators => TI-BASIC => Topic started by: DJ Omnimaga on June 01, 2013, 11:36:28 pm
-
Some of you probably remember those rumors about the Flash ROM eventually wearing out on Z80 calculator models if it's rewritten like 200000 times or sooner if it's defective (like one of the 2009 contest guy). However, when you use StorePic on a TI-84 Plus C Silver Edition, it stores a 22 KB large picture file directly into archive.
What I was wondering is if a BASIC game that continuously uses the StorePic command during extended periods of time could eventually cause such problems with the calculator Flash chip, or if it was written differently so that it won't cause those issues (assuming they're not just an urban legend)?
Also, does using StorePic on a 84+CSE eventually causes Garbage Collecting? If so, then I guess heavy use is out of the question in games, since some people would end up having to garbage collect every 3 minute or so.
-
I guess since it does write to archive then naturally if you were to use it over and over it would wear out FlashROM.
Perhaps an ASM lib can be made that will allow you to 'storePIC' to the extra RAM pages instead?
-
Yeah I'm curious in case TI might have addressed the issue (assuming there was an issue at all to begin with, but I'm sure there was, since the 84+CSE uses the same hardware (other than the LCD) as the older 84+SE, which were heavily based on the 1999 83+ calcs.
An ASM lib to StorePic to extra RAM would definitively be nice, even if just a few pics. In my case, I was wondering, because in Zelda I would like to speed up map display by storing the generic map stuff into a pic for future display, but I would have to recall the pic everytime Link moves to a new room.
-
An ASM lib to StorePic to extra RAM would definitively be nice, even if just a few pics. In my case, I was wondering, because in Zelda I would like to speed up map display by storing the generic map stuff into a pic for future display, but I would have to recall the pic everytime Link moves to a new room.
Recalling the pic shouldn't wear out the Flash ROM as far as I know. It's the writing that would be the problem. So if you don't have to constantly store the screen there shouldn't be a problem.
-
Ah right that's true. There still is the issue about storing often, though (when switching to another dungeon)
-
You could try to make a tilemapper somehow (even though it takes longer to draw the screen), the flash wouldn't wear out.
-
I guess you can test it by filling the memory of your CSE untill it can only store a few images, then call storePic a few times. If it starts garbage collecting, you know it can't be used in games.(That is, assuming that pics are handled as normal files, and that the calc doesn't reset the pages the pic is on every time you call storePic)
-
You could try to make a tilemapper somehow (even though it takes longer to draw the screen), the flash wouldn't wear out.
Due to the way the maps are drawn, I bet a tilemapper would take at least 10 more seconds.
I guess you can test it by filling the memory of your CSE untill it can only store a few images, then call storePic a few times. If it starts garbage collecting, you know it can't be used in games.(That is, assuming that pics are handled as normal files, and that the calc doesn't reset the pages the pic is on every time you call storePic)
Yeah I will probably have to try that.
-
UPDATE!
StorePic causes GarbageCollecting eventually. I ran a loop counting down by 21956 every loop, starting around 3500000. Eventually, it got slightly slower, but not very noticeable, then it Garbage Collected. However, it didn't ask me if I wanted to do it: It simply started GC'ing automatically, like when you try to send an APP to the calc.
So yeah it does the same thing as when you archive a standard variable. Basically, I would be fine using it in Zelda, as long as it's not too often (basically, only StorePic when switching dungeons). I still have to keep in mind the people who will have most of their archive filled.
-
That is interesting.
But it would kinda suck if you play and suddenly garbage collect >.<
and 3000th post!!!!!! Let's party! :D
-
WOOOOOOOT SORUNOME!
-
That is interesting.
But it would kinda suck if you play and suddenly garbage collect >.<
and 3000th post!!!!!! Let's party! :D
Well, not if it automatically starts GCing, since you can't accidentally select "1:No". In ROL1 and 2 we could select No so if someone kept mashing the 1 or ENTER button before a battle, he had big chances to stop game execution by mistake, losing his progress.
-
Yay ! Everybody dance !