Thu, Nov 28, 7:03 AM CST

Renderosity Forums / DAZ|Studio



Welcome to the DAZ|Studio Forum

Forum Moderators: wheatpenny Forum Coordinators: Guardian_Angel_671, Daddyo3d

DAZ|Studio F.A.Q (Last Updated: 2024 Nov 26 6:59 am)



Subject: Strange issue with mesh 'spiking' in D|S


Blackhearted ( ) posted Thu, 23 August 2012 at 11:44 AM · edited Sun, 24 November 2024 at 2:06 PM

file_485604.jpg

hi folks,

i have had two D|S customers report an issue with my GND4.2 bikini bottom.  apparently when loaded in D|S it loads with spiked polygons all over it.

does anyone have any idea why this is happening, so that i can release a fix?

the attached image is from Studio 4 64-bit.  ive never seen anything like this before. the bikini is supposed to look like this

cheers,
-Gabriel



Bejaymac ( ) posted Thu, 23 August 2012 at 1:13 PM

Is the mesh unwelded and the morphs in .PMD ?


Blackhearted ( ) posted Thu, 23 August 2012 at 1:32 PM

morphs arent in a PMD - everything is distributed in CR2 format.

the bottom has unwelded verts - but so does the top and the top seems to work fine. both meshes in the update have been unchanged since 2008 (when the original product was released).

a lot of people own it and so far only two D|S 64 users have complained about the spiking.



Ian Porter ( ) posted Thu, 23 August 2012 at 2:33 PM

I have this bikini and I have just tried opening it in DS 4.5. It opens fine without spikes. I downloaded a new copy from my account here and it worked fine for me.

I tried a variety of things on it. Converted to SubD fine, Triangulated  fine, Applied Smoothing  fine. I treid most of the morphs and they work as expected. I was not able to get spikes or any strange effects. This is with the bikini loaded into the runtime folder, within the DS content library.

If the people with problems could describe exactly how they are loading it I would be happy to try to replicate the problem. Failing that, perhaps one of them could export the spikey object and email it to you, so you can see what has changed?

 

Cheers

Ian

 


Blackhearted ( ) posted Thu, 23 August 2012 at 2:35 PM

thank you very much Ian!

i will direct both of them to this thread,

cheers,

-Gabriel



Bejaymac ( ) posted Thu, 23 August 2012 at 2:55 PM

4.0 has problems with any figure/conformer that has an unwelded mesh, as it auto-welds it on import, this changes the vertice count, which causes some morphs to explode (usually those in PMD).

They altered it in 4.5 so that while it still welds the mesh it adapts the morphs to suit so they no longer explode.

However if that's the default unposed/unmorphed shape then it shouldn't have exploded in the first place, so that one has me stumped as to why it happened.


Blackhearted ( ) posted Thu, 23 August 2012 at 3:00 PM

^that is a morphed shape. and you may have stumbled upon why the bottom loads exploded and the top doesnt.

the top loads with the classic 2008 mesh and CR2, but with a dozen or so additional FBMs that are dialed to zero by default.

for the bottom i included several styling morphs which change the base shape - such as one to spread the straps, change to a brazilian back, etc. in the CR2 some of those are dialed to varying strengths to alter the bikini bottom when it loads.



Ian Porter ( ) posted Thu, 23 August 2012 at 3:13 PM

You are welcome Gabriel. I am in the UK, so apologies if I am offline sleeping while you guys are having fun. I will keep an eye on the thread while I am awake. ;-)

Bejaymac. I was not aware DS 4.0 did that, but I don't have it installed now so can't compare. It would be useful to know which version of DS the two users have.

It is noticable that the straps on the right side, on the screenshot look normal, for some reason...

The only mesh explosions I have seen so far in DS 4.5 was if I loaded an old scene created in DS 4 into DS 4.5 and than saved it as a scene from 4.5, but it looked a lot worse than the screenshot.

 


Blackhearted ( ) posted Thu, 23 August 2012 at 3:20 PM

i directed the original customer who noticed the issue - and took that screenshot - to the thread, hell be replying as soon as he gets home.

many thanks to everyone for helping figure this out.

cheers,

-Gabriel



theglennk ( ) posted Thu, 23 August 2012 at 8:20 PM

The same objects which loaded with errors in Studio 4 load properly in 4.5. All of the morphs seem to work properly, but not automatically. The preset morphs also load correctly.

I did not re-download or reinstall the content, I would agree that Bejaymac nailed it in one.

Glenn


kadix ( ) posted Mon, 27 August 2012 at 1:07 PM

I agree with Beyjemac,

Facing this problem, you are sure that there is a problem in vertex "indexes", so either it comes from using a pmd, or from a change of vertex by the software itself. Glad you solved your problem.


RLSprouse ( ) posted Thu, 30 August 2012 at 9:26 AM

Hi Gabriel (and all).  Glad to see you are aware of this and will be addressing it.  I had exactly the same result when I tried to use the bikini.

Hope you are able to fix it.

  ~ Russ 


cedarwolf ( ) posted Mon, 03 September 2012 at 10:53 AM

file_486033.jpg

Could that explain this: 

I don't have the spike problem pre-render but I do post-render.  It's dynamic cloth for DAZ Studio, I'm using 4.5 Pro (the newest download) and the preinstalled Dynamic Cloth plug-in because I'm saving to purchse the full plug-in.


Zev0 ( ) posted Thu, 06 September 2012 at 12:28 PM

If that is dynamic cloth, then I think you just need to add some collision smoothing. Try changing your dynamic cloth setting so the clothing folds arent so stiff or increase the steps.

My Renderosity Store


cedarwolf ( ) posted Thu, 06 September 2012 at 4:41 PM

Okie doke.  I'll have a look at the settings again.


Privacy Notice

This site uses cookies to deliver the best experience. Our own cookies make user accounts and other features possible. Third-party cookies are used to display relevant ads and to analyze how Renderosity is used. By using our site, you acknowledge that you have read and understood our Terms of Service, including our Cookie Policy and our Privacy Policy.