Hi Clement - Windows 10 here. I’ll find someone running 7.
-Pascal
Hi Pascal, what happens if you enter a comma as decimal seperator ? I can repeat that timeout problem here using that instead of a dot.
Edit, that’s not it, with a dot it also happens…
_
c.
Hi Clement - OK - thanks, we’re trying to reproduce it here… JB has a Windows 7 running…
@clement
Hi Clement - can please you run SystemInfo and paste the results here? Just in case there is some combination of system/build/video etc that we need to duplicate and check. So far Windows 7 on VMware (Slow) is a little laggy but not at all like what you’re showing in your clip.
thanks,
-Pascal
Hi Pascal, here it is: SystemInfo.txt (1.7 KB)
_
c.
Thanks! Nothing leaps out at me here except that we do see problems with Radeons - it just does not strike me as something video card related but I am only guessing… I’ll check with the developer.
@clement - I’m not making any noticeable progress on this one - basically no one here can reproduce the problem so far. I’m still checking with the developer in case he has a clue as to what else we can try.
-Pascal
Thanks Pascal,
if i compare the command with Rhino 5, it is unusable as i have no control when calculations are performed. Today i tried it again on a smaller mesh. The settings from my last V6 session where used so i needed to change all fields in the dialog. It does not remember the checkbox for hair which i always need to turn off. In Rhino 5 i see a timeout too, when i click on the “Apply” button, but that is OK as i can control it and only have to wait once. In V6 everything takes much longer, because it constantly tries to update. I wonder what is the purpose of having a realtime preview on every setting change in that command ? Why was the Apply button removed ?
_
c.
Yes, please.
Hi Charles - are you also seeing delays or ‘not-reposonding’ Rhino when making changes in this panel? Are you also running on Windows 7?
thanks,
-Pascal
Yes, delays.
And no, Windows 10.
Hi David - thanks for the detailed test - can you tell if Worksession is relevant ? Here, an ‘attached’ mesh with 25 million points and two surfaces just… works. I do have a fairly hefty machine, I’ll try my dinky laptop at the other extreme…
-Pascal
Thank you Pascal. I can try with a Win10 machine on the weekend to double check.
_
c.
@pascal I had deleted my post before your reply appeared because I’m not certain whether some other variables such as other open software affected the results, and also not sure about the timings…
I don’t think Worksession is significant. I use it to have the background data such as meshes from photogrammetry in separate files from the modeling. I also usually use a considerably faster desktop, and have the files on an internal HDD. The files I loaded were from a project which is a couple of years old but were available.
I’ll try to run a more definitive test tomorrow.
Hi David - got it, thanks for testing…
-Pascal
@pascal - Test results
I systematically tested the V6 Beta and V5 versions of PointDeviation using a file with 697,476 points and a surface. The points are close to the surface but most are not on the surface.
V5 takes about 8 seconds to execute PointDeviation after selecting the points and the surface. The results are updated in about 2 seconds after changing the distance parameters for colors and clicking on “Apply”. Version 5 SR14 64-bit
(5.14.522.8390, 5/22/2017)
V6 Beta takes about 50 seconds to execute PointDeviation after selecting the points and the surface (8X longer than V5 for the same task). Changing one of the distance parameters results in a wait of another 50 seconds.
BETA
(6.0.17339.11131, 12/5/2017)
System Info from V6 Beta:
Rhino 6 SR0 2017-12-5 (Rhino WIP, 6.0.17339.11131, Git hash:master @ 01128be76fcfa21764b3cd10786b227fe05fc7bb)
Windows 10.0 SR0.0 or greater (Physical RAM: 12Gb)
GeForce GTX 860M/PCIe/SSE2 (OpenGL ver:4.5.0 NVIDIA 369.09)
OpenGL Settings
Safe mode: Off
Use accelerated hardware modes: On
Redraw scene when viewports are exposed: On
Anti-alias mode: 4x
Mip Map Filtering: Linear
Anisotropic Filtering Mode: Height
Vendor Name: NVIDIA Corporation
Render version: 4.5
Shading Language: 4.50 NVIDIA
Driver Date: NA
Driver Version: NA
Maximum Texture size: 16384 x 16384
Z-Buffer depth: 24 bits
Maximum Viewport size: 16384 x 16384
Total Video Memory: 2 GB
C:\Program Files\Rhino WIP\Plug-ins\Commands.rhp “Commands”
C:\Program Files\Rhino WIP\Plug-ins\rdk.rhp “Renderer Development Kit”
C:\Program Files\Rhino WIP\Plug-ins\RhinoBonusTools.rhp “Rhino Bonus Tools”
C:\Program Files\Rhino WIP\Plug-ins\RhinoRender.rhp “Rhino Render”
C:\Program Files\Rhino WIP\Plug-ins\rdk_etoui.rhp “RDK_EtoUI”
C:\Program Files\Rhino WIP\Plug-ins\rdk_ui.rhp “Renderer Development Kit UI”
C:\Program Files\Rhino WIP\Plug-ins\NamedSnapshots.rhp “Snapshots”
C:\Program Files\Rhino WIP\Plug-ins\RhinoCycles.rhp “RhinoCycles”
C:\Program Files\Rhino WIP\Plug-ins\Toolbars\Toolbars.rhp “Toolbars”
C:\Program Files\Rhino WIP\Plug-ins\3dxrhino.rhp “3Dconnexion 3D Mouse”
C:\Program Files\Rhino WIP\Plug-ins\Displacement.rhp “Displacement”
C:\Program Files\Rhino WIP\Plug-ins\Calc.rhp “Calc”
Hi David - thanks, that’s ugly for sure… We’ve added an ‘Apply’ button, here, and that works but I’m not convinced that we’re getting at the real problem. Still poking at it here.
-Pascal
Pascal - attached is the file I used for testing: PtDevTest20PC.3dm (16.0 MB)
The initial difference in speed is before the “Apply” button is relevant.
Hi David - thanks, testing it now…
@davidcockey, @clement, @Charles - I’ve attached a Commands.rhp plug-in. If you could, please give this a try as follows:
- Download the rhp.
- Right click on the saved file and choose Properties - if it is blocked, click on Unblock and then Apply. (https://wiki.mcneel.com/rhino/unblockplugin )
- Rename the Commands.rhp plug-in that is in the Rhino installation > Plug-ins folder.
- Copy the new plug-in into this folder.
(You may need to provide need admin confirmation for steps 3 and 4) - Start Rhino and drag and drop the new plug-in onto it to load it up.
- Try the same point deviation tests that were giving you head-aches before and let us know if there is any change…
Commands.rhp (7.3 MB)
thanks,
-Pascal
Hi Pascal,
thank you for the update. Feels much better and i can change the text field values without interruption if i turn OFF the “automatic apply changed” checkbox. Once i click the Apply button it takes a while (20 seconds for testing a mesh with 759775 vertices against a surface with 32x32 control points) but that is ok. I have not compared the time to V5 yet as David did. If i cange some values and then use Apply again, it is faster, 8 seconds.
btw. After clicking the Apply button the dialog vanished. If i hover over a toolbar tab it comes up again. When i used the End button, then closed the dialog and run it again, it did not vanish after clicking the Apply button.
_
c.