@Simeon - not locked out of app, chose to restore but didn’t work. Do I need to reinstall the new version?
Are you still taking testers?
@JakAttak join us, dm me your email
The thread was quite long so I didn’t read the whole thing, but has anyone else noticed sluggish scrolling? Everything except the main page (the file screen) feels slow for me, including the sidebar. I’m on an iPhone X with iOS 12.1 if that helps.
@JakAttak that is odd, it seems OK on my iPhone X. Is it with any shader?
Notes from day one:
- The tutorial needs an update around the Emissive Strength and Emissive Color. Neither of those options exist from what I can see and find. I eventually solved it by dragging a Color node to the Emission equals connector - and that caused another connection to populate which seems to be right.
- If an example shader ends up named the same as another shader, it will overwrite if opened. I’ll try to reproduce it tonight on a screen share. I noticed this with one of the Intermediate Examples (the 2 spheres with noise layers) was named New Shader, and when I went to open my tutorial shader (named New Shader) it was the 2 spheres. Deleting and recreating it only lasted until I opened the 2 spheres, which would then overwrite the one I made.
@athros oops, that tutorial is still referencing the old Surface node. Emissive Strength and Color are just combined now (the intensity of the color defines the strength.
Did you put your shaders in the example folders?
That could very well be it - I was searching through the file browser when I hit Create New Shader, and it must have created in th examples folder.
Hmm…I created a new shader and it copied the 2 spheres outside the examples folder. After removing the new file and renaming the 2 spheres from New Shader to 2 spheres, it now errors on new creation. I’m working on a screen recording now.
EDIT 1:
Video
EDIT 2:
It looks like it was recreated after the crash, and if I delete it, then close and reopen the app it also recreates it.
@athros wow, thanks for the video that is really helpful. We have a trello board here for logging bugs too (a bit more organised than a forum thread) https://trello.com/invite/b/KcQn3GhD/c8197f8f9a4e932469cd02440a505ed7/shade-feedback
@Simeon @athros I looked at the picture of the “Pic of the error” and that’s the same error I posted on the trello board on Oct 20, so you don’t need to post it again unless you want to.
@dave1707 - I’ll add the video link to your ticket for added information.
@Simeon - Invite accepted!
It doesn’t slow down with smaller shaders, but anything starting to get somewhat complex is a problem.
I tried to capture an example but it’s hard to tell how slow it is without seeing/feeling the input.
On the Cloud shader: https://imgur.com/a/fHTZevG
Minor spelling: if you are going to capitalise mathematical function names then you should use ASin rather than Asin and so on.
(On reflection, I wouldn’t capitalise mathematical functions at all.)
@jakattak that is pretty slow. I think we need an option to pause the live preview or render it ever second or third frame when the shader gets complex.
@loopspace aesthetically I’d like to have all the names in title case because of consistency. So I prefer ASin over asin. Not sure if we can fit in the change though (at the moment the nodes are just lower case internally and title-cased on word-by-word basis)
So, dumb question - the 14 day trial ran out (been busy changing jobs and with other life stuff). If I buy the full, will that transfer over to the release version of Shade?
@athros You’re listed as a beta tester, I assume that’s for Codea. Did you ever send a request to @Simeon to be a beta tester for Shade. The beta version of Shade in TestFlight still has 58 days left before it expires.
@athros If you buy the unlock it won’t charge you. You’ll notice it will say something like Environment: Sandbox, this is due to it being a TestFlight app.