BlackMojito Posted February 28, 2018 Share Posted February 28, 2018 Hi Folks, I am getting below GL error when calling scene.pick() since 3.2.0-alpha8. I am not able to reproduce it with a simple background. Would any one of you know what (which commit) might cause this? Everything worked correctly with alpha7. [.Offscreen-For-WebGL-0C016078]GL ERROR :GL_INVALID_OPERATION : glDrawElements: uniform buffers : buffer or buffer range not large enough at index 0. And the result is that my CustomRenderTargets in the Scene cannot be rendered any more... Quote Link to comment Share on other sites More sharing options...
RaananW Posted February 28, 2018 Share Posted February 28, 2018 Hi, would you be able to reproduce this on the playground? so we can see exactly what went wrong? Quote Link to comment Share on other sites More sharing options...
BlackMojito Posted February 28, 2018 Author Share Posted February 28, 2018 I tried but I could not reproduce it in a simple playground. But in my code, I am pretty sure that it is when executing scene.pick() that the GL error occurs. Would you please give me some debugging instructions so that I can narrow a little bit the cause? In the meantime I will try to see how I can reproduce it... Thanks. Quote Link to comment Share on other sites More sharing options...
RaananW Posted February 28, 2018 Share Posted February 28, 2018 This can happen due to many reasons, but I doubt scene.pick is one of them. it might be a callback executed after the scene pick has returned. Try removing callbacks registered and see which one is causing this. The try reproducing this specific function on the playground so we can understand what was changed and if it is a bug. Quote Link to comment Share on other sites More sharing options...
Guest Posted February 28, 2018 Share Posted February 28, 2018 also, you can share your page online with a reference to babylon.max.js so we can debug it live Quote Link to comment Share on other sites More sharing options...
BlackMojito Posted March 1, 2018 Author Share Posted March 1, 2018 Sorry it hasn't been deployed yet. Everything is executed at localhost at the moment. BTW, when using Webpack, how can I link babylon.max.js instead of babylon.js? Quote Link to comment Share on other sites More sharing options...
brianzinn Posted March 1, 2018 Share Posted March 1, 2018 Have you tried this: 1. add babylon.max.js as a script to your HTML: <script src="https://preview.babylonjs.com/babylon.max.js"></script> 2. add to webpack config: new webpack.ProvidePlugin({ BABYLON: 'babylonjs', }), I didn't actually try that, but should work. https://webpack.js.org/plugins/provide-plugin/ edit. or via externals: https://webpack.js.org/configuration/externals/ Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.