RaananW

Members
  • Content count

    1,834
  • Joined

  • Last visited

  • Days Won

    47

RaananW last won the day on November 16

RaananW had the most liked content!

About RaananW

  • Rank
    retired time traveler
  • Birthday 07/04/1981

Contact Methods

  • Website URL
    https://blog.raananweber.com
  • Twitter
    RaananW
  • Skype
    raananw

Profile Information

  • Gender
    Male
  • Location
    Berlin

Recent Profile Visitors

4,340 profile views
  1. The new Babylon Viewer

    Firefox fullscreen was fixed. As I always love to say - gotta love web "standards"!
  2. moveWithCollisions

    There are a lot of unexpected characters in the code you pasted, for example: "left.position.x -= 100;\\r\\n\\r\\n\\r\\n/**\\r\\n * \u001f\u0010qÜb¶\\r\\n" Maybe we should have not allowed to save this PG in the first place, but this PG will not work. Having said that - if anyone else experiences this behavior, it might be on our side and needs to be fixed. @Lary, can you try again while making sure it runs before you save? the pasted code should have never worked in the first place.
  3. The new Babylon Viewer

    Everything is available in the repo, we tend to keep everything as open-source as possible
  4. The new Babylon Viewer

    Got it, will be fixed soon. Thanks!
  5. The new Babylon Viewer

    Hi boys and girls, I don't know if you noticed, but the repository has a new directory called "Viewer" : https://github.com/BabylonJS/Babylon.js/tree/master/Viewer The viewer is a simple way of displaying a model without the need of JavaScript at all. It (obviously) uses babylon, and can be customized to your needs using HTML tags and HTML attributes. The only two important lines in your page would be: <babylon model="https://playground.babylonjs.com/scenes/Rabbit.babylon"></babylon> <script src="https://viewer.babylonjs.com/viewer.min.js"></script> Which will result in this: https://viewer.babylonjs.com/basicexample You can read about how to use it and how to customize it here - http://doc.babylonjs.com/extensions/the_babylon_viewer It is currently in a very early stage. The (public) project can be found here - https://github.com/BabylonJS/Babylon.js/projects/6 , including future plans. I am in the process of simplifying the development, build, and deploy process and it will soon be available on NPM as well, if anyone wishes to embed it using webpack/imports/require/whatever
  6. This is because the file is restricted and not public. It returns 403 (Unauthorized). Not a bug, moving to Q&A
  7. How did we get to browser incompatibility using a single canvas element beats me Quaternion is always your friend, I am happy it is resolved this way.
  8. best practice for sharing instances

    Hi Tomer, I am not sure a class with only static members make sense. The singleton pattern makes sense when you really need a single instance, but you need an instance per scene. Not only there, when you init the camera again, the old instance is simply gone... Use babylon's native functions (like you suggested), set IDs to each object (or use .uniqueId), and I think it'll be better. But this is really up to you, and the way you see your application.
  9. That's interesting It seems to me like a failed calculation of the view matrix that happens, for some reason, in firefox. It was fixed in 3.1, but I can't find the actually lines that were added / changed to cause this. If anyone else knows, you might be able to get it fixed with 3.0.7, but I would simply recommend using 3.1.0-beta , as it is stable enough and will soon be released.
  10. Playground Error

    Ok, should be working now. Please refresh
  11. Playground Error

    The playground works for me on chrome. There seems to be a problem with firefox, I will look into that
  12. Collision Issue with bounce

    Wow, that's a quote from 2015! I guess it was fixed back then. Probably by me if DK said so... You can increase the scene's gravity to avoid the "flying" behavior. You could force the ellipsoid of the object to be bigger just to not walk on top of it. You could run a beforeRender loop, forcing the person to always have a static y position (no idea if this would really work).
  13. A better link http://doc.babylonjs.com/babylon101/cameras#followcamera
  14. Hi, maybe the follow camera can be of help? http://doc.babylonjs.com/features/cameras#follow-camera
  15. Picking with boundingBox broken?

    I remember I once implemented such a function, which had a single problem - you don't get the intersected point in the pickingInfo, as it is impossible to calculate. I will try finding it and add it as a suggestion for a quickPick function.