Messages

No idea, sorry. I don't have an Android.

Another idea: I haven't tested this, but maybe you could move the camera, and from the camera callback, teleport the hero at the camera position. This way, the camera will not return at its initial position.

I entered an issue for this: https://github.com/christopho/solarus/issues/484
This will be done in 1.3.
In the meantime, you should be able to workaround the problem by moving an invisible hero (this is a dirty hack).
It is also possible to do chain successive camera movements without returning to the hero before the last move. I don't know if it can help

Did you run it with some quest data in the same directory?

Try to add self:set_optimization_distance(0) in on_created. The default optimization distance is often the source of problems with bosses and I will try to remove it in 1.3.
See http://www.solarus-games.org/doc/1.2/lua_api_entity.html#lua_api_entity_set_optimization_distance

Nice!
One remark though: you are loading the image "hud/small_key.png" several times (in a loop). You should load it outside the loop, even outside the function in a variable local to the script.

This is strange, nothing has recently changed with OpenAL.

This is an internal bug of the engine. It should now be fixed by commit e23651e. Thanks for the report!

I had exactly the same problem. It is a bug in SDL 2.0.0, fixed in SDL 2.0.1. Unfortunately, Ubuntu 13.10 only provides SDL 2.0.0
Debian provides SDL 2.0.1, so you can download the debian .deb packages:
http://packages.debian.org/jessie/libsdl2-2.0-0
and then
http://packages.debian.org/jessie/libsdl2-dev

Hi,
I agree with all your suggestions I added them to the bug tracker on github.
For the x icon of tabs, note that you can already close tabs easily by pressing Ctrl-W.
Thanks for your feedback

There is a syntax error in your Lua code.
crista.0.shop_mushroom_done_dialog_finished is not a valid expression, you cannot index a table (crista) with 0 like this.
Also, the function you declare is not local, it is in a table because there are dots in the name.

You can do a local function like this:

Code Select Expand


local function shop_mushroom_done_dialog_finished()
  game:set_value("i3001", game:get_value("i3001")+1)
  hero:start_treasure("trading", 2)
end

if destination == main_entrance_shop and game:get_value("i2021") == 10 then
  game:start_dialog("crista.0.shop_mushroom.7", shop_mushroom_done_dialog_finished)
end

But there is even a simpler way if the function is only used there:

Code Select Expand


if destination == main_entrance_shop and game:get_value("i2021") == 10 then
  game:start_dialog("crista.0.shop_mushroom.7", function()
    game:set_value("i3001", game:get_value("i3001")+1)
    hero:start_treasure("trading", 2)
  end)
end

Note: I removed the quotes around main_entrance, because since Solarus 1.0, the destination is a real entity type, not a string with the destination name.

Strange problem. Is there a joypad connected to your computer? Sometimes it may interfere.
Have you the same problem with other games? You can try this one for example (another Zelda fangame in C++/SDL too and that also runs on Debian/Ubuntu) : http://www.zeldaroth.fr/us/zroth.php

No, you are right, sorry, all sprites can have any size.
There are two notions of size: the size of an entity and the size of its sprite.

From the point of view of the obstacles of the map, the hero has a size of 16x16, no matter his sprites. You can make a sprite of 48x48, but then the behavior with walls will be weird: a large part of the sprite will overlap walls.
So for the hero, I think the sprite should not exceed 24x32.

You can set the quest size in quest.dat to something like 640x480, see for example https://github.com/christopho/zsdx/blob/master/data/quest.dat.
However, for now, most of your sprite will have to stay with a size of 16x16. Most entities have a size of 16x16 hardcoded. This will change one day, but not soon.

In the meantime, what you can do is keep sprites of 16x16 but use a pixel filter that scales the resolution. Scale2x is available in the latest release (Solarus 1.1) but the next release (1.2) will provide more filters, including hq2x, hq3x and hq4x.

Thanks