Monday, January 7, 2013

Some insights to Roll the Ball 2

RTB2 concept Art

Roll the Ball is a little android game I made with friends as a school project.

Version 2 of the game will be using Unity (3?), so we can concentrate on the game itself instead of the engine. A first testworld is already in development to evaluate what can be done, without loosing much performance.

But before starting I made some concept art, that will help to get the right look and feel for the levels:
Testlevel
Fireflies


more coming soon...

Performance

When we started RTB1 we designed it to be running best on a Samsung Galaxy S1. It runs with ~40fps and the phones native resolution. The current generation of phones (like S2 and S3) has no problem running it at 60 fps, but the resolution is quite low, especially on tablets.
One thing I learned from this: hardware power develops much faster than you think. Since this project will take about one year to be finished (maybe more), RTB2 will be developed for current super phones. With Android gaming consoles on the horizon, and chips like tegra4 available soon, this will hopefully be the right decision (we can always tweak down some settings).
Making lifelike animations and characters on a smartphone is hard enough, but having moving lights, detailed textures and other effects (don't forget sound-design) drives the frame rate down to the lower end very fast.

Character design

Those firefly monsters communicate with light, since it is very dark where they live. They don't speak or make noises, so they don't attract enemies. Their lights will react to different situations: fear, curiosity, attack or idle.

Level design

There will be light. Having lights and (faked) shadows [unity indie version :( ] will make a great atmosphere.
Evolving sound patterns will provide a great feeling of progress and error. 
Like RTB1, there will be different World designs, driven by a story.

BB10 Alpha Device arrived!

BB10 Alpha Device arrived!


... and HTML5 runs much smoother.

I thought I have to give up on programming Processing.js webworks apps, but the new browser handles everything pretty well.

My particle clock runs at 48 fps. In comparison, my playbook with QNX 2 manages about 12 fps.

Try it out yourself: Particle Clock Link

Just an Alpha Device



Despite the fact that the OS version is 10, it's not the final consumer software. It is stripped down to fulfill the developers needs, and also includes a nice overlay for cpu usage, memory, fps,... that can be shown via swipe gesture.

Telephone service is disabled, and it comes with only a few apps (you can sideload some apps like facebook from the playbook via DDPB installer or different programs).

The camera is just great although video recording is not fully working (stuttering). Nothing more to say.

Wednesday, December 19, 2012

Panoramas

Microsoft ICE is an excellent tool for panoramas:





Give it a try. The quality is much better than most smartphone panorama apps, since it is stitched in full resolution. Simply make some pictures and add them to Microsoft ICE on your PC. Everything is done automatically, with only a few artifacts, depending on your pictures.

It also works great with games:








Link:
Microsoft ICE

Wednesday, December 12, 2012

Blackberry Webworks Error

So I tried getting a Blackberry Webworks application for a playbook to package my html5 app and always got this error:


out: Error loading: C:\Program Files (x86)\Research In Motion\BlackBerry WebWork
s SDK for TabletOS 2.2.0.5\jre\bin\client\jvm.dll

out: [INFO]                     Packaging the bar file

error: java.io.FileNotFoundException: C:\Users\Patrick\AppData\Local\Temp\widget
Gen.5953573461355327252589.tmp\particleClock.swf (Das System kann die angegebene
 Datei nicht finden)

error:  at java.io.FileInputStream.open(Native Method)
        at java.io.FileInputStream.<init>(Unknown Source)
        at net.rim.tumbler.file.FileManager.copyFile(FileManager.java:481)
        at net.rim.tumbler.airpackager.AirPackager.run(AirPackager.java:232)
        at net.rim.tumbler.WidgetPackager.go(WidgetPackager.java:152)
        at net.rim.tumbler.WidgetPackager.main(WidgetPackager.java:77)

out: [ERROR]                    Air Packager exception occurred

On the BB support forum I read that it is a problem with the msvcr71.dll. Some suggests putting it in the System32 folder, or even place the whole BB bbwp folder there.
Since nothing of this worked I found a solution:

Open the bbwp.properties found in "[C:\Program Files (x86)\Research In Motion]\BlackBerry WebWorks SDK for TabletOS 2.2.0.5\bbwp\bin", or where ever you installed it, and change the Java tag to your JRE:


For example:
<java>C:\Program Files (x86)\Java\jre7</java>

While you are at it, you can also set the path to your debug token.

For example:
<debug_token>C:\Users\Patrick\Local Settings\Application Data\Research In Motion\debugtoken.bar</debug_token>

I hope this information helps someone someday.
Mfg Pat
 

Monday, December 3, 2012

Hello world

Hello world,
I hope blogger gives me the freedom I want to regularly post about things...
Let's see...