Vorion

Members
  • Content Count

    31
  • Joined

  • Last visited

About Vorion

  • Rank
    Advanced Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Vorion

    Combine Babylon.js with Pixi.js

    Ok, thank you, I will switch to your solution then
  2. Vorion

    Combine Babylon.js with Pixi.js

    Is this the best solution to combine pixi.js and babylon.js? I'm currently also using pixi.js for my game gui, but as I haven't found any examples, I just set up a second canvas for pixi.js. Which one would be better, performance-wise? My approach looks like this: https://jsfiddle.net/yapv3Lfc/1/
  3. Ah ok, thank you, didn't know that. I think it would a good idea, to add a note to the documentation (http://doc.babylonjs.com/how_to/optimizing_your_scene#instrumentation) about it.
  4. Hi, I've got a strange problem with the drawCallsCounter from SceneInstrumentation, it only outpus 0 as the current (and min/max) value. Here is a playground example: https://www.babylonjs-playground.com/indexStable.html#0QHUKY#3 The strange thing about it is, if I output the drawCallsCounter object in the console, and click and the getter for current, it displays the correct value. This also seems to happen for activeEvaluationTime and ParticlesRenderTime. It worked before, so I don't know exactly whats happening here, maybe it's on my end. Switching from the latest preview release (3.3.0-beta3) to 3.2.0 stable doesn't change anything. Another problem I encountered, is the gpu frame time, which also only shows 0, but the console output of the object doesn't show anything different, and the gpu frame time has been this way for quite a while, so I don't think this is related to the other problem. Did I do something wrong here? Thanks
  5. Thanks for the reply. Just saw that it was changed in this commit about a month ago https://github.com/BabylonJS/Babylon.js/commit/56b22596f0649336fed094df319f9187c244a1f1#diff-d65f22b9bdc1d52cee1b465fc49604c0
  6. Hi, I wanted to try the latest preview release, but my IDE says that "Image" does not exist on type "typeof GUI". By looking at the available types from the GUI, the IDE suggests GUIImage, so I replaced everything with GUIImage. Now I get a console error in my browser, saying "TypeError: BABYLON.GUI.GUIImage is not a constructor". I get the same error on the playground, which btw also suggests GUIImage. By looking at the source code, I think this was intentional, but it isn't mentioned in the what's new file for the preview release. You can see the error on the playground https://www.babylonjs-playground.com/#K60448#22 Is this a bug, or do I need to change something else to get it working? Thanks.
  7. Vorion

    Latest 3.2 Alpha B and C PBR Errors

    Have you tried the latest nightly version? There have been some pbr bug related commits 2 hours ago, so maybe it's already been fixed on nightly build (https://github.com/BabylonJS/Babylon.js/commits/master).
  8. I think he meant mesh.freezeWorldMatrix(). The function freeze() is only used for materials, as far as I know. You can find some info here: https://doc.babylonjs.com/how_to/optimizing_your_scene
  9. Has this been fixed? I saw your commit about adding support for stop and die on gpuparticles, but it doesn't seem to be working. The targetStopDuration just stops the particles and does not reset them as the normal particlesystem variant does. Also by manually calling the reset() function, the gpu particle get visually removed, but still seems to use a draw call each until I restart the game. I'm using the current nightly version you've just published.
  10. Thank you both for your input. I've created a github issue as suggested: https://github.com/BabylonJS/Babylon.js/issues/3897
  11. Hi, do you plan on adding button masks for gui buttons, so that we can have buttons that are only clickable on the desired areas? Here's an example: http://www.babylonjs-playground.com/#WWBIKZ The button image is a circle, but the clickable area is actually a rectangle. Buttons can also have other different shapes, like cut off edges. I guess the best way would be to add some kind of button mask, maybe an optional second image that contains information about the clickable/hover area (like white color => clickable, alpha=0 => gets ignored) Thanks.
  12. Hi, I switched to the new GPUParticleSystem, and I noticed, that the particles freeze on the screen in their last state, when the targeStopDuration was reached. This doesn't happen when using the normal ParticleSystem. Is this a bug, or intended behaviour? Here's a playground example: http://www.babylonjs-playground.com/#7H1RN9#2 (left box is normal ParticleSystem, right box is GPUParticleSystem, both using identical settings) Thanks
  13. Hi, is it possible to link a gui control, like the one in this example https://www.babylonjs-playground.com/#XCPP9Y#20, to a TransformNode, instead of a mesh? Thanks