It will open slowly because Grasshopper recalculates everything when it opens a file. My laptop takes nearly three minutes .
Sorry, just seen the picture in your following post - if Q1 relates to 1 in the picture, then 1 is another data dam, but showing that there is data waiting to be let through. But this only needs to be opened if you are using the smoothing option. Use of the smoothing option is optional and is controlled by the Filter component. If you toggle the Boolean Switch in the middle of your picture on then the smoothing branch will operate, if you leave it toggled off then it is bypassed.
The Data dams at 2, 3 and 4 all show that there is nothing to be let through, so you don’t need to do anything with them at that moment. Only open a dam (by clicking on it) when you have changed something upstream and it shows the Triangle. Only open one at a time, working downstream. (Of course if you have a PC with lots more power than my laptop you may not need all the dams.
2 & 3: these dams are there because the quad remesh takes a long time and while it runs grasshopper becomes unresponsive. That is really annoying when you are trying to adjust a slider! Blocking the data allows you to adjust all the parameters without that difficulty.
4: This dam is less important when you have reduced the target mesh significantly with the Quad Remesh, as theSubDMesh component runs quickly, but if the mesh is large then it will take longer. It is useful to check the QuadRemesh (QRMesh) output before creating the SubD as often you will find a combination of parameters leaves gaps, or merges too many branches together.
The dams are just there as gateways - the output from a dam is the same as the output of the component feeding it, so the dam doesn’t need to display in Rhino.
SnappingGecko is a plugin that helps you line up your components on the canvas. If you like things neat and tidy then its for you, if you don’t care then you don’t need it (although other viewers might appreciate you using it).
This .gh file had the input surface and point data internalised by vikthor, so it will work with an empty Rhino file, or with any of your model files. If you want to transfer the internalised data to a rhino file you can simply bake it out. Internalising is advised when you post in the forum, because then you don’t have to have the Rhino file as well.