Client Troubleshooting
First of all, if you experience any problems with the client please file a bug report. We will try to fix the problem as fast as possible!
Known Problems
- Client Launch: On some installations you may have to reboot if your client can not connect to the virtual machine. If it still fails check the VM directory for a stale lock directories and files. Delete all *.lck directories and files in C:\Documents and Settings\All Users\Application Data\vSwarm Client under XP or c:\ProgramData?\vSwarm Client under Vista and Win7.
- Blender: Using post processing (e. g. motion blur) in a job shows 99% progress after the first render pass is completed
- Blender: Clients that do not have enough power to process a work unit within the given timelimit (60 mins), have not enough RAM for a job or a too slow internet connection to download or upload the job data within 15 mins are not excluded from this job. Instead the work units processed by these clients are marked as "error" and must be restarted manually. After restarting hopefully another client grabs the failed frames.
- LuxRender: LuxRender reaches 99% progress fast but then stays there and finally the job times out after 60 minutes. No known fix at the moment. This is seems to be a LuxRender Bug, we are checking how to work around or fix it. This is connected to haltspp parameter.
Other Software
You may get problems if you have another VMware virtualization product than VMware player already installed. The client may not work then. If you have an old version of VMware player installed be aware that the client updates this install to a newer version. In all cases with VMware player installed the client changes the network configuration (the IP address) of the virtual host-only network adapter.
