Dead Stop

[Bananarama]

All I know is that Max appears to export just fine (for now). I don't know what caused the earlier issue, and I'm not sure how it got fixed along the way. At any rate, we need to figure out what's going on here. I suspect 3DC users out-number those with Max, and to have a possible limitation sitting in the wings does not bode well for 3rd-party content creation. Rich mentions he hasn't run into these issues, but clearly something is going on. What 3DC version are you using?

BTW, have you contacted RS.com directly?

[SMMDigital]

Yes Rich said he is using an older version of 3DC, and as I mentioned, I haven't had these problems out of my crossing signals, which were made with the first version of the 3DC-8 series (I'm using 8.2 right now). Rich is using the 7 series, and it's interesting to note that files made in 8 are not compatible with 7.

I have not contacted RSC as of yet, but I have sent an e-mail about the problem to Amabilis. I believe I should probably see if I can dig up my 8.13 installer, put it back on my computer, and see if that makes a difference.

[rgarber]

It wouldn't be 3D Canvas I wouldn't think but the exporting tools. Just guessing.

As I understand, and I'm not a big follower of 3DC so don't quote me, but 8 was mostly a GUI upgrade. 8 wasn't supposed to even have exporting tools for train stuff and then somehow they happened. That's my *big emphasis* guess where the problem may be.

That problem you're having looks a whole lot like the same problem we had in MSTS with the... oh what was that??... the bounding box skewed or maybe it wasn't the axis of origin was centered so the whole building set in the bounding box... something like that.

Been awhile.

With 3DC it's pretty easy to get the axis points way off in timbuktoo-land if you're not careful.

Not that I think this will help but maybe. What I do is if I don't have a primitive centered I will create one and stick it in the middle of the building and then make it the top of the heirarchy of the model (making sure the axis of origin is set so the building sets on the ground - rather than in it). Other than that I haven't done anything special. Lots of times though I don't have to do this trick because something is usually close enough to center I can use it. Beats me but I don't think 3D Canvas is the actual culprit. But then.... what do I know!?? - Rich

[rgarber]

Oh.. nice looking tanks. Love the man cage stuff. Well done! - Rich

[pwillard]

I think 8.13 is going to have some lingering issues that will complicate matters... you really want to do a fresh 8.2 install.

[g_nash]

I see it's been "stitched" back into a single object (with exception to the shadows, which continue to be problematic if too large).

I've been told that a hierarchy isn't needed in RW

hi

Just 2 queries , When you say stitched , is that attached or collapsed , and , I was under the impression that hierarchy was indeed required . ??

[SMMDigital]

Alright, a little further testing today.

I uninstalled 3DCanvas Build 8.2, and reinstalled build 8.1.1.7, and 8.1.1.3 and their associated plug-ins. In both programs, I was unable to make even a small factory asset that did not disappear at certain angles.

Then, I downloaded 3DCanvas 7.1.1.2 and installed it, with no extras or plug-ins. I made a small (200x20x200) simple asset, textured it, and exported it. The only movement I made was to make sure that the center of the asset was at x0, y0. The object did not flicker or disappear in the sim. I then made an 1100x20x200 and a 1500x60x300 simple asset, textured and exported them to the sim. The assets are completely stable, with no flickering or vanishing up close or from afar, when looking in from any angle.

Now there are many variables to computers, and just the fact that I still had 3DC 8 installed on my computer could have influenced the outcome (although I did have 3DC7 installed into my User/Program folder instead of the normal c:\Program Files folder), and the fact that I did not have Decapods extras installed in 3DC-7, so I cannot definitively say that the Railworks exporter on version 8 is gimped. But at this point is is highly suspect of causing this problem and will be reported to Amabilis immediately, where it will be promptly ignored by their non-existent customer support. My suggestion is to used caution when upgrading to the newest version of this software.

[Trainguy76]

I am on 7.1.2 and don't seem to get this issue, even with the (new) exporter.

[Bananarama]

Just 2 queries , When you say stitched , is that attached or collapsed , and , I was under the impression that hierarchy was indeed required . ??

"Stitched" was used as a metaphor for "attached." As for the heirarchy comment, you need to finish reading the statement. In it I also said: "...but I've found fewer issues when using them." And note too that I included an example of the model's hierarchy.

[Bananarama]

...so I cannot definitively say that the Railworks exporter on version 8 is gimped.

After reading of your tests, I would have.

[pwillard]

Maybe version 8 still has a few bugs... we might want to have a conversation with Paul Gausden (who I feel might be more knowledgeable about EXPORT tools for railsims) about what we see here to maybe get some confirmation on whether or not this is some sort of "bug".

Opinion Alert: I can honestly say, based on version 8's current state of development... I still prefer version 7. It wasn't until version 8.2 that I could reliably load models I created prior to version 7.12 and that was important to me since I have quite a few models and many many saved objects in older versions. ...and as you may have noticed... once a model has been touched by a newer version of the software... and older version of the software won't like it in it's native format. I'm sort of a version +1 sort of person, having worked in IT for so long. Meaning, I'm much more trusting of version numbers like 8.2.11 versus 8.2 or 8.3.