It looks to me like you are experiencing the same bug I was... It crashed for me and I am on a Windows PC. I would just load it from a previous point, I don't think there was anything wrong with your weapon.
Note I didn't actually check, I just ran the game to see if it crashed the same way mine did when I experienced the bug. Still don't know what caused it, but I think somehow the file got corrupted. Your map literally responded in the exact same way. I loaded it, and then it just froze.
What kind of freeze is it? Does the game just stop responding, or does it display an error message?
Both would mean different things. Freezes usually come from a break in the actual editor code, or some kind of infinite loop that has gone unchecked. It is possible that you have discovered a bug in Blizzard's code. The editor is supposed to catch all these infinite loops and destroy them, but, as you probably know, the editor has a tone of leaks. If you found an area that the editor fails to garbage collect, that is probably what is happening. The point is that a simple beam should not freeze the editor. A corrupt file is a possibility, because the same data would have been used to run the file on the mac computer. Perhaps starting over is your only option. If it is an error message, copy and paste it into the forum so we can see it.
(FYI one of my maps actually experienced this. When I save, the map actually saves to 2 locations. I had to delete the corrupt file and start from the old one. This is possibly what you are going to have to do)
Rollback Post to RevisionRollBack
Great to be back and part of the community again!
To post a comment, please login or register a new account.
@DMc298: Go
It looks to me like you are experiencing the same bug I was... It crashed for me and I am on a Windows PC. I would just load it from a previous point, I don't think there was anything wrong with your weapon.
Note I didn't actually check, I just ran the game to see if it crashed the same way mine did when I experienced the bug. Still don't know what caused it, but I think somehow the file got corrupted. Your map literally responded in the exact same way. I loaded it, and then it just froze.
Great to be back and part of the community again!
What kind of freeze is it? Does the game just stop responding, or does it display an error message?
Both would mean different things. Freezes usually come from a break in the actual editor code, or some kind of infinite loop that has gone unchecked. It is possible that you have discovered a bug in Blizzard's code. The editor is supposed to catch all these infinite loops and destroy them, but, as you probably know, the editor has a tone of leaks. If you found an area that the editor fails to garbage collect, that is probably what is happening. The point is that a simple beam should not freeze the editor. A corrupt file is a possibility, because the same data would have been used to run the file on the mac computer. Perhaps starting over is your only option. If it is an error message, copy and paste it into the forum so we can see it.
(FYI one of my maps actually experienced this. When I save, the map actually saves to 2 locations. I had to delete the corrupt file and start from the old one. This is possibly what you are going to have to do)
Great to be back and part of the community again!