One man sub

[Eddie Paul]

Here is a sub I built for a project I am working on

[Innoventive Software, LLC]

Thanks for sharing this, but the .u3d file (user 3d file) you uploaded references "="User Objects\One man sub with color" which you didn't upload, so unfortunately no one can use or see this object. If you could also upload that missing file, that would be great.

[Eddie Paul]

Thanks for sharing this, but the .u3d file (user 3d file) you uploaded references "="User Objects\One man sub with color" which you didn't upload, so unfortunately no one can use or see this object. If you could also upload that missing file, that would be great.

I am new at this and still don't understand how to uplaod the files I will work on it .

[Innoventive Software, LLC]

Thanks for sharing this, but the .u3d file (user 3d file) you uploaded references "="User Objects\One man sub with color" which you didn't upload, so unfortunately no one can use or see this object. If you could also upload that missing file, that would be great.

I am new at this and still don't understand how to uplaod the files I will work on it .

No worries. Basically there are two types of object files you can create in FrameForge 3D Studio -- a User Object (which has the extension .u3d) which is a bunch of standard Frameforge 3D Studio Objects (typically from the building blocks folder but they don't have to be) glued together. All that is saved in the .u3d file is a "blueprint" about how these objects are glued together, what their orientations, sizes, colors, textures and so on are. When the user drags this virtual object onto the set it is autoamtically rebuilt from the object library using this "object blueprint."

You can, however, import a wrl or convert a glued object to a true FrameForge 3D Studio 2 object which results in a 3dxf file which is a real new object not found in the normal object library. What you appear to have done is a mix of the two -- you created a true FrameForge object then applied some textures to it and created a virtual object that referenced it.

But without that referenced true FrameForge object, then this blueprint .u3d file isn't particularly useful.

[Eddie Paul]

Thanks for sharing this, but the .u3d file (user 3d file) you uploaded references "="User Objects\One man sub with color" which you didn't upload, so unfortunately no one can use or see this object. If you could also upload that missing file, that would be great.

I am new at this and still don't understand how to uplaod the files I will work on it .

No worries. Basically there are two types of object files you can create in FrameForge 3D Studio -- a User Object (which has the extension .u3d) which is a bunch of standard Frameforge 3D Studio Objects (typically from the building blocks folder but they don't have to be) glued together. All that is saved in the .u3d file is a "blueprint" about how these objects are glued together, what their orientations, sizes, colors, textures and so on are. When the user drags this virtual object onto the set it is autoamtically rebuilt from the object library using this "object blueprint."

You can, however, import a wrl or convert a glued object to a true FrameForge 3D Studio 2 object which results in a 3dxf file which is a real new object not found in the normal object library. What you appear to have done is a mix of the two -- you created a true FrameForge object then applied some textures to it and created a virtual object that referenced it.

But without that referenced true FrameForge object, then this blueprint .u3d file isn't particularly useful.

I will try it again.

[Eastojamson]

Three are usually cheap Ralph Lauren available for sale each and every time you wish to buy. Zwembaden aanleg