OctaneRender™ 3.0 for LightWave™ - Beta build 3.00.14.0
Moderator: juanjgon
- BorisGoreta
- Posts: 1413
- Joined: Fri Dec 07, 2012 6:45 pm
- Contact:
Adaptive container works partially, I can see the volume rendering but it isn't positioned properly, as if it doesn't read what the current adaptive container position is inside the entire container.
19 x NVIDIA GTX http://www.borisgoreta.com
Hmmm, yes, this was the problem that I remember. OK. I'll test it and talk with Jascha about this problem.BorisGoreta wrote:Adaptive container works partially, I can see the volume rendering but it isn't positioned properly, as if it doesn't read what the current adaptive container position is inside the entire container.
-Juanjo
I need to add the TFD support for Mac. Don't worry, it is fairly easy ... the problem was that for the first version of the LightWave TFD SDK, OSX was not supported. It is fully supported now in the last TFD builds, so I'll add this feature for the next plugin release.barone998 wrote:Where is the turbulent option in lightwave on MAC. I see the option to locate turbulent plugin in windows but not on my mac plugin.
-Juanjo
Hi,
since upgrading to the latest version i can't get the slave to work. It worked like a charme in the previous version. Now the deamon starts and quits short after. One message was something like
"
Nothing changed on the systems besides the new octane files.
Any ideas what causes this behavior? Thanks for any help.
Master is Win 8.1, slave runs on Win 7 64
since upgrading to the latest version i can't get the slave to work. It worked like a charme in the previous version. Now the deamon starts and quits short after. One message was something like
"
" ... the other one wasmultiple connections requested for slave monitor
."slave crashed or was stopped via CTRL-D"
Nothing changed on the systems besides the new octane files.
Any ideas what causes this behavior? Thanks for any help.
Master is Win 8.1, slave runs on Win 7 64
Win 10 64 | 2x RTX 3080Ti 2x Xeon E5 2650v2 Supermicro X9DAi 128 GB
Win 10 64 | 1x RTX 4090 i9 9900K Gigabyte z390 128 GB
Win 10 64 | 2x RTX 3080Ti i7 2600 K 32 GB
Win 10 64 | 1x RTX 4090 i9 9900K Gigabyte z390 128 GB
Win 10 64 | 2x RTX 3080Ti i7 2600 K 32 GB
There is a bug in the slaves in this beta 3. It is fixed in the beta 4, but I need to update the plugin.
viewtopic.php?f=33&t=54110
-Juanjo
viewtopic.php?f=33&t=54110
-Juanjo
- FrankPooleFloating
- Posts: 1669
- Joined: Thu Nov 29, 2012 3:48 pm
Juanjo, I thought the region cropped stuff was good-to-go now... I just tried setting a crop (L) in F9 render and it still renders past the samples I have set in RT. What am I doing wrong? How do we get region cropped to work as me and Boris (et al) want?
Win10Pro || GA-X99-SOC-Champion || i7 5820k w/ H60 || 32GB DDR4 || 3x EVGA RTX 2070 Super Hybrid || EVGA Supernova G2 1300W || Tt Core X9 || LightWave Plug (v4 for old gigs) || Blender E-Cycles
This is a problem without solution currently. The render region is designed for standalone to work forever while refining parts of the image. The workaround is render by time, not by samples. Anyway I will check this issue again after the Octane 3.0 release, next week.FrankPooleFloating wrote:Juanjo, I thought the region cropped stuff was good-to-go now... I just tried setting a crop (L) in F9 render and it still renders past the samples I have set in RT. What am I doing wrong? How do we get region cropped to work as me and Boris (et al) want?
-Juanjo