Version 3.06-TEST4.1 (WORK IN PROGRESS BUILDS)

[PiotrAdamczyk]

Getting an "invalid version" error on the network preferences even though both computers are running the same daemon version. (both have same standalone and plugin and i uninstalled the old daemon on both and installed the one from this test version on both)

Slave should have same versions as plugin. Invalid version means that not equal versions on both side

I have the same problem.

Both computers have standalone 3.06, on the master my plugin is 3.06- TEST4, the invalid version info is in the attachement

[aoktar]

I have the same problem.
Both computers have standalone 3.06, on the master my plugin is 3.06- TEST4, the invalid version info is in the attachement

3.06 and 3.06-test4 is not equal. You have to use matching versions to master for every node of network. 3060005 is core number. Plugin should have same core version. Check the console output to see numbers

[PiotrAdamczyk]

I have the same problem.
Both computers have standalone 3.06, on the master my plugin is 3.06- TEST4, the invalid version info is in the attachement

3.06 and 3.06-test4 is not equal. You have to use matching versions to master for every node of network. 3060005 is core number. Plugin should have same core version. Check the console output to see numbers

Thanks, i guess i will have to wait for 3.06 plugin version, 3.06 test 4 is the only plugin version i can dwonload now.

[aoktar]

Thanks, i guess i will have to wait for 3.06 plugin version, 3.06 test 4 is the only plugin version i can dwonload now.

Here it's

[magnuscreative]

I want to say congrats to the development team on the new Adaptive Sampling addition to Octane! Holy smokes-it's a huge speed increase-thank you!!! I've also noticed that it more quickly cleans up the noise in bokeh portions of an image-out of focus elements used to be quite noisy and this is a welcome addition.

THANK YOU!!!

[Tag12345]

Will we see improvements in Work load management?


I noticed that in a scene where I have many Grass Polygons and other scenery objects in my scene.


Working with 1114 objects at 39 mil polys.


My setup is 3 GTX 1080's 8GB and for some reason Octane cant handle it and keeps coming up with a not enough memory error.


Anyway to use my existing setup to load larger scenes?


I feel like I can Never work on large and detailed scenes with octane due to this limitation. Its both hardware and software, but itd be nice If I could use my cpu cores or extra RAM to help process out scenes that are limited from my GPU Ram.


Not to sure if there are any settings that are preventing this too, maybe im doing something wrong??


Thanks

[aoktar]

Will we see improvements in Work load management?


I noticed that in a scene where I have many Grass Polygons and other scenery objects in my scene.


Working with 1114 objects at 39 mil polys.


My setup is 3 GTX 1080's 8GB and for some reason Octane cant handle it and keeps coming up with a not enough memory error.


Anyway to use my existing setup to load larger scenes?


I feel like I can Never work on large and detailed scenes with octane due to this limitation. Its both hardware and software, but itd be nice If I could use my cpu cores or extra RAM to help process out scenes that are limited from my GPU Ram.


Not to sure if there are any settings that are preventing this too, maybe im doing something wrong??


Thanks

Switch to "ALL MOVABLE" if it happen in Picture Viewer.

[Tag12345]

https://gyazo.com/2a1c9038dcddf33219f284a1e2cdd69e

https://gyazo.com/ebdee07bf5c2abe798c4fe2bd54cf96e

https://gyazo.com/c8a0e8ce4882abcd8e2d28ad176ebca4

Switched to movable also, and it crashed C4D -- It also just hangs and wont do anything for like 20 minutes.


Something wrong with my settings?

[aoktar]

Switched to movable also, and it crashed C4D -- It also just hangs and wont do anything for like 20 minutes.


Something wrong with my settings?

I'm not sure what i'm seeing here. But optimisation and detecting the problems that start with doing some tests and understand how plugin works. Especially movable vs. static geometries.
See these:
https://docs.otoy.com/#cinema-4d-v3-plu ... -rendering
https://docs.otoy.com/#cinema-4d-v3-plu ... object-tag
https://docs.otoy.com/#cinema-4d-v3-per ... renderings

Also please define the error: Where it happens and what's the message? Is it out memory in plugin side or happens after "updating" message? What do you have in your scene? Some plant plugin is used or just polygons?
If this is an out-of-memory in plugin then "all movable should" fix it. But it requires a different attention if that's a gpu side crash.

[Tag12345]

Recheck images for my settings.

Using Forester, set the geometry made by forester to low settings and editable and copied grass objects around my scene (not sure if using Instancing would be better?)

Same with Trees,etc


Objects 1000+
Polys - 39 Million


Getting an error in the Octane IPR, red text letting me know not enough memory to handle the scene.
Changing to Moveable just makes it Stall after "Updating" doesnt do anything.


Better way to optimize scene and settings to be better for Octane? or is Octane not at a point where its fast enough to still do large scenes?

Ive noticed in various ocassions where Octane is still relatively slow even with 3x 1080 GTX video cards. On single objects and more towards presentation and design aspects--its amazing, but not so much for hi quality CGI scenes.

Trying to figure out if its because I need better equipment or if Octane isnt there yet -- im assuming not until OSL if thats the case.