I copied a connection line from one object in the VS and pasted it into another similar object. Then a strange problem occurred. As soon as I touch this pasted connection line, AGM immediately crashes. Clicking it with either the left or right mouse button always causes a crash.
Selecting it with a mouse drag also causes a crash. As shown in the image, I have been crashed countless times…
Through repeated error analysis, I found that if I select an area with the mouse that touches both other connection lines/actions and this problematic connection line simultaneously, it does not crash. At that moment, I deleted it and copied a new connection line with the same conditions from elsewhere into the place, which resolved the issue.
However, this bug is quite scary. I worry that one day, an project I have poured much effort into could be destroyed, so I decided to report it.
According to the error log, the exception code is: 0xc0000005 = Memory access violation
I think the best way we could help this is to email us the project and in the email include the steps on how to replicate. I’m sure we could narrow it down further.
I’m sorry, but I can’t restore it. The problematic object’s connection condition was deleted.
The problematic link’s condition was: “When the XX switch is turned on.”
However, after deleting it, copying the same condition worked fine. I don’t know the specific reason or why it triggered.
Ok I understand now. I wouldn’t worry to much about an absolute failure. At most you could send the project to us next time it happens and if you cannot fix it yourself and we could delete the link inside the .vs file itself. We have options!
Thank you very much. Next time, I will keep a copy to send for reproduction purposes.
I’m recalling what actions I took that might have caused this issue. It’s a bit subtle.
I placed a .tscn object in the scene and copied it three times (the same .tscn file), but assigned three different visual scripts (VS) to them. The actions in these VS files were basically the same, except for the final generated variable values.
So, I copied VS_2 and VS_3 from VS_1. Later, after adding an SE (sound effect) playback action to VS_1, I completely deleted the soundless VS_2 and VS_3, and then recreated two copies based on the final version of VS_1.
But something strange happened: the copied VS_2 and VS_3 did not inherit the sound playback action condition; instead, they retained the old action paths based on the previously deleted parameters.
I wonder if this happened because the naming convention was the same after copying, causing the old action paths to be retained?
Therefore, I deleted all the outdated action connection conditions and used the mouse to select and copy actions from VS_1, then pasted them into VS_2 and VS_3.
That’s how it unfolded. When I copied and pasted a certain connection line, this bug causing an inevitable crash appeared. This is the entire process; perhaps some mysterious error occurred within.
