Conversation
Yay, it renders!
...the CI runner doesn't support anything newer, apparently.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Implements #41
This branch aims to make the impossible possible and adds a watchOS target. Since
GameplayKit(andUIKit's views/view controllers) are unavailable, we had to get a bit creative and implement the relevant subset of these APIs ourselves, including a custom implementation of perlin noise (seeWatchGameplayKit). Using SwiftUI for input handling, the game actually runs on the watch:The camera can be rotated by dragging, the player can jump by tapping the screen and move forward by rotating the crown.
(Of course, this shouldn't be taken all too seriously, the gameplay experience is... well, but hey, it's feasible!)