ExtendSrf: New behavior override?

Rhino Rhino for Windows
1

Hi I’ve noticed an update to ExtendSrf, which has been harshing my vibe lately because ExtendSrf is a big part of my workflow. It there a way to override this new auto-linear-extend thing and make it behave as in V6?

image
image1105×188 10.7 KB

It seems to do this whenever a side edge is trimmed, and it fails where V6 would surely have succeeded.

To illustrate, lets say I want to extend the yellow surface. (The upper edge is a trimmed edge with no funkiness):

image
image1219×820 52.8 KB

Here’s what I get in V7:

image
image1165×858 48.5 KB

Here’s what I want, and what I was accustomed to getting in V6 (I get this in V7 after I untrim the surface):

image
image1207×828 45.6 KB

Clearly the workaround is to untrim and re-trim every surface that I want to extend, but it’s inconvenient.

Thx.

2

Hello - can you post a file with that surface please?

-Pascal

3

ExtendSrf.3dm (12.3 KB)

4

Thanks - so far, I do not get the behavior you report… if Type=Smooth and Merge=Yes, I get either end of this surface extended with no extra points.

image
image834×359 28.1 KB

-Pascal

5

Weird. I get this every time now.

6

Can you please run SystemInfo and post the results? maybe there was a fix since your build.

-Pascal

7

Rhino 7 SR4 2021-3-19 (Rhino 7, 7.4.21078.01001, Git hash:master @ a432d22ab7f0f7b53d157d578278070c8bf6eff4)
License type: Commercial, build 2021-03-19
License details: Cloud Zoo

Windows 10.0.19041 SR0.0 or greater (Physical RAM: 64Gb)

Computer platform: DESKTOP

Standard graphics configuration.
Primary display and OpenGL: NVIDIA GeForce RTX 3070 (NVidia) Memory: 8GB, Driver date: 3-10-2021 (M-D-Y). OpenGL Ver: 4.6.0 NVIDIA 461.92
> 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

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-10-2021
Driver Version: 27.21.14.6192
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:\Program Files\Bongo 2.0 (64-bit)\Rhino6\Bongo.20.rhp “Bongo 2.0”
C:\Program Files\Bongo 2.0 (64-bit)\BongoUI.20.v60.rhp “BongoUI20v60”
C:\Users\armat\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\NVIDIADenoiser\0.4.0\NVIDIADenoiser.Windows.rhp “NVIDIADenoiser.Windows” 0.4.0.0
C:\Users\armat\AppData\Roaming\McNeel\Rhinoceros\packages\7.0\rhinopbrmaterial\1.1.4+v6.16\RhinoPbrMaterial.rhp “RhinoPbrMaterial” 1.1.2.0

Rhino plugins that ship with Rhino
C:\Program Files\Rhino 7\Plug-ins\SolidTools.rhp “SolidTools”
C:\Program Files\Rhino 7\Plug-ins\Commands.rhp “Commands” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\WebBrowser.rhp “WebBrowser”
C:\Program Files\Rhino 7\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino 7\Plug-ins\RhinoScript.rhp “RhinoScript”
C:\Program Files\Rhino 7\Plug-ins\AnimationTools.rhp “AnimationTools”
C:\Program Files\Rhino 7\Plug-ins\IdleProcessor.rhp “IdleProcessor”
C:\Program Files\Rhino 7\Plug-ins\RhinoRenderCycles.rhp “Rhino Render” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\RhinoRender.rhp “Legacy Rhino Render”
C:\Program Files\Rhino 7\Plug-ins\rdk_etoui.rhp “RDK_EtoUI” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino 7\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino 7\Plug-ins\Alerter.rhp “Alerter”
C:\Program Files\Rhino 7\Plug-ins\RhinoCycles.rhp “RhinoCycles” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\Toolbars\Toolbars.rhp “Toolbars” 7.4.21078.1001
C:\Program Files\Rhino 7\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino 7\Plug-ins\Displacement.rhp “Displacement”

8

@hanscad - there has indeed been a fix since 7.4 - I will check the 7.5 RC to see if the fix is available there.

Yes - the fix should be in 7.5 - you can get the fixed (7.5) version by changing the ‘Update frequency’ in Options > Updates and Statistics page to ‘Service release candidate’

-Pascal

1 Like
9

Excellent, thanks Pascal. Have I told you recently how much I appreciate you?

2 Likes
10

Aw shucks…

-Pascal

11

Well I just got my Thank You badge, and I’m the sheriff round here now.

1 Like