291–300 of 350 posts
Love all of it except for the camera controls on iOS. Not sure how you could improve them but they need some work. Camera gets too close to the character a lot. Might consider two touch controls that separate movement direction and camera position.
I spent more time enjoying the graphics and style than actually playing. it runs so well on a mobile device, I've never seen something like this. as for the game itself, I couldn't understand how to deliver the messages.
It's gorgeous. But I can't figure out why they didn't just use real japanese text instead of fake text.
* I love the writing, it's witty and poignant
* I was impressed that WASD controls worked with my keyboard set to Dvorak :)
* Unfortunately have to second the comments about nausea; the oddly paced camera (it feels like it is panning through molasses then suddenly accelerates to switch views) is probably responsible, I'm guessing the "overshoot view then correct" "feature" is also a factor. Additionally seconding the comments about allowing the camera to follow the mouse (if feasible somehow while not losing cross-form-factor support) would go a long way to help here as well.
* The font that shows you where you are is cute in an orientalist sense, but imho it is very difficult to read (even knowing what it says from context clues and previous hints)
* Not a criticism but it is odd to have jumping when there is no mechanism that uses it in-game
* 99.99% a me problem: I had a hard time with spatial awareness and a difficulty building a mental map of the world and my best guess is that it's because I personally found the default field of view to be too "zoomed in".
One of the most impressive things about this is that it transfers only 5.7 MB of data on initial load and then caps out at 17.5 MB for the final load. It seems to be making smart choices about compression techniques. This is a good showcase of how well games can work on the web if done well.
So many techniques that made web games good, in terms of smart loading, have been lost or abandoned since the mid-2000s when bandwidth limitations were common, and at the same time "engines" like Away3D and Starling were starting to leverage AS3's ability to handle async calls and async uploads to the GPU. JS engines now try to bundle that behavior into asynchronous asset loading calls, but it's not ever really diale…
There's no market for flash style web games so you don't see it.
Earlier quoted context omitted.
Can always use Electron or Tauri to turn it into a native app
Electron and native do not belong in the same sentence AFAIK unless you mean 'native to the browser (which happens to be included in the package)'. Tauri is the same, just bring your own 'browser' (webview, really).
One of the most impressive things about this is that it transfers only 5.7 MB of data on initial load and then caps out at 17.5 MB for the final load. It seems to be making smart choices about compression techniques. This is a good showcase of how well games can work on the web if done well.
Am I wrong in feeling that 5-15MB is... more than enough data for the world we see? There's not that much information here. I'm not trying to be a demoscene smart-ass here, either (I expect demoscene masters would've packed the equivalent in under 1MB). Just that, models are low-poly, the world is small and made up from pieces that feel simple to describe; as long as you're not trying to bake everything into a static…