I initially tested Crowdrender by adding my laptop as a remote node. Since my use case is typically the reverse (desktop as remote), I copied my blend file to my laptop but when I attempted to render, it never completed. After poking around a bit, I discovered that the local node lists my desktop GPUs (two 980s) as well as my laptop (1050 Ti):
The issue persists after deleting the Crowdrender directory in my user data folder (all settings were still loaded when I opened the file). This seems to indicate the settings are stored in each .blend file.
I propose the following changes:
- Enumerate compute devices on file load.
- Compare with list of saved compute devices.
- If a mismatch is found,
-- Revert to the default compute device (CPU).
-- Issue a warning notification under "this machine:" saying "WARNING: Compute device change detected! Please select new compute devices."
-- After user does so and presses OK, prompt the user to save the file to commit the changes.
I should have clarified that I copied the blend file to my laptop because I wanted to edit and initiate renders from it. So flushing the node will not work since that will only update the temp file on the desktop - the faulty settings are on the laptop's local copy.
For now I have simply deselected the non-present GPUs in the compute device list on my laptop, which allows my laptop to render.
Hi Scott,
Confirmed this, you're correct in your assertion that the settings are being stored in the blend file. We've opened an issue to solve this. It's going to make it into the next release, which will be 0.1.8.
In the mean time, if this is causing a problem for you, try removing that node, save your file, then add it, connect to it, and save it again. This should flush the blend file of the node and its settings and replace it with a fresh copy.