strange F5 behavior
Fixed. Thanks so much for the rapid response!
Jon
On 6/28/2023 12:15 AM, Revar Desmera wrote:
Texture face reversal bug has just been fixed. Please download the
latest BOSL2 code.
- Revar
On Jun 27, 2023, at 7:12 PM, jon jon@jonbondy.com wrote:
I now have some ... simple? ... code that behaves erratically. I've
tried clearing the cache without making any headway. I am using the
most recent snapshot and BOSL2. At one point I thought it was the
render(), which I removed and achieved success, but the next time it
failed, so that was just random.
Perhaps the rough internal surface is sometimes generated so that the
difference() works and sometimes it fails. I do not know whether
the "rough" texture is computed differently each time, or is static;
the former could explain what I am seeing.
Any other thoughts? I have no idea whether this is reproducible or not
Jon
// when I F6 this code, sometimes I get
// - a solid bar with a triangular cross section
// - a hollow bar with a triangular cross section and a "rough"
interior finish
// - the error message "ERROR: The given mesh is not closed! Unable
to convert to CGAL_Nef_Polyhedron."
include <BOSL2/std.scad>
inches = 25.4;
eps = 0.01;
th = 2;
sl = 7 * inches;
sw = 1.8 * inches;
// render()
difference() {
tex = texture("rough", roughness = 0.5);
linear_sweep(regular_ngon(n=3, d = sw + 4*th), h=sl,
convexity = 10);
translate([0, 0, -1])
// Pick a smooth interior (next line) or a rough interior (line after
that) by commenting one line out
// linear_sweep(regular_ngon(n=3, d =
sw), h=sl + 2, tex_size=[10,10], style="min_edge",
convexity = 10);
linear_sweep(regular_ngon(n=3, d = sw), texture=tex,
h=sl + 2, tex_size=[10,10], style="min_edge", convexity = 10);
}
On 6/27/2023 10:02 PM, Jordan Brown wrote:
Something has changed with respect to how stuff is displayed on the
console. The output used to be displayed incrementally, as it
happened, and now it is all displayed on completion.
for (k=[1:10]) {
for (i=[1:1000], j=[1:1000]) {}
echo(k);
}
On 2021.01, that displays the numbers 1 through 10, about two per
second, for a total of 6 seconds.
On 2023.06.06, it pauses for about 10 seconds and displays all of
it, for a reported total of 10 seconds.
The slowdown is also of interest.
OpenSCAD mailing list
To unsubscribe send an email to discuss-leave@lists.openscad.org
OpenSCAD mailing list
To unsubscribe send an email todiscuss-leave@lists.openscad.org
In addition, it used to be that, while F5 was "blocking" and OpenSCAD
was frozen during F5, when using F6 OpenSCAD still responded to things
like saving a file. Now the hourglass appears during all of F6, which
is a reduction in utility, at least for me.
Jon
On 6/27/2023 10:02 PM, Jordan Brown wrote:
Something has changed with respect to how stuff is displayed on the
console. The output used to be displayed incrementally, as it
happened, and now it is all displayed on completion.
for (k=[1:10]) {
for (i=[1:1000], j=[1:1000]) {}
echo(k);
}
On 2021.01, that displays the numbers 1 through 10, about two per
second, for a total of 6 seconds.
On 2023.06.06, it pauses for about 10 seconds and displays all of it,
for a reported total of 10 seconds.
The slowdown is also of interest.