Hi Richard

I seem to have hit a major problem with a set of loco wheels.
The export from 3DC seems to go ok but when I try to load the .x file into any app that supports DX animations nothing is visible...no geometry...nothing.

I've tried loading it into Blitz,Ultimate Unwrap, Fragmaotion etc etc....I don't get an error message...just can't see anything.

The last time I exported a wheel set was with 6.5.0.0 (I think) and it all worked ok, so has something changed with the export to DX Frame Hierarchy with later versions.

I've tried it with 6.5.1.0 and 7.0.1.2 but no luck at all.

The hierarchy of the model is correct...it seems to be a problem with the exported .x file.
The only luck I've had is when loading the file into Giles...it loads fine but Giles doesn't support animations so mayby there is a clue here.
Also if I export the wheelset as a .x object it loads without any problem at all.

Any ideas...I've just spent the best part of two months building this loco.

Bazza

This message has been edited. Last edited by: Amabilis Support,

An Update...I just tried loading the .x file into Decorator (a 3d paint app)...got the message...
This file doesn't contain any geometry....please check the file and try again.

Bazza

And another update...if I try to import the offending .x file back into 3DC I get an error..
'Invalid File Format'

Yet earlier wheelset created prior to 6.5.1.0 import ok..but without the animation.

Bazza

Solved it..Yippppeeee
It's taken me nearly two days to find the problem.

When naming one of the objects I'd used a Question mark after the name '?' Really just to draw my attention to it later.
This is what was causing the problem, I don't know if it's DX or 3DC that doesn't like the question mark in the naming of objects. I thought you could use all of the character set.

So is it a bug....not sure

So....
Left Piston Rod is ok.
Left Piston Rod? will cause the error.

However if you export as a DX Object you can use the '?' symbol but not if you export as DX Frame Hierarchy.

Bazza

I'll add a function to warn about invalid characters. I thought I already did this, but obviously not.

This is resolved in 7.0.2.2