Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rendering on iPhone SE 2nd Ed. broken (upstream) #35

Open
caroparo opened this issue Jan 12, 2024 · 3 comments
Open

Rendering on iPhone SE 2nd Ed. broken (upstream) #35

caroparo opened this issue Jan 12, 2024 · 3 comments
Labels
bug 😅 Juju did a bad thing nope 😑 Not gonna happen in the foreseeable future

Comments

@caroparo
Copy link

Also tested on v2023.6; rendered results are broken for the test project.
Using latest runtime, built with Xcode 15.1.
Target device is iPhone SE 2nd generation, with iOS 16.1.2.

Attached is the result on iOS:
image0

And the expected result rendered on PC:
screenshot_1120 2024-01-12

@JujuAdams JujuAdams added bug 😅 Juju did a bad thing nope 😑 Not gonna happen in the foreseeable future labels Jan 12, 2024
@JujuAdams JujuAdams changed the title [iOS] Not working with GM v2023.11 Rendering on iPhone SE 2nd Ed. broken (upstream) Jan 12, 2024
@JujuAdams
Copy link
Owner

Upstream issue somewhere. I'm using a lot of varyings for the fragment shader which is likely part of the story.

However, Clean Shapes is not in active development and I will not be addressing this issue in the immediate future.

@caroparo
Copy link
Author

caroparo commented Jan 15, 2024

Thanks a lot for the reply!
There's indeed this error in XCode's Run/Console logs:

Error linking program:
ERROR: Implementation limit of 32 varying components exceeded. Unable to allocate 'v_vCircleInnerColour'.

I was able to remove varyings and distance functions for shapes I don't intend to use in my project, and render correctly.

@JujuAdams
Copy link
Owner

Great! Very likely possible to reduce the register count in the general case by reusing varyings but I leave that as an exercise to the reader.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug 😅 Juju did a bad thing nope 😑 Not gonna happen in the foreseeable future
Projects
None yet
Development

No branches or pull requests

2 participants