The ranchecking can take a long time due to your scene. When you press ‘Prepare Project’, RANCHecker does:

1. Save the original scene
2. Check your scene/assets/settings
3. Save the ranchecked scene
4. Open the log window of the project.
5. Pack the project (a zip containing your scene, assets and some files needed by the farm)
6. Load the original scene

Thus, if you scene takes time to save/load, it will considerably increase the preparation time. But:

• to lower the saving time, you can use xref files. The main scene will be lighter and will be saved quicker.
• by using the option ‘Do not reload’ in RANCHecker, the original scene (your scene) won’t be reloaded. Keep in mind that if the log contains an error you will have to reload the original scene yourself.

By default, RANCHecker uses the C drive in order to prepare the project. If your C drive is full, you can simply change the archive directory and the export directory to use another drive in the advanced settings of RANCHecker.

It's possible the your camera moves through an object (wall, pole, etc.).

If during the preparation by RANCHecker you get a message regarding .Net 3.5, you may need to do the following steps:

1. Right-click Start, and click Run
2. Type regedit.exe and click OK
3. Go to the following registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\WindowsUpdate\AU
4. In the right-pane, if the value named UseWUServer exists, set its data to 0
5. Exit the Registry Editor
6. Restart Windows
7. Right-click Start, and click Run
8. Type regedit.exe and click OK
9. Open CMD.exe and click OK
10. Exit CMD
11. Type optionalfeatures in CMD and press Enter (it will open the Windows Features window)
12. Activate the case named “.NET Framework 3.5” or something similar then press OK

You will notice this if there is a popup window during the project preparation.

RANCHecker is written in MAXScript so any crash will add an error log in the MAXScript Listener Window (Press F11 from your keyboard in 3dsmax to open it).

Please send us the full error log contained in this window in order to fix the crash. We can fix most problems within 1-3 hours during our working hours.