Metasequoia BBS

[6765] Mr. / Marc Wilmet

Done [Bug report, ] Response

Hi,

I just downloaded the latest version 4.5.7 (64-bit).
I'm using the licensed standard version for Windows.

When I import a mesh in Wavefront OBJ format that contains textures/Materials, these ones are not properly loaded because the drive's letters are not included in the file's name.

Example : Material3994, the Reference is : /textures_MD/Silk01.jpg
But it would be :
E:/textures_MD/Silk01.jpg

I consider that Metasequoia 4 is one of the most user-friendly application for modeling. Its interface is superb.
Thank you very much.

:-)

2016-11-20 06:39

[6766] Re: Mr. / Administrator

Response

>Hi,
>
>I just downloaded the latest version 4.5.7 (64-bit).
>I'm using the licensed standard version for Windows.
>
>When I import a mesh in Wavefront OBJ format that contains textures/Materials, these ones are not properly loaded because the drive's letters are not included in the file's name.
>
>Example : Material3994, the Reference is : /textures_MD/Silk01.jpg
>But it would be :
>E:/textures_MD/Silk01.jpg

This is a correct behavior on the Windows and UNIX. The leading slash means that the file is placed under the root folder.
The software used to export wrote a wrong path. If you want to load the texture file from a relative path, the path must be written like as texture_MD/Silk01.jpg or ./texture_MD/Silk01.jpg in the .obj file.

2016-11-21 14:00

[6767] Re: Mr. / Marc Wilmet

Response

>>Hi,
>>
>>I just downloaded the latest version 4.5.7 (64-bit).
>>I'm using the licensed standard version for Windows.
>>
>>When I import a mesh in Wavefront OBJ format that contains textures/Materials, these ones are not properly loaded because the drive's letters are not included in the file's name.
>>
>>Example : Material3994, the Reference is : /textures_MD/Silk01.jpg
>>But it would be :
>>E:/textures_MD/Silk01.jpg
>
>This is a correct behavior on the Windows and UNIX. The leading slash means that the file is placed under the root folder.
>The software used to export wrote a wrong path. If you want to load the texture file from a relative path, the path must be written like as texture_MD/Silk01.jpg or ./texture_MD/Silk01.jpg in the .obj file.

2016-11-22 05:20

[6768] Re: Mr. / Marc Wilmet

Response

>>>Hi,
>>>
>>>I just downloaded the latest version 4.5.7 (64-bit).
>>>I'm using the licensed standard version for Windows.
>>>
>>>When I import a mesh in Wavefront OBJ format that contains textures/Materials, these ones are not properly loaded because the drive's letters are not included in the file's name.
>>>
>>>Example : Material3994, the Reference is : /textures_MD/Silk01.jpg
>>>But it would be :
>>>E:/textures_MD/Silk01.jpg
>>
>>This is a correct behavior on the Windows and UNIX. The leading slash means that the file is placed under the root folder.
>>The software used to export wrote a wrong path. If you want to load the texture file from a relative path, the path must be written like as texture_MD/Silk01.jpg or ./texture_MD/Silk01.jpg in the .obj file.

Hi,

I'm sorry for the duplicated post. Please could you delete it? (I had some difficulties to understand how this BBS Editor is working.)

Thank you for your fast reply.

2016-11-22 05:38

[6769] Re: Mr. / Marc Wilmet

Response

Again, I'm sorry.

In my previous comment, please read this :

In the Material's Reference, I find this : /textures_MD/silk01.jpg

2016-11-22 05:44

[6770] My apologies, there is no bug. / M W

Response

You're absolutely right ! There is no bug.
My sincere apologies for my mistake.

The solution was to simply mention the drive letter as absolute path in the configuration.

2016-11-28 06:30

[6771] Re: My apologies, there is no bug. / Administrator

Response

Thanks for your report. Please continue to feel free to ask here if you have any questions or problems.

2016-11-29 12:12