engine VS webgl-framework

10 × PlayCanvas Personal plan for 12 months

For some reason that I cannot understand in my case the calculated shading normals are pixelated. Compared to playcanvas.com (probably a forward renderer), mine is like utter shit.

PlayCanvas has been using WordPress for 12 years now. Generally speaking, it's been fine. However, after much consideration, we have migrated away to Jekyll + GitHub Pages. I thought our experience might be of interest to other WordPress users (if only to confirm why you wouldn't consider switching): https://blog.playcanvas.com/moving-from-wordpress-to-jekyll-a-case-study/ Interested to hear peoples' thoughts...

It's just a cool tech demo that pushes CSS to its limits, but it's completely useless if you want to create usable 3d models. If you want to model in the browser, you can check out vectary, playcanvas, or spline

Hey, I do not have any experience with deepar.ai so I’m not super familiar with the process using that platform. In my opinion I’d probably recommend another platform to try and accomplish this. Since you mentioned that you have everything set up in a engine already (lens studio) I’d recommend you just use a webxr engine. In my experience the two best engines are https://playcanvas.com and https://wonderlandengine.com. I think that going down this route may be the best option for your needs. I am willing to help out or do some of the work for you just pm me if you have any questions or anything.

If you want the closest thing to Unity that's focused on browser-based (mobile and otherwise) development, try Playcanvas: https://playcanvas.com/

Release Notes: https://github.com/playcanvas/engine/releases/tag/v1.62.0 Clustered Arealights Demo: https://playcanvas.com/demos/arealights/

After the terrain we draw a sky hemisphere object with the basic DiffuseShader, and then draw 11 cloud sprites. Then we draw a sun sprite. These transparent objects are rendered without writing to the depth buffer. Clouds and sun have trimmed geometries for less overdraw. You can read about this optimized sprites technique here. We decided not to use soft particles for clouds because scene size allowed us to place them so that they don’t intersect with other geometries while still partially occluding some peaks. Not using soft particles is beneficial for performance because they require additional render pass to render scene depth.

Historically, the web demo was created first — it was used as a prototyping playground to compose a scene and to fine-tune shaders. Also, this really helps in sharing work between a team of two people without necessity to learn Android Studio for both. And when everything was polished and looked good enough, an Android app was created quite fast based on the web demo code. Porting code to Android is a quite straightforward and easy process because our WebGL framework has the same method signatures as the framework used in Android apps.