I have a fairly simple structure (so far it consists of steel beams, joists, girders and columns, and concrete tilt-wall panels) that I'm trying to analyze in Ram Structural System but it seems that a lot of the model is lost in translation. The Model exports from Revit 2019 to an ISM file with all of the necessary structural components mapping (the ISM model is identical to what I see in Revit). But then when I try to bring the ISM file into RSS, it doesn't recognize that I have any steel beams and it can't seem to find half of the columns. Any suggestions for what I can try to get my full model into RSS?
Make sure to use the latest versions (currently RAM SS - 16.01.00.06, Synchronizer - 10.03.01.06, ISM Revit plugin - 10.03.00.08). I tested this with a user yesterday and I saw good fidelity. There are some items RAM SS cannot import because some materials and geometry are not possible in RAM SS. If your case is clearly something that should be coming across then send us the files. Secure File Upload
Has there been any progress on this? I am experiencing similar issues - I have a test Revit 2019 model that transfers well into ISM, however when I try importing the ISM model into RSS one of the columns disappears.
I believe the relevant error message is "Object reference not set to an instance of an object", it is cited with the ISM ID number of the missing column. Is there some way this can be systematically fixed?
I don't think there have been any changes since my post from 2 months ago. If the column is properly assigned a material and not importing then I would try a couple of tests. What happens if that column is the only thing in the ISM file (you can make a new export from Revit using selection sets to test)? What happens on another machine? If you don't have one, send the file over here.
Seth, thank you for getting back to me. I tried out exporting the problematic column only - it still doesn't appear in the RSS model.
Your suggestions gave me an idea to try out two other things:
This seems to be a location-specific issue, perhaps not at all related to the object. I will try running through this on another machine sometime later today; maybe I come up with some other tests that will be of interest.