What kind of things can be scaled up with no bugs? I’m learning some these clean processes, clean files things. Such as retracing curves into a pretty clean closed curve after making the mangled up hybred freaks. Also the problem with triangles on trimmed surface edges, etc that come from commands that never had real trim command in them. Only the rhino processing that somehow involves a trim. That problem and dupborders as I go will definitely help. ANyways, I was just wondering about say scaling up curves, and how scaling up curves that would be hard to create again clean might fare as far as bugs/bad objects? I suppose someone could scale up their curves, then go trace with only NEAR osnap on, and get a fairly exact clean version.
hi pascal, the sphere was created with the sphere command from the menu (Solid > Sphere > (First one from the menu, not sure about the name at this point), no crazy stuff happened as far as I know. I’ve encountered this only with spheres several times today during workshops with 2nd year architecture students. Perhaps it was scaled a bit, (factor 10 max?)
That is odd- if you can turn on CheckNewObjects for a while, while working as you have been, you will be warned when this kind of thing turns up- it would be good to know what causes it- I see that the sphere is located quite far from the origin, that may have something to do with it.
This problem has returned in Rhino 6. See attached file please. Has something to do with the origin, but on my test file, the distances are not outrageous, unless I misunderstand Rhino’s limitations.
Hi all, I was having problems using the gumball on a sphere created from native sphere command. It had a radius of 2996.78, some arbitrary size I arrived at through modelling in place. I created a new sphere at radious 3000 and everything worked fine.
A bad object / invalid surface will not be transformed. Other than that, I have no clue why Rhino would produce an invalid surface with the sphere command.
I set my Nvidia Quadro card to “workstation app - dynamic streaming” and the problem seemed to disappear. There is some information on discourse about this, but I can’t locate an ‘official’ or recommended setting for our cards.Please inform if there is such a setting.
Windows 10 (10.0.19045 SR0.0) or greater (Physical RAM: 32Gb)
Computer platform: DESKTOP
Standard graphics configuration.
Primary display and OpenGL: NVIDIA Quadro RTX 4000 (NVidia) Memory: 8GB, Driver date: 3-28-2023 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 528.89
> Accelerated graphics device with 4 adapter port(s)
- Windows Main Display attached to adapter port #0
- Secondary monitor attached to adapter port #1
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Graphics level being used: OpenGL 4.6 (primary GPU’s maximum)
Anti-alias mode: 8x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: High
Vendor Name: NVIDIA Corporation
Render version: 4.6
Shading Language: 4.60 NVIDIA
Driver Date: 3-28-2023
Driver Version: 31.0.15.2889
Maximum Texture size: 32768 x 32768
Z-Buffer depth: 24 bits
Maximum Viewport size: 32768 x 32768
Total Video Memory: 8 GB
Rhino plugins that do not ship with Rhino
C:\Users\abelov\AppData\Local\Programs\Enscape\Bin64\Enscape.Rhino7.Plugin.dll “Enscape.Rhino7.Plugin” 0.0.22334.1442
C:\ProgramData\McNeel\Rhinoceros\7.0\Plug-ins\Datasmith Rhino Exporter (d1fdc795-b334-4933-b680-088119cdc6bb)\DatasmithRhino7.rhp “Datasmith Exporter” 5.0.2.0