Denial

I installed it through the market, but unfortunately it crashes upon start. I have an old Android 2.2 tablet. I didn't get a message that v2.2 is too low. "The app ViceVIC20 (process it.opbyte.vicevic20) has stopped unexpectedly." Could you please provide a logcat? You can use an app like...

Looks promising! and fun
Looking forward to the final version.

Schema wrote:Pretty interesting. I played around for it for a minute, but can't figure out how to attach or load a program file.

Click the back button to open vice menu. Move with the virtual joystick.
From there you can load a prg file or open a d64 disk.

https://github.com/pelya/commandergenius

Here the codebase. It's for the c64. I did very small changes to it, like putting the right ROM files for the Vic.
If you need more information just ask.

So the bug is that I didn't take the line number + space and 5 chars for print (instead of the opcode for it) into account on length calculation.
Quick fix: decrease 86 to 78
Thanks for the advices!

When I wrote about the 88 character limit, I didn't mean the character count inside the quotes, or the length of the tokenized line in memory, but the total length of the BASIC line when LISTed. Now most of the lines exceed that limit and you can't edit them anymore. :( And, please, what's the reas...

True. Difference in speed is minimal. I had a chance to try it out anyways (I like to optimize programs) and the good thing is a 25% save in size, so I was able to fit 6 more frames in the same 16K ram. Here is the result: http://www.opbyte.it/vic20/megaman.prg Here is the generation prg, which can ...

The converter optimizes already a lot by leaving out {RVS ON} and {RVS OFF} control characters, when they're not necessary. But in the worst case, a single line could still contain 22 control characters, 22 printed characters, 2 quotes, 1 semicolon, 8 characters for the line number and PRINT, i.e. ...

KingTrode wrote:Just had a quick play on this whilst testing GB20.

Nice little puzzle game you have put together here, great job for your first VIC game.


KingTrode / Jim

Thanks

On a side note, I'd like to know if anybody get it to 100

matsondawson wrote:Cool, a bit of runtime compression on that with diffs between frames you could be in 6fps land there!

Yes, and a simple optimization for both size and speed would be to put two drawing lines on a single line of code (so half the print instructions).

Thanks! What score? Easy or hard?
So I'm not the only one who doesn't sleep at night

Just for fun I modified Mike's program to make poxel animations. About 4fps are achievable.

Here is a sample output:

http://www.opbyte.it/vic20/megaman.prg

16k expansion needed (24 frames, about 800 bytes per frame)

Thanks for the advice.
Sometimes I tend to be a bit too minimalistic, especially when doing 1.5K progs hehe!

Awesome!
Thanks very much Mike!

Kweepa wrote:Awesome stuff!
Any chance of 'true' aspect ratio?

Thanks
About the aspect ratio, I would need to investigate this a bit: with all the devices and os versions out there it probably won't be trivial...