A big scene works on an old computer , and don't on a new one. Uh?

MaloneXI

Hi all, 

I have a little problem about a big scene I'm creating for my comic book. 

This one : 

As you can see , the render worked well. On a core i7, sli of Geforce GTX 590 , 32 go Ram. WIN7 64. 
Without any doubt, I installed DAZ on my machine at work, an i7 next gen, WIN10 64,  48 G RAM, Gforce GTX 1060, with 442 driver . The last one , studio version. (I tested with all the last an old releases). 
What a [big] surprise ... the scene doesn't load on this machine. At my home , ok , I have to wait about 4 minutes before the scene loads. But here , at work ... I'm waiting one hour, and nothing. huhu. 
I don't have the version of the driver I've installed at my own computer , at home. But I do not understand wtf is going on... The GTX 1060 has 6 gb of video ram.... 

Ok , the scene is really heavy...About 170 Mo . If you know the model , the GRIM armor I have adapted on genesis 8 figure , is a really really high detailed model for such a work. 

In your opinion , does the sli make a difference between the twomachines? Why it doesn't work on the work machine , stronger than mine ? I'm a bit lost ... If someone could help... 


Thanx a lot. 

 

kenshaw011267

If its not loading its not the graphics cards and there is no way that scene ever rendered on those 590's. Fermi hasn't been supported in iRay since 4.11, IIRC.

More than likely it is issue with where the assets are stored or something like that.

Padone

The scene loading time has nothing to do with the video card. Probably there's someting in the scene that DS 4.12 doesn't like. You may want to check the log for errors.

As a rule of thumb though, especially in production, I'd avoid porting old projects to new studio versions. There may always be incompatibilities, also because iray gets a new version and there may be differences in rendering as already happened with sss and emission for example.

And if you use plugins remember they need to be updated too.

Mattymanx

If you look at native DS content, models, you will notice that they have their own Data folder.  This is the model itself plus the rigging info and any morphs plus the UVs of each piece.  When you save a scene with native DS content, DS will not write new entries into the data folder but instead reference it when loading the scene.  If however you were to load in a non natiive DS model, either importing an OBJ file or loading poser content, DS will convert them to its own format when you save the scene so that it is not importing the OBJs again.  So when the scene is saved, DS writes new entries to the Data folder for the items you imported.  If you need to transfer that scene to a new computer, you will need to know the exact file path to the info DS wrote in the data folder.  The easiest way to get the file paths to the data would be to save a scene subset of just the items you need on your old machine and then look at the ss file in Notepad++ to see where it references the data from.  Then you can retrieve them from the data folder and recreated the needed path on the new machine and copy the info there.

Paradigm

kenshaw011267 said:

If its not loading its not the graphics cards and there is no way that scene ever rendered on those 590's. Fermi hasn't been supported in iRay since 4.11, IIRC.

More than likely it is issue with where the assets are stored or something like that.

Yeah, seriously. I count, what? 10-11 figures? Each wearing clothing? And each allegedly being G8M?

There's a 100% chance it was rendering on the CPU lol. 

MaloneXI

Than for all your answers, I've came back home. I'm agree with the folder where all the assets are, and where Daz is looking for them. But in the two cases, my library is on an external drive, a SSD I keep always with me that I connect on my pc and the one at work. Of course, the backup is on a second drive. But when I'm working, I'm always working from that portable SSD. So the paths are always the sames. Second argue, seeing others who had compatibility problems between Daz and graphic drivers, I came back on the Daz 4.10 wich is the version I created the scene. More of that, and I don't know if it can deal with it, I don't render in iray, but in 3delight, because the manga shader applied on every asset only works with this engine. And, I'm not so much experimented with all that "performance trickss" with Daz, So I don't understand why do you say it's the CPU that renders the scene... Above a certain weight of the scene, Daz prefers the CPU? OK, but in that case, why it's working on my old i7 and not on the new Gen one at my work? Thanxx à lot. Ah, and I made the same scene with the grim armors, but with the original M3 figures. So the same number of polygons for the armors, but with simplier figures and the scene loads... Does the G8 has an effect on something? I must specify that, thanks to a script from a member, I convert each asset normally done for iRay into a 3Delight compatible, of course. So in my scene, there are no more ready-to-iray assets. I don't know if I'm clear in my tells, I"m typing with a Bluetooth keyboard quickly, with an approximative English, sorry for that.

kenshaw011267

3Delight only renders on the CPU so your GPU's are moot.

Iray renders on a GPU only if the scene fits on the GPU's VRAM. A 590 has 3Gb of VRAM. The scene you showed would take something closer to 20.

You claimed the scene wasn't loading not that it wasn't rendering. We're trying to diagnosis the problem you reported if it isn't the problem then tell us the actual problem.

MaloneXI

I just said that the scene doesn't load on my pc at work. It loads on the one at home, but in one hour now. This night, I have waited 2 hours before the scene appears on Daz lol. Daz was not responding, but I left it. And it worked. But at work, even if I'm waiting 5 hours, nothing appears. It's not a render problème, may I explained the problem Badly... The solution should be to duplicate all the g8 poses into m3 poses... But there is no converter for that.

cm152335

MaloneXI said:

I just said that the scene doesn't load on my pc at work. It loads on the one at home, but in one hour now. This night, I have waited 2 hours before the scene appears on Daz lol. Daz was not responding, but I left it. And it worked. But at work, even if I'm waiting 5 hours, nothing appears. It's not a render problème, may I explained the problem Badly... The solution should be to duplicate all the g8 poses into m3 poses... But there is no converter for that.

in your new setup pc,
does other similar scene are loading?

could be your new install have problem with administratives rights
try using to daz shorcut "run as administrator"

another test,

copy your library in to another place harddisk, set path and load the scene
 

Leana

Running DS as an administrator is a bad idea and can cause problems for later uses, so no, don't try that.

Have you looked at the log file to see what DS is doing?

MaloneXI

cm152335 said:

MaloneXI said:

I just said that the scene doesn't load on my pc at work. It loads on the one at home, but in one hour now. This night, I have waited 2 hours before the scene appears on Daz lol. Daz was not responding, but I left it. And it worked. But at work, even if I'm waiting 5 hours, nothing appears. It's not a render problème, may I explained the problem Badly... The solution should be to duplicate all the g8 poses into m3 poses... But there is no converter for that.

in your new setup pc,
does other similar scene are loading?

could be your new install have problem with administratives rights
try using to daz shorcut "run as administrator"

another test,

copy your library in to another place harddisk, set path and load the scene
 

Thanx a lot for answer me , first :) I thouht about admin rights , of course , but similar scenes are loading normally. As I said , if I lod the same scene , but with M3 figures wrearing GRIM armors , instead of G8 Male , it loads normally . But I don't know what to think about it... That would be the first time G8 bugs the system... So I loaded others scenes with G8 wearings other kind of armors , and there were no problems. 

Effectively , today I'll copy my library on one of my hard disk in my work machine, and I'll see. I'm pretty sure that putting the library on a mobile drive is not as a good as putting it on a hard disk , for the access speed etc. But for me it was much easier for many reasons... And I chose a drive supposed to be fast... 

 
 

Leana said:

Running DS as an administrator is a bad idea and can cause problems for later uses, so no, don't try that.

Have you looked at the log file to see what DS is doing?

No I didn't not yet... *ahem* I don't know where to find it ^^'


Edit : Ok I find it. 

I tried to lad the scene , and the log says that : 

2020-02-14 09:59:04.281 *** Scene Cleared ***
2020-02-14 10:00:49.715 *** Scene Cleared ***
2020-02-14 10:00:50.360 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.360 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.360 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.361 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.361 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.364 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.365 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.365 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.365 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.365 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.365 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.365 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.368 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.368 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.369 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.369 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.369 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.369 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.369 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.372 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.372 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.372 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.372 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.373 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.373 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.373 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.376 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.376 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.376 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.376 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.377 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.377 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.377 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.380 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.380 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.380 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.381 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.381 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.381 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.381 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.384 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.384 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.384 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.385 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.385 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.385 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.385 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.388 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.388 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.388 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.389 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.389 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.389 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.389 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.392 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.392 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.393 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.393 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.393 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.393 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.393 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.397 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.397 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.397 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.397 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.397 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.398 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.398 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.401 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.401 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.401 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.401 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.402 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.402 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.402 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.405 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.405 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.405 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.406 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.406 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.406 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.406 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.410 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.410 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.410 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.411 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.411 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.411 JSON interpreter warning: Unexpected numeric member: version
2020-02-14 10:00:50.411 JSON interpreter warning: Unexpected numeric member: version

 

On the forum , I see that somone got the problem too : 

 

https://www.daz3d.com/forums/discussion/255351/problem-after-reinstalling-moving-library

But no idea how to fix it... 

 

edit : I link the last entire log. 

 

Zilvergrafix

I have the grim armor, it is not heavy geometry and you can make instances, believe me I've inserted Zbrush assets converted to OBJ and the gazillion of polys are not a problem for DazStudio, but the mix of shaders in 3Delight and importing runtimes from Drive D to Drive B or C can be the problem.

Tip1: no need to change your G8 males for M3 figures just hide body and show the head.

Tip2: the armor is for itself an entire figure if you use the suit below like the figure to parent the rest.

Tip3: save all your soldiers individually like subsets, already posed so, if you need to repose do it outside the entire scene and subset save again.

MaloneXI

Yep , I know, that's why I found it strange. That's not the first time I'm working with Sanctum Art assets. I just didn't convert it for G8 until know. Same for the mix of shaders , I did more complicated scenes with manga shader , and never had a problem. 

All the G8 bodies are hidens :) I do that everytime for armores characters hihi. 

But I thought about your tip3 yesterday evening (in France) , and one the scene was kidn enough to load , I save all the poses of each of my characters. At least , it's done . So I can recreate the scene at anytime without loading all in one block . But it's a wait of time in a comic project , and not a small one huhu. Excuse me but I'm not familiar with all the vocabulary of DAZ (even after all these years on it lol) , what do you call "subsets" ? 

I'm not familiar with instances too , I think the scene like a movie-stage without paying attention to technical aspects... it's a big default you know... I think I'm paying it now huhu. (T.T)

(I verified all my paths for a big part of contents in my library, and all the assets are correctly loads from my drive , no others repositories anywhere)