Simply, the FBX C4D exporter is buggy: the bigger problem is the texture
exporting in this format.
In fact, no textures fbx sdk compliant section is exported from C4D in a
correct way. Osg convert plugin isn't able to interpret the fbx texture section
correctly, but this problem seems to be kn
Can you tell me more about the incompatibility of Cinema 4D with 3rd party
software? I have been instructed by one of my peers to try and create a few
menus combining features in C4D and Blender, but I am becoming a bit deterred
based on your statement.
--
Read this topic online
In my experience I have no found any problem about geometry. I don't know about
animation even if a simple rotation "animation take" has worked fine in the
past, but is a too much simple example.
However, no problems with geometry.
sth wrote:
>
> we ditched FBX for C4D export completely, beca
Hi,
Am 28.10.10 10:34, schrieb Dario Minieri:
> Someone else has a similar experience about fbx files from C4D?
we ditched FBX for C4D export completely, because we had missing
geometries / vertices, wrong animations, etc. And the culprit was
cinema4d, because even the FBX-viewer for Quicktime co
Hi,
I want to update this post to update any interested peoples on the situation.
It seems that, in fact, the FBX file 2010.2 exported by cinema4d (R11, R11.5,
R12) are not compliant with the autodesk fbx format for some reason.
The QTFBXViewer is able to visualize the object geometry but not t
Hi Dario, if the file appears correctly in FBX QuickTime Viewer but not in
the latest version of OpenSceneGraph then please send the file over to me in
a .zip with associated textures, and I'll take a look.
On 10 June 2010 21:09, Dario Minieri wrote:
> Hi,
>
> anyone has any other information ab
Hi,
anyone has any other information about this problem?
Thank you!
Cheers,
Dario
--
Read this topic online here:
http://forum.openscenegraph.org/viewtopic.php?p=28796#28796
___
osg-users mailing list
osg-users@lists.openscenegrap
Hi,
I've tried right now to import in 3DSMAX some FBX 2010-2 and 6 exported from
cinema4d. 3DSMAX is able to read correctly these files. Except some minor
problem in the perspective viewer, all selection and material are in their
correct position and the render works fine.
So, at this point I
Hi,
At this time I just found that malfunctioning. The first thing I noticed is the
use of LayeredTexture but obviously this is not the problem from what you say.
The problem is in the export C4D tool, but it is unclear where he is. Apart
from the use of LayeredTexture, the two files seem rough
Odd, the SDK doesn't seem to be able to get the FileName or the
RelativeFileName from the FBX file. I don't know why (it works fine for all
other FBX files I've tried it with) but it sounds like something may have
gone wrong during export. Cinema4D isn't an Autodesk product so their FBX
export may
Hi,
Thanks for your reply. I tried your trick but the result seems the same as
above. Seems strange that nobody else in the forum has the same problem. You've
encountered this kind of problem?
Some friends also, are having this problem and, as I said earlier, we used both
version 2.8.3 (with
Hi Dario,
Maybe the FBX code doesn't use the FBX file's directory as a base dir for
textures; try copying the FBX+textures in osgconv's dir for testing. I may
(should?) investigate this, but I'm far too busy right now.
Help, anyone?
Sukender
PVLE - Lightweight cross-platform game engine - http:
12 matches
Mail list logo