0 Members and 1 Guest are viewing this topic.
Quote from: calc84maniac on October 22, 2011, 12:01:30 amfred30w, it looks like the reason Kirby's Dream Land was crashing for me was a glitch I accidentally introduced in the development version. Beta 0.1.07 seems to run the game fine. Are you using the latest version of wabbitemu from http://wabbit.codeplex.com/?Thanks calc84maniac! Kirby runs great now! I appreciate you bringing to my attention the update for WabbitEmu. I'm not sure if this is a bug with WabbitEmu or the emulator, but now Kwirk runs super slow. I know game compatibility is not your goal at the moment, but on TIBoy 1.03, the game ran fine. Sound slows the game even further. I would be more than happy to make one of the calc screen videos but I don't know how. Can you explain to me how you do that?
fred30w, it looks like the reason Kirby's Dream Land was crashing for me was a glitch I accidentally introduced in the development version. Beta 0.1.07 seems to run the game fine. Are you using the latest version of wabbitemu from http://wabbit.codeplex.com/?
In other news, Frey continues kicking unprecedented levels of ass.
Quote from: fred30w on October 22, 2011, 05:19:13 pmQuote from: calc84maniac on October 22, 2011, 12:01:30 amfred30w, it looks like the reason Kirby's Dream Land was crashing for me was a glitch I accidentally introduced in the development version. Beta 0.1.07 seems to run the game fine. Are you using the latest version of wabbitemu from http://wabbit.codeplex.com/?Thanks calc84maniac! Kirby runs great now! I appreciate you bringing to my attention the update for WabbitEmu. I'm not sure if this is a bug with WabbitEmu or the emulator, but now Kwirk runs super slow. I know game compatibility is not your goal at the moment, but on TIBoy 1.03, the game ran fine. Sound slows the game even further. I would be more than happy to make one of the calc screen videos but I don't know how. Can you explain to me how you do that?Press backspace to start. Press backspace to end.
Hmm, it seems Kwirk was one of those games that sometimes polls the hardware to check the LCD drawing status. Now I seem to have fixed the issue by toggling the status at every scanline.
I know this is a bit offtopic, but why does it seem that this older calculator seems more snappy than my new one (rev. P-0410P). For example when the ram is cleared, its almost instant on this old one, but it takes about 1 sec longer (there is the progress bar on the top right for a sec) to clear the ram on my new one. What causes this? I can always make a video if you need one.
calc84maniac ti-boyse 1.0.7 broke my cousins calc by it ran out of battery while he was playing pokemon
Quote from: annoyingcalc on October 30, 2011, 12:48:54 amcalc84maniac ti-boyse 1.0.7 broke my cousins calc by it ran out of battery while he was playing pokemonIf the battery was empty then the calc isn't broken, right?
nope it fails :'(