Tue, Nov 26, 8:54 PM CST

Renderosity Forums / Poser - OFFICIAL



Welcome to the Poser - OFFICIAL Forum

Forum Coordinators: RedPhantom

Poser - OFFICIAL F.A.Q (Last Updated: 2024 Nov 26 1:43 pm)



Subject: Couple Of Importing Questions


adinelt ( ) posted Tue, 27 July 2010 at 7:19 AM · edited Sat, 23 November 2024 at 5:34 AM
  • I am making a model in Cinema 4D and using Riptide Pro to export it to Wavefront OBJ.  Riptide Pro preserves materials and textures where Cinema 4D's native OBJ exporter does not.  I import the Wavefront OBJ file into Poser 7, and all materials and textures are there.  So far, so good.  However, when I spawn props in the Group editor, the newly spawned props lose all the textures and materials.  Is this normal behaviour and if not, is there some setting that I am missing to prevent that from happening?
  • Let's say I am building a complex model in C4D for someone to use in Poser 7.  I am sending small sections as they are being completed in Wavefront OBJ format.  When each section is imported into Poser 7, the sections do not maintain the same scale and position in relationship to previous sections that have been sent.  For instance, say I am modeling a car in C4D.  I finish building the main body of the car.  I export that and send it to the other person.  Then I build the doors in C4D, using the same body as previously mentioned.  The doors fit the body perfectly in C4D, I delete the body object then export the doors.  When the doors are imported into Poser 7, they are much larger and not aligned properly in relationship to the body that was previously imported into Poser 7.  As in question 1, is this normal behaviour.  If not, is there some setting or work around that can be used to prevent this from happening?

Thanks...
Al


Fugazi1968 ( ) posted Tue, 27 July 2010 at 7:45 AM

On the second point, when importing are you unticking

Center Object
Scale to % size of figure?

(something like that, cant remember the exact wording.

If not then the model will be place in the center point of the scene, and rescaled to whatever % you entered (default 100%) of the standard figure.

The only option I have selected when importing obj files is "Make Polygon Normals Consistent".

John,

Fugazi (without the aid of a safety net)

https://www.facebook.com/Fugazi3D


hborre ( ) posted Tue, 27 July 2010 at 8:40 AM

To answer the second question, it is normal behavior become of scaling differences between applications.  The best solution would be to import into Poser and export once scaling and positioning is achieved.


markschum ( ) posted Tue, 27 July 2010 at 8:40 AM

Yup, uncheck the percentage option, thats a strange scaling to the standard figure size. It can be useful for some props, but is a killer for what you are doing.


PhilC ( ) posted Tue, 27 July 2010 at 11:37 AM

The spawn props texture issue may be addressed by using a Python script. Details are in this forum thread:-

http://www.philc.net/forum/viewtopic.php?t=3150

Hope that helps :)


adinelt ( ) posted Wed, 28 July 2010 at 7:56 AM

Thank you everyone for your quick replies. 

It makes sense to turn off the scale option if it is going to scale each imported OBJ to the size of a human.  Will try that later on tonight.

I did try the script that PhilC linked to.  I could see it processing the different props and then hung part way through.  I eventually had to kill Poser 7.  I am running this in Windows 7 64 bit with 4 GB RAM.  Not sure if that had anything to do with it or not.

Also, PhilC, I was playing around with InterPoser Pro in an attempt to bring a Poser character into Cinema 4D, and I got a warning that several different 'temp00?' files were missing from the Wardrobe Wizard folder.  A quick Google search led me to your website.  Is Wardrobe Wizard required to bring Poser characters into C4D?  I believe it was the missing files that caused C4D to eventually crash during the import.  I was able to bring in other characters, but not the one that I wanted based on the Don character.  A work around is to export to OBJ, then import into C4D, but I then have to rig it and create all the actions for it (e.g. lip movement, blinking, etc.)

Thanks...
Al


estherau ( ) posted Wed, 28 July 2010 at 8:09 AM

 No, WW is not required to make IPP work correctly.
Love esther

MY ONLINE COMIC IS NOW LIVE

I aim to update it about once a month.  Oh, and it's free!


PhilC ( ) posted Wed, 28 July 2010 at 8:12 AM

Wardrobe Wizard is completely unrelated to C4D import.

Although Wardrobe Wizard will create temporary files during its process they will have nothing to do with the final model.

If your system is hanging it is most probably because the script is trying to write a file, temporary or otherwise, but you do not have sufficient administrative permission to do so. In my opinion, Windows continually makes it harder and harder for the user to actually use their computers. Under these conditions it would make sense to me for it to pop up a window saying that an application is trying to write a file but you the user have not as yet sacrificed the required chicken/bull/or first born depending on the size of the file. However it appear to take the view that all sharp objects should be kept away from small children least they hurt themselves so just sits there tapping its foot expecting you to "just know" what to do.

Drives me nutz :)


adinelt ( ) posted Wed, 28 July 2010 at 10:32 PM

Hi Phil,

I tried importing the file through InterPoser Pro again.  The file location that InterPoser is looking for is:

C:Program Filese frontierPoser 7RuntimePythonposerScriptsPhilCWardrobe Wizardtemptemp004.obj

I created the path thinking that maybe it needed it in order to create the temp004.obj, but the dialog box that appears is trying to load that file.

I searched my entire hard drive for temp004.obj, and it doesn't exist anywhere on it.

As for the script that spawns the props and keeps the textures, I think the problem may be with the focus being taken away from the script window while it is running.  Once I closed anything that could interfere with the focus of the window running the script, it ran to completion.  This is something that I will note for the future.

Thanks for creating such a useful script Phil.

Al


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.