OTOY Forums

coilbook wrote:

neonZorglub wrote:

ramone163 wrote:I confirm that the material editor is much faster. Thank you neonZorglub.

Nice to hear, thanks:)

ramone163 wrote:But open Octane Render Setup, Camera modify parameters is still slow. I don't know, it is 3ds max or Octane problem?

coilbook wrote:3ds max mas still gets very slow after using octane viewport even selecting mesh objects.

> Try to 'Disable all Octane ToolTips' in global preferences / Trouble Shooting.
I may have missed something. I will keep investigating.

Thanks.
Can you please look into fog density precision. At certain point fog just turn off instead of becoming even less denser. viewtopic.php?f=81&t=71250

I posted some fog samples in this thread. Some scaling could also influence some precision or limit. If you can't get smooth density variation, could you post a simple scene ?
Thank you

There is a problem with Update Static geometry and itoo forest.
We have animated primitives and itoo is scattered on them (more detailed cars are scattered on moving boxes.). When update static geometry is unchecked itoo objects quit moving even though itoo geometry and itoo forest itself are set as movable proxies. For some reason octane recognizes itoo only as a static element.
Because of this update static geometry must be checked and this makes processing time go from 5 sec to 30.

Can you add an option to recognize itoo as movable proxy too?

UPDATE:
There is a problem with processing times and high count of itoo objects like high poly trees in this example. When green trees are enabled processing times goes from 13 seconds to 54 each frame. There are 244000 trees. Why? I thought once it is loaded into vram there shouldn'r be any processing times.
I think the problem is octane updates itoo every frame because update static geometry is on but we cannot turn it off because we use itoo to distribute on moving planes as detailed moving cars. If we uncheck then itoo cars wont move since octane sees itoo as static object only. Making itoo forest as movable proxy wont work. Please fix it that way we can make itoo as a movable proxy if we want. I think octane updates itoo every frame now




Thanks

Thanks
I will share the scene soon. It's just large scenes 5-10 miles thats when everything looks foggy and you cannot get no fog first 1-2 miles and then lots of fog far away. It would be nice to get a custom value no fog zone from the camera. Maybe instead of a sphere you should add a sphere with a shell so ther wont be for to the first inner wall of the sphere
Ideally it would be nice if you guys can make more effective fog with a noise option. Please look at the unreal fog in this video. iwish we had the same https://youtu.be/zKu1Y-LlfNQ?t=199

When I load a scene created with 6.12 after updating to 6.16 all textures in the render window disappear... I have to MERGE the object onto a new empty max file to be able to render properly..how to fix?

Edit:
Man this sucks!!

even after I merge the objects to a new file...if I save it and re-open the materials are gone again in the render..but not in the MatEditor or Viewport.

I even activated conversion and had to re-start max to no avail

why?!?!

Edit02:
I had to install 6.14 and now renders appear as they did in 6.12... please see the issue with 6.16 as soon as possible.. I'd love to have to a good performance with Mat Editor

coilbook wrote:There is a problem with Update Static geometry and itoo forest.
We have animated primitives and itoo is scattered on them (more detailed cars are scattered on moving boxes.). When update static geometry is unchecked itoo objects quit moving even though itoo geometry and itoo forest itself are set as movable proxies. For some reason octane recognizes itoo only as a static element.
Because of this update static geometry must be checked and this makes processing time go from 5 sec to 30.

Can you add an option to recognize itoo as movable proxy too?

UPDATE:
There is a problem with processing times and high count of itoo objects like high poly trees in this example. When green trees are enabled processing times goes from 13 seconds to 54 each frame. There are 244000 trees. Why? I thought once it is loaded into vram there shouldn'r be any processing times.
I think the problem is octane updates itoo every frame because update static geometry is on but we cannot turn it off because we use itoo to distribute on moving planes as detailed moving cars. If we uncheck then itoo cars wont move since octane sees itoo as static object only. Making itoo forest as movable proxy wont work. Please fix it that way we can make itoo as a movable proxy if we want. I think octane updates itoo every frame now




Thanks

Hi coilbook,
I try testing itoo animated objects proxy movable, it seems to work.
Itoo version?
Regards
Paride

paride4331 wrote:

coilbook wrote:There is a problem with Update Static geometry and itoo forest.
We have animated primitives and itoo is scattered on them (more detailed cars are scattered on moving boxes.). When update static geometry is unchecked itoo objects quit moving even though itoo geometry and itoo forest itself are set as movable proxies. For some reason octane recognizes itoo only as a static element.
Because of this update static geometry must be checked and this makes processing time go from 5 sec to 30.

Can you add an option to recognize itoo as movable proxy too?

UPDATE:
There is a problem with processing times and high count of itoo objects like high poly trees in this example. When green trees are enabled processing times goes from 13 seconds to 54 each frame. There are 244000 trees. Why? I thought once it is loaded into vram there shouldn'r be any processing times.
I think the problem is octane updates itoo every frame because update static geometry is on but we cannot turn it off because we use itoo to distribute on moving planes as detailed moving cars. If we uncheck then itoo cars wont move since octane sees itoo as static object only. Making itoo forest as movable proxy wont work. Please fix it that way we can make itoo as a movable proxy if we want. I think octane updates itoo every frame now




Thanks

Hi coilbook,
I try testing itoo animated objects proxy movable, it seems to work.
Itoo version?
Regards
Paride

Hi Paride,
I attached the scene it is not working. Itoo cars are not moving. When you turn off update static geometry and set itoo as movable proxy itoo forest does not move even though it is set as a movable proxy

I think out of core has not been working properly.
Now I get cuda error failed to move image texture out of core

Also why am i even getting this error. When I went to octane viewport I am borderline close to my vram limit and RAm is not even being used.

I will also send you the scene soon that has slow eval tiems due to itoo forest.

is there any way to have more precision of color. Changing red values from 255 to 234 changes nothing and then changing by 1 number changes red a lot. I need red inbetween. Thanks

coilbook wrote:is there any way to have more precision of color. Changing red values from 255 to 234 changes nothing and then changing by 1 number changes red a lot. I need red inbetween. Thanks

Hi coilbook,
maybe it could help:
you https://render.otoy.com/forum/viewt ... gb#p143144
Regards
Paride

Hi,
There is a problem with GPU failure message.
1. When the message appears and you hit OK 3ds max tries to render next frame and message appears again. So you have to be very fast to hit OK on that message and then quickly hit cancel rendering.
2. After you cancel all this 3ds max just crashes and closes instead of exiting rendering window.