GameMonetize Posted March 9, 2017 Share Posted March 9, 2017 Hello my friends!! I'm happy to announce that the Playground can now let you pick the version you want to use (latest or 2.5 so far). We did it because of the upcoming breaking changes introduced by 3.0 (I'm removing all functions or features marked as deprecated in previous versions) jerome, adam, aWeirdo and 8 others 11 Quote Link to comment Share on other sites More sharing options...
NasimiAsl Posted March 9, 2017 Share Posted March 9, 2017 thanks @Deltakosh Quote Link to comment Share on other sites More sharing options...
Dad72 Posted March 9, 2017 Share Posted March 9, 2017 Could we have a list of functions or features removed in 3.0 ? Should we now use MeshBuilder only to create primitive objects for exemple? What are the replacement functions to remove function? A list might be useful ways to put our project updated with aperture 3.0. I find this a very good thing to remove all its features deprecated. I guess the tutorials will be updated by removing all its features deprecated? gryff 1 Quote Link to comment Share on other sites More sharing options...
Vousk-prod. Posted March 9, 2017 Share Posted March 9, 2017 Excellent!! Quote Link to comment Share on other sites More sharing options...
gryff Posted March 9, 2017 Share Posted March 9, 2017 @Dad72 makes some good points. I ran into a "has been deprecated " this last week when I tried to change the scene gravity with BJS 2.5. cheers gryff Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted March 9, 2017 Author Share Posted March 9, 2017 Hello, you know that I'm the big knight of backward compatibility. The only affected code is the one related to Physics. We used to used a lot of functions on mesh about physics. Now they are on mesh.getPhysicImpostor(). See this commit for the list of affected functions: https://github.com/BabylonJS/Babylon.js/pull/1849/commits/582d21e43967e6740e01ca267aa546107e4bce6c Nothing else will be removed davrous 1 Quote Link to comment Share on other sites More sharing options...
Dad72 Posted March 9, 2017 Share Posted March 9, 2017 I thought you would withdraw for 3.0 BABYLON.Mesh also all and only keep BABYLON.BuilderMesh. This surely lighten the weight minimize file for 3.0. I think the version 3.0 of babylon and WebGL 2 (major change) should use what is to replace the new features. version 2.5 if you want to use the old functions. But then with the documentation I do not know how it would happen with such a change. These are just ideas. Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted March 9, 2017 Author Share Posted March 9, 2017 I do not want to remove functions which are just helpers. The change will be minor in size and I do not want to force users to pick MeshBuilder. I see it as an advanced feature on top of new Mesh Quote Link to comment Share on other sites More sharing options...
Dad72 Posted March 9, 2017 Share Posted March 9, 2017 Ah, ok. I understand GameMonetize 1 Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted March 13, 2017 Author Share Posted March 13, 2017 Hello! here is the official list of breaking changes: https://github.com/BabylonJS/Babylon.js/blob/master/dist/preview%20release/what's%20new.md#breaking-changes This is EXTREMELY exceptional. I agreed to do it only because we are heading to a major release (3.0) jerome, adam and Dad72 3 Quote Link to comment Share on other sites More sharing options...
JCPalmer Posted March 14, 2017 Share Posted March 14, 2017 I encourage the "turkey dump". Couple of questions from the what's New: You should double check the major changes to ensure very item is still going to be there I know that putting in Mesh.updateVerticesDirectly() was my doing. Now that mesh.updateVerticesData() is float32Array friendly, that is what I use. Unless, geometry.updateVerticiesDataDirectly() is still being used underneath, nuke it to. Doubt anybody even knows it is there. As far as the "redecorating" of physics calls, how are these going to represented in JSON? Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted March 14, 2017 Author Share Posted March 14, 2017 1. Did you find one that is wrong? I double checked but I can be wrong 2. I changed the what's new a bit to point users to UpdateVerticesData but I won't remove the geometry.updateVerticiesDataDirectly() as it provides support for offset. 3. No change in file format Quote Link to comment Share on other sites More sharing options...
JCPalmer Posted March 14, 2017 Share Posted March 14, 2017 Holocamera?? thought it my be a sore point to itemize Quote Link to comment Share on other sites More sharing options...
GameMonetize Posted March 14, 2017 Author Share Posted March 14, 2017 huhu:) Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.