OTOY Forums

Hi! This is the fourth beta release of the OctaneRender™ 4.0 for LightWave™ plugin version 4.00.0.15, available for LightWave 11.6, 2015.3 and 2018.0 Windows x64 and OSX. This build is compiled using the Octane 4.00 RC5 core, including some of its new features, like the lights linking or the new Universal material. The new UDIM node will be available in the next plugin build.

As with all experimental and test releases, please do not use this build for production work, and please note that we still classify this as an experimental release.

Important notes:
- NVIDIA Driver version 387 or higher is required on Windows and Linux, and any CUDA driver for Mac should work that supports CUDA 9.1.
- Octane no longer supports Fermi GPUs.
- When starting Octane for the first time, you'll see a window to download the cuDNN lib. Occasionally when we upgrade cuDNN, you may see this again at a later date. You can simply click Download and Octane will download the file needed. If you have any trouble with this process please let us know. If you need to, you can manually download the file and copy it into place next to the plugin .p file

For introductory material on V4, please see the viewtopic.php?f=33&t=66013 and viewtopic.php?f=33&t=68283


Release 4.00.0.15 regular license
https://render.otoy.com/customerdownloa ... _Win64.zip
https://render.otoy.com/customerdownloa ... ve_OSX.zip

Release 4.00.0.15 subscription license
https://render.otoy.com/customerdownloa ... n64_vr.zip
https://render.otoy.com/customerdownloa ... OSX_vr.zip

Standalone version for the network rendering nodes
https://render.otoy.com/customerdownloa ... C5_win.exe
https://render.otoy.com/customerdownloa ... _macos.dmg


=============================================
RELEASE 4.00.0.15
=============================================

* OCTANE FEATURES AND BUGS FIXED:
- Octane is now trying to prevent the computer to go to sleep.
- Made a change in the render pipeline that hopefully increases the refresh rate at the beginning of rendering.
- Octane prints now a warning in the log if the environment variable CUDA_VISIBLE_DEVICES or CUDA_LAUNCH_BLOCKING is set. The effect of these is that not all GPUs are visible, causing rendering to be slower.
- Added support for emitters with "surface brightness" disabled to hair geometry.
- Fixed bug causing hair geometry emission to not to work at all.
- Fixed a bug where denoised alpha causes artifacts in denoiser output.
- Fixed a crash of an OSX net render master when a slave connects with it.
- Fixed incorrect alpha weight of beauty passes causing noisy, aliased edges.
- Fixed incorrect transition of the shadow passes to the background and between active and inactive layers.
- Fixed crash or incorrect normal import of subdivided, deformed meshes.
- Fixed crash of the net render master (on OSX) when a slave connects with it.
- Fixed incorrect values displayed in the not-enough-memory error message of the denoiser.


Thanks,
-Juanjo

a BIG thank you again to abstrax and juanjo for this fast fix. i checked mac <-> mac networking and also added my windows machine with 5 GPU's to the network. all working very well until now, no issues with authentication, no single hickup or crash. will report here if i find any issues.

I have an issue while rendering animation : My firts frame (zero one) is still black after opening the scene and hit F10.
Can anybody else confirm this issue ?

I have a kitchen scene that cannot be fully rendered with F10. The render stopped after about 20 frames
I still investigated this very simple scene and let know what I get.

pixym wrote:I have a kitchen scene that cannot be fully rendered with F10. The render stopped after about 20 frames
I still investigated this very simple scene and let know what I get.

With or without Denoiser?

With Denoiser On

I had an experience when Octane with a renderer increased the paging file several times on my hard drive, after which the system blocked Octane's work. I still did not understand what needs to be done to prevent this from happening, but my last animation render (2k x 2000 frames + Denoiser) went quite well.

pixym wrote:I have a kitchen scene that cannot be fully rendered with F10. The render stopped after about 20 frames
I still investigated this very simple scene and let know what I get.

If you enable the log file while rendering the sequence, perhaps we could have a clue on it about the problem. As always, feel free to send me the scene to try to reproduce the problem here.

Thanks,
-Juanjo

pixym wrote:I have an issue while rendering animation : My firts frame (zero one) is still black after opening the scene and hit F10.
Can anybody else confirm this issue ?

I have the same issue. Saving first frame in the animation sequence is empty file. Doesn't have to be 0 frame.

I have several times the same thing.