Quote from: pimathbrainiac on February 16, 2014, 03:25:57 pm

I think that this is a terrible idea. I really don't mean to be rude, but asking people to pay for calculator programs/apps is wrong. Period. Nothing else I can say.

I think that is a bit harsh. Fiat money is in you wallet, Tic's is on your calc, and is nothing more then a way to have users try harder to get to the next level. Xeda is right, for example you have a lot of monopoly games on ticalc.org, one could be a multiplayer game that uses tic's as value, or buy a Pokémon with tic's, of a boss level with TIc's. Optionally have a poker game with kerm's online bridge and bet with Tic's. They wouldn't really have value, because lets face it anyone who programs on ti-8x knows that its open source or at least not worth payment. Basically the possibilities are endless.

Keep in mind that one of those endless possibilities is users simply hacking in as many as they want. When the system that generates them is as weak as a calculator, it's impossible to validate the rightfulness of their existence.

Edit 2: In response to Runer's earlier question, I mainly limited the app names because I didn't want people doing things like making two apps called PokemonR and PokemonB, which would happen to use the same save file names.

If the user specifies an 8-character name for a ROM that has a 32KB cartridge, just echo out a (appropriately flashy) warning mentioning this. I think the ability to have 8-character names if you're made aware of the issue greatly outweighs the likelihood of someone ignoring the warning message, making two apps with 32KB cartridges that differ only by the last letter, and sending them both to their calculator and trying to run them. And if they ignore the warning message and screw up their save, that's their own fault.

Also, if you do take up my suggestion to save emulator settings in an appvar and think this still could be an issue, you could block out the possibility of this occurring entirely by saving the application name with the emulator metadata. Then you can check that the appvars being loaded by TI-Boy correspond to the app of the correct name.

No, I hit the same slowdown he hit. For some reason, the game runs a fair amount more slowly in Oak's lab than in other areas.

EDIT: Also, rw24 is absolutely correct. At least in Pokemon games, saving doesn't appear to work. In Pokemon Red, I'm positive I saved my game a couple of times before closing the emulator, checked that the appvars were there when going to start it up again, and lo and behold, no continue option. In Pokemon Silver, I got the continue option, but it told me the save was corrupted.

EDIT 2: Should I be getting garbage/data printed to the screen when I exit? For the past few times I've exited, I've gotten mostly white with some strips of random black and white pixels that looks like data, as well as some rows that look like the tree-like structure you get of sending the raw bytes 0-255 in a pattern to the screen.

EDIT 3: Is there any way that key polling could be improved? Quick key presses are often ignored.

EDIT 4: Feature request: saving emulator settings in an appvar. I know I can set the zoom mode, pick the palette, and set the frameskip on startup myself, but having it do those all automatically just seems a lot cleaner and nicer, especially if you get confused like I do about which palette or frame skip setting you actually decided on the last time you spent a minute or two carefully comparing them. And hopefully, there will be more cool features to come and their settings could go in there as well.

Quote from: Runer112 on February 15, 2014, 03:55:48 pm

Quote from: rw24 on February 15, 2014, 01:00:06 pm

Oh, and would Pokemon Gold and Silver be in color? Because they work on the Game boy, but they are in color.

Those are Game Boy Color games. The Game Boy color is not supported for emulation due to a number of increased technical difficulties in emulating it.

Correction: Those games ARE Gameboy games. They were released right when the Gameboy Color was first released and so retained backwards compatibality with the Gameboy. I can prove this because I have a Gameboy original that can play Pokemon Silver. When run on a Gameboy, it simply uses monochrome textures.

Really? I always knew they were shaped like Game Boy cartridges, so I guess it isn't that surprising. Maybe with some work, they could function in full color, but I certainly wouldn't hold my breath for this. I guess we'd have to wait to hear what calc84maniac thinks of its feasibility/infeasibility.

EDIT: Confirmed that Pokemon Silver does indeed run, although it suffers from the inability to save properly like the other Pokemon games currently. A note to anyone who does want to load up a generation 2 game, though: they seem in general to run more slowly. Regardless of the frameskip setting I was using, it took about 2 seconds longer to walk 8 squares in Silver than in Red in their respective starting towns.

Nice job on the progress. Has any research been done into the late-era Game Boy games that try to provide their own limited form of palette color data (of course we're talking about Pokemon)? It's entirely possible that the palettization they do only looks simple and is in fact much more complicated under the hood, but I'm pretty sure that a large portion of TI-Boy users use it to play that (especially now with the guaranteed ROM and RAM space).

If you're not that interested in researching it to support it, I could offer to try.

I believe a full-screen, 320x240 mode is planned for development. He will try to support stretching the screen to completely fit, so 2x horizontal scaling and 1.66x vertical scaling (probably without any interpolation). I guess a clipped mode with 2x vertical scaling is also possible, but I don't think he's as interested in supporting that, at least not yet, as one of the nice benefits of the larger screen was ditching the screen scrolling code that TI-Boy for monochrome calcs needed.

Sounds like your ROM might have been infected by bootfree. I believe some versions of Wabbitemu decided to randomly splice the third-party bootfree boot code into ROMs, which breaks flash unlocks designed for the real TI boot code, which Axe relies on. I'd recommend updating Wabbitemu to the latest version, which I believe shouldn't unexpectedly do this, and trying to replace your ROM file with a fresh one from your physical calculator.

Make speed a variable and slowly increase it over time? That's a pretty standard arcade game mechanic that seems like it would work pretty well with this kind of game.