Jump to content


  • Content Count

  • Joined

  • Last visited

About jschwuch

  • Rank
    Advanced Member

Recent Profile Visitors

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

  1. I made a cabinet planner for a webshop. It's in german only but maybe you would like to take a look anyway There might still be some bugs, if you find one feel free to tell me. The first (room layout) and second (planning your cabinet) steps are done with orthographic cameras. The third step then uses an arc rotate camera and one can switch to a walkthrough mode and see what it would look like in your cabinet. I'm curious about your feedback. https://www.frank-schranksysteme.de/3d-schrankplaner/
  2. Hi @FelipeBaltazar, I really think we shouldn't modify the meshes when exporting the scene as I don't think people expect this to happen. Maybe we could add a flag if the function should bake the vertices or calculate the coordinates from worldMatrix defaulting to calculating the coordinates. I would be highly irritated if my meshes change when exporting a scene and it could cause major problems for people who build their meshes from scratch.
  3. Hi! The bake of bjs applies the transformations you set to the vertices. So you change the meshes. Additionally the baking seems to update the worldMatrix from the rotations and translations set on the mesh. But because i never set rotation and translation in my project but the world Matrix directly the baking doesn't work for me. If you're ok with changing your meshes you can instead use the baking. It just doesn't work out for me
  4. Thx! @FelipeBaltazar, this was a great point to start at. I changed some things because I'm abusing BJS when it comes to worldMatrices (I'm setting them directly) so this code exports as if transform where baked into the vertices. I also fixed the problems with the indices. Problem was, that obj doesn't start counting from 1 again when a new object begins, so we have to keep track of how many vertices we already exported. Here's my version: function exportOBJ(selectedItems) { var output = []; output.push("mtllib savedFile.mtl"); var v = 1; for (var j = 0; j < s
  5. But I could export all meshes of my scene to one obj file without merging them? That would be great for rendering my scenes in blender and giving the renders to customers.
  6. That's some new info for me too thx @Sebavan !
  7. @aWeirdo That's exactly what i wanted to say but i called it opacity as that's what I call it in my project Sorry for that and thx for your correction
  8. @Deltakosh is this documented anywhere? And can I export a whole scene to .obj or another format so I can get the my scene from babylon to Blender? This would be great!
  9. @Hersir you could maybe try copying the ._delayLoadingFunction over to the new mesh, but I don't know if that would create any new problems... I'll sniff around the source a bit later today... really wouldn't expect this to happen.
  10. Are you sure this only occurs when you are cloning the mesh? I'd have done the cloning exactly that way and don't see why it would cause this error
  11. My guess is, what you want can be done with MultiMaterial and submeshes. Here's a tutorial, hope it helps https://www.eternalcoding.com/?p=283
  12. @aWeirdo the left-handedness of BJS has nothing to do with the Y-Axis beeing "up". The left-handedness means, that bigger x values mean the object moves to the left not the right. You can have a right-handed coordinate system that has Y going up too. Y beeing up instead of Z is just another design decision one has to make besides the handedness Example for left and right handed coordinate systems from wikipedia: https://en.wikipedia.org/wiki/Cartesian_coordinate_system#/media/File:3D_Cartesian_Coodinate_Handedness.jpg
  13. Hi! Can you reproduce it in the playground? I just tested it and they are not visible in my test playground http://www.babylonjs-playground.com/#600LYK#1 If you can't reproduce it and need a workaround. You can set the meshes opacity visibility instead of the materials alpha, maybe that works as expected, ultimately you could set the meshs layermask to zero if it's materials alpha is zero. But those are of course options on a per mesh basis and not per material which may be a problem in your project I'll try my best to find the problem if you can reproduce it in the playground.
  14. Ok, thx for the info, than I'll consider changing my setup to using rendertargettextures.
  15. I suspect you tried to use the screenSpaceCanvas. It's expected that it is only visible on "one" eye as it's positioned relative to the screen, which is "split in half" for VR, and not to the scene. I prepared an example utilizing the worldSpaceCanvas that shows canvas2D elements on both eyes http://babylonjs-playground.com/index.html#NJBBC9
  • Create New...