M
mikeonenine@web.de
Sat, May 31, 2025 1:51 PM
Manually adjusting the viewport to the size one wants is very fiddly. Could this not be done by setting parameters such as $vpw (width) and $vph (height)?
That would be useful for producing a series of pngs or gifs that would all need to be the same size.
Manually adjusting the viewport to the size one wants is very fiddly. Could this not be done by setting parameters such as $vpw (width) and $vph (height)?
That would be useful for producing a series of pngs or gifs that would all need to be the same size.
TP
Torsten Paul
Sat, May 31, 2025 1:54 PM
On 31.05.25 15:51, Caddiy via Discuss wrote:
Manually adjusting the viewport to the size one wants is very fiddly.
Could this not be done by setting parameters such as $vpw (width) and
$vph (height)?
On 31.05.25 15:51, Caddiy via Discuss wrote:
> Manually adjusting the viewport to the size one wants is very fiddly.
> Could this not be done by setting parameters such as $vpw (width) and
> $vph (height)?
Window->Viewport-Control
M
mikeonenine@web.de
Sat, May 31, 2025 4:45 PM
On 31.05.25 15:51, Caddiy via Discuss wrote:
Manually adjusting the viewport to the size one wants is very fiddly.
Could this not be done by setting parameters such as $vpw (width) and
$vph (height)?
Window->Viewport-Control: do you mean the line at the bottom left of the screen?
I do use $vpf in conjunction with perspective sometimes, but that doesn’t control the format (relationship of width to height).
The easiest thing to do at present is to open the search function in the editor and open the viewport as far as it will go, which gives it a width of 1005. I can juggle with the height by opening the console and raising or lowering the top. But that is a not-very-elegant workaround. Getting a square (height = width) viewport is a little more tricky.
It would be nice to be able to specify the format in the code together with the other $vp’s.
Torsten Paul wrote:
> On 31.05.25 15:51, Caddiy via Discuss wrote:
>
> > Manually adjusting the viewport to the size one wants is very fiddly.
> > Could this not be done by setting parameters such as $vpw (width) and
> > $vph (height)?
>
> Window->Viewport-Control
Window->Viewport-Control: do you mean the line at the bottom left of the screen?
I do use $vpf in conjunction with perspective sometimes, but that doesn’t control the format (relationship of width to height).
The easiest thing to do at present is to open the search function in the editor and open the viewport as far as it will go, which gives it a width of 1005. I can juggle with the height by opening the console and raising or lowering the top. But that is a not-very-elegant workaround. Getting a square (height = width) viewport is a little more tricky.
It would be nice to be able to specify the format in the code together with the other $vp’s.
TP
Torsten Paul
Sat, May 31, 2025 4:50 PM
On 31.05.25 18:45, Caddiy via Discuss wrote:
Window->Viewport-Control: do you mean the line at the bottom left of the
screen?
I mean the menu entry. This will give a window that allows to
control various things about the viewport including a fixed
aspect ratio and/or a specific size.
Controlling the viewport size is tricky and this feature
seems to sometimes cause a lockup. I believe this does not
happen anymore after the first preview (F5).
(This is not available in the 2021.01 release version)
ciao,
Torsten.
On 31.05.25 18:45, Caddiy via Discuss wrote:
> Window->Viewport-Control: do you mean the line at the bottom left of the
> screen?
I mean the menu entry. This will give a window that allows to
control various things about the viewport including a fixed
aspect ratio and/or a specific size.
Controlling the viewport size is tricky and this feature
seems to sometimes cause a lockup. I believe this does not
happen anymore after the first preview (F5).
(This is not available in the 2021.01 release version)
ciao,
Torsten.
M
mikeonenine@web.de
Sat, May 31, 2025 5:10 PM
(This is not available in the 2021.01 release version)
Ah! That’s the version I’m using. Looks like I need an update.
Torsten Paul wrote:
> (This is not available in the 2021.01 release version)
Ah! That’s the version I’m using. Looks like I need an update.
M
mikeonenine@web.de
Sat, May 31, 2025 5:22 PM
(This is not available in the 2021.01 release version)
That’s the only version on the OpenSCAD homepage.
Which version does what I want, where can I get it and would it be a good idea to change?
Torsten Paul wrote:
> (This is not available in the 2021.01 release version)
That’s the only version on the OpenSCAD homepage.
Which version does what I want, where can I get it and would it be a good idea to change?
TP
Torsten Paul
Sat, May 31, 2025 5:26 PM
On 31.05.25 19:22, Caddiy via Discuss wrote:
Which version does what I want, where can I get it and would it be a
good idea to change?
Nightly build: https://openscad.org/downloads.html#snapshots
You can have both release and nightly build installed in parallel.
For maximum compatibility and sharing, you can still use the
release version. For accessing the latest features, use the
nightly build (I'd also suggest to go into preferences section
Advanced->3D Rendering and change "Backend" to "Manifold").
ciao,
Torsten.
On 31.05.25 19:22, Caddiy via Discuss wrote:
> Which version does what I want, where can I get it and would it be a
> good idea to change?
Nightly build: https://openscad.org/downloads.html#snapshots
You can have both release and nightly build installed in parallel.
For maximum compatibility and sharing, you can still use the
release version. For accessing the latest features, use the
nightly build (I'd also suggest to go into preferences section
Advanced->3D Rendering and change "Backend" to "Manifold").
ciao,
Torsten.
M
mikeonenine@web.de
Sat, May 31, 2025 6:41 PM
On 31.05.25 19:22, Caddiy via Discuss wrote:
Which version does what I want, where can I get it and would it be a
good idea to change?
Nightly build: https://openscad.org/downloads.html#snapshots
You can have both release and nightly build installed in parallel.
For maximum compatibility and sharing, you can still use the
release version. For accessing the latest features, use the
nightly build (I'd also suggest to go into preferences section
Advanced->3D Rendering and change "Backend" to "Manifold").
ciao,
Torsten.
Interesting, need to check out all the new features, but preview F5 is much slower than with the release.
My laptop has:
Windows 10
Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz
4.00 GB RAM
119 GB SSD SAMSUNG MZ7TE128HMGR-000L1
Intel(R) HD Graphics 4600 (113 MB)
64-Bit system, x64-based processor
Should be adequate?
Torsten Paul wrote:
> On 31.05.25 19:22, Caddiy via Discuss wrote:
>
> > Which version does what I want, where can I get it and would it be a
> > good idea to change?
>
> Nightly build: https://openscad.org/downloads.html#snapshots
>
> You can have both release and nightly build installed in parallel.
>
> For maximum compatibility and sharing, you can still use the
> release version. For accessing the latest features, use the
> nightly build (I'd also suggest to go into preferences section
> Advanced->3D Rendering and change "Backend" to "Manifold").
>
> ciao,
> Torsten.
Interesting, need to check out all the new features, but preview F5 is much slower than with the release.
My laptop has:
`Windows 10`
`Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz`
`4.00 GB RAM `
`119 GB SSD SAMSUNG MZ7TE128HMGR-000L1`
`Intel(R) HD Graphics 4600 (113 MB)`
`64-Bit system, x64-based processor`
Should be adequate?
TP
Torsten Paul
Sat, May 31, 2025 7:27 PM
On 31.05.25 20:41, Caddiy via Discuss wrote:
Interesting, need to check out all the new features, but preview
F5 is much slower than with the release.
That's surprising, there were a number of changes that generally
have improved performance.
With slower, do you mean from F5 to the model showing up the
first time, for does that apply to interacting with the viewport
to rotate/translate...?
If you have a reasonable small model you could share, you could
post that in an issue on github. But such cases are often quite
difficult to pin down, so there might not be a good answer.
|Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz|
|4.00 GB RAM |
Should be adequate?
Should be totally fine if you keep resolutions a bit on the
lower side. The new Manifold engine is also a bit easier on
memory. A bit more memory might be needed for larger designs
(but depending very much on how it's implemented).
ciao,
Torsten.
On 31.05.25 20:41, Caddiy via Discuss wrote:
> Interesting, need to check out all the new features, but preview
> F5 is much slower than with the release.
That's surprising, there were a number of changes that generally
have improved performance.
With slower, do you mean from F5 to the model showing up the
first time, for does that apply to interacting with the viewport
to rotate/translate...?
If you have a reasonable small model you could share, you could
post that in an issue on github. But such cases are often quite
difficult to pin down, so there might not be a good answer.
> |Intel(R) Core(TM) i5-4300M CPU @ 2.60GHz|
> |4.00 GB RAM |
> Should be adequate?
Should be totally fine if you keep resolutions a bit on the
lower side. The new Manifold engine is also a bit easier on
memory. A bit more memory might be needed for larger designs
(but depending very much on how it's implemented).
ciao,
Torsten.
M
mikeonenine@web.de
Sat, May 31, 2025 8:44 PM
That's surprising, there were a number of changes that generally
have improved performance.
With slower, do you mean from F5 to the model showing up the
first time, for does that apply to interacting with the viewport
to rotate/translate...?
It takes 27 sec. for the model to appear from F5 - this delay also applies to animation, which is a problem.
But rotate/translate works nicely, smoother than with the release.
The code has about 600 lines, depending on what you count, for what that’s worth. Elementary stuff compared to other codes I have seen, no include BOSL2 or similar, which can slow. Editing out the render on one part does’nt help. Like most of my stuff, the error list in the console for this code is quite long, but that doesn’t slow the old release.
A simple cube previews instantaneously.
Torsten Paul wrote:
> That's surprising, there were a number of changes that generally
> have improved performance.
>
> With slower, do you mean from F5 to the model showing up the
> first time, for does that apply to interacting with the viewport
> to rotate/translate...?
It takes 27 sec. for the model to appear from F5 - this delay also applies to animation, which is a problem.
But rotate/translate works nicely, smoother than with the release.
The code has about 600 lines, depending on what you count, for what that’s worth. Elementary stuff compared to other codes I have seen, no include BOSL2 or similar, which can slow. Editing out the render on one part does’nt help. Like most of my stuff, the error list in the console for this code is quite long, but that doesn’t slow the old release.
A simple cube previews instantaneously.
