OSL and Motion Blur
Moderators: ChrisHekman, aoktar
Please post this kinda small problems on release topics. It's not a stable production and gives confusion.
Octane For Cinema 4D developer / 3d generalist
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
3930k / 16gb / 780ti + 1070/1080 / psu 1600w / numerous hw
In my experience, motion blur works with OSL cameras just fine until you have animated geometry when it causes a cuda 700 crash. Unfortunately, not that many of us are playing with OSL so it probably went unnoticed. Thank you for bringing this up, I didn't notice this before.mentor972 wrote:Sorry, I wasn't sure if this was a known, regular thing that OSL doesn't do or if this was a minor bug. Was trying to verify.
What's your experience? Is it crashing (render failure) or...?
Regards
Milan
Colorist / VFX artist / Motion Designer
macOS - Windows 7 - Cinema 4D R19.068 - GTX1070TI - GTX780
macOS - Windows 7 - Cinema 4D R19.068 - GTX1070TI - GTX780
It doesn't crash., the render continues. just doesnt seem to work at all, seems like it just got overlooked really. not a huge big deal, just pointing it out for when it's time to RC... one other thing iv'e noticed is that i get errors across my VCA's when trying to net render with OSL shader / camera... so probably also got overlooked since theres a big "TODO:" error in the daemon console.... other than that, everything else seems to be pretty solid (as far as my scope goes)
amazing work as usual Otoy team!
amazing work as usual Otoy team!
lovelyabstrax wrote:In case you want to try it out: The fix was included in 3.08.4 we released today.

Launching net render slave (3080400) with master 192.168.10.51:1025
TODO: implementation missing (ShaderCode::deserialize)
invalid message received from network connection
integration data doesn't contain valid shader data
