An application also has shortfalls. There's the problem of documentation as well as upgrades. Applications usually include a huge and often critic user manual. And applications will only receive the latest patches if the user notices and applies the fix. This is why the website is so appealing... it's easy.

default colors and transforms for babylon [image: 1670164849700-febb97cd-3c8c-425f-a7b4-703746fd89f4-image.png]

@z3dev got my first email from this user group and daily digest. That is great news that you got this working.

@jess-yan threejs has this ready-made somewhere(taking mouse point and returning meshes under it), I will most definitely post it on the forum here when I have this feature. This MAY require a shift away from how jscad works now, but hopefuly can be done with current jscad setup. The idea I have for now is to run a AST transform to inject line number information into the script and then run the modified script. This is something I am able to do, but I have other stuff in the pipeline before this

@z3dev hope you are well and refreshed, and ready to smash some PR's ... also a reminder that CadHub is waiting for your feedback to continue formally with jscad integration.

@platypii @danmarshall I think both of will be able use your preferred engine, and get specific benefits depending on a task at hand. Actually I am planning to split the necessary code so that it becomes rather easy to use any of the 3 engines I found to be interesting (regl, threejs, babylon) regl it is the current engine and is compact CON: lack proper WEBGL2 support and there are NO plans for supporting it in the future example for extremely compact page that has jscad script and render and all under 99kb is great example why regl is still very useful by @platypii https://paradr.one/ threejs and babylon larger but can be cut down for basic rendering (I managed to get 400k version of threejs that works with jscad) support wegl2 instancing can bring performance regl just will not ever be able with webgl1 are working actively on great next thing: WebGPU WebGPU might be the future for jscad if we can come up with ways to utilize compute shaders for performance having also these big engines as an option is good for when we want build fancy stuff and ake advantage of huge knowhow of their communities you have likely already seen my instancing demo: http://3d.hrg.hr/jscad/three/threejscad2.html?uri=model.logos.js in threejs you can track progress of my new prototype that is supposed to provide the mentioned integrations of all 3 engines I found interesting. https://github.com/jscad/OpenJSCAD.org/discussions/944 ... I will post a topic as soon I have any rendering integrated .. it is still in testing of some ui concepts phase