thanks for updating us about this just installed and started it up and just looking at the menus looks like we have a lot more options even remembers shows where I've saved to on my other drive. Got a question there is a custom section that has seperate? options for besides face, arms, legs and torso I clicked the buttons and it looks like you can do something to those textures? 

You can load up any texture you want now! So you can use Victoria 8 textures instead of base Genesis 8. Or Greylien. Whatever you want, as long as the UV matches the base. I have not experimented much with this yet myself. FG still seems to work best with the base textures. But now you can edit the base textures to your liking and have FG use them instead.

 

Does this mean i first load victoria 8. Then set the uv to base. The save it. Then load up FG with the face i want then set it to custom and load victoria textures and export then open the file i saved and load in the face dail and tExtures? Or is there another way? I find that if i use the genesis 8 basis model and load in FG textures the face loses its general sructure of the pores... so when you zoom in there is less detail then normal

No, what happens is you can link to whatever texture you want to use before you export the morph/texture settings.  

If you are literally editing the item then no, because using GoZ removes grouping (and surfaces). GoZ is mainly set up for morph creation, which should not create a new model in the scene but just add a property to the existing model. More substantial editing is better handled via OBJ export/import.

Based on what I've observed, it seems like the process is something like this. If somebody knows better please enlighten me:

• When you hit Render, raw scene data is read from disk into system RAM. On my 64GB system I've loaded multiple scenes until this value gets over 30GB in order to stress my system.
• Once it's all in system RAM, the CPU gets busy, and the Iray code within Studio starts converting that raw scene data into Iray calculations (light bounces and stuff). This Iray data ends up being a fraction of the memory requirement of the raw scene data. In my case, with a total of 19GB VRAM capacity across two GPU's (11 plus 8), the VRAM fills to around 17GB, or 1GB below each GPU's capacity. So VRAM usage is roughly half of the raw scene usage in system RAM. 
• Once it's converted to Iray, the code checks to see what memory is available by summing all the available GPU VRAM. This number varies based on stuff like:
  • Whether other apps are using some portion of the VRAM on any card (like running a monitor, etc.), making the available VRAM  on that card less
  • Some overhead required for the GPU driver and other stuff needed to run and schedule each GPU
  • The total VRAM requirement. Maybe it doesn't need all available VRAM from all cards for the particular scene
  • Other stuff
• Once it sees what's available it allocates/grabs the VRAM, then starts sending the iray calculation code via PCI to the GPU's, using all available VRAM as one big chunk.
• Once the entire scene is loaded into the GPU's and ready to be calculated, the user sees the first grainy Iray render in the preview window. 
• After that, the GPU's just keep cranking, with no more transfer into or out of VRAM.
• When enough calcs have been done to make an updated preview image, a new image is sent to Studio and to the monitor.

I'm especially unclear on the first couple of steps above, since when you load a big scene, before you hit Render, the scene is visible, but doesn't load up system RAM very much. Not sure how that happens...

Interesting theory.  I have 32 gig of RAM, and like you say, when I'm doing a large scene, my RAM loads to around 20 gig, or 2 gig less than the combined VRAM of my 1080 Ti's.  However, when I run 3 cards, it still only loads to 20 gig, and by your theory it should load to 25 gig.  On this particular scene, the 980 Ti ran for a while then crashed.  On a smaller scene, that allows the 980 Ti to run to completion, the RAM only filled to 11.9 gig.  The cards are seeing 5.5 gig, 5.1 gig and 4.1 gig respectively.  So 14.7 gig all told.  Minus 3 gig, 1 for each card, is around the 11.9 gig of RAM ... so it seems that there are other calculations that the system is doing.  In the first case, something is telling the system that the scene is too large for the 980 Ti, and so the RAM loads to accomodate the 1080 Ti's.  Why the 980 Ti runs at all for a while is still a mystery.  It should have been precluded from running at all, and maybe it would have been if the scene was a gig larger.  When it's allowed to run, sometimes it finishes...but when it runs for a bit and then fails, all 3 cards crash to CPU.  When it's not allowed to run at all, the 2 bigger cards finish the render.  That may answer my crashing question.  The scenes were in that in between place that almost allows all 3 cards to run, but not quite.

It is noteworthy that my RAM stays at whtever the load size was until the render is done.  I would have thought it would flush itself but it doesn't do that until the scene is completed.  I batch render, and when the scene finishes, the RAM flushes and then loads up again for the next scene.

Sculpted morphs are actually pretty easy with more modern meshes/rigging... but not the Millennium Dog, which may be why folks have had trouble in the past.

All you have to do is export JUST the dog (not whiskers) zeroed out, base resolution.

Then you do Morph Loader Pro to bring it back, and that... pretty much does it. If you are using the base dog, you don't have to do anything special. Then turn on the morph (may want to change the location in Parameters from Morph Loader to something nicer, like Actor/Breed or something), Edit mode, ERC Freeze the morph, then save the morph as a Figure/Morph asset.

If you are starting from a dog with actual morphs dialed in already, at the Morph Loader Pro stage you want to expand the options and click 'reverse deformations' to, well, reverse deformations.

There might be a detail or two I'm missing, but that should do it. You can go look up how to use Morph Loader Pro elsewhere for a more rigorous description with screenshots.

But Millennium Dog... woof. I actually had this elaborate alien dog morph made up for MilDog at one point, but trying to share the morphs for it was next to impossible.

In GenX2 "Morphs" tab , is your new morph listed ?

Hello,

I am writing a script which needs to get all the vertices of a geometry.

This action can be done by writing a loop using a myGeometry.getVertex(i).

This loop takes 5 seconds when the mesh has 350,000 vertices.

Is there a function like myGeometry.getVertices() which would be able to transfer all the vertices in only one function and which would make this action faster.

I thank you for your replies.

 Iray doesn't care about rigging or morphs - and sends that to the GPU.

Ahhh...thanks...That's what I was trying to figure out, what scene stuff was unnecessary to transfer when rendering. 

BTW, I'm trying to figure out what "uncompressed" means when it comes to textures. Presumably most are JPGs, which by definition are compressed. And I'd think the renderer needs high-res textures to calculate the image. So if you compress the already-compressed JPG textures you're losing definition in your image.

Hmmm.....

Iray has its own compression routines, the thresholds at which they are applied are set in the Advanced tab of Render Settings.

Someone else needs to fill in the gap of my memory.

I have a slider in my list of Parameter settings that slides between male and female.

I've turned creatures that were missing a male/female character into the opposite gender.

I can't remember what I bought or how it got there and I don't remember it always being there.

Which is why I think it's attached to an actual item in the store.

Someone clued me in before, but damn, I'm blank.

Oh man, someone has to know about that, but that's my suggestion -> turn the females into males.

That should do it.

----------

And there's a UV Swap product(s) that lets you transfer the "skins" or textures.

That should get you a consistent material(s) look for your characters.

Someone should chime in shortly with the exact stuff cause my brain is fogged right now and I can't recall.

Here's a quickie. Nothing too fancy with lights and setup... I just wanted an excuse to put the Hellhound next to the French Bulldog.

The Hellhound could have been a great ugly dog morph, but the horns are something you'd have to deal with. Maybe a head of hair would help (if you took out the horns)...

it looks like those other vertices are welded to some of the ones you select

the only way you could move parts of it is using magnets or rigging, or reweld the whole thing which could destroy the UV mapping.

Thanks for answering.

I don't think it's that, because if I use "grow selection", it works perfectly. The problem is only with "soft selection".

I just found a way: I tried the various settings for the reimport of the obj file and found that selecting "Create a Polymesh per Material" solves the pb. There's only one material so it creates only one mesh, as with the default setting ("Create a single polymesh"), but this way the soft selection works. Don't ask me why ...

Of course there's no rigging anymore, but I think I know how to put it back with DazStudio. And UV mapping is still here !

you could load it in DAZ studio on the top via morphloader and save it as a morph asset

make sure is base resolution 

check with an obj import if it's the same scale and position 

Best I can do with the Doberman with the tools inside DS. :) Had to take a d-former to the neck because there's no morph to make the neck more slender...only longer. There's a lot of scaling around the body too.

Laurie

 

 

Looks good but i'm not an expert. Looks like it might be easy to morph into a collie.

If I could get a grip on the morph imports and stuff inside DS, I'd take it into Hexagon and just go nuts. But where I always had an easy time in Poser with morphs, DS seems to be more of a challenge for me (I've had some really crazy accidents....lol). Things just aren't as straight forward ;).

Laurie

Best I can do with the Doberman with the tools inside DS. :) Had to take a d-former to the neck because there's no morph to make the neck more slender...only longer. There's a lot of scaling around the body too.

Laurie

 

 

Looks good but i'm not an expert. Looks like it might be easy to morph into a collie.

Best I can do with the Doberman with the tools inside DS. :) Had to take a d-former to the neck because there's no morph to make the neck more slender...only longer. There's a lot of scaling around the body too.

Laurie

True, the claws on those dogs look like bear claws!

Is there a morph to make them smaller?

Yes, -100 for longer & +100 for clipped (but they really look shorter, not clipped)

Cool! Thank you! 

Thank you for the nice comments, Novica and L’Adair.  And thanks, Novica, for the help...I’ll give that a try.  I don’t like the claws either, I figured I’d try removing them in Photoshop, but I’ll for sure use the morph to make them shorter.

True, the claws on those dogs look like bear claws!

Is there a morph to make them smaller?

Yes, -100 for longer & +100 for clipped (but they really look shorter, not clipped)

True, the claws on those dogs look like bear claws!

Is there a morph to make them smaller?

No, the gaming industry uses tools like bumps, normal, displacement and so on because it's faster, easier, more accurate and lets them automate more of the process then hi-res sculpting because their old work flow is high-res sculpting to lo-res model plus those various geometry image maps for details.

That approach makes for smaller downloads, lets LOD be a function of GPU capability and not something that requires extra storage and work to create for pre-inclusion, and so many other advantages that I wonder when they are going to come up with 3D models that are nothing more than a set of mercator and/or some other styles 2D projection maps as appropriate for the data that are put together at runtime at a level of detail that the GPU the SW is running on can handle. 

HUH?? I didn't understand a word you just said...

Exactly. The process is low-res, then add in high res details. The normals come from the hi-res details so the mesh can stay low poly. That's why if you think you can sculpt hi-res and get a HD morph, you're absolutely wrong.

Where is G8 better than older figures? Good question. When I saw G8 first I noticed no difference. I bought a heavily reduced Lucas8 and Stefanie8 out of curiosity and was annoyed about the new base pose and the difficulty to use old stuff with them.

The latter problem was solved with the change to 4.10. Any old clothing fits G8 well. It is especially nice that I can use Genesis stuff on G8 much easier than on G3, out of the box.

To the former question, "G8 better than G3?", over the time I felt the difference mainly in the shoulder area in some positions. G3 is better than G2 here and G8 is better than G3. If you make only close-ups or use certain positions it may not be even noticable. And perhaps it depends also on what figure of the G8 family you use, what body morphs and so on.

The thing is that some of the morph packages can overcome the shortfalls in the standard G3 figures and characters. I mean the aforementioned Zev0 packs and I also recently bought the Musculature HD Morphs Bundle which has a nice discount of 70% (still so, I've just checked). Together these add realism to any G3 character but that requires a bit of slider-pushing. That, for me, is great fun but I guess others prefer to buy pre-made characters rather than dialing-in their own creations.

 Iray doesn't care about rigging or morphs - and sends that to the GPU.

Ahhh...thanks...That's what I was trying to figure out, what scene stuff was unnecessary to transfer when rendering. 

BTW, I'm trying to figure out what "uncompressed" means when it comes to textures. Presumably most are JPGs, which by definition are compressed. And I'd think the renderer needs high-res textures to calculate the image. So if you compress the already-compressed JPG textures you're losing definition in your image.

Hmmm.....