There were a few problems with using C4D on windows:
The adaptor runtime client was failing to find pywin32 when attempting to connect: ModuleNotFoundError: No module named 'win32file'
There were some misdirection in the stack trace when failing to load pywin32. It would complain with NameError: name 'main' is not defined. Did you mean: 'min'? since we were catching the above error
The adaptor was trying to load the posix interface to communicate
What was the solution? (How)
Documented the requirement to install pywin32 into C4D's python environment.
Removed the try/except around loading the runtime client to make it easier to debug
Swapped HTTPClientInterface to the OS-agnostic ClientInterface to work on both Linux and Windows.
Resolves https://github.com/aws-deadline/deadline-cloud-for-cinema-4d/issues/40
What was the problem/requirement? (What/Why)
There were a few problems with using C4D on windows:
ModuleNotFoundError: No module named 'win32file'
NameError: name 'main' is not defined. Did you mean: 'min'?
since we were catching the above errorWhat was the solution? (How)
HTTPClientInterface
to the OS-agnosticClientInterface
to work on both Linux and Windows.What is the impact of this change?
You can render on Windows!
How was this change tested?
The adaptor was also able to successfully render a job
Was this change documented?
Yup!
Is this a breaking change?
Nope!
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.