We have for some time now noticed a Max crash associated with RailClone, but have been unable to pinpoint what is the root cause of it. It has generally been fixed by not using the "point cloud" method of displaying the objects, but recently I have been working fine with my RailClone objects displaying as point clouds. Until yesterday, when my file just wouldn't save, no matter what I did. Every time I went near the save button, CRASH... out went Max. This morning I asked my colleague to open the file to see if he could save it, and he did without a problem. It was at that point I noticed that he had the RailClone objects set to display as box, more importantly, degrade to box, not point cloud. It was then that I realised that what had changed in the scene was that I had added a new RailClone object that was set to box display as default, and it crossed my mind that perhaps the problem is actually with multiple RailClone objects displaying in different ways? So it was fine when the single object was set to point cloud, and fine when both were set to box, but when one was set to point cloud and one as box it seems to cause a rift in the Max-Save continuum!!
In this particular situation we are using Max 2017 and RailClone 2.7.5. I have not yet done any simple scene experiments to see if it can be reproduced always, as I have a very pressing deadline, but when I get time I will look further into it. I thought it was worth putting it out there to see if anyone else has the problem.