| Age | Commit message (Collapse) | Author |
|---|
|
I've left in a CHECKME for the part of the code I'm not 100% sure.
Unfortunately, this can't really be tested yet until animations
work properly
|
|
|
|
This fixes all of the scenes that expand over the screen (e.g. 101, 104,
109 in Phantom, as well as the several scenes in the Dragonsphere intro).
Also added a new debugger command, "set_camera", which sets the scene
camera to specific coordinates
|
|
|
|
|
|
|
|
Scene 105 in Phantom uses 9 dynamic hotspots
|
|
|
|
|
|
|
|
|
|
|
|
manually disable some features that are sub-optimal on the Pi when they don't pass a host parameter
|
|
|
|
This updates the German language file to address the changes introduced
in commit 19db601
|
|
isObject instead when needed
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Previously created Spanish saved games are broken though,
need to restart the game
|
|
|
|
|
|
|
|
DISPMANX because it controls whether dispmanx rendering backend is enabled or not on the Raspberry Pi.
|
|
to dispmanx.
|
|
|
|
modern Raspbian that uses multiarch.
|
|
According to johndoe it's correct to pass the entire coordinate,
rather than just X, to the car in these cases as well. I can't
tell any difference at all in the behavior, but I guess it doesn't
hurt either. After all, we can easily zero the Y coordinate, if we
ever want to.
|
|
|
|
|
|
addReverseSpriteCycle
|
|
Use an enum in various calls of _scene->_dynamicHotspots.add()
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
