EDEM crashed with API
Find more posts tagged with
Hi,
That's a perfectly valid value for the time, why do you think it's weird?
You would have to debug line by line to see where your issue is. If you're saying the only new bits of code are custom properties and reading prefs file values, start there. It's very easy to read in incorrect values in a preference file.
Richard
Hi Richard,
Because I saw time was a negative value.
Regards!
Ah, I missed that. Not sure I've seen a negative time value in EDEM before, impressive!
I'd still debug a line at a time and check all your values for the source of your error
Hi Richard
Thanks, because sometimes the simulation can finish, and crash happens at the beginning of simulation, I have debugged the code and the values read from the preference file were correct. That's why I am confused.
Regards!
Hi Richard
Thanks, because sometimes the simulation can finish, and crash happens at the beginning of simulation, I have debugged the code and the values read from the preference file were correct. That's why I am confused.
Regards!
I'm intrigued now. I'm not guaranteeing anything but if you can post your code I'll take a quick look
Sorry, I upload again.
Lines 323 to 326 you're adding to four components of the custom property "InitialOverlap" but it only has one element in the definition on line 740. That needs increasing to 4. That's leading to completely unknown behaviour because you're writing to memory that you have no idea about and the effects are completely unpredictable ...like negative time
Lines 323 to 326 you're adding to four components of the custom property "InitialOverlap" but it only has one element in the definition on line 740. That needs increasing to 4. That's leading to completely unknown behaviour because you're writing to memory that you have no idea about and the effects are completely unpredictable ...like negative time
Ah, I missed this, thanks for pointing out this problem.
Sorry, I upload again.
Lines 323 to 326 you're adding to four components of the custom property "InitialOverlap" but it only has one element in the definition on line 740. That needs increasing to 4. That's leading to completely unknown behaviour because you're writing to memory that you have no idea about and the effects are completely unpredictable ...like negative time
Hi,
That's a perfectly valid value for the time, why do you think it's weird?
You would have to debug line by line to see where your issue is. If you're saying the only new bits of code are custom properties and reading prefs file values, start there. It's very easy to read in incorrect values in a preference file.
Richard