OTOY Forums

face_off wrote:

Change texture scale in one command instead of many wouldbe great. Is that possible?

Hi Jeroen - this has been requested previously, and I've done some preliminary work on it, but it is not straightforward, but can be done. So yes, it is planned for the future.

Paul

I have refreshed the installers at the top of this thread with:

2.2.0.7
- Compiled against Octane 2.02
- Fixed issue where deleting a rendertarget from a view was not working
- Fixed issue where if a rendertarget saved to a view had the same name as a material, it would not be saved

Paul

Thanx for the update

Archicad 18 is out, when do you think you can make the plugin for it?

I've now done some work on this, and there are very major changes required to the plugin in order to get it to work with AC18 (due to major changes in the AC18 API). So I think it will be quite some time and effort before an AC18 version of plugin will be available - sorry.

Paul

Is it posible to implement the local database for materials?

Is it posible to implement the local database for materials?

I have submitted this as an enhancement request to Otoy, so hopefully it will be possible in the future.

Paul

Hi Paul,

below you can see the cuda log...
..seems I reached a limit of GPU memory.
Probably by using too much textures or otherwise?...
i have used 41 LDR RGB textures
I tried to take a few steps back in what I was doing and succeeded to get a rendered viewport again by setting the resolution from 3000x1800 to 1500x900.
How can I solve this if I want to render bigger res?... by making the textures less big in pixels, use less textures in total.. maybe you have another suggestion?

edited: And I do not understand why I get to th omax so quick, because the estimated size of all textures used is about 40MB or so?

It would be handy if the plugin shows a approx of what is used by what and what is left to use, because now I just went over the max without having any idea. I know it shows aused and frse Memory, but not what is dedicated to Resolution and textures.

Just before I had a blue screen... (aik%$@#)78... ) can that be due to this issue?

edited: maybe I should have posted this in the general forum and not in the Archicad plugin forum? Sorry to bug you..But now it is too late


Edited again: I solved my own created misere
I used a very high poly OBJ for a proxy and that ate my Memory. Still it would be very handy to be able to monitor what is consuming the memory

Greetings, Jeroen

Started logging on 11.07.14 14:16:32

OctaneRender version 2.01 (2010000)

CUDA error 2 on device 3: The API was unable to allocate enough memory to perform the requested operation.
-> Failed to allocated device memory
CUDA device 3: Failed to allocate post-proc buffers
CUDA error 2 on device 1: The API was unable to allocate enough memory to perform the requested operation.
-> Failed to allocated device memory
CUDA device 1: Failed to allocate post-proc buffers
CUDA error 2 on device 2: The API was unable to allocate enough memory to perform the requested operation.
-> Failed to allocated device memory
CUDA device 2: Failed to allocate post-proc buffers

Hi Jeroen

Glad you solved the issue. Yes, proxies can use a lot of "hidden" memory, because they might have a lot of polys, and use a lot of HiRes texturemaps, but not be visible in the ArchiCAD scene - so use with caution.

Paul

Hi Paul,

I noticed when using a cube or other Archicad object for assignig proxies makes a difference.
The cube seems not to assign the origin in the cneter (even when the Arhcicad anchor of the cube is in the middle).
When using a cilinder it is OK.
I always use a Cilinder, but now I encountered teh problem with using a cube and I remembered why I use a Cilinder and just wanted to let know.

greetings,

Hi Jeroen - I suspect the cube may have some sort of offset being applied that the plugin is not taking into account. If you send me the scene with the cube, I can take a closer look.

Paul