geep opened this issue on Mar 10, 2009 · 20 posts
geep posted Tue, 10 March 2009 at 2:57 PM
Here's the situation:
In Poser:
Load the "Torus" prop from the Primitives Folder in the Props Library
Export the Torus to a Wavefront OBJect file named "Torus.obj
Open Wings 3D and Import the Torus.obj
......... Now the mystery ................
The Torus appears in the list of objects in Wings but has 0 polygons, 0 edges, and 0 vertices,
and is not visible !!!!!!!!!!!!!!!
Why ??????????????????????????????????????????????????????
??????????????????????????????????????????????????????????
??????????????????????????????????????????????????????????
Note - The Torus.obj shows up normally when Imported to Carrara and UVMapper.
Anyone? ..... Anyone? ..... Anyone? ..... Bueller? ..... Bueller? ..... Anyone? ..... Anyone? :blink:
Remember ... "With Poser, all things are possible, and poseable!"
cheers,
dr geep ... :o]
edited 10/5/2019
BAR-CODE posted Tue, 10 March 2009 at 3:03 PM
Its probable too Small for Wing to see it...
Try loading and scale it 5000 times in poser and then export it..
But the No edges polys etc etc seems to be a game breaker for my idea..
But just try it scale 5000 times... and see
Chris
IF YOU WANT TO CONTACT BAR-CODE SENT A PM to 26FAHRENHEIT "same person"
Chris
Winterclaw posted Tue, 10 March 2009 at 3:15 PM
Tried doing that with hexagon and got a read error whenever I loaded it. I'm guessing the .obj is corrupted somehow so not everything can read it.
One other thing: I was poking around the geometries folder in poser and there are two torii listed. Maybe that is part of the problem.
WARK!
Thus Spoketh Winterclaw: a blog about a Winterclaw who speaks from time to time.
(using Poser Pro 2014 SR3, on 64 bit Win 7, poser units are inches.)
Adom posted Tue, 10 March 2009 at 3:27 PM
Have no idea (yet).
I checked in Hex and got an error.
Then I wanted to load original obj for torus (from poser geometries) and same error as above.
:)
edit: oops! Winterclaw, I didn't notice you already mentioned about it:)
ockham posted Tue, 10 March 2009 at 3:27 PM
The torus.obj as exported has "fo" lines instead of "f" lines. After I
edited the file to make them all "f" lines, it showed up properly in Amapi.
From the official Wavefront OBJ format:
NOTE: Any references to fo (face outline) are no longer valid as of
version 2.11. You can use f (face) to get the same results.
References to fo in existing .obj files will still be read,
however, they will be written out as f when the file is saved.
Adom posted Tue, 10 March 2009 at 3:31 PM
And the case is solved:)
jdcooke posted Tue, 10 March 2009 at 3:33 PM
You can use a text editor to find an replace the "fo " to "f ".
good luck
Adom posted Tue, 10 March 2009 at 3:34 PM
@**ockham
**so if I corectly understood your note than after exporting from poser as obj all FO should be replaced with F but I got FO again. ?
ockham posted Tue, 10 March 2009 at 4:41 PM
How did you get the FO lines again? After running it through another modelling app?
Adom posted Tue, 10 March 2009 at 4:44 PM
First I loaded torus prop into Poser, then
I exported torus as obj in (note: from) Poser.
I opened that new obj in editor and FO were there.
ockham posted Tue, 10 March 2009 at 4:51 PM
Yes, that makes sense. The original obj (TorusThin.obz) has
the FO lines, so Poser just copies them on export.
After changing them to 'f' lines, other applications will accept the OBJ.
Adom posted Tue, 10 March 2009 at 4:55 PM
So it means that Poser is "not so clever" as those line should be changed after exporting:)
ockham posted Tue, 10 March 2009 at 5:02 PM
Yes, that's right!
Adom posted Tue, 10 March 2009 at 5:13 PM
Quote - Load the "Torus" prop from the Primitives Folder in the Props Library
Export the Torus to a Wavefront OBJect file named "Torus.obj
So there are two answers to above question:
I think nobody expected this:)
ockham posted Tue, 10 March 2009 at 5:30 PM
Yes. Poser's import/export functions haven't been modernized in newer
versions..... they are basically the same as in version 3.
geep posted Tue, 10 March 2009 at 8:37 PM
Thank you all for your speedy responses.
Come to think of it, I had this same problem several years ago and had completely forgotten about the solution.
Thanks again.
Please make notes about this solution so when I ask this question again in 2-3 years, you'll have the answer ready. :lol:
cheers,
dr geep <------------------------- feelin' kinda stoopid :sad: ... needs to up the memory pills, too.
;=]
Remember ... "With Poser, all things are possible, and poseable!"
cheers,
dr geep ... :o]
edited 10/5/2019
nickedshield posted Tue, 10 March 2009 at 9:38 PM
another way, without a lot of editing is to open the torus in UVMapper, do nothing, and save.
I must remember to remember what it was I had to remember.
geep posted Tue, 10 March 2009 at 10:22 PM
Excellent !!!
Thanks nickedshield.
cheers,
dr geep
;=]
Remember ... "With Poser, all things are possible, and poseable!"
cheers,
dr geep ... :o]
edited 10/5/2019
pakled posted Wed, 11 March 2009 at 6:49 AM
oh...I thought we'd discovered an interdimensional object...;) I've had strange things happen when importing objects from one program to another. I'll have to remember that stuff...thanks all (Pakled is not smart...;)
I wish I'd said that.. The Staircase Wit
anahl nathrak uth vas betude doth yel dyenvey..;)
nickedshield posted Wed, 11 March 2009 at 8:55 AM
@Geep
You are welcome.
One note for those who are using Hex. I found out I had to ungroup the imported torus before I could completely modify it.
I must remember to remember what it was I had to remember.