I purchased Modern House 2 and Poser 2014 can't find files through the DSON importer or anyway. the first missing file is "First Floor Interior Parlor North Wall{b799e919-c7cc-ba32-35bd-0fa5c1b1798d}.obj" the file does not exist and if it does I can't find it. How do I fix this? The house will not load and it's supposed to be working for Poser as well as Daz Studio. Where do I go for help? Thanks, Sherrie

I'm not sure but the Modern House 2 here in the market place is Poser Only and the "First Floor Interior Parlor North Wall{b799e919-c7cc-ba32-35bd-0fa5c1b1798d}.obj" is not part of that product so, is it that product or ...

I think you should be more specific with the product description or a link. There are several modern house models and the one you are posting about is only for Poser. More info please.

Same problem here. I sent a message to the vendor (RPublishing) about it. Since sending it I had found where the OBJ's were hiding. I tried creating a Poser CRF from DAZ Studio and that didn't work either. It has to be something in the DUF file that is either corrupt or not set up properly because I've never had Poser prompt me for an OBJ file when using a Poser Companion File.

I usually get a prompt for a PMD (Morph) file that doesn't exist and just ignore it. If you try ignoring each of the error messages, it will take a long time to get through all of them because this house has a lot of parts.

I'm not messing with it anymore. I spent a good part of today trying to fix this and will wait to hear from the vendor.

By the way, it's called "Modern Home 2" not "Modern House 2." I think there's another vendor who has a model called "Modern House."

Edited to add: Modern Home 2

The .obj files are not included with the product, but are generated by the DSON importer, and should live in the Writable Runtime Folder specified in Poser's Scripts>DSON Support>Importer Preferences, under Runtime/DSON/auto-adapted/data ; drill down to the desired figure there.

WandW posted at 12:38PM Mon, 04 January 2016 - #4247101

The .obj files are not included with the product, but are generated by the DSON importer, and should live in the Writable Runtime Folder specified in

Poser's Scripts>DSON Support>Importer Preferences, under Runtime/DSON/auto-adapted/data ; drill down to the desired figure there.

I don't think you are understanding the problem. I have worked with DSON imports many times before and know how they work. This one is not working. Yes, it creates OBJ's after first running the DSON importer. However it should not be prompting to load and search for them when using the Poser Companion File because the newly created CR2 should already include references to those OBJ's. In the case of this model, it doesn't work this way.

Here are the steps I took. I tried reinstalling a second time to create these steps.

1. Loaded !Preload House and Lot Without Grass
2. DSON Importer starts
3. First window pops up asking to locate "First Floor Interior Parlor North Wall{b799e919-c7cc-ba32-35bd-0fa5c1b1798d}.obj"
4. Subsequent windows ask for the rest of the 90 OBJ's. It should not be doing this since the newly created CR2 should already have references to where these files are located. Also each OBJ file has it's own folder with a subfolder so if manually linking is done that is a lot of work for 92 OBJ's. It's not like they're all in one folder unless someone chooses to place them there.

Option 1:  Cancel then get prompted for the next 90 OBJ's.  Instead of going through that process, I had to close out Poser using Task Manager

Option 2:  I chose to go through all of the OBJ's and click Cancel for each one.  Fortunately it didn't seem to go through all of the OBJ's because I know I didn't cancel 91 times.  Just when I thought something was loading, Poser crashed.  I turned off my computer for a couple of hours then tried it again with the same results.

This is odd behavior for a PCF. My assumption is the DUF file has bad coding in it. Since DAZ Studio doesn't use OBJ's, I am assuming it skips over any references to it since it loads fine in DAZ Studio. The problem isn't with the DSON created PCF because I used both the one provided with the product and one I created myself from DAZ Studio. Neither worked so it has to be the DUF file creating all the problems.

No matter what process is used for this product, it is a lot of work for the end user to clean up. I even tried using Netherworks' Creator's ToyBox on the DSON-created CR2 (which was a mess) and it had problems. I use ToyBox a lot for PCF conversions and never had a problem like this before. Usually it does a great job and allows me to move OBJ references to its own Geometry folder. This is the only time it didn't and I don't blame ToyBox.

Poser is obviously not finding the .objs. referenced in the cr2. The question I was attempting to raise is, have they actually been generated, since they are not being found? Since you say they have been generated, there must be an issue with the filename or the path specified on the cr2. The PCF's are simply scripts that call the DSON Importer. The actual generated cr2s are in the same runtime as the generated .obj, under Runtime/DSON/auto-adapted/content_files; if one looks inside with Wordpad (I'm presuming you are using Windows) one can check the path in the reference near the top.

Still, one certainly shouldn’t have to go through this for a purchased product....

WandW posted at 8:55AM Tue, 05 January 2016 - #4247202

Since you say they have been generated, there must be an issue with the filename or the path specified on the cr2.>

Still, one certainly shouldn’t have to go through this for a purchased product....

That's what I told the vendor. I've tried installing several times including after deleting all the old install files.

I never had this problem before purchasing this model and I've converted hundreds of DUF files using the PCF. I would blame it on the DSON converter except I just converted several DAZ models a couple of days before purchasing this one.

The only problems I have had were afterward when sometimes parts of the model disappear or shift. I can name many instances of this with DAZ models, but no problems with having to find OBJ's while trying to install.

I'm using WordPad to look inside the DUF and see if there is anything unusual. I have a better understanding of Poser files than I do of DUF's.

Hello whbos,

Do you have all the same files (like shown in the attached image) in the same folder?

Are you loading from the Poser Character Library?

I will be glad to gift you a different product. Without being able to duplicate your problem, I just don’t have a good way of figuring out how to fix it. I have attached a screenshot of my Poser Pro 2014 loading the cr2 from Poser’s Character library, and then one after the DSON importer automatically does everything just like it normally does.

I’m very sorry for the frustration and inconvenience, and I wish I knew what was going wrong.

Just a wild thought, but try going to the poser icon on your desktop, right click and select "run as administrator" - then do as Rpublishing does above. Depending on your version of windows and the location the importer is trying to write too, what might be happening is that the importer is trying to right to a sub-directory of your program files directory, which your standard user login may not have write privileges for, causing the script to be unable to write the files needed, causing the problem you describe.

RPublishing posted at 6:30PM Fri, 15 January 2016 - #4247376

I just stumbled upon this a little late. I noticed the credit in my account a couple of days ago.

Hello whbos,

Do you have all the same files (like shown in the attached image) in the same folder?

I had the same files as your picture shows.

Are you loading from the Poser Character Library?

Yes I was and it didn't work no matter how many times I did it. It kept looking for Object files like I told you.

I will be glad to gift you a different product. Without being able to duplicate your problem, I just don’t have a good way of figuring out how to fix it. I have attached a screenshot of my Poser Pro 2014 loading the cr2 from Poser’s Character library, and then one after the DSON importer automatically does everything just like it normally does.

I’m very sorry for the frustration and inconvenience, and I wish I knew what was going wrong.

I posted in your private area that I exported the product from DAZ Studio to a Poser Scene file (PZ3) and I managed to get it to import in Poser without it prompting for Object files. It took a few tries because, like I said before, the textures weren't loading. The thing I don't understand is I had loaded a number of DSON files before and after your product without the same problem so there has to be something in the DSON file that is not interacting well with my computer.

I'm not using DSON anymore since I restored my system and reinstalled Poser to remove any traces of DSON. If a product isn't made for Poser I won't be buying it because the conversion process is too much work. Some DAZ models do not convert at all. The PZ3 exports seem to be the only solution for exporting props from DAZ Studio.

trobbins67 posted at 6:42PM Fri, 15 January 2016 - #4247514

Just a wild thought, but try going to the poser icon on your desktop, right click and select "run as administrator" - then do as Rpublishing does above. Depending on your version of windows and the location the importer is trying to write too, what might be happening is that the importer is trying to right to a sub-directory of your program files directory, which your standard user login may not have write privileges for, causing the script to be unable to write the files needed, causing the problem you describe.

Thanks for the suggestion, but I don't think that would solve the problem since I never had to run Poser as Administrator for other DSON products. This is the only time I had a problem like this. I'm using Windows 8.1 and Poser Pro 2014 64bit. The object files that were created from those installs were on an external drive where all of my runtime folders are. In Poser it didn't seem to matter where I selected them to go because they would install just about anywhere on that drive including other runtimes I didn't want them in.