OTOY Forums

i renamed the .cfg now, and back to work normally,.. so i try to back the old .cfg, and it works again

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

3.0.3.94
- Compiled with Octane 3.0 alpha 3
- Changed Ray Epsilon to a Modo "distance" property so very small numbers are displayed correctly
- Removed the Octane settings defaults system. Instead, set your preferences Octane settings to a blank scene, and then use Modo->System->Preferences->Defaults->Application->assign the Default Scene to the scene you just saved
- Added "Shutter Interval Approach" to the Kernel Animation settings (to match the same setting in Octane Standalone)
- The "Shutter Speed" property is now a double, rather than an integer, allowing a greater level of precision when setting the shutter speed
- Added preliminary support for Modo Cubic projection mapping
- Fixed issue where the Out Of Core enabled setting was incorrectly set when first starting Modo
- Fixed bug when animated focus distances where not being loaded into the Octane timeline when Load All Frames Into Octane was checked

Paul

Thanks

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

3.0.4.95
- Compiled with Octane 3.0 alpha 4
- Removed IES and HDR from the background image load types
- Added EXR to the Image node load types
- Added preliminary support for VDBVoxel volumes, which if Generate Voxel Mesh is UNTICKED, will be loaded into an Octane Volume node. Material editing is not possible yet - however you can experiement by editing the medium connected to the Octane Volume by typing "octane.command showNodeGraph" (any changes made are lost on the next scene refresh)
- Added the Timeline to the Modo901 Octane layout (you will probably need to delete your Modo901/902.cfg for this to be seen)
- Spread the nodes out more (in the up/down direction) in the Schematic when loading LiveDb presets or adding Octane Overrides
- Refreshed the LiveDb. Pls download the latest version from https://docs.otoy.com/Modo/?page_id=909

Paul

Hi Paul,

I have 4gb card memory, But octane shows that is using only 3gb. Why?


.

I have 4gb card memory, But octane shows that is using only 3gb. Why? ]

Which version of the plugin are you running? What graphics card do you have? Windows, Linux, or osx? Can you post a screenshot showing the incorrect memory being reported pls? Does this happen in Octane Standalone too?

Paul

modo 902 - 3.0.4.95 - windows - standalone not tested

980ti 6gb - 980 4gb - 680 4gb

Tharso, can you pls see what Octane Standalone reports for that scene. Perhaps you have other processes using VRAM such as Modo or Windows?

face_off wrote:Tharso, can you pls see what Octane Standalone reports for that scene. Perhaps you have other processes using VRAM such as Modo or Windows?

Yes I have! First monitor with 980ti and second monitor with 680. Maybe is that, then?

Yes I have! First monitor with 980ti and second monitor with 680. Maybe is that, then?

Did Octane Standalone report the same memory usage as Octane Standalone?

Paul