Hello, I think that this message can be interesting for support only.
Robot version - 2015, SP1 installed.
I have modifying model in Robot (changing numbers of Load Cases) and then made undo (Cntr+Z).
After that Robot begin to "devour" all amount of RAM which installed on the PC in the calculation process (I'm attaching model in this message).
What I've tried to do:
1. Open file in Repair mode - Negative;
2. Changing Solver - Negative;
3. Trying ro remove all Combinations - Negative.
So, only way to recover model was copy whole structure to the new file, thus work wasn't lost.
But I think it can be intresting for development team to invistigate this case.
Thanks in advance.
Solved! Go to Solution.
Solved by Artur.Kosakowski. Go to Solution.
Thank you for information. We'll investigate this situation.
Try to delete and define again these corrupted load combinations.
If you find your post answered press the Accept as Solution button please. This will help other users to find solutions much faster. Thank you.
Hi, Artur,
It works, thank you! But in any case I can't understand how combinations was corrupted.
We will check the performance of the undo command after renumbering the load cases. Do you remember what were the original definitions of these combinations. Were they the Newmark ones?
Artur, my actions were done in this order:
1. Having Load Cases I wanted to add new one with number 2.
2. For this - I've opened tables with Load Cases, then exported this to Excel, changed values for all except first. For example 2 became 3, etc.
3. Then I've pasted new numbers into Robot. But for some reasons Robot pasted numbers in not correct order.
4. So, I've tried to undo with Cntr+Z press.
After that Robot froze (without calculation)...
About combinations - it were manual combinations, I think, quite simple.
Something like this: 1+2+3+15+18
Thank you for providing this information. We will try to recreate this situation to check what happened.
Hi Igor,
We have made several tests but we have not managed to create the similar situation as yours. We will keep trying.
Hi, Artur,
Yes, you are right - I've tried to repeat this situation and in this time Robot undid without any problem. Probably, it was one-off event, but in any case thank you for your help.