Using the default render script with a camera set orthographic inside the same game object as the sprite works as you intend. You have to offset the sprite in order for it not to be in the corner.
Instead of moving the player through the world, you could move the world around the player. The camera needn’t synchronize with the player object at all, then.
I was considering this, but what complicated it is the physics and that the end result will be a realtime multiplayer game with many game objects whizzing about. I haven’t quite figured out how to handle all that with the player effectively stationary.
I have not looked into exactly why, but I presume that it is because the sprite is updated in the go property and orthographic being updated in script updates. The go animate property works separately from update functions so depending on the life cycle, there will be some jitter due to LUA being behind the internal go animate. Orthographic is great extension but given the new camera functions of Defold it is a bit outdated. The functions you need from orthographic could easily be implemented into the current camera component, such as shake and following.
Just a followup on this: Using the new camera component and moving it inside the moving game object works perfectly. No stutter, utterly smooth, always. To me, this is major!
You have enabled use_fixed_timestep for physics, so for all physical objects and for the camera you need to add yourself interpolation of their position and rotation in time. In short, using vmath.lerp/vmath.slerp.
My workaround, if the gameplay of the game allows, i.e. it does not require a strict constistency in the application of forces: is to disable fixed timestep for physics, but set engine.max_time_step = 0.05 (i.e. 20 fps) or less. And limit max fps to 90-120 via display.update_frequency. So that objects don’t fall through if the game slows down at the player or the window loses focus (in a web game). Suitable for 2D only, as Box2D handles floating dt perfectly.
:
