Or maybe it's just the framerate being played on browsers ... who knows.

An interesting thought. Its possible I caused issue with the screenshots themselves, but not the core. Although the screenshots are based on the core timing i believe.

Also walk me through the steps for exporting. You sent the group to wabbit and then tried to extract the progs? I could see that being an issue. Also extracting groups from wabbit will not work. I'm 99% positive. However I just tore apart the importvar function, so groups don't currently work and I can't test...

So apparently there have been some complaints lately about wabbitemu running faster than normal. Its entirely possible that in my mucking in the calc_run_all code that i made a mistake and made it run faster than should. So naturally i did some testing. First, all tests were on the following calc (and a rom of the same calc):
TI-84+SE from 2006 (hardware revision F)
OS 2.43
Boot code 1.02

I tested using the a fresh release build (which you guys don't have yet, but there are no differences to the timer code)
I tested using Dr Dnar's stopwatch program. I ran each test twice for accurate results. For testing i ran the prog on each then when both were ready and held my calc up to the comp screen to watch as the timer ran. This way i could see roughly how close they were to start. In 20 seconds there was no noticable difference between the emulator and the calc. I also ran the program for 300 seconds (5 mins). By the end the emu was approximately .5 seconds behind the real calc.
If you guys want to run the same tests, be my guests. I will also accquire some calcs from people on my floor and run the same tests. The ti83+ is probably the most important other one to test, because it doesnt have crystal timers. Make sure the batteries in it are fresh when you test

tl;dr: There is no time difference you guys could notice from just running a normal program.

In Task Manager under Processes, the mem used by Wabbit keeps increasing (at least on my comp).

32 bit or 64 bit wabbit and which version are you running on your comp OS?

I'm on XP with a 32 bit system and the starting memory usage was 7544 and then five minutes later and playing with it for a bit it seemed to top at 8556, though I thought I saw it at over 9000 (no, not a meme reference) at one point but it must've gone back down (obviously).

Hmm did you see it increasing by 8s if you let it just sit there not playing with it? It would be quite unfortunate if you did

Just running it causes it. it makes me very sad (((

open up task manager while running wabbit. watch the memory count

Cool to hear ^^

Are you planning to continue working on WabbitEmu regularly after the ticalc.org release? I should maybe put a sub-forum for it in Major community projects if you plan to, so it will be easier to find stuff about it (although there's always RevSoft as well for info, especially the Mac/Linux builds)

of course. i probably wont be as on top of it as i am now, but if you want something added or changed it will get done.

i have a question
i've just downloaded wabbitemu, but when I start it up, it crashes after 1-2 minutes.
does anyone have this problem too and how can i solve it
btw, I have the latest version.

How much RAM do you have in your machine. There is a bitch of a bug that cause memory to be eaten away in release builds that I for the life of me cannot track down.

For the skin issues mighty moose, I tried every rom I have, which is as far as i know all models, and all skins loaded properly. I tried cutout and non cutout modes and switching back and forth between them several different ways. Can you give me any specifics to follow (ROM model, computer OS, and then steps that causes yours issues)