With My experimental Shadertoy renderer and GLView #37
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.
I have been working these months on my own Shadertoy renderer for iOS, mostly in Swift 5.0.
Some of the shaders that the original version cannot render can be successfully renderer by this experimental version, such as ‘Super Mario World 1-1’ and ‘Happy Jumping’.
Some other shaders that can be properly rendered by the original version, however, look bad on my version, or even crash sometimes. I am still trying to solve that. Thus I just preserve the original renderer and make mine as an alternative version: By tapping the “info” button you’ll get a “Try using experimental GLView” option, then click it to switch to my renderer.
In order to debug OpenGLES function calls in case the Xcode’s GPU debugger does not work properly, I also duplicated another build target ‘Shadertoy_debug’ which uses fishhook to hook all GLES 3.0 function calls.
In addition, I also updated AFNetworking version to fix some compatibility issues.