Scan-and-Solve for Rhino

Simulate Early, Simulate Often... In Rhino


We've heard some early reports of problems loading SnSFusion on Windows 8.  Please standby as we try to understand the source and solution for the failure.

If you experienced the loading problem and discovered a solution, please share.

Note: a valid installation of SnS 2014 is required in order for SnSFusion to  load in Rhino.  If SnSFusion cannot find a valid license on the first attempt to load, you will see the following:

Clicking on [Details] shows this:

Clicking on [Details] shows this:  (We'll be updating the vendor information.)

You can see what type of license you have installed by opening the Scan&Solve license file in Notepad.  The license file may be found at:  C:/ProgramData/Scan&Solve/license.lic

The license file should look something like this:

snsnotforresale  may also be one of snsacademic, snscommercial, snsstudent, or snsevaluation.

Please let us know if you have any questions.


Views: 614

Reply to This

Replies to This Discussion

Hello Serhat,

Sorry for the confusion.  The system variable: %ProgramData% refers to C:/ProgramData/.  The license should be at: C:/ProgramData/Scan&Solve/license.lic.

If the license file is valid, there is the possibility of another problem of some sort.


Hello Serhat,

C:\Program Files\Scan&Solve\ is actually a different location than C:\ProgramData\Scan&Solve.

C:\ProgramData\* contains folders where programs can read and write their settings.

Anyway, it's also possible the problem lies somewhere else.



As it stands today (2/25/2015), SnSFusion is built against the following version of Rhino:

  Version 5 SR10 64-bit
  (5.10.41201.11145, 12/1/2014)

It is likely that SnSFusion will not work if you are running an earlier release of Rhino 5.


Hello Michael,

I have the same license file layout (in the folder C:/ProgramData/Scan&Solve) as you are showing in your example and I am using Win7 and Rhino 5 SR10 and Fusion still does not want to load. Please advise.




At the moment, this seems to actually be a problem with the configuration of the tools we use to build SnSFusion.  We are working on a solution.

Thank you for your patience.




© 2022   Created by Michael Freytag.   Powered by

Badges  |  Report an Issue  |  Terms of Service