Search the Community

Hi all, I updated to the latest preview version of BJS, and now the camera panning behaves differently: What I want: http://playground.babylonjs.com/indexstable#MA1ADL Current behavior: http://playground.babylonjs.com/#MA1ADL What has changed? Thanks

Hi, I've replaced a previous 3.1-alpha with the latest preview, and now when I use a registerBeforeRender to set the alpha and beta rotation values, it allows you to rotate the camera before the render, and after the rotation is reset. Now: http://playground.babylonjs.com/#RWSSKV Then (August 17): http://playground.babylonjs.com/indexstable#RWSSKV Is it a bug? Thanks.

Reporting bug regarding instances and their parents not being rendered when HighlightLayer is used. http://babylonjs-playground.com/#29SZC0#10 Ping @Sebavan /Swiftwork

Hi I have spoken to @Nockawa already and he suggested I turn to the forums which I agreed with. When using a bundler such as Webpack, the developer imports the the BabylonJS library rather than including it in a script tag. The problem that arises is that Earcut has been defined in it's own namespace and is available only in the babylon.js file or globally when using script tags. However in Webpack each imported module is treated as an isolated scope and doesn't have access to other modules or global variables unless they have specifically been required/provided. Because Earcut is never exported and in it's own namespace it is literally unreachable for module bundlers: > babylon.js defines Earcut module > babylon.js defines and exports BABYLON module > Webpack provides the BABYLON module from babylon.js to all other libraries > babylon.canvas2d.js extends and exports BABYLON module x babylon.canvas2d.js uses BABYLON and Earcut (but Earcut is not provided nor in the same namespace) This leave 2 solutions as I see it: Add Earcut to the BABYLON namespace so that they get exported together and can both be provided by bundlers. Keep Earcut in it's own namespace and export it so that it can be imported by both babylon.js and babylon.canvas2d.js or provided using a bundler. Ping @Deltakosh, moving forward it might be worth looking into npm more. They offer the for example the option to add @next version tag for alphas/betas of packages. I am sure Babylon.JS would benefit from having more users testing/working with the preview build and finding issues. Kind Regards Swiftwork

I got the latest babylon.js preview release build from git, and it seems like the statistics window from the debug layer is partially hidden. I tried it both in Chrome and Firefox. It doesn't happen with the stable 2.2 version.

Which tools do you use to create game preview - image with launched game on iphone/ipad/etc. I tried to use simple iphone simulator but it is not so comfortable and requires additional Photoshop-ing to cut desktop background, visible over rounded corners.