intel mini render node problems - Polyloop

lateralis · 22nd January 2007, 23:27

I posted this over at the DAZ forums but haven't been able to figure it out. basically I have an issue where squares rendered by my intel mini are incorrectly processing global illumination and indirect lighting.

after much trial and error I have determined that it is DEFINITELY the mini.

exhibit A:

I've blurred out the center graphic as it's proprietary and not for release yet - just know that that's NOT what I'm talking about ;)

fixes attempted:
one suggestion was that there was a discrepancy between installed pluggins. I've never installed any (that I know of) so on a lark I cracked open the app package on all the machines and made sure the extensions folder was identical between them all - still no dice.

i reinstalled the main app and all the render nodes from the universal binary installer. i didn't update any of the PPC machines when the UB came out since the version # was the same but I guess there was more to the update than just going to UB. still no dice

finally I tried scouring the mini and removing ANYTHING even remotely eovia (now DAZ) related and reinstalling - still no dice.

This is a reproducible issue that happens whenever NON-ambient occlusion indirect lighting is used including things like caustics. I can render the exact same file with the intel mini turned off and get a great render. however, since the mini cuts render times almost in half, coupled with my desire to buy a mac pro and several more mini's i NEED to know that I can resolve this issue.

other important info: full setup is a dual 2.5 G5 workstation with 4 render nodes - 3 G4 minis and the 1 Intel mini.

PLEASE HELP!!!

lateralis · 22nd January 2007, 23:58

here's a perfect example of what I'm talking about using one of the built in scenes from carrara. it almost looks like the node is calculating the lighting in a completely different way!

Piem · 23rd January 2007, 00:57

Hmm I have heard of similar problems a long time ago..before the 5.1 patch.
But it was in the french part of the forum carrara, I am sure of this. I am pretty sure that the problem was fixed (by the french user that I'm looking for)
I have to search. (it's about midnight over here

)

Piem · 23rd January 2007, 01:06

I have found a first post ..It was before CS5.04
Sorry you'll have to translate

lateralis · 23rd January 2007, 01:11

thanks! translating now. here's hoping it helps.

ap-brian · 23rd January 2007, 13:59

It's a big bad bug - daz know's about it- hope they fix it.

you can still go an get a mac pro, i've got one and all renders great.

ap-brian · 23rd January 2007, 14:04

wait, I had the same problem (master was intel, slaves G5). This is to be the problem. With all programs you can get render problems when the processor typs are diferant (intel/G5). The next time at the office I'll try netrender on G5 only

lateralis · 23rd January 2007, 16:24

so basically, it's an architecture issue on PPC vs intel. so If I get a mac pro and a few more intel mini's as nodes, everything should be great right?

Altered_Ego · 31st January 2007, 16:08

The new Mac Minis have integrated graphics chips made by Intel. They're akin to the graphics "cards" found in laptop computers.

They're not incredibly powerful or sophisticated.

If you're doing professional work, I think you'd at least want an iMac.

I have my eyes set on a 24" iMac, with an nVidia graphics card... If "my ship finally arrives."

22nd January 2007, 23:27	#1 (permalink)
lateralis Vertex Join Date: Dec 2005 Location: Cleveland Posts: 26	intel mini render node problems I posted this over at the DAZ forums but haven't been able to figure it out. basically I have an issue where squares rendered by my intel mini are incorrectly processing global illumination and indirect lighting. after much trial and error I have determined that it is DEFINITELY the mini. exhibit A: I've blurred out the center graphic as it's proprietary and not for release yet - just know that that's NOT what I'm talking about ;) fixes attempted: one suggestion was that there was a discrepancy between installed pluggins. I've never installed any (that I know of) so on a lark I cracked open the app package on all the machines and made sure the extensions folder was identical between them all - still no dice. i reinstalled the main app and all the render nodes from the universal binary installer. i didn't update any of the PPC machines when the UB came out since the version # was the same but I guess there was more to the update than just going to UB. still no dice finally I tried scouring the mini and removing ANYTHING even remotely eovia (now DAZ) related and reinstalling - still no dice. This is a reproducible issue that happens whenever NON-ambient occlusion indirect lighting is used including things like caustics. I can render the exact same file with the intel mini turned off and get a great render. however, since the mini cuts render times almost in half, coupled with my desire to buy a mac pro and several more mini's i NEED to know that I can resolve this issue. other important info: full setup is a dual 2.5 G5 workstation with 4 render nodes - 3 G4 minis and the 1 Intel mini. PLEASE HELP!!!

31st January 2007, 16:08	#9 (permalink)
Altered_Ego NURBS Booleans are your friend Join Date: Apr 2006 Posts: 135	The new Mac Minis have integrated graphics chips made by Intel. They're akin to the graphics "cards" found in laptop computers. They're not incredibly powerful or sophisticated. If you're doing professional work, I think you'd at least want an iMac. I have my eyes set on a 24" iMac, with an nVidia graphics card... If "my ship finally arrives." __________________ My Site: http://www.ronknights.com/ My Forum: http://www.ronknights.com/forum/

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode

22nd January 2007, 23:58	#2 (permalink)
lateralis Vertex Join Date: Dec 2005 Location: Cleveland Posts: 26	here's a perfect example of what I'm talking about using one of the built in scenes from carrara. it almost looks like the node is calculating the lighting in a completely different way!

23rd January 2007, 00:57	#3 (permalink)
Piem Booh! Join Date: May 2003 Location: Rennes/fr Posts: 6,639	Hmm I have heard of similar problems a long time ago..before the 5.1 patch. But it was in the french part of the forum carrara, I am sure of this. I am pretty sure that the problem was fixed (by the french user that I'm looking for) I have to search. (it's about midnight over here )

23rd January 2007, 01:06	#4 (permalink)
Piem Booh! Join Date: May 2003 Location: Rennes/fr Posts: 6,639	I have found a first post ..It was before CS5.04 Sorry you'll have to translate

23rd January 2007, 01:11	#5 (permalink)
lateralis Vertex Join Date: Dec 2005 Location: Cleveland Posts: 26	thanks! translating now. here's hoping it helps.

23rd January 2007, 13:59	#6 (permalink)
ap-brian Vertex Join Date: Oct 2005 Posts: 10	It's a big bad bug - daz know's about it- hope they fix it. you can still go an get a mac pro, i've got one and all renders great.

23rd January 2007, 14:04	#7 (permalink)
ap-brian Vertex Join Date: Oct 2005 Posts: 10	wait, I had the same problem (master was intel, slaves G5). This is to be the problem. With all programs you can get render problems when the processor typs are diferant (intel/G5). The next time at the office I'll try netrender on G5 only

23rd January 2007, 16:24	#8 (permalink)
lateralis Vertex Join Date: Dec 2005 Location: Cleveland Posts: 26	so basically, it's an architecture issue on PPC vs intel. so If I get a mac pro and a few more intel mini's as nodes, everything should be great right?