sub objects did not appear in asset-manager preview

Hi JAW

Congrats you found the problem …. well done

A bit more experimenting seems to suggest that the problem is actually that the names in the railsim custom field need to be all the same.
I have been having a problem with one particular component that would not export if it was in its own group, when I checked it had the name ‘building’ in the RailSim custom box.
making this blank (the same as all other components cured this).

So all blanks is ok.

I also found that if you use the grouping make sibling of the ‘Main’ it inserts a name in the RailSim Custom Field, and its the last type of export you used with the wizzard.

Well done.. if its ok with you I will post the news over at UKTrainSim (with fullcredit)

Sly

Hi
yes that’s ok.
thanks too.

solve the problem is a good news and have to be shared.

J+�-�r+�-�me

I’m not sure if this is the same problem I see. I don’t use the export wizard for setting up and exporting my models, and name things for myself, yet still occasionally get a similar problem.

If I reimport the .igs file back into 3DC then it shows that the model has not been exported correctly from 3DC.

I usually solve the problem by taking a group and combining it with another, or taking a group out of the heirarchy, exporting the model and then bringing the group back intot he hieracrhy. I am well below the maximum 24 groups allowed with railsim.

Cheers,
Kevin

Hi Kev

I don’t use the wizzard for loco’s either, but I have used it for buildings,

I have just done multiple repeats of the test..

Pick an object and enter something in the Railsim box… if all other objects have empty boxes it will not go through the asset editor.
Remove same name and it goes through OK..

Could do with someone else trying it

just thought.. this may only be for objects that have Default Railsim names and sit in their own group.

All my problems have been with things like

Shadow_Engine
PrimaryDigit_1
Softshade_loco

Cured it for me <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>

Sly

Hmmmm…this is definitely useful information.I’m not quite ready to get going on this yet,but should be soon.

If anyone has something that simply doesn’t export, they can send it to <!– e –><a href="mailto:support@amablis.com">support@amablis.com</a><!– e –> and I can have a look in detail when I get going on this.

Done some more checking… it is not specific to Objects that use RailSim naming conventions.

It seems pretty straight forward.. If it doesn’t export chances are you have an erronous entry in a Custom RailSim box.

How it gets there seems to be a knock back from the improvements made in 7.1.2 ?… where your last entries remain in the export wizzard.

Until JAW found this, the only cure seemed to be keep moving things around in the hierarchy and it probably would eventually work.

This is because only if you move an object to be sibling of the main does it add the last used RailSim Type, and this may be session specific, so chances are you eventually overwrite the Entry.

Please consider keeping the entries in the wizzard, I don’t think its any big deal now we know where to look if we get a problem.

To test for yourself

Using the wizzard export a simple cube as a building.

Go back to the cube and declare it as ‘main’ as in a loco
Place a cylinder as a child
Using the file menu export the IGS as a ‘loco’… after after blueprinting this should show OK.. Import IGS all should be OK.

To initiate the error

Select the cylinder and make a sibling of main
If you look in the properties you should see that it has ‘building’ as your erronous entry in the railsim custom box.
It will make no difference if you put it back to a child……. the entry stays.

Export this IGS and then reimport to check and you should find that there is no Cylinder present.

I have not actually tried the importing back in, I blueprinted the items as a check and can recreate the error at will.

Thankyou JAW again <!– s:) –><img src="{SMILIES_PATH}/icon_e_smile.gif" alt="" title="Smile" /><!– s:) –>

SLy

Further explanation of this problem

If like me you use the export iGS option from the file menu… it does not report an error if you have groups named the same and the object inside is named uniquely.. howvever this then gives the missing sub objects upon blueprinting.

seems we could have had two different problems giving the same error.

I have repeated here OK with a very large model file..

Confirmation from others appreciated.

Sly

Hi Sly

Yes, I can confirm this. Two groups with the same name, does not report an error upon exporting through the file menu.
After blueprinting, all my sub objects where missing, except the main group.

regards

Gerrit