Trouble with Maclean's Streets

dougsnashdougsnash Posts: 7
edited December 1969 in New Users

I am running Daz 4.6.1.39 in Windows 8.1. I have installed Maclean's Streets using the Install Manager and it tells me it installed two packages, one being a "Streets" package and one a "Streets Studio CF" package. Initially, I am only able to find about half the content of the streets package in a Content Library directory /Maclean/exteriors/streets_presets. Using the browse-to location feature in the Install Manager I was able to locate the missing Streets components and copy them into another sub-file beside the Streets_Preset file which I named "Streets". After re-starting Daz both directories show up under "Exteriors" in the Content Manager and I am able to find the complete set of streets content in the two files. Unfortunately, when I click on any of the content in either file folder it does not load. I have clicked on all of the icons in both files; some of icons give a "must click on object" error but most do absolutely nothing. Most of the Streets package content is .DSA files, could this be why they won't load?

This is not the first time I have encountered this kind of mysterious failure to load error with Daz content since I "upgraded" to Windows 8 (thanks a lot Microspoof). I had similar issues with V4 and V4.2 but was able to manually move some files around and get most of that working. With Streets, however, I am not having any success manually moving things around to fix the issue.

I've tried Streets on a Windows 7 computer with the same version of Daz and it worked fine but I can't get streets to work on my home machine with Windows 8.1.

Does anyone have any ideas?

Doug M

Comments

  • fixmypcmikefixmypcmike Posts: 19,583
    edited December 1969

    What you are seeing is the DAZZ Studio material presets, which need to be applied to the actual props. The props themselves will be in Content Library > Poser Formats > [your content folder name] > Props

  • dougsnashdougsnash Posts: 7
    edited December 1969

    I understand the the material presets are what is showing up in the Streets Presets file. The problem is there is no mention of Streets in the Poser/My Library/Props folder where I also would have expected it to appear. There are other items located in the Props directory (the other content I would expect to find there) but no Streets.

    I'll try manually copying the "Streets" folder to the same location as the other content and see if that works.

    Doug M

  • JaderailJaderail Posts: 0
    edited December 1969

    These are the 4 Streets you get, you must use them to build the sets you want....

    Capture-001.png
    301 x 482 - 120K
  • macleanmaclean Posts: 2,438
    edited December 1969

    Thanks to everyone for replying.

    Doug,

    I PMd you before I saw this thread, but as I said in the PM, the issue seems to be that you're trying to load the presets and the Poser content isn't showing up.

    You mentioned that you do see some of the props, but not the streets? Is it possible the download was corrupt? I don't understand how some show up, but not others.

    What's the installer size? I have 2 installers. Poser = 57.9mb and DS = 6.33mb. If yours are different, it might be worth downloading again.

    Let me know how you get on.

    mac

  • dougsnashdougsnash Posts: 7
    edited December 1969

    Hmm. the plot thickens. I checked my Runtime/Library/Props hard drive directory (where the Poser content lives) and found the directories for the few items which show up in the Content Library under Poser but there were also several other long lost items living there as well. Turns out this is where I'd manually copied the Streets folder from in the first place. For whatever reason the content showing up in the Runtime/Library/Props directory was not all showing up under the Poser data in the Content Library.

    Just to try something new, I made another copy of Streets and placed it directly in the Runtime/Library/Props directory. It still did not show up in the Poser/Props Content Library but that didn't really surprise me

    Next problem is, the .pp2 files were not showing up in any of the Streets Content Library directories. The .pp2 files were in the hard drive directory folders as they were supposed to be but were unassociated file types in windows. I manually associated the .pp2 files with Daz and then when I clicked on one of them, the streets scene opened is Daz. Yeah, progress.

    Next I opened the file association tab under Properties. The Runtime/Libraries/Props directory was not listed under the Poser content in the associations list. I added this directory to the Poser list and amazingly all of my streets content now shows up under the Poser Content in the Content Library (along with a bunch of content I'd forgotten I even owned). I am mow able to add the Streets content to the workspace.

    Thank you both for all of your help.

    Doug M

  • mjc1016mjc1016 Posts: 15,001
    edited December 1969

    [quote author="dougsnash" date="1391170159" The Runtime/Libraries/Props directory was not listed under the Poser content in the associations list. I added this directory to the Poser list and amazingly all of my streets content now shows up under the Poser Content in the Content Library (along with a bunch of content I'd forgotten I even owned). I am mow able to add the Streets content to the workspace.

    Thank you both for all of your help.

    Doug M

    Ummm....you should not have to add specific directories like that, unless you have nested Content folders. You probably have something like this...Content>Runtime>Runtime...

    Post a screenshot of your Content folder, from your OS file manager, with the subdirectories showing...

  • dougsnashdougsnash Posts: 7
    edited December 1969

    The problem with my data structure might be the hard drive arrangement in my computer or else it might be a feature of Windows 8. I have a small SSD for my primary boot drive and thus have to install all of my DAZ content on a secondary drive. I have encountered this issue of having to manually add a directory into the content database in the past (with V4 and 4.2 if I remember correctly.).

    I think I am really going to need to go through and clean up my content library as this incident has shown me there is a bunch of content I've paid for in the past that I can't access.

    Thanks everyone for your help and suggestions.

    Doug M

  • macleanmaclean Posts: 2,438
    edited December 1969

    Well, at least you're able to see the files now. But I think mjc is right. It sounds like the directories aren't nested properly.

    mac

  • mjc1016mjc1016 Posts: 15,001
    edited January 2014

    dougsnash said:
    The problem with my data structure might be the hard drive arrangement in my computer or else it might be a feature of Windows 8. I have a small SSD for my primary boot drive and thus have to install all of my DAZ content on a secondary drive. I have encountered this issue of having to manually add a directory into the content database in the past (with V4 and 4.2 if I remember correctly.).

    I think I am really going to need to go through and clean up my content library as this incident has shown me there is a bunch of content I've paid for in the past that I can't access.

    Thanks everyone for your help and suggestions.

    Doug M

    No, not anything to do with Win8/multiple drives...unless there's a permissions problem.

    The symptoms you are having, most often, indicate a nested Runtime (if you were having the same problem with DS only content, then it would be completely nested content directories).

    You shouldn't have to map any deeper than the top-level of the content directory...

    I've got 4 primary content directories and they are mapped...

    P;/Content (that's my old DS3 stuff)
    P:/My Library (DS4)
    P:/Poser
    P:/mrsparky

    And that's it...no 'deeper' mappings. And I've got the same mappings in both DS and Poser formats...except I left the Poser one off the DS formats, because there is no specifically DS content in that one.

    I've also got 2 'temp' ones that keep wanting to add themselves whenever I update/rebuild the database/etc...

    But if you have nested folders...like that Runtime>Runtime (or Content > Runtime > Content) then everything in the 'nested' Content/Runtime won't be found, because the search stops when the first 'level' of Runtime is found.

    Post edited by mjc1016 on
Sign In or Register to comment.