V-Ray is not running when file path contains spaces

[mtp_thomas]

When rendering from a blend file which contains spaces in it´s filepath I get the following debug error:

V-Ray/Blender: Recieve image error: V-Ray is not running

The same scene renders fine when I put it in a directory with no containing spaces.
I tried to fix this in the render.py file by putting the scenefile (line 1750) and imgfile (line 1762 + 1831) in double quotes. This is recommended by the command line docs from the V-Ray help page. But it still doesn´t work. Any ideas?

Thomas

[bdancer]

Re: V-Ray is not running when file path contains spaces

So the issue is only the message or you're missing some functionality?

[mtp_thomas]

Re: V-Ray is not running when file path contains spaces

I see, I forgot to tell what the problem is. V-ray doesn't render anything. All vrscene files where exported successfully but after that nothing happens just this error.

Thomas

[bdancer]

Re: V-Ray is not running when file path contains spaces

Fix in git, please check if it'll work for you.

[dddjef]

Re: V-Ray is not running when file path contains spaces

By the way, i got the same error with accents.

[mtp_thomas]

Re: V-Ray is not running when file path contains spaces

Sorry for the late reply. It still doesn´t work.

Further steps I took to track down the bug:
- First, I printed out the command that vb25 executes. I found nothing wrong. So I opened my Terminal and tried a very simple cmd-line rendering:

vray -sceneFile="/Volumes/Media/IES Profiles/test blend/vrscene/Lights_scene.vrscene"
[2013/Sep/23|15:13:20] error: Error parsing command line

- Escaping the spaces in the path (with \) was my next step:

vray -sceneFile=/Volumes/Media/IES\ Profiles/test\ blend/vrscene/Lights_scene.vrscene
[2013/Sep/23|15:13:30] error: Error parsing command line

As you can see I always get the "Error parsing command line" error. But when I render from a directory that does not contain spaces, everything renders fine.
So the next question is, can anyone with the latest V-Ray Standalone on a Mac confirm this problem? Because I´m not sure if this issue is related to the demo-version which I´m currently using/testing. If confirmed I strongly believe that this is a bug in V-Ray not in vb25.

Would someone please confirm?

Thomas