#41 Windows path name separator not recognized

open
nobody
None
5
2012-09-20
2009-10-18
Anonymous
No

I just tried aqsis 1.6.0 on Windows and found a possible bug with the windows path name separator ().

In my rib file I have:
MakeTexture "C:\Users\name\Documents\cases\pipe-box\rib\pipe-box-flow_texture0.tif" "C:\Users\name\Documents\cases\pipe-box\rib\pipe-box-flow_texture0.txt" "periodic" "periodic" "box" 1 1
FrameBegin 0
Display "C:\Users\name\Documents\cases\pipe-box\rib\pipe-box-flow.tif" "file" "rgb"
Display "+C:\Users\name\Documents\cases\pipe-box\rib\pipe-box-flow.tif" "framebuffer" "rgb"

Which causes the error:
10/17/2009 20:26:16 ERROR: (3, 2) Could not find file C:UsersnameDocume
ibpipe-box-flow_texture0.tif in RI searchpath texture
10/17/2009 20:26:17 ERROR: Invalid texture file - Could not find file "C:Usersna
ibpipe-box-flow_texture0.txt" in path: ".:C:/Program Files/Aqsis:"
ibpipe-box-flow.tif: Cannot open.umentscasespipe-box

All the other file paths in the file use the windows backslash. If I escape the backslash (\) or use the Unix forward slash (/) path separator then it works fine. Also parts of the error messages are truncated due to the size of the Command Prompt window.

Hope this helps.

Discussion

  • renderguy
    renderguy
    2009-10-28

    Thanks for the report.

    I believe a single backslash is treated as an escape character within the official RIB protocol, which is why either a forwardslash or double-backslash is necessary.

    For this reason I've moved the topic to our "Feature Requests" tracker instead, where it can be considered for a future Aqsis release.

     


Anonymous


Cancel   Add attachments