Firtina Ozbalikci

Also confirming that it works fine in Edge and Internet Explorer.

OK. It looks like on Chrome it's spending an awfully long time on getting stack traces for prop type validation errors... and somehow that's making it miss some frames for...

I couldn't reproduce the debug id error but it could be a clue! I will have more time this evening UK time to take a look.

And a newer version of React :) I think 15.1.

OK, I fixed the _debugId issues on #77 , will keep an eye on the weird chrome lighting issue still

Hmm... Okay I will fix this asap, looks like I forgot to wrap a call in dev flag checks, sorry about that On Wed, 15 Jun 2016, 15:46 Robinnnnn, [email protected]...

@Robinnnnn can you please provide a link to a repro build? I could not reproduce this on my end

@ashtonwar do you still see this issue?

Could you paste a gist and the full error please?

Please try the modifications in here: https://gist.github.com/toxicFork/9dafb302cbbadf0544c11d6af4b85738/revisions After adding the `ref="shaderMaterial"` and ``` jsx componentDidMount() { this.refs.shaderMaterial.extensions.derivatives = true; } ``` I am no longer getting errors. I did not...