[Bf-committers] Re: Win32 paths

Alfredo de Greef bf-committers@blender.org
Fri, 30 Jan 2004 11:01:56 -0800 (PST)

> Actually, I spoke too soon.  Removing the trailing >
slash does fix the 
> problem with finding Python scripts, but it does
> not fix the YFexport 
> problem.  Console output is:
>    Starting scene conversion.
>    Scene conversion done.
>    Could not open input file
>    Could not execute yafray. Is it in path?

Whatever it is, it is not the slash, that was fixed
some time ago, have to look into this. You would be
the first windows user who'd actually want to set the
path yourself though, all the complaints we got about
this when it was first released...
Anyway, the 'Could not execute yafray. Is it in path?'
message, that is only a generic message that doesn't
always have to do with what actually happened, yafray
was executed, that is were the 'Could not open input
file' message comes from, it also prints that message
when you stop yafray with ctrl-c. So the problem must
be in the filename passed to yafray. It is not spaces
either, that was solved as well.


Do you Yahoo!?
Yahoo! SiteBuilder - Free web site building tool. Try it!