Deltakosh

Road to Babylon.js v3.0

9 posts in this topic

Hello all, next version will certainly be 2.6 but it could also be 3.0 depending on my progress regarding WebGL2.0 support

I'll use this thread to track progress.

Done so far:

adam, getzel, Vousk-prod. and 7 others like this

Share this post


Link to post
Share on other sites

Great news, but I think there is no need to rush, since all browsers will (as usual) take time to fully and natively support WebGL 2.0, probably still a full year... But I can be wrong, that would be awesome ! How is Edge roadmap on that ?

Share this post


Link to post
Share on other sites

Sounds awsome!

I would totaly love to see Multiple Render Targets, wich is part of WebGL 2. Making modern deferred Lighting possible!

Keep up the good work!

Share this post


Link to post
Share on other sites

I remember when my parents bough me my first PC, i was about 12, i started to buy me some game magazines to play demos, the hole day and the hole night (my mother was worried ) but i guess i was not much different from any other child. So after two months some Graphic Card Company releases something new (hardware-accelerated T&L or - can't recall it right)  and every developer just run into it, so i can't play half of the demos no more, with my nearly brand new PC , i was angry.

From my experience the game industry always pushing the limits.

So babylonjs supports now 2 of 88 WegGL2 functions, right ? :)

Share this post


Link to post
Share on other sites

@Deltakosh Some of the guys here works for or in big companies, they get money  for sitting the hole day in a nice office and looking into the screen. And if i look at some playgrounds here, nobody ever reads the doc. Most of them still writing the hole road of code to get e.g Mouseposition, Userinteraction etc.  The big change of 2.4 to 2.5 was onPointer is deprecated. I mean if someone request a features it will stays in the history of the engine a long time.

So maybe it would make scene

  • to write a doc how to

instead of putting it right away into to community.js babylonjs. And make this guys sweating a bit more. I understand if someone works on a game in his free time, (this is challenging ) but not if someone is just to lazy to read some tutorials out their and work for a high payed project.  

Kill the capitalism, back to the roots. 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.