OTOY Forums

Its the crash of the Slave on the neu built
All 6 GB 2 x 980 Ti and 1 x Titan old.
(not to much Polys, not too less VRam)
The one who has programmed that deamon slave "MUST" be able
to decode these error messages.

"data texture 4 was not initialized"
"failed to unload module"
"failed to bind device to current threat"
...

Are all these lines listet just for fun?
I really would like to know whats the problem here
and how I can solve them!

thanks
Mike

Hi mike,
please go to the Octane Texture manager and share a screenshot with us. I have a suspect.
ciao beppe

Hi Tom,

I will do, but I'm at another project right now.
Give me some time.

The strange thing is, that on my other Slave I have a Titan Z
(also 6GB) and this slave is rendering without any problems.
So it must be related with my new built I think.

Also a big problem in general is, that if only one slave fails, the entire
rendering prozess is broken.
The Master and working slave 1 only has rendered 9 frames
within 5 hours because slave 2 crashed.

thanks!
Mike

Hi Tom,

I've send the screen to PM

But again, non of the Otoy-programmers can say something about
these errors?

regards
Mike

try with single gpu for detecting if it's a gpu problem.

short update!

after fighting all night with hardware of my new built (unpluging Gpus, changing pci-slots,
fighting with bios and booting issues ......) it seams, that its working now.
So far I have not got these strange crashes with all these strange messages anymore.

But I still cannot understand, (if that was really the problem) that deamon-slave
crashes, when Gpus are set in different slot orders.
The Asus X99 E WS has 7 PCI-16 Slots. So 3 Cards should work in any slot.
And I still would like meaning of these error-messages.

Will see in next days whether this nightmare continues

regards and thanks for your patience!
Mike

miohn wrote: The Asus X99 E WS has 7 PCI-16 Slots. So 3 Cards should work in any slot.

sometimes for PCI 's, Its depending how Cpu Slots and RAM slots are populated on motherboard , check your mobo doc...

Glad you solved! These type of errors seem like that they are mostly hardware related. Always better to test gpus/drivers/installations/HW and trying different combinations before posting here. Programmers cannot help you for Hardware issues.

Hi Ahmet,

sure, but programmers should be able to interpret
their own error-codes, or not

F.e. "data texture 4 was not initialized" they should be able to tell,
what this means and point someone to a maybe working solution.
Otherwise a message like "error" only would be enough.

regards
Mike

miohn wrote:Hi Ahmet,

sure, but programmers should be able to interpret
their own error-codes, or not

F.e. "data texture 4 was not initialized" they should be able to tell,
what this means and point someone to a maybe working solution.
Otherwise a message like "error" only would be enough.

regards
Mike

I don't know because i'm not gpu programmer. Even sometimes Otoy guys cannot know because these are produced by Cuda's itself.