The Global ARCHICAD Community

Stay informed. Get help. Share your knowledge.

Import/Export to other CAD/BIM formats (DWG/DXF, IFC, SketchUp, 3DS etc.), spreadsheets, databases etc.

Moderators: Karl Ottenstein, LaszloNagy, ejrolon, Barry Kelly, gkmethy

User avatar
By Barry Kelly
Mats_Knutsson wrote:
Thu Nov 08, 2018 8:41 am
Sherlock Kelly, you're right.
At least you know what it is now.
I just seem to be in investigation mode at the moment.
Trying to set up for version 22 and all I seem to be doing is finding problems that really shouldn't be there.
You seen one of the others (copying hotlink modules).
But there are more when you go looking.
I wish I had picked these up in Beta testing.

By Mats_Knutsson
We have lot's of issues ...unfortunately there is no time for investigating seriously. 110% busy every day with internal support :P
User avatar
By dkovacs
Hello Everyone,

Found the problem!

It looks like the issue is that if the name of the surface has a non-english character in it. Apparently when we generate the MTL file and the OBJ file, they can use different conversions for these types of characters, and so there won't be a match when the OBJ file tries to load the texture through the MTL file. The reason I couldn't reproduce this at first is that I was testing in the INT version, and everything is written with english characters in that version.

I have added the issue to our list and we will fix it as soon as we can. Once it is fixed, you will find it in the update release note as fix #257744.

In the meantime, please avoid using non-english characters in surface names if you plan to export to OBJ format, or if that is not possible, then export through another format (e.g. FBX, TM, SKP, etc.).

By Mats_Knutsson
dkovacs wrote:
Thu Jan 10, 2019 1:36 pm
Hello Everyone,

non-english character.

Well...with Brexit and Trump...we can use Swedish as universal language...Å Ä Ö are very handy in Swedish... Or we could use that was a bad idea...