Found this gem a few days ago. I received my PlayDate recently and this game is a sure buy once it's out. Good luck with the development!
SkyArcher
28
Posts
37
Followers
27
Following
A member registered Apr 12, 2016 · View creator page →
Recent community posts
This is lovely and the very thing that pushed me to finally get a Playdate, after looking forward to the console for so much time. Waiting for it to ship then this is the first game I'm going to buy!
Just my two cents by looking at gameplay videos: I believe the spline system driving the train/camera is not smoothing the corners correctly, the motion feels twitchy.
This is a beautiful jump into the memory lane, fills me with nostalgia. Thanks a lot for making this!
Though, for some reason this is running poorly on my Macbok Pro 2012 even at low settings.
EDIT: still thinking a lot about this. I would love to help improve it, so if you may need something, don't mind asking.
Are these fixes into #195? Because yesterday I played #192 and had the same problems as Arakorn, but only during one of the two playthroughs I did, both on Tourist.
The first one went totally smooth (render scale 0.7x, AA 2x). The second instead, hours later, was all jittery no matter the graphics setup, even after starting a new level many times. Menu was always fine though! Pretty weird.
I'll update to #195 asap to check it out. By the way, have you considered a Discord server for the game?
Been playing the game for a while and I find it really, really good, totally in my top three games for Quest. Love the atmosphere and the locomotion of course. I have some gripes with it though (Quest version)!
Performance is kinda bad compared to other games. To play decently smooth I have to play with 0.8x resolution, direct-to-vr on, no AA or Bloom... It's quite dull and pixelated. But I recognize it's a custom engine and the non-euclidean space makes things a bit heavy (multiple cameras everywhere). I hope there's room for improvement, the Quest version could really stand out with just a bit more detail.
In my experience using Unity, shadows and shaders are what kill Quest performance. Reducing polycount helps mostly with memory, but probably there's something in the shaders that is slowing down things? The game looks already very lowpoly, I believe there's something else going on.
The elevator section with the cannons is pretty harsh. Lots of crouching to avoid death (even with crouching disallowed in the options), hard to see where the elevators will go when having multiple branches... The shield droid can only help some. After a couple runs it feels annoying rather than scary/anxious.
That's all, I believe. Keep on with the amazing work!
Played yesterday on Quest in a very small space (4x2 cells), still had a blast. Felt kinda tense at times, maybe due to the feeling of not knowing what to expect... Totally looking forward to play more and in larger spaces!
Aside from some slight fps drops, I’d like to report a bug: I grabbed one of those small flying worm/disc bots that stick to walls, and thrown it out of a rooftop... It flew around a bit, then the game crashed hard, forcing me to reboot Quest. Maybe it didn’t find a wall to stick on!
I really enjoyed my first run with it, the driving difficulty is just right and satisfactory. Love the overall feeling!
Time for bug reporting: I have some issues with menu controls. I couldn't highlight "SELECT" when choosing a car. Then I linked a mouse to the laptop, clicked randomly, and it went on... No cursor was showing up anyways. Also I couldn't figure out how to change weather. One last thing: how do you reverse?
Great work anyways, will follow for sure. Hope in an OSX or iOS release later on!