@Zachary-Keim good to hear. Guess it was a temporary issue 🙂

@gilboonet that is excellent, it may be possible later on to integrate that one with jscad or at least take your experience for ideas how to improve 2D use-cases in jscad.

@z3dev Yes, add Memory would be great, I felt the difference when I changed from 4 Gb to 8. For the moment I'm simply starting to use my laptop as main computer.

@jess-yan Hello, the point selection is made with an external tool, Openscad Simple Polygon Editor. I modified it so that I could use it along with OpenJSCAD. But it was with a very old version and with v2 I don't see how to do the same.

Update: This was fixed after I upgrade the chrome to version 90.
Thanks.

Finally I made it fit into one file using obj2jscad.js. It can be seen here.

@z3dev Thank you for your suggestions. What I did was only translating the code so it run on V2 regardless of placement. I'll try to implement helper function for cube and cuboid, then it should work.

We have been posting to this thread.

https://openjscad.nodebb.com/topic/196/a-collection-of-jscad-projects-on-github

You can find some really interesting projects by following the Used By links on the right side of the Github project.

Yup. The old fixTJunctions() function is not present in V2. There's a pull request to add this functionality back, which is under review now.

@z3dev Hello, I didn't open an issue because it's V1, but I will do it so we could keep track of the solution I used. Yesterday I tried my little html5 app on my android tablet with Firefox and it works perfectly
0_1579956207318_android1s.jpg
even the PDF creation part
0_1579956263650_android2s.jpg

Thank you. I will try something similar, it just needs to add a parameter to choose a design number, if the table of random values doesn't have values for this number they are randomly feeded, else they are used for the rendering. Such "mechanism" could be handy for designs using both random values and more than one viewing mode.

The simple solutions are always the best. Taking a super thin slice is a great idea, and maybe even the best.

The core library will be for core functions, as we expect others (like you) to contribute some really nice high level functionality, such as slicing. If we get the core library rock solid then anything is possible.

Projections on to arbitrary planes is on the wish list, but not there yet.

Thanks for the awesome posts!

@kaosat-dev At first I tried to use a 10K triangles model but as it didn't render I downscaled to 5K, 3K, 2K then 1K. And after, I made another model with 2x more slices that this script was unable to render even with a 1K model, so I changed the script to make it render chunks of slices, and it was ok. I suppose it could work with higher resolutions models.
0_1564473765365_Capture d’écran de 2019-07-30 10-02-14.png

It seems to me that the ‘Code’ tab in the upper right exposes the code in BlocksCAD. I was able to select and copy the code.