Old Zark stuff

wickedprince3d_fd273b40ac

Ok, so I still have a lot of really ancient bits and pieces in my runtime like this: https://www.sharecg.com/v/32682/view/11/Poser/Shackles-and-chains-colelction-for-Poser  ; and I've had these items forever. I'm not worried about the chains, they've never worked right as far as I can see, but the belt USED to. In fact I just loaded Aiko3 up in DAZ2.3 on my old WinXP machine and then loaded and parented the belt to her - no problem what-so-ever. But when I try to load the belt into a scene in DAZ4.10 it apparently causes everything in the scene to become size 0. If I increase the size of the belt to anything higher than 100% the scene returns to normal and the belt shows up. But if I parent it to anything, again the whole scene becomes size 0. At least that's what it LOOKS like to me. Can anyone please figure out what is up with this?

SixDs

I don't know specifically what DAZ Studio is doing there, but I have a pretty good idea regarding the why. That product, as its name states, is for Poser. Now, there is a great deal of older Poser content that works more-or-less fine in DAZ Studio, but that particular content states in its description "python scripts to help posing". Oops. Sorry, no python support in DAZ Studio - never has been. The other problem of scale is probably associated with the fact that it is in Poser units, not DAZ Studio units, which are not the same. If you really must use the belt, I would suggest that you simply import the .obj file for it into DAZ Studio, being sure to specify that it is using Poser scale (which it probably is). It will now be a static prop and you can scale/fit it to Aiko as you see fit. If there are texture maps, you'll need to set them manually in the Surfaces tab and adjust settings for DAZ Studio as necessary. Once satisfied, you could then export the object as a new one complete with the materials to an appropriate location. The morphs you'll need to forego, I'm afraid.

WandW

Python isn't involved here, as it isn't supported in Studio 2.3, either.  Nor are the units an issue, as Aiko 3, being a Poser figure (as are all DAZ figures before Genesis), loads with the same units.

If the belt is visible after loading it and increasing the scale, I would try saving it to the library as a .duf; File>Save As>Support Asset>Figure/Prop Assets.  Then start a new scene and try conforming it to Aiko and see if it works...

SixDs

OK, I messed around a bit with the belt and, just like you, loading it from the original .cr2 caused everything in the viewport to disappear, and dialing the scale to anything over 100% made everything re-appear. Bizarre. There is obviously something amiss in that .cr2 file, since the behaviour does not occur with any of the other parts. I have no idea why it would work in DAZ Studio 2.3. I would suggest that you load A3 in a new scene, then the belt, adjust the scale to 100%+ so that everything is visible, then adjust the belt to fit A3 using the X and Y scale sliders (since its made to fit V4 by default). Then, with the belt only selected, export it as a new .cr2, naming it waistbelt2 or somesuch, Restart DAZ Studio and load whichever scene you wished to use, load the new .cr2 that you saved for the belt and it should work as expected. You can parent it without issue. Once you are satisfied with the new .cr2, you could delete the original, then rename the new one the same as the original if you wished.

WandW's suggestion will work as well, except that you will need to convert the belt to a weightmapped figure first.

wickedprince3d_fd273b40ac

Sorry that I let this go for so long, I got sidetracked and totally forgot I put this thread up and I wasn't getting any heads-up notifications. I tried what WandW said after converting it to a weightmapped figure but I have no clue where it hid it. I followed ths save path she described but I don't know how to find the belt now so I can use it. I'll have to try SixDs suggested with the hopes that I do it right. I'm kind of a tech idiot and I usually have to try things a couple dozen times before I get it right.

 

So here's a bit more of the story: I have 2 desktops: a dual-core running WinXP that has an old copy of DAZ2.3 still installed on it; and. I also have a quad-core machine with Win10 and DAZ4.10 with a lot more ram that I'm doing my renders on. I just started playing around with the Genesis2 line. I've been using 2.3 pretty much exclusively for a very long time because I couldn't get an install of DAZ3.x that would work properly back when the dual-core was my main machine. Finally decided to upgrade some months back to see if the new DAZ would work on the quad. Now I'm learning my way around D4.10 and the Genesis figures and spending money like it's water. I've been at this rendering thing for around eleven years but as mentioned I was only using D2.3 and 3Delight. After all that time I've picked up a lot of stuff from various places and sometimes the thing I really need for a scene is one of those old ancient items like this belt.

 

Anyways if you look over the files that come with the set of items the belt is missing a couple - with one of the missing ones being mis-named. I made a copy of that file with the same naming convention as the rest of the pieces but there is still one file missing.

 

In any case as I mentioned: I can load the belt in DZ2.3 fine and since it's designed as a parentable object I can use it as intended in D2.3, but when I try to do anything with it in D4.10 it seems like it's zeroing the size in everything in the scene or something. Call it into a scene and the whole scene "goes away" until I increase the belts size above 100 - and then everything comes back. But if I parent it to any figure as it's intended to be used once again everything "goes away" and the only things that will fix it are to delete the belt from the scene or unparent it. I am guessing that the missing file is why the belt doesn't work when the rest of the set does - but I have no idea how the files work or how one would generate the missing file. It could theoretically be an error in the other files too but I'm not talented enough to have the faintest clue how to do anything with those files.