Quantcast
Channel: Answers by "Noise crime"
Viewing all articles
Browse latest Browse all 90

Answer by Noise crime

0
0
From the sound of it, this is the 'OnEnable' bug with script execution order. That is I suspect your 'framework' script does not have an OnEnable method in it, in which case for some odd reason it will get trumped in execution order by the scripts that do, despite any ordering you add to the script execution. To fix this issue, simply add an OnEnable method to your framework script.

Viewing all articles
Browse latest Browse all 90

Latest Images

Trending Articles





Latest Images