Installation for SketchUp 2017

Installation troubleshooting for SketchUp 2017 and IRender nXt

It's possible that the files that we install to let SketchUp 2017 find our plugin did not get installed into the proper location.

If you are having problems installing into SketchUp 2017, read the comments below.

By default, we install the ruby files in your ProgramData folder.

        C:\ProgramData\SketchUp\SketchUp 2017\SketchUp\Plugins

Note: On your machine, the "ProgramData" folder may be spelled differently, for your version of Windows.

Run the installation again, choosing the Reinstall choice, and notice where we are installing the SketchUp plugin files.

You should see SketchUp 2017 listed as one of the plugin folders that we will populate:

Install 2017.png

After reinstalling, here are some instructions to check the installation location:

C:\ProgramData\SketchUp\SketchUp 2017\SketchUp\Plugins

Look in that folder in Windows File Explorer, and make sure there is a folder called RPS_IRender_nXt and a file called RPS_IRender_nXt.rb:

Plugins 2017.png

Note: If you don't have the View option for showing known extensions un-checked, you will just see the file as being named "Rps_IRender_nXt".

You can change the Folder View Options, if you want to check the .rb extension:

Folder view options.jpg

If that file and folder are not there, then you will need to reinstall IRender nXt and make sure that the Ruby Plugins files get installed into your ProgramData folder.

After reinstalling, if IRender nXt still does not load, please do this:

Start SketchUp and open the SketchUp Ruby Console window:

Ruby console.png

Type, or use Copy and Paste (Note the single quote marks and the backwards slashes used here.):

load 'RPS_IRender_nxt.rb'

in the ruby console window, and then click Enter.

Then enter this line:

load 'RPS_IRender_nXt\RPS_IRender_nxt2.rb'

and also try entering the full path for the file to load:

load '\ProgramData\SketchUp\SketchUp 2017\SketchUp\Plugins\RPS_IRender_nXt\RPS_IRender_nXt2.rb'

Then copy all the text that appears in the Ruby Console and send it to us.

Hopefully all of that will give us a clue, if there is an error message or the files cannot be found to load.