Border Black Screen During Walk

ID:71538
 
Jun 5 2009, 11:05 pm (Edited by moderator on Jun 11 2009, 8:48 am)
Resolved
BYOND Version:441
Operating System:Windows XP Pro
Web Browser:Chrome 1.0.154.65
Applies to:Dream Daemon
Status: Resolved
This issue has been resolved.
Descriptive Problem Summary:

When I walk too speedy the border gets blackened in the direction opposite to the direction of my Walking..
Noticed in this version --
It wasnt there in previous versions

[edit by Lummox JR]
This bug exists in 440 as well; it is not new.
Jun 8 2009, 1:37 pm
I tried to look into this but was not able to reproduce the problem in my test world. Do you have a demo project that shows the problem?
Jun 9 2009, 3:10 am
Well its my game that has it . More over every game like has it. More than one people has observed it. Trust Me. Well I have a code, this changes client eye a lot. It works like a Quake provindin an earthquake effect.Falacy has also observed this Bug.
Jun 9 2009, 4:37 am
I still need some kind of demo. As I said, I was unable to reproduce this on my own.
Jun 10 2009, 9:01 pm
OK here it it add this code in any game -
proc
    Quake_Effect(mob/M,duration,var/str)
        if(!M.client)return
        if(M.client.mob.Shake!="On")    return
        spawn(1)
            var/oldeye=M.client.eye
            var/x
            for(x=0;x<duration,x++)
                M.client.eye = get_steps(M,pick(NORTH,SOUTH,EAST,WEST),str)
                sleep(1)
            M.client.eye=oldeye
verb/Quaker(e as num,k as num)
                Quake_Effect(usr,e,k)

Verb Quae Effect and Put e= 100 and k=2+
Jun 10 2009, 9:20 pm
If he's talking about when you move the camera updating about a millisecond later, then yea I get that bug without any code, just moving. it's a bit annoying but its not really important.
Jun 11 2009, 8:51 am
I've verified the issue with Getenks' sample code, except it is not new to 441 as per the original post. It appears for me only when joining the game over a remote connection, and only intermittently. The problem appears to be that the client wants to draw a map update before the server has sent full map info, ultimately making it a timing issue. This bug is verifiable in at least 440, and probably goes back as far as 413 or even BYOND 3.0.
Jun 11 2009, 5:44 pm
It started in 440, there was a conversation about it on the forums somewhere, in the old bug report section I believe. Its another one of the problems that came up with that gliding fix.
Jun 12 2009, 4:27 am
The quaker demo shows the same problem in 439. If there is a new issue then that demo does not adequately demonstrate it. I have found no evidence of any new issue, either when playing locally or over the network.
Feb 18 2011, 5:20 am
This issue was resolved in an earlier version. New tests confirm the timing problem has disappeared.