OTOY Forums

boris wrote:no offense but you can't blame otoy or karba for failing client delivery. it's your software choice and your job to calculate the risk of using it in your production pipeline.

So he should blame himself for Octane bugs?
In that case they should provide the SDK so we could fix stuff on our own.

Suv

boris wrote: no offense but you can't blame otoy or karba for failing client delivery. it's your software choice and your job to calculate the risk of using it in your production pipeline.

Do you tell that to your clients?

suvakas wrote:

boris wrote:no offense but you can't blame otoy or karba for failing client delivery. it's your software choice and your job to calculate the risk of using it in your production pipeline.

So he should blame himself for Octane bugs?
In that case they should provide the SDK so we could fix stuff on our own.

Suv

come on suv you know what I mean. for me it was clear, as early adopter of gpu rendering one must live with limitations. i was frustrated from times to times, too, not having access to exactly that feature I needed at that moment. but the benefits were always obvious for me. if it's really important, you have to have a plan B.

geo_n wrote:

boris wrote: no offense but you can't blame otoy or karba for failing client delivery. it's your software choice and your job to calculate the risk of using it in your production pipeline.

Do you tell that to your clients?

no. but i haven't failed on a clients deadline since 16 years.

'fixed displacement bug' ?

Hi
Having a major problem with displacement.
It used to work fine but now all objects with displacement materials on do not show up in the render.

Not sure if this is a memory issue? Does displacement use loads of gpu memory?

Is there a limit to the ammount of displacement maps or materials you can use?


Using 570 2.5gb + 580 3gb with latest nvidia drivers on 3ds max14 with latest octane release, win7 64

When clearing the displacement maps the materials reappear in the octane render viewport.

This is the message in the error log...

CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> kernel execution failed (pick)
device 1: picking failed
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to copy memory to device.
device 1: failed to upload data texture 17 of context 0
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to deallocate device memory
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> could not get memory info
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to load symbol data to the device (camera data)
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to allocated device memory
device 1: failed to upload data texture 17 of context 0
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to load symbol data to the device (camera data)
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to allocated device memory
device 1: failed to upload data texture 17 of context 0
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to load symbol data to the device (camera data)
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to allocated device memory
device 1: failed to upload data texture 17 of context 0
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to load symbol data to the device (camera data)
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to allocated device memory
device 1: failed to upload data texture 17 of context 0
CUDA error 719 on device 1: An exception occurred on the device while executing a kernel. The context cannot be used anymore and must be destroyed. All existing device memory allocations from this context are invalid and must be reconstructed.
-> failed to load symbol data to the device (camera data)

boris wrote:

suvakas wrote:come on suv you know what I mean. for me it was clear, as early adopter of gpu rendering one must live with limitations. i was frustrated from times to times, too, not having access to exactly that feature I needed at that moment. but the benefits were always obvious for me. if it's really important, you have to have a plan B.

Recent issues are related to Max SDK and not GPU programming.

Suv

bit of progress with displacement maps problem...

if I turn off all disp maps I can open octane viewport no problem.
I can even make multiple copies of all the geometry and octane viewpoert will still happily open.

memory used is around .6 of 1.2 so should be plenty of room for the displacement maps when I turn them back on?

Or not. When I turn the disp maps back on the octane viewport doesn't open and clicking render does work but all the geometry with disp maps on doesn't appear. Or max gives a 'max is running out of memory and you're all going to die' message

Do disp maps use loads of memory to make the amazing images - ie does it actually make the geometry for the render? Hope not as it would have been really great to use displacement.

Rik wrote:bit of progress with displacement maps problem...

if I turn off all disp maps I can open octane viewport no problem.
I can even make multiple copies of all the geometry and octane viewpoert will still happily open.

memory used is around .6 of 1.2 so should be plenty of room for the displacement maps when I turn them back on?

Or not. When I turn the disp maps back on the octane viewport doesn't open and clicking render does work but all the geometry with disp maps on doesn't appear. Or max gives a 'max is running out of memory and you're all going to die' message

Do disp maps use loads of memory to make the amazing images - ie does it actually make the geometry for the render? Hope not as it would have been really great to use displacement.

I am working in displacement stability. Hopefully will make a new release this week.

boris wrote:hi karba
we got some strange issues with the frame buffer in higher resolutions:

stripes.jpg

the clone to framebuffer worked, the image also looked like it had to.

win8.1
nvidia driver 335.23
one gtx used for display, all other gtx 680 rendering, no memory overflow (all have 4 gb)

How does normal render look like?

Karba wrote:

boris wrote:hi karba
we got some strange issues with the frame buffer in higher resolutions:

stripes.jpg

the clone to framebuffer worked, the image also looked like it had to.

win8.1
nvidia driver 335.23
one gtx used for display, all other gtx 680 rendering, no memory overflow (all have 4 gb)

How does normal render look like?

we never us normal render for stills, but I just tested: no problems there.

did some tests (in octane viewport):
- this was a old scene from 1.53
- merged everything into fresh scene, same result
- first pass looks good, it starts with second refresh (5 passes)
- it also happens with lower resolutions
- it happens with all kernels, motion blur on/off, autoupdate MP on/off etc
- it happens with nearly no geometry (after turning off nearly all layers)
- it happens with white env light only
- it DISAPPEARS when switching to region and then go back to normal mode
- it does not happen with Octane3dsMaxSetup_2_0_7a.zip
- it does not happen on my partners 3 GPU machine (win7, same driver), mine is win8.1
- can't reproduce it with a new scene doing wild stuff

hope this helps somehow (have you seen the 7th post from twinsk8, looks like he has the same issue?)
cheers
boris