Loading...
> >

Outfit causing crash

kaotkblisskaotkbliss Posts: 2,914
in The Commons

First, a little background. I found some cool sets on sharecg but were 3dsmax (.max) files. The author also included .objs with them (yay!)

So I loaded to obj's in Hex and cut out the figures, cut apart the clothes to make different sections (shirt, pants, boots, etc.) then sent them over to Daz, rigged, shaded and rigged them.

Then I packaged them up and put them in my archives in case I ever needed to reinstall.

 

Problem is, one of my suits causes Daz to crash about 90% of the time but only when it's trying to load the entire suit at once. If I load it into the scene piece by piece, it seems to be fine, but if I try to load a saved scene that has the whole suit, or if I try to load my "full suit" preset, good chance Daz will crash.

If I open Daz, set the view to wireframe, then load the saved scene then it's loaded fine (so far) but it crashed again right after saving the scene.

 

I can't redestribute the pack as I've also added an undershirt for the suit to collide with and would violate the lisence, so I'm just looking for places to look for common errors first. I did check the log and seen some "known invalid rgb" errors and some "missing morph" warnings but I see those in scenes without the suit as well so I don't know if those are directly related to the suit..

Comments

  • DzFireDzFire Posts: 1,473

    Can you screen grab a picture from your modeler? might give us an idea what's happening.

  • kaotkblisskaotkbliss Posts: 2,914

    I did all the cutting in Hex, you want me to send the outfit to hex then? what info should I make sure is on the screen?

  • FistyFisty Posts: 3,416
    edited February 2016

    Load a clothing piece in Hex, go to Selection-> Select over-4-point faces.  If anything gets highlighted that's your problem.

    If that is indeed the problem either fix the n-gon in Hex and then update the figure geometry in DS with the fixed obj and resave your figure (probably will break any morphs you've made for the firgure) / or / use the polygon group editor tool to select all the polys of the figure, invert normals (it's somewhere in one of those right click or corner menus when that tool is active), then reverse the normals again, and resave your figure.  (Probably won't break your morphs)  DS will find any over 4 point polies and turn them into triangles when you tell it to reverse normals because it doesn't know how to do that function otherwise..  happy accidental functions.  =)

    Post edited by Fisty on
  • mjc1016mjc1016 Posts: 15,001

    You can triangulate the mesh another way...but it amounts to the same thing as reimporting it from a modeling program and will break the morphs.  It's very useful when importing a mesh for the first time...but you need to know if you have n-gons to begin with.

    On the Export dialog is a Triangulate n-gons check box. 

    So after you import the item, you immediately export it, with that option and reimport it...before you start rigging.

  • kaotkblisskaotkbliss Posts: 2,914

    I'll look into the n-gons, thank you.

    I'm pretty sure I already triangulated them though as I had already read in other posts that Daz hates them. But then again, I may not have.

  • mjc1016mjc1016 Posts: 15,001

    Another thing Studio doesn't like very well..no material zones.  If the item has none, it could cause problems (yes it should come in and be assigned a 'default' but sometimes that doesn't quite work).   And on the subject of Material zones, sometimes if the same polys are in more than one zone, it can cause problems (never had a crash with that one, though...but rather very odd behavior with materials).

    Stray vertices are also another problem.  Usually they don't lead to a crash, but rather odd faces shooting off into the distance or bridging two parts of an item.

  • kaotkblisskaotkbliss Posts: 2,914

    Thanks. I'm not sure how to check for those ones but as soon as I'm able I'll get that Hex screenshot up as DzFire requested.

  • mjc1016mjc1016 Posts: 15,001

    The stray verts is usually easy to spot...

    The materials problems, not so easy...but if you use the Geometry Editor and select by surface it can show up there (providing, that something with the materials isn't the source of the crash).

  • kaotkblisskaotkbliss Posts: 2,914

    I thought it might have been the materials because when I was trying different ones it ended up keeping the old and applying the new one some how. Anyways, I went into the dsf files and removed references to the old material and thought that had fixed it because right after it loaded fine, but then crashed again durring the next couple loads so that wasn't it :(

  • mjc1016mjc1016 Posts: 15,001

    Look in the log file...there should be something when it starts to load it.

  • kaotkblisskaotkbliss Posts: 2,914

    Here's the log file of the relavent part... not much there

     

    *** Scene Cleared ***
    File loaded in 0 min 4.1 sec.
    Loaded file: CyberSeraph_Full.duf
    WARNING: libpng warning: iCCP: known incorrect sRGB profile
    Loaded image bursts_0034_Bursts-18.png
    Saved image: C:\Users\kaotk\AppData\Roaming\DAZ 3D\Studio4\temp\d12.png
    WARNING: libpng warning: iCCP: known incorrect sRGB profile
    Loaded image bursts_0034_Bursts-18 TM.png
    +++++++++++++++ DAZ Studio 4.9.0.63 starting +++++++++++++++++

     

    The image "bursts" are from Ron's explosiones placed over a primitive cone for engine flame effect. 

  • kaotkblisskaotkbliss Posts: 2,914
    edited February 2016

    Here's the screenshot from Hex

    Screenshot.png
    1920 x 1080 - 274K
    Post edited by kaotkbliss on
  • kaotkblisskaotkbliss Posts: 2,914
    edited February 2016

    Ok, I'm pretty sure it's a texture issue. When I load a scene with the outfit in it, if the scene view is set to wireframe or smooth shading it loads fine. If I try to load with textures or change from wireframe/smooth to texture shading, it tends to crash.

     

    So I guess my solution is to send the parts back over to Hex and delete all the mat zones/UV mapping and redo it?

    In the UV mapping window off to the left (when open in Hex) if I delete the map area from there, is that enough or do I need to do more?

     

    *edit* or better yet, is there a way to do it in Daz so I don't have to re-rig the model?

    Post edited by kaotkbliss on
  • kaotkblisskaotkbliss Posts: 2,914

    I don't mean to post so much in a row, but I think I've narrowed it down to something to do with the wings.

    I loaded the body, then attempted to load the wings preset but Daz crashed. Then I tried to just load one of the wing tips and Daz crashed. There are no n-gons but when I sent it to Hex, the wing is invisible until I select it. Then if I deselect it, it turns invisible again :(

    I'm so lost I don't know if I will be able to fix this.

  • mjc1016mjc1016 Posts: 15,001

    You could try to remove all the textures or use a 'blank' Daz default shader preset (if you don't have on, create a primitive, select the surface and Save As > Shader Preset).

     

  • kaotkblisskaotkbliss Posts: 2,914

    Last night before I went to bed I tried a couple tests. I loaded everything up individually (except the engine flames because that was always like the last thing to load before crash in log file)

    Saved the test scene, and reloaded. Opened fine.

    Added the engine flames to the scene and resaved.

    Loaded the scene and it crashed. Tried again and it crashed again.

    Loaded it up using wireframe layout and applied the DS default shader to the sngine flames, resaved.

    Loaded the scene and it opened fine!

     

    So it seems the engine flames are a big part of it. (which I think I forgot to include the images for the flames in my package anyway)

    But That still doesn't explain the crash and invisibility in Hex with the wingtips so I think there's multiple issues going on.

  • JGreenleesJGreenlees Posts: 2,249

    you might have checked this already but mesh resolution, make sure it's not too high and that you don't have it set to high resolution in studio this can cause crashes on heavy figures

  • nonesuch00nonesuch00 Posts: 18,780

    Seems the problem then was the shader applied. That's the easiest way to crash Unity too.

  • kaotkblisskaotkbliss Posts: 2,914
    JGreenlees said:

    you might have checked this already but mesh resolution, make sure it's not too high and that you don't have it set to high resolution in studio this can cause crashes on heavy figures

    It looks like they are all default settings. I've never messed with those options in any scene/model I've messed with but Sub D is 1, resolution level is base, render sub d level is 1.

     

    nonesuch00 said:

    Seems the problem then was the shader applied. That's the easiest way to crash Unity too.

    Well, part of the problem. I still had the crash when loading the end part of the wing which is shaded exactly the same as all the pieces before it. I still have more testing to do on this part.

     

    I know how difficult it is to try and troubleshoot a problem you can't see firsthand and I really appreciate everyones input so far.

  • kaotkblisskaotkbliss Posts: 2,914

    YES!

    I know there are probably other errors in the file, but for now it's loading without crashing :)

    I had to delete my engine flame prop and rebuild it. (I had reset the texture on the primitive cone to DS defaults then manually re added all the textures back on, but it still crashed it. So I created a new cone and re added the textures and now no crashing)

     

    Thank you everyone :)

  • nonesuch00nonesuch00 Posts: 18,780

    congrats

Sign In or Register to comment.