-
-
Notifications
You must be signed in to change notification settings - Fork 87
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
[V2] Weird things happening on 2018.3.0b6 macOS #1
Comments
Probably because a lot of things have changed in 2018.3 and this has not been updated in months. It should pretty much be understood that most anything major like this will not be compatible with 2018.3 unless it otherwise specifies that it is compatible with 2018.3 |
Well, to be honest I wasn't expecting it to work at all, seeing how other similar project rarely even run on mac. However, considering that the README says it was last tested on 2018.2, 2018.3 didn't change that much (in the "legacy" rendering path), it was very likely to work. And on windows it probably does. |
Sorry I didn't answer earlier: I wrote one compute shader which does pretty much all particle calculations and thus has all kinds of parameters. But I only pass those which are required (if ColorOverLife is disabled, no information about color evolution needs to be passed to the GPU). This used to work. Apparently Unity now requires you to pass arguments for all parameters. I currently don't see why they made that change, but it probably has to do with optimization. Anyways: V2 is not stable at all. I decided to completely rewrite the project to make some drastic improvements performance wise, but due to other projects and studies I never finished. BUT: I still have hope that one day I might pick it up again. Or Unity's out-of-the-box particle system surpasses this. |
Better late than never, I suppose, lol. |
I get this error on run
Used version from v2 branch
And this one every frame
Using Unity 2018.3.0b6 on macOS High Sierra 10.13.5 with Nvidia 1070ti
V1 works fine however
Edit:
Changing the color to be
Over Life
instead ofConstant
"fixed" it. It then gave an error about the color. Set that toOver Life
too and then it worked. However the editor then looked like thisThe text was updated successfully, but these errors were encountered: