Kainjy said:

Imago said:

Silvhe said:

Imago said:

Silvhe said:

 perché ci sono le figure,

 Sai che le figure ci sono anche nel DIM?

Ti basta selezionare i prodotti, fare click destro e scegliere "Retrieve Thumbnail" e ce le hai tutte.

Solo che alla DAZ non hanno aggiustato gli archivi e le immagini sono 6000x6000, per cui una volta che ha scaricato tutto devi ridurre le dimensioni delle immagini usando un batcher.

Questa non la sapevo, interessante. Grazie 

Il povero vecchio Zio Imago continua a ripetervi di leggere le istruzioni ma nessuno da ascolto al povero vecchio Zio Imago... 

Di nulla, comunque!

E' giustissimo Zio Imago, solo che le istruzioni di DAZ sono come un puzzle da 1.000 pezzi da ricomporre da solo. Tra un manuale che non spiega quasi nulla, pagine online risalenti alla vecchia wiki, link a pagine non più funzionanti, video su youtube di gente che ha smesso anni fa (molti non hanno più pubblicato nulla e i video vanno dai 5 anni fa in su) e una valanga di post del forum in cui provare a cercare info ai vari problemi... trovare qualcosa è una vera caccia al tesoro. 
Non ti dico quanto ho sudato per cercare info su come creare morph, ora le sto cercando sulle weightmap (vorrei creare/editare dei vestiti e il Transfer da problemi..). Inoltre anche Iray non mi è ancora chiaro in alcuni punti...(per Filament mi sono dovuto andare a vedere la guida ufficiale di Google !)

Appunto...

Imago said:

Silvhe said:

Imago said:

Silvhe said:

 perché ci sono le figure,

 Sai che le figure ci sono anche nel DIM?

Ti basta selezionare i prodotti, fare click destro e scegliere "Retrieve Thumbnail" e ce le hai tutte.

Solo che alla DAZ non hanno aggiustato gli archivi e le immagini sono 6000x6000, per cui una volta che ha scaricato tutto devi ridurre le dimensioni delle immagini usando un batcher.

Questa non la sapevo, interessante. Grazie 

Il povero vecchio Zio Imago continua a ripetervi di leggere le istruzioni ma nessuno da ascolto al povero vecchio Zio Imago... 

Di nulla, comunque!

E' giustissimo Zio Imago, solo che le istruzioni di DAZ sono come un puzzle da 1.000 pezzi da ricomporre da solo. Tra un manuale che non spiega quasi nulla, pagine online risalenti alla vecchia wiki, link a pagine non più funzionanti, video su youtube di gente che ha smesso anni fa (molti non hanno più pubblicato nulla e i video vanno dai 5 anni fa in su) e una valanga di post del forum in cui provare a cercare info ai vari problemi... trovare qualcosa è una vera caccia al tesoro. 
Non ti dico quanto ho sudato per cercare info su come creare morph, ora le sto cercando sulle weightmap (vorrei creare/editare dei vestiti e il Transfer da problemi..). Inoltre anche Iray non mi è ancora chiaro in alcuni punti...(per Filament mi sono dovuto andare a vedere la guida ufficiale di Google !)

Try to use Filament rendering - all possible seams are easily spotted there.

jakiblue said:

oh how weird! It never did that before! i see it written in the scene tab "environment options" and it shows up in the render settings like normal now. Bizarre. I take it that's new with 4.15?

edit: cos my keyboard had a major fit and even I couldn't understand what I had typed. 

It is as far as I remember a 4.15 thing (I think it turned up with filament, maybe). I'm not really sure if it's a bug or a just a design choice though, as it could be either!

If it is not a bug, then perhaps we could have it as an option like "create default camera". 

No blame or praise for Daz3D going Iray or Filament for Studio.  Just pointing out that Studio has a useful feature for people who want line art, but that it is tied to 3Delight.  Daz3D is de-emphasizing 3Delight, yet is not updating the feature (so far) to work with the render engines it is promoting.  Many of the new products the Daz store is curently selling do not come with 3Delight optimized shaders.  They can be converted.

Just the way it is.  No speech by me that the younger generation should get off my lawn, or that defense wins championships, or shaking my fist at a cloud.  Just a heads up.  If a person is interested in using 3D rendering programs to aid in comics development, consider Studio because Studio has a potentially useful tool that can be calibrated more finely than Carrara's multi-passes.  But, Daz does not seem interested in updating the tool for the render engines it is currently emphasizing, or making sure new products have shaders optimized for use with the tool (and optimization is relevant if the purported advantage is the ability to finely tune line detection). 

Given those trade-offs, I still find a lot of value in Carrara.  For example, the vertex modeler in the Assemble room crushes Studio's 'meshgrabber' plugin. Another example, Carrara has many more multi-pass optons than just outlines and toon filters.  Others more familiar with Studio's tools will evaluate the trade-off differently. 

Well, we can't blame Daz for going Iray and Filament. It was either introduce these things or watch the crowd move on. It's sweet of them to leave 3Delight in for folks that don't feel like following the pack - at least not yet.

I doubt that I'll ever prefer the modern PBR over our ray tracer. I just like how it does what I want it to.

Curious, have you played around with DCG's Toon Pro?

I haven't yet. 

It was just the other day when I needed to make an animation of some soldiers moving through the facility - and it was for a security screen. So I tried DCG's Wireframe Pro for the first time. Minutes (minutes!!!) later, I had four separate renders that were exactly what I was looking for - and here I thought that it would be difficult to use!!!

So I'd like to try Toon Pro and see if that has the same ease-of-use.

RE: Line Render 9000 and Studio.  Few people know that Studio has a line renderer built in the 3Delight render engine.  However, the default is clunky and hard to deal with.  The Line Render 9000 is a plugin script the author came up with to give more control to the user to identify lines.  For example, you can assign an ID by material zone, or by object, or by...   And you can adjust the sensitivity of the program to differences in color to draw a line somewhere, or not.  So, that part is good.  However, it is built into 3Delight, and Daz is moving content development to Filament and IRay.  Not insurmountable, but just another example of the tradeoffs.  

My familiarity with the tools will keep me with the Carrara mutlipasses and toon filters for a lot of stuff.

So it all started that my render crashed to a black frame withn that unavailable device notification - this happened out odf a sudden with nothing (literally changed on the system. ISoetimes i could do a first render when in textured mode viewport (previously iray) but the second definitely failed. Seems like daz was noit freeing up the VRAM after closing a render.

next step was that also the textrued viewport slowed down to a crawl, actully every viewport rendering mode, with Filament now being the most responsive, still nothing I could seriously pose a character, though. Even selecting or clicking any thing in the scene as well in the DAZ GUI takes ages.

Lately, DAZ started to gave me frequent notifications that I need to revalidate due to chages in may system (not true) and today Figure metrics - which I loaded on a character through smart content (!) gave me a warning I would need to install and register the script plug in. What??? It is in my library but checking the installed plugins it actually is not there???

So I think it is time to bite the bullet and do a as clean install of DFAZ withz least as possible remainders without sacrificing any of my work. How to proceed?

Nitty gritty details: Win 10 20H2 and DAZ on NVMe PCIe SSD, Library on a separate NVMe SSD, 64GB of DDR4, 1080ti as the primary adapter feeding 2 monitors and a cubic extender with 3 TitanX Maxwell cards. Everythign on the latest drivers 4.66.27 (although happened on461 wasw ell) and no, no Stidio drivers as theere are none form my Maxwell cards, though I tired with the Cubix shutt down and the 1080Ti alone. Disabling security Suite (Bitrdefender) is also nothing that showed effect. And, again, on the exact configuration everything worked fine as a breeze until early this year and everything aside DAZ studio still does, even demanding games and VR have no problem, so it MUST be something eith that particular software, regular and Beta, too.

Help and hints greatly appreciated.

I found interesting the thing about using Filament for faster and more accurate viewport, sadly I tend to use mesh lights a lot more so it's still not very useful to me

The Blurst of Times said:

barbult said:

There has already been a lot of discussion about the Filament node, suggested settings, sample renders, bugs identified and reported, etc. Mec4D shared a lot of valuable tips for everyone months ago. Here is one thread where Mec4D suggests setting Filament ISO Scale to 0.56. That has worked pretty well for me. That thread is worth reading through from start to end, if you are interested in Filament. Maybe you got more and better tips in the webinar. If you are restricted from sharing information, you can at least share your successful renders, can't you? I'd enjoy seeing them.

The Filament tips in the webinar weren't so much about Filament itself, but how he used a Filament viewport as part of the process in evaluating decisions on how to light a scene for Iray.

The webinar output was Iray render, but he did make good use of Filament viewports to achieve the end result. (And in that regard, it was really interesting to see how he did the work even if the 3-point lighting theory is not unfamiliar.)

I keep meaning to try to learn how to do better work in Filament, but there hasn't been the time lately.

I'm glad you enjoyed it and found it useful in your workflow. 

barbult said:

There has already been a lot of discussion about the Filament node, suggested settings, sample renders, bugs identified and reported, etc. Mec4D shared a lot of valuable tips for everyone months ago. Here is one thread where Mec4D suggests setting Filament ISO Scale to 0.56. That has worked pretty well for me. That thread is worth reading through from start to end, if you are interested in Filament. Maybe you got more and better tips in the webinar. If you are restricted from sharing information, you can at least share your successful renders, can't you? I'd enjoy seeing them.

The Filament tips in the webinar weren't so much about Filament itself, but how he used a Filament viewport as part of the process in evaluating decisions on how to light a scene for Iray.

The webinar output was Iray render, but he did make good use of Filament viewports to achieve the end result. (And in that regard, it was really interesting to see how he did the work even if the 3-point lighting theory is not unfamiliar.)

I keep meaning to try to learn how to do better work in Filament, but there hasn't been the time lately.

There has already been a lot of discussion about the Filament node, suggested settings, sample renders, bugs identified and reported, etc. Mec4D shared a lot of valuable tips for everyone months ago. Here is one thread where Mec4D suggests setting Filament ISO Scale to 0.56. That has worked pretty well for me. That thread is worth reading through from start to end, if you are interested in Filament. Maybe you got more and better tips in the webinar. If you are restricted from sharing information, you can at least share your successful renders, can't you? I'd enjoy seeing them.

Richard Haseltine said:

Actually I said I would ask if it was OK - it seems reasonable, but I didn't ant to take it for granted.

Everything around information about the SP has been a challenge from a SP-holder's perspective. We've come to expect a certain information gap, but with the SP, it's felt a lot more uneven. The webinar itself was quite good, but then can we even share information that we learned from it? (not to mention the link) Like, everything other than the existence of the Filament node... how and why you might use the node, for instance.

It's weird having information, as a user, that I'm not sure I can share with other users.

It would be nice if SP holders had a space to discuss SP items like this and share SP-related information.

Muscleman said:

Silvhe said:

Imago said:

Sono anni che dico che DAZ Studio da dopo la 4.12.0.86 è sempre più rotto, ma vengo puntualmente preso per scemo da tutti.

Finalmente non sono più solo! Spero che la tua voce sia più "importante" della mia e che si decidano a fixare i bug. Se riesci a farti dare la 4.12.0.86 non lasciarla mai più e vivrai felice.

See figurati se mi danno retta. Però uno raccomandato ce l'abbiamo... Muuuusclemaaaan dove sei? Potresti dire una cosetta a quelli della DAZ?

 

Avanti, ditemi che posso fare...Imago non farmi un papiro chilometrico please...XD 

Impossibile non fare un papiro, Ragazzone...

Tutto questo accade in 4.15:

Come ripeto sempre, la timeline è rotta, se creo un keyframe muovendo un oggetto, il suddetto keyframe NON può essere mosso lungo la timeline se prima non seleziono la figura e poi premo "create keyframe" sulla timeline. In una animazione complessa dovrei fare questo centinaia di volte per ogni elemento che viene mosso...
Sempre nella timeline, il copia-incolla è frantumato, se copio e incollo anche solo un keyframe e faccio partire l'anteprima, tutti i valori della figura impazziscono e vanno su "n%n" o una roba simile e DAZ Studio freeza o crasha. Qualche volta non crasha ma l'intera scena sparisce nel oblio, non è possibile vedere nemmeno il grid di base. L'unica soluzione è quella di selezionare tutti i keyframes, impostarli su "linear" e poi di nuovo sul tweener che mi serve. E non sempre risolve. In una scena complessa dovrei farlo ogni volta per ogni elemento...
Frame selected, anni che lo ripeto, manda la visuale anche più lontano di come era prima di usarlo. Se mi serve inquadrare qualcosa perchè non devo risucirci?
Il Puppeteer non registra tutti gli alias e morph, perfino quelli commerciali venduti dalla DAZ stessa.
Gli Undo Stack, non registrano tutte le azioni, specie delle telecamere. Se fai l'errore di spostare una telecamera pensando sia il Perspective e poi pigi CTRL+Z per rimediare, non succede nulla.
Le ombre in Filament vengono spezzate di netto in base alla posizione della visuale e del orientamento del Dome. E' l'ultimo ostacolo al utilizzo "serio" del renderer.

Questi sono i peggiori, ce ne sono altri mille, ma ci si può anche convivere, tipo il fatto che le impostazioni dell'interfaccia vengono eliminate a caso o che le tab vengono riordinate in modo casuale da un caricamento all'altro.

Silvhe ne ha scovati altri, a quanto vedo, fatti fare la lista anche di quelli.

In ogni caso, non cambierà nulla di sicuro. Diciamo che questo è l'ultimo tentativo con poca speranza. Mi tengo 4.12.0.86 e basta.

Richard Haseltine said:

Masterstroke said:

Simple rules for any DS user:
No Mac,
no AMD
 

AMD GPUs are not useful for Iray (they can be used for dForce and Filament), AMD CPUs are fine.

True, sorry.
 

The Blurst of Times said:

Lyoness said:

I too really enjoyed the webinar.  I thought it was well presented and showed a nice simple way of setting up one classic lighting setting.  Based on that, it would be fairly easy to expand that out to other classic lighting setups. I found his tips on using filament really helpful.

Definitely.

Just the fact that there is a separate Filament Draw Options Node was incredibly useful to see, not to mention his preferred Filament node options (although I'm sure we'll all tweak those numbers for our own setups).

I mean... now I kind of understand WHY there's a separate Environment Node when you're also using the Filament Draw Options Node. I used to edit the Environment Node to make it work with Filament, and then change it back to re-render in Iray as a separate pass/layer.

Now that I know that I can modify the Filament Node and leave the Iray Environment Node settings alone?
That's a huge benefit. And then manipulating things in the Filament viewport (as separate from any other viewport, such as an Iray viewport)... that's useful as well.

Nothing to do with 3-point lighting, but from a workflow perspective, it was good stuff. It was useful seeing how he used Daz, and not just the 3-point lighting theoretical setup.

Hopefully we can share this information more generally because it really was useful to see.

yes. I've never discussed how to improve my filament renders and I don't spend TONS of time playing around. So most of the info was useful and really easy to blend into my current workflow.  I do love that he uses the HDRI for the fill like I do. I love using HDRIs in my renders.

Lyoness said:

I too really enjoyed the webinar.  I thought it was well presented and showed a nice simple way of setting up one classic lighting setting.  Based on that, it would be fairly easy to expand that out to other classic lighting setups. I found his tips on using filament really helpful.

Definitely.

Just the fact that there is a separate Filament Draw Options Node was incredibly useful to see, not to mention his preferred Filament node options (although I'm sure we'll all tweak those numbers for our own setups).

I mean... now I kind of understand WHY there's a separate Environment Node when you're also using the Filament Draw Options Node. I used to edit the Environment Node to make it work with Filament, and then change it back to re-render in Iray as a separate pass/layer.

Now that I know that I can modify the Filament Node and leave the Iray Environment Node settings alone?
That's a huge benefit. And then manipulating things in the Filament viewport (as separate from any other viewport, such as an Iray viewport)... that's useful as well.

Nothing to do with 3-point lighting, but from a workflow perspective, it was good stuff. It was useful seeing how he used Daz, and not just the 3-point lighting theoretical setup.

Hopefully we can share this information more generally because it really was useful to see.

The Blurst of Times said:

barbult said:

Another tutorial rehash of 3 point lighting? That doesn't sound very special. I hope there was more to it than that, for what you paid for the SP to get special tutorial content. 

It was useful in that there were practical applications with the current Daz, including uses for Filament windows, tools from 3d Universe (swapping to Base Mesh resolution for everything with a single button, which is especially impactful given that 8.1 figures tend to use higher SubD than Genesis 8 by default), a little bit of PhotoShop.

Did I NEED a tutorial for 3 point lighting? No. It was interesting to see how someone applies it in Daz, though. Everyone does their work differently, so seeing that, "Here is how I do it" was useful... not saying that I'll do it that way (I don't have the ability to crank out multiple Iray Viewports LOL), but it gave me things to think about.

(I think there were about 48-49 people at the peak of the webinar, and there were names you'd recognize in the audience chat as well.)

I too really enjoyed the webinar.  I thought it was well presented and showed a nice simple way of setting up one classic lighting setting.  Based on that, it would be fairly easy to expand that out to other classic lighting setups. I found his tips on using filament really helpful.

barbult said:

Another tutorial rehash of 3 point lighting? That doesn't sound very special. I hope there was more to it than that, for what you paid for the SP to get special tutorial content. 

It was useful in that there were practical applications with the current Daz, including uses for Filament windows, tools from 3d Universe (swapping to Base Mesh resolution for everything with a single button, which is especially impactful given that 8.1 figures tend to use higher SubD than Genesis 8 by default), a little bit of PhotoShop.

Did I NEED a tutorial for 3 point lighting? No. It was interesting to see how someone applies it in Daz, though. Everyone does their work differently, so seeing that, "Here is how I do it" was useful... not saying that I'll do it that way (I don't have the ability to crank out multiple Iray Viewports LOL), but it gave me things to think about.

(I think there were about 48-49 people at the peak of the webinar, and there were names you'd recognize in the audience chat as well.)

Hello everyone,

I am writing a script and want to allow the user to select which kind of rendering to do, or script-wise, the UserDrawStyle. I believe these are the choices you see on the viewport drop down (see image).

I belive the object is: DzUserDrawStyle - http://docs.daz3d.com/doku.php/public/software/dazstudio/4/referenceguide/scripting/api_reference/object_index/userdrawstyle_dz

And I can set which one in the viewport by typing in the name manually:

oViewportMgr.getViewport(0).get3DViewport().setUserDrawStyle("Filament (PBR)");

But how do I get all the selection choices so I can put them into a selectBox in my script?

Any help is greatly appreciated.

thanks