03-02-2012, 02:05 AM
Redstone
|
03-02-2012, 02:13 AM
That's not a crash...
Run as administrator?
03-02-2012, 02:15 AM
03-02-2012, 02:27 AM
Restart computer? XD
03-02-2012, 06:14 AM
Error messages are read from the system, so whatever the system language is, the error will be in that language.
Error code 10013 is weird, but I have my suspicions - we're using a feature (that I have been against from the very beginning) that we don't block the port, meaning two programs can listen on the same port. Now, MS has made some adjustments to the socket security and you need to be an administrator (possibly even with UAC elevation, not sure) to be able to specify this parameter. I keep saying that we should remove the parameter, making it on-demand. Now you see why
03-02-2012, 07:48 AM
But he never had the problem before? wtf
03-03-2012, 04:00 AM
Lol!
I'll investigate, it probably has something to do with the 1.2 update EDIT: Oh right, first of all get r354 and see if you still have problems
03-03-2012, 08:25 AM
Hello,
There is still something wrong with the redstone. Firstly, sometimes blocks are not correctly refreshed (there is no power on connected wire and vice versa). Also, it is possible to place wire on wire. In addition, when I remove block under redstone torch, it remains floating in the air. This happens very often. After a while the server crashes with stack overflow. Here is the dump: http://dl.dropbox.com/u/29021761/crash_mcs_ee4.dmp Another interesting thing is that touching repeater results in placing new block on it. Of course repeater is not working, but it's probably not implemented yet... Hope it'll be fixed soon and sorry for my poor English |
« Next Oldest | Next Newest »
|
Users browsing this thread: 3 Guest(s)