Thought I'd repost this with a little more dramatic topic title... I can't believe I'm the only one who is trying to use FBX exports - would be nice to have this issue corroborated.
I created a scene in iC7.1 for FBX export and there were several faults.  I had not experienced these faults in iC7.0.  I made a little demo to illustrate - in a nutshell, the camera framing is way off and there are 'bumps' in the animated camera path.  Looking at the co-ordinates of the camera and geo that are being exported, it actually looks as if the camera is correct but the geo is significantly smaller and/or further away - basically nothing like what you're trying to export.  Also, attaching individual objects to the floor so they export in the correct position is kind of a pain - but having to 'reset transform' every object that has been scaled is downright rude.  This is not the case in any other FBX export capable software I use, so whether it's a bug or another iClone 'quirk' it should be addressed.

Hi  guys,
I haven't tried to export in FBX yet, and perhaps you already know this, but there is a nice tutorial from Warlord where he talks about merging sub props (edit menu) before exporting in FBX . You can check from 2:20 to 4:00 minutes:

https://www.youtube.com/watch?v=U9mQsrxUDL0

This won't solve the camera problem but perhaps might help for props.






Ryzen R9 5950x, RTX 3090, 128Gb Ram ,2 x 2 TB Samsung 980 Pro M.2 SSD

Horror Stories in VR
Immersive Sound VR
Immersive Sound VR on Oculus TV

Merging sub props does exactly that... it makes them all into one prop - so, you freeze all animation you may have had on the props.  I have tried various "simple" scenarios with inconsistent results - sometimes the camera is correct, but the prop animation isn't - sometimes the camera is correct, the prop animation is correct but the prop scaling is incorrect.  Exporting an FBX scene from C4D opens exactly the same in Fusion and Blender (with lights!) - no extra steps or work around required... I don't recall having these issues with iCv7.0.

Exporting an FBX scene from C4D opens exactly the same in Fusion and Blender (with lights!) - no extra steps or work around required... I don't recall having these issues with iCv7.0.

It seems like a great feature. When it work of course!    ;)
Let's hope Reallusion fix this soon.

Thanks again for your export & import camera camera tip and video.  

Ryzen R9 5950x, RTX 3090, 128Gb Ram ,2 x 2 TB Samsung 980 Pro M.2 SSD

Horror Stories in VR
Immersive Sound VR
Immersive Sound VR on Oculus TV

@IllusionLAB - 
If you export the scene Alembic, does the same "bad stuff" happen?  I am guessing no, just want to see if you had tried different exports and gotten consistent or different results .  
I have gone from iClone to 3DS Max, and it worked fine before, hadn't tried since last update.  Usually just avatar stuff, not too much prop stuff. 
I know 7.1 is full of bugs, let us know if the alembic one does or doesn't have the same issues as the exported FBX, and I think this is even further instance of bugginess. 
I will add it to the list of items I had prepared in the 7.1 thread for us.  We are looking for a #8! (or #7, or whatever it is...)

Pixtim'Store : Motions and models (marketplace and preview)

76% of original size (was 664x19) - Click to enlarge

FaceBook group : Pixtim for Reallusion Iclone and CC3

I haven't experienced any troubles with Alembic, but have yet to try in this situation - primarily as I have no desire to export an entire 'set' and then have to manually re-apply all the textures.  I'm not transferring from C4D to iClone - it's the other way around.  I'm sorry to say the problem lies completely with iClone - exported FBX from iClone is consistently wrong in C4D, Fusion, Nuke and Blender (I have access to Maya, Max and Houdini too... but don't feel the need to go that far).  I don't have time right this minute, but last night I did discover that the problem is "props scaling".  The iC7.1 camera export shows the same coordinates in the other programs... and the "floor" object from iC also shows x0y0z0 position in all programs.  iClone objects have a series of 'transforms' that conform their coordinates - that is, all objects start at zero with pivot point at the bottom... so, to correct that there is a transform for repositioning the pivot, a transform to transform the position etc.  My "floor" object had been scaled to 300% before attaching the other props... this is directly related to the framing being completely wrong in the FBX export.  I suggest you try it yourselves to see what I mean.  Create a floor and scale it to 300%, add 3 primitives and then move two of them X 100 and X -100.  Attach the 3 primitives to the floor.  Create a simple camera move and export the "floor" and "camera" to FBX - open in another 3D software... the result will not be what you expect.  ;-)

A scale other than 100% is problematic in some cases, also in iClone. That's why I usually re-scale.

Anyway, it would be great of there was an open-source, generally accepted export format other than FBX, which is proprietary and always seems to give problems in one direction or the other, as we never know how the implementation on the other side is. It like having an interface between two systems without having a proper interface definition.

Blender has had its problems with FBX over the years and so has DAZ.

The problem with FBX also seems to be that there is a new version every year, which to me defeats the status of it being a standard exchange format; rather it's a moving target.

---

76% of original size (was 664x19) - Click to enlarge

Yeah, I think there are great points here:
1) Maybe baking the animation by frame will yield better results
2) could be version of C4D, FBX export, and/or FBX export mode

The camera itself seems to be the issue right? 
I think some trials with a moving a camera should be easy to replicate and test.  I will try in 3DS Max.

FBX is evolving, like any software - so hardly a moving target.  It's safer for companies, like RL, to develop on older versions as they offer the necessary features and are stable - using the 'latest' FBX is a gamble with "non Pro" software.  All the major CG platforms always support multiple versions of FBX export/import to ensure compatibility.  I made a quick cross platform video to illustrate... simple animation and geo created in C4D and exported to FBX 7.2 (2012).  As expected, there are no issues on any of the other platforms.  TDP, if you review my previous posts you will see I have discounted the camera being the problem - it's a scaling issue that iClone creates on exported geometry.

I didn't start this post for 'theories' on why it's not iClone... just try it for yourselves - maybe you don't have any need to export FBX, but I'm sure that I'm not alone in having bought into the full iClone Suite for that very purpose.