#Not rendering custom material 0.8
14 messages · Page 1 of 1 (latest)
Ah yes, I will check if that resolves
It looks like it was the inheritance, it hits the shader now
Thank you, that would have taken a long time to spot
Still nothing though, I checked ComputedVisibility to be true, it only seemed to care for the shader for a second
I fixed it, I am setting Visibilty to false for everything each frame, before setting those I want to be true. It didn't like that. Letting everything stay visible it gave me shader errors and after fixing them it rendered. Reverting back then worked. A little weird I think, all the visibility changes happen within the same system so I don't think anything should be propagating.
That's interesting - try simply calling visibility.set_changed() in your system to see if that also triggers the behavior
I've made too many changes, can't(won't, not under git) replicate. It seemed to be intermittent though so it might just have been tiredness, although I went back and forth multiple times to check before posting. I would only note it.
It is with intention that no child without a parent with VisibilityBundle will render right? I just want to be sure, it's not very clear from the migration guide/news, and neither very intuitive. I expected it to work like transform (and it is presented as), propagation being possible, not necessary.
I agree. Can you please file an issue to swap this behavior?
Yes
Thank you very much 🙂
Before I post stupid, the situation is the same with TransformBundle, the parent needs it for the child to render, tested on 0.7 too. Not something basic I overlooked?
Genuinely unsure; go with the results of your testing