Hello!
I have a problem, (or babylon have a problem) with multiply transparency.
Look at this example scene in attachment
Just look around in this scene. Do you see how behave colored objects at different angles? They suddenly go out or become brighter.
Same problem in Unity discussed here: http://answers.unity3d.com/questions/609021/how-to-fix-transparent-rendering-problem.html
Waiting for Your solution...
Thank you!
p.s. exported from 3dsMax
Im going to freak out if I lose one more shader that I'm working on by hitting backspace or some other fluke...
Can we please get the back lock like we did on the playground? Im about to freak out Im running out of time and this is the third time Ive lost progress just because I tried to delete a character...
goToFrame has no lasting effect on running animations.
It's effect on paused animations is lost on resume.
Example here:
http://babylonjs-playground.azurewebsites.net/#1MLKDF#2
The example sets up a running animation and three keybinds:
g -> goToFrame, s -> pause, r -> resume
Steps to reproduce the bug:
1)
Click on the animation to set the focus to the canvas, so keystrokes go to the action manager. (You can open the console to make sure the keystrokes are actually reaching the engine, there is a console.log for each key.)
2)
press "g" -> goToFrame is called, there is no effect
3)
press "s" -> the animation is paused
4)
press "g" -> goToFrame is called, the correct frame of the animation is displayed
5)
press "r" -> the animation is resumed, but it skips back to the frame where it was before goToFrame was called
My bug analysis (based on babylon.2.4.max.js, from github dist) :
In Animation.prototype.animate (within the engine) a local variable "currentFrame" is calculated without checking the this.currentFrame while the animation is running.
Line 26891 (babylon.2.4.max.js):
var currentFrame = returnValue ? from + ratio % range : to;
"this.currentFrame" goes completely ignored.
And after that in Animation.prototype._interpolate the new calculated value is assigned to this.currentFrame.
This means the "goToFrame"-Function never has any effect on running animations.
It also means, you can't pause or stop the animation and use goToFrame because when the animation starts again, currentFrame is recalculated.
If you specify texture customType = "BABYLON.HDRCubeTexture" and the other HDRCubeTexture properties... With .hdr as the
name... It will still try to use as regular CubeTexure and look for _px and _nx cube texture files:
I think babylon.texture.ts Parse function:
now is :
if (parsedTexture.isCube) {
return CubeTexture.Parse(parsedTexture, scene, rootUrl);
}
and should be something like:
if (parsedTexture.isCube) {
if (parsedTexture.customType === "BABYLON.HDRCubeTexture")
return HDRCubeTexture.Parse(parsedTexture, scene, rootUrl);
else
return CubeTexture.Parse(parsedTexture, scene, rootUrl);
}
OR IS THERE MORE to make HDRCubeTextures load from serialized .babylon file instead of only hand coding?
Might be a bug or it could my expectations (again). However the problem could be at the root of people having difficulties placing pivots.
If you rotate a parent them translate its child using LOCAL axes the child moves and positions as you would expect.
However if you rotate a parent then translate its child using WORLD or use position the child moves again in the direction of LOCAL axes but distances depend on the rotation of the parent.
The PG http://www.babylonjs-playground.com/#1J7LGZ shows the effect. The cylinders mark the positions of the child mesh (the pilot) as it and the parent (sphere) move. The red cylinder marks the expected final position following the final move of -2 in the direction of the world x axis. The pilot meshes show the actual positions.
Commenting out the pilot and sphere moves and uncommenting them in turn will show the sequence.
This is the version v2.4.0 and later of the problem.
"halloween.gltf" was successful in loading. However, "halloween_gltf.txt" was failed in loading.
BABYLON.SceneLoader.Load("./", "halloween_gltf.txt", engine, function (newScene) {
Version v2.3.0 previously did not have a problem.
I will sometimes post jsdo.it the JavaScript code. jsdo.it is a coding community for JavaScript users.
File name is changed to when registering the assets in jsdo.it.
BABYLON.SceneLoader.Load("/assets/0/2/I/8/", "02I89", engine, function (newScene) {
Because I want to post a sample of Babylon.js to jsdo.it in future, I hope that this problem is resolved.
When i do a engine.fullscreen, all the html i have for gun disappears... Is that by design or a bug...
If by design ... how am i supposed to show my game hud in full screen on a browser... not targeting mobile so soft wanna use canvas2d.. just pure html.
I've got a mesh as an avatar and clone it twice to get red and blue avatar "prototypes".
Then I call createInstance on on the red-avatar the new mesh is ok and visible.
Afterwards I call createInstance on the blue-avatar (ok), but this has the side-effect that the first instance disappears.
It seems that the first time when createInstance is called on a prototype it somehow impacts the other clones. It did work on 2.3.0.
http://www.babylonjs-playground.com/#1VVRMK#2
BTW: Excelent framework, I love it !!!
I edited to be more clear. When you use the left finger to control movement on iphone, if you happen to touch near the left edge (starting to drag to previous page in browser) the delta move value become high and you run very quickly at left which feels little strange and buggy.
It would be nice if there was a solution for this.
kind regards
Tomas
Hi, please check this playground: http://www.babylonjs-playground.com/#26DHSA
currently i always get the error "Cannot read property 'replace' of null" when i try to load a data url.
I checked the sources already. I think the handling of data urls inside Engine.createTexture () is broken somehow.
Hello world 
First of all, BIG THANKS to @Sebavan for its amazing PBR Material ! I'm taking a lot of fun playing with the differents features.
On monday, I enjoyed playing with microsurface parameter. It worked really fine until I added a bumpTexture.After diving into the code, I understood that microsurface is handled in two different ways :
Both ways seem to work fine when I don't use bumpTexture. But if I add a bumptexture to the PBR material, then only the first option works.
With the second option, we can see some flickering or pixelation, I don't know how to call that (left plane on the picture) :
Here is a basic PG showing the PBR material with all these parameters (this one should work !) : http://www.babylonjs-playground.com/#19SMAD#3
And here is the same PG, but I intentionally disabled the extension, to see how it works on devices which do not support the extension : http://www.babylonjs-playground.com/#19SMAD#4
It's less striking on the PG (don't look perpendicular to a face), that's why I posted the picture above.
Maybe it's not a bug and it's really impossible to have both microsurface and bumpmap working when the extension isn't available ? What do you think ?
Have a good day 
Hi,
I use new version of Blender(2.78a) and I have my model in it, so I tried to export it to .babylon file.
I got exporter file from Github just now and I have already move io_export_babylon.py to Blender's addons.
When I tried to export my model it got this error(in the picture that I have attached), but when I tried to export a normal cube, I could do it.
With the same model, I can do it with the babylon exporter that come with babylon v2.4 and previous version of Blender.
But for both new version of Blender and Babylon i can't.
Thank you in advance
Peace
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:
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
Hi,
Tools.CreateScreenshotUsingRenderTarget() returns a texture with a download error.
Tools.CreateScreenshot() returns an error with a black texture.
This produces if I leave the camera as is is loading the scene. If I look at the sky, it works for one, but the other always has a black texture.
When i reload the web page (Most times) when there has been a good amount of stuff in the scene like particles and lensFlares etc... When i reload the web page to reshow or start the scene... Or even i go to another page and come back to my page with the scene... First split second it show what was on the previous screen or sometime it show some 'garbled' collage of squares and what looks like old tv snow. What is that about... It there some kind of 'clear' or 'reset' that needs to be called in not to 'flash' what was left of the previous scene when showing the loader for the new scene.
Any info is really kool 
I just added highlightlayer to a scene with fire material already in it. Enabled stencil. While both effects still happen, 5 compile errors get logged.
Hi, in my current project i would like to use instances. I also need multiple viewports. The problem is that the instances and even the master mesh are only visible in the first viewport.
Here a simple playground with this issue: http://www.babylonjs-playground.com/#SSEQG#1
If you remove lines 23-26 the master sphere will be visible in both viewports.
Seems like Sprites do not work anymore on version 2.5 ( see Sprites tutorial playground showing empty scene for example : http://babylonjs-playground.azurewebsites.net/?8 )
Hey Delta... Did you get a chance to put the missing light.onDispose and camera.onDispose just like the mesh.onDispose has???
Highlight layer looks very strange in the PG's.
Looked ok 1 or 2 days ago.
Some resent update that was made wrong?