Tom_P
August 24, 2023, 5:43pm
1
Rhino Mac current WIP and also Rh7 create different / wrong results compared to the Windows Version
using the following setting on both systems
mac fails to create enough cvs.
the refit 0.001 value is lost
G1 Edge is not correct
find attached file to reproduce ?
sweep2_mac_bug_rh7.3dm (5.9 MB)
there are similar quite old topics
Hi everyone.
I found a Sweep2 error (bug maybe) in my Rhino course when I followed teacher’s steps with my mac.
The problem was that sweep2 could not make a surface to blend 2 mirror surfaces with keeping G2,even i chose G2 both in the rail curve option.
I am sured I have built correct cross line. Because sweep2 created a perfect, symmetrical surface when I opened the same file in rhino 5 for windows.
you can compare the surface in Layer 2.
the version of my rhino for mac OS is 2014-4-21(5…
thanks for having a look at this.
also see here - other feedback to current WIP on Mac
Today I used Rhino WIP V8 first time in Classroom…
some stuff is really nice - but still some work to do.
great to have a more unique UI with Windows and Mac Os X
Stuff that needs to be fixed
Version 8 WIP (8.0.23234.12306, 2023-08-22)
Expires October 6, 2023 on a Intel Macbook 2019
Mac os X 13.5.1, AMD Radeon Pro 5500M 8 GB
(Rhino) Notes are not show in Finder - is there some Mac os x setting I am missing ?
working with synchronised Monitor via Airplay, Performace of Graphic is miserabl…
kind regards - tom
Tom_P
August 24, 2023, 5:51pm
3
wow that was fast - thanks
but see the difference in the results as well !!
CV-Count and zebra is not the same.
pascal
(Pascal Golay)
August 24, 2023, 5:55pm
4
Yeah, that is because the curves are not refit - 0.00 = ignore. 0.01 does add points, just not as many as .001 would if it worked.
Am I seeing clearly or is there more to it?
RH-76552 Sweep2: refit tolerance limited
-Pascal
Tom_P
August 24, 2023, 7:01pm
5
ok - maybe the problem really is, that the input 0.001 becomes a 0.00 - and therefor refit is ignored.
(not only a hidden / not displayed 0.001)
I did a Scale up by x10
then do the sweep2 with 0.01 tolerance
then scale down the new surface by 0.1
the result is more or less like expected.
so hopefully it is really a interface / dialog issue and not some stuff deeply hidden in the sweep2 algorithm…
thanks
kind regards -tom