In this update we have updated the engine to UE4 4.26 which has enabled us to use a new loading system which has been optimized for SSD's. This should result in faster load times in general.

There is also a fix included that should help prevent a crash when loading a large scene for the first time which shows an error message similar to:

Over the last few weeks we have been working on a lot of different parts to improve things. There should be some overall performance improvement and there are some Quality of Life changes as well.

We changed from deferred shading to forward shading which has improved performance in our tests by up to 6 milliseconds (ms) in some places. The target render time for us is 11ms (roughly 90fps) so that it remains as smooth as possible for different devices even if a device has a lower target framerate.

The reflections will be noticeably different as we cannot use Screen Space Reflections however they were causing artifacts that we were not happy with; there are still reflections but they are less mirror-like. If there are frame rate issues then try turning on the Async Projection in SteamVR (also known as motion smoothing) to see if that helps.


The controls have been adjusted so that the jets will propel you in the direction that you have the controller pointing at. We changed the grapple hook system to be less of a hook and pull system (like Widowmaker in Overwatch) and more of a swinging system (Spiderman, Windlands, etc). Lastly, we added thumb-stick turning for Oculus devices.


The majority of the music has been finished and placed in the final game which means the level tracks have been changed so the music that has been in the demo level has changed to another one (don't worry, the original track is in a different level). Sound effects are still being worked on but will be in the final game.


Up until now the crash reporter sent the reports to Epic Games which may have helped them if it was an engine related crash but we were unable to view them so if it was a game related crash, we wouldn't know. Now they are re-routed to our crash event handling back-end so we are able to view them and forward them to Epic if we are not able to fix it.

The only data that will be sent to us is your machine specifications (OS, CPU, GPU, RAM, etc), a mini-dump\call-stack that tells us what broke and where in our game specifically (nothing else), and the install location of the game (e.g. D:/MyGames/Steam/SteamApps/Common/Ink). If you do not want us to have this information then click on "Close Without Sending", or the equivalent, when the crash report window shows up however we will not receive any information and cannot take action on it.

An example crash report call stack (from intentionally crashing the game):

If the game crashes without showing the crash report window, it has been our experience, an issue with SteamVR and was fixed by restarting SteamVR then launching the game again.


We will be working on an updated tutorial level as the current one was designed for the old controls (the text has been updated though) and more sound effects so keep an eye out for that.