jerome

Members
  • Content count

    3,443
  • Joined

  • Last visited

  • Days Won

    82

jerome last won the day on January 14

jerome had the most liked content!

About jerome

  • Rank
    Advanced Member
  • Birthday 03/17/1970

Contact Methods

  • Website URL
    http://jerome.bousquie.fr/BJS/demos/

Profile Information

  • Gender
    Male
  • Location
    France / Rodez

Recent Profile Visitors

4,444 profile views
  1. https://www.babylonjs-playground.com/#EP87PX#1
  2. new mesh type : dashed lines

    nope... the vertex number, so the dashes number, can't be changed, only set at different positions
  3. OfficeGames project

    it's linux with a mysql db
  4. the most efficient way to check collisions with a dynamic terrain or any BJS Ground objects (although they aren't the same) keeps to use the methods getHeightAtCoordinates(x, z) and getNormalAtCoordinates(x, z) or getHeithFromMap(x, z) and getNormalFromMap(x, z) depending on the object class https://www.babylonjs-playground.com/#J6FMJ#7 https://github.com/BabylonJS/Extensions/blob/master/DynamicTerrain/documentation/dynamicTerrainExamples.md It's hundreds of times fastest.
  5. BabylonJS Dynamic Terrain Doc examples not working

    didn't notice there was a ribbon also in the scene ... (btw, the dynamic terrain itself is ribbon-based)
  6. OfficeGames project

    to fire : left clik or keyboard SHIFT key
  7. BabylonJS Dynamic Terrain Doc examples not working

    well, this is strange because this lag didn't exist initially and the extension wasn't modified for ages... I have no idea why it behaves that way now. As you say, mabe something changed with the arcrotate camera behavior since This demo still runs and also became a bit laggy on my computer compared to the original release : http://jerome.bousquie.fr/BJS/demos/flightSim.html especially in chrome what used to be the fastest and the smoothest browser of my Linux. Since the v63 release, I noticed that things started to went wrong. No idea whether it's the reason though. I will have to investigate this and profile accurately.
  8. OfficeGames project

    Well, I refactored an old project to get at least (almost) one first game to publish, even if it's not finished yet. Some other less combative will come. It's just the first step to provide something already running else the procrastination will always win and nothing will arise out from my coding attempts The target platforms are explained in the site. The process to publish the games is not explained though but is simple : once a game is playable even not finished, it's published. Then it's improved and worked according to the user feedback if any... continuous improvement and fixing, you know. [EDIT] Johnk helped me to write a correct english text, I'll publish it next monday.
  9. OfficeGames project

    With pleasure
  10. OfficeGames announcement

    Announcement (and shameless auto-promotion) to a new project :
  11. OfficeGames project

    Hi people, I'm glad to introduce you to my new project : OfficeGames. http://officegames.eu Well ... 3D games for office computers (not only, though). As said in the text, there's only one game for now and it's not even finished. I need your feedback and ideas to improve it and get it to the right direction. So please let your opinions, comments, criticisms, wishes, whatever in this thread. I won't answer everyone but will read them all for sure. Have fun [EDIT] FYI, my best score ever is 10200.
  12. ok got it something wrong in the call to computeNormals() in this very case fix in progress [EDIT] PRed
  13. Seems weird indeed ... I'll check this as it seems (probably) related to the particle visibility. Currently my work PC is quite broken, I'll check this asap. [EDIT] anyway, sounds weird because the updateParticleVertex() feature hadn't been modified for ages