OctaneRender® for ArchiCAD - build 1.37 [OBSOLETE]

[kxl]

Happens in every new scene. problem is that the error refers to ArchiCAD 16, but I've only installed ArchiCAD 17. And i can't use any material saved by me in the 1.20 version.

[face_off]

Have you followed the instructions in the manual regarding extracting the images from the ArchiCAD library? http://render.otoy.com/manuals/ArchiCAD/?page_id=169?

Paul

[kxl]

Yes, I tried to extract the textures and the same problem plus the materials stored in version 1.20 doesn't work any more.

[face_off]

Yes, I tried to extract the textures and the same problem plus the materials stored in version 1.20 doesn't work any more.

This looks like an ArchiCAD library issue.

The error messages are indicating that the texturemap C:\Program Files\GRAPHISOFT\ArchiCAD 16\ArchiCAD Library 16\[Img] Textures 16\Wall Finishes 16\Bricks 16\Brick Running Alpha.png is missing. Is that file on your hard disk? Are you able to provide a screenshot of the C:\Program Files\GRAPHISOFT\ArchiCAD 16\ArchiCAD Library 16\[Img] Textures 16\Wall Finishes 16\Bricks 16\ folder pls? You can see my ArchiCAD install below has this file.

Based on the error - I would guess that the above file is not there on your PC, so it is not possible for the Octane plugin to file that file.

The situation would have existed in the old plugin (1.20) too, so it's odd you weren't getting these error then. Has anything else changed?

Also, can you post a screenshot of your File->Libraries and Objects->Library Manager screen with the '+' items expanded.

Thanks

Paul

[kxl]

do i have to reinstall archicad 16 so that the plug in can find the missing texture?

[face_off]

do i have to reinstall archicad 16 so that the plug in can find the missing texture?

I think what is happening here is that when running the plugin on AC16, you've saved all material as a "Default" and those defaults are referencing the AC16 folder and not the new AC17 folder. So you can:

a) Reinstall AC16 to get these texturemap files back on your hard disk (do this option if you have a highly customized set of Octane material defaults that you do not want to loose), OR

b) Delete all your default Octane materials (delete all files in C:\Users\[username[\AppData\Local\OctaneRender for ArchiCAD\Defaults)

I need to add a function into the plugin to automatically change all the AC16 references to AC17.

Paul

[BfPuVAK]

octane 1.27 140128 193600.log

(2.23 KiB) Downloaded 375 times

Hi Paul!

I've remarked that the 1.27-plugin seems to reset nearly all textures to a default size - the mapping
from Archicad is igored.
Doesn't matter if it's a new started project or an old one which worked perfectly with 1.20-plugin up to now.

Here some screenshots...
AC17 + 1.20, all OK:



AC17 + 1.27, when opening viewport error, like "kxl":



AC17 + 1.27, final image with wrong mapping:



Here the cuda-log-file:

octane 1.27 140128 193600.log

(2.23 KiB) Downloaded 375 times

The texture paths were not changed of course, also no changes were made before opening the 1.27-viewport (=just as it was in 1.20).

Hope you have a solution soon

Thaks in advance & greetings,
Artur

[face_off]

Hi Artur - good to hear from you again.

I've remarked that the 1.27-plugin seems to reset nearly all textures to a default size - the mapping
from Archicad is igored.
Doesn't matter if it's a new started project or an old one which worked perfectly with 1.20-plugin up to now.

If you reconvert a material from ArchiCAD, the scale will be picked up. But because the scale pin has been replaced with the transform, if you use a material which has a 'Default" Octane node setup (stored in C:\Users\[username[\AppData\Local\OctaneRender for ArchiCAD\Defaults) then that default will be loaded with the old scale, which will not be used, so you will loose your scale in that situation. So your options are:

a) Reconvert the materials from ArchiCAD material to Octane materials where the scale is wrong, OR
b) delete the "default" for the materials which have incorrect scales, so they automatically convert from ArchiCAD when next used, OR
c) if you have many many materials in this situation where is it not viable to reconvert them, I can see if the plugin can automatically convert the scale pin to a scale transform when loading a "default" Octane node setup for a material.

The texture paths were not changed of course, also no changes were made before opening the 1.27-viewport (=just as it was in 1.20).

I suspect these files were missing in Octane 1.20, however Octane 1.20 was not reporting these missing texturemaps so you never knew about the problem. If you check the log, you can see you have Octane materials (probably "defaults" in C:\Users\[username[\AppData\Local\OctaneRender for ArchiCAD\Defaults) which are referencing ArchiCAD 16 texturemaps, and you are on AC17 and probably no longer have AC16 installed.

So either reconvert those materials, or reload the AC17 image map into the "RGB Image Node".

As stated above, I will look at an automated way of migrating your "Default" Octane materials from one ArchiCAD version to another. This will be needed when AC18 is released.

Paul

[BfPuVAK]

Hi Paul

option
a) is not working, the scale is getting even worse (I've noticed that the tiling is (sometimes!) about 12,5 times too small)
b) sorry, don't know what you mean by > delete the "default" <
c) would by perfect - I have generally more then 50 textures per project!

I don't use Archicad 16 at all, but all the images listened in the log-file ARE in my active loaded library. Of course the path
displayed in the log is wrong (=old) of course.
The first file for exemple can be found by Archicad/Octane here: C:\BIBLIOTHEKEN 17\[TImg] Texturen 17\Verputz 17\Putz_Alpha.png.

Perhaps the general reconverting of the materials (option "c)" ) would solve this updating(?)-problem too?

By the way: I just started a completely new Archicad17-project; the mapping is also completely wrong here...




Greetings,
Artur

[face_off]

By the way: I just started a completely new Archicad17-project; the mapping is also completely wrong here...

Yes - you are right - it is the inverse of what it should be. I will fix this. I am also adding conversion of the ArchiCAD material rotation.

Paul