Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Camera bug that crashes game/client #33377

Closed
biznessmannnn opened this issue Dec 7, 2017 · 17 comments
Closed

Camera bug that crashes game/client #33377

biznessmannnn opened this issue Dec 7, 2017 · 17 comments
Labels
Bug Correct Functionality BYOND Issue We are trapped in the belly of this horrible machine Needs Reproducing Nobody will fix your issue unless you do this Priority: CRITICAL We really messed up
Milestone

Comments

@biznessmannnn
Copy link

ROUND ID: 79818
I was the head NukeOp, and when I went into the camera console for a custom placement, it froze the game for roughly 2 minutes before the client went unresponsive.

@ShizCalev ShizCalev added Bug Correct Functionality Needs Reproducing Nobody will fix your issue unless you do this Priority: High and removed Priority: High labels Dec 8, 2017
@ShizCalev ShizCalev added this to the Client Crashes milestone Dec 8, 2017
@WJohn
Copy link
Contributor

WJohn commented Dec 8, 2017

There's been multiple reports on something like this, advanced cam consoles seem to be causing this a lot but it's not consistent or reproducible.

@KomradeSpectre
Copy link
Contributor

Happens occassionally on/around blob overmind entities, AI Eye entities, Slime Management Console Cursor entities, as well. The screen freezes just as reported.

@praisenarsie
Copy link
Contributor

i bet you it's more consistent on 512 rather than 511

@ghost
Copy link

ghost commented Dec 9, 2017

Can confirm, happens to me too sometimes when I use advanced camera consoles like the clockcult or abductor one.

@sosowskiFS
Copy link

It does appear to be tied to Byond 512. My client crashed 3 times in about 5 minutes while playing AI, and after I downgraded back to 511 midround, I played a good 40 minutes without getting another crash.

@ShizCalev ShizCalev added the BYOND Issue We are trapped in the belly of this horrible machine label Dec 12, 2017
@WJohn WJohn added the Priority: CRITICAL We really messed up label Dec 17, 2017
@WJohn
Copy link
Contributor

WJohn commented Dec 17, 2017

I think I'm gonna mark this as critical because xenobio, AI, abductor, and clock cult are largely unplayable due to this. It really needs fixing badly, and it's been around for a long while now.

@AnturK
Copy link
Member

AnturK commented Dec 17, 2017

Problem is this is very hard to reproduce in clean environment and without that chances of getting a fix are low.

@LetterN
Copy link
Contributor

LetterN commented Dec 19, 2017

Happens if you're using byond 512, also same thing happens when you are an ai

@Buggy123
Copy link
Contributor

Can confirm, happens constantly as AI, not actually sure how to check version but I think i have 512.

@MrStonedOne
Copy link
Member

MrStonedOne commented Jan 10, 2018

I'm not going to take this report seriously until people start mentioning server and their full byond version.

@Jalleo
Copy link
Contributor

Jalleo commented Jan 10, 2018

@Buggy123 please post here with your byond version and when it next happens with the ROUND ID and SERVER NAME. And please inform if it does happen WITH 512. WE NEED DATA.

@Jalleo
Copy link
Contributor

Jalleo commented Jan 18, 2018

Server: Terry
Round ID: 82132
Byond Client Version 512.1403
Using a nagivation console for placing the pirate ship (whenever I overlaid the landing area with walls it crashed). It was crashing me after about 20 seconds by a freezing of the client possibly by infinite loop

@ghost
Copy link

ghost commented Jan 23, 2018

Byond 512.1403, Sybil, Bagil, Citadel, and Hippie.

basically tg and it's close derivatives

@MrStonedOne
Copy link
Member

1404 is out

@KomradeSpectre
Copy link
Contributor

Crashes persist in 1404.

@MrStonedOne
Copy link
Member

1404 fixed the crash we were able to reproduce, using the shuttle placer thingy. I was able to confirm this.

So what we need to do is reset, as too much info here applies to an old bug.

bugs relating to hangs on clients that involved mobs that can see all turfs have been fixed 3 times since 512 first came out.

What I need is more examples of what is going on when the hangs happen.

Close this issue report, I'll open a new one, What I need is for everybody to list times you have crashed on 1404 only. state the general area you were looking at when it happened for each time, state what kind of mob you were in, state what view mode changes you had active (mason vison, darkness toggling, huds or invisability changes, etc.)

If the turfs you had seen had changed since their round state, state any you remember, like being changed, being filled with a gas or gas overlay, being on fire, etc.

@Cyberboss
Copy link
Member

This issue isn't useful enough to stay open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Correct Functionality BYOND Issue We are trapped in the belly of this horrible machine Needs Reproducing Nobody will fix your issue unless you do this Priority: CRITICAL We really messed up
Projects
None yet
Development

No branches or pull requests