-
Notifications
You must be signed in to change notification settings - Fork 5
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
Recent crashes #4
Comments
I realize that my lines above are not the same as this github's but it's In my own version I check if the neck bone was found and if so this part run as shown here,
|
Does it crash with the original code or my fork? When does it crash? The only instance where I think this would crash is when a playermodel doesn't have any bones. Also please at least provide all your modified code or give the logs of the crash with the original code or my fork so I can be certain of the location of the issue. Anyway what I mean is that I need to know more about the context of the crash because I don't know why this happens to you and I never got any crash with the original code nor my own fix for Lua errors. Lua panic is something I rarely get so I forgot that was a thing. |
My players seems to crash on joining after they start spectating someone, I believe it happen with any model but can't be sure I only have the crash log I posted above. My gamemode is murder. I unfortunately don't have information for the last two questions. I never experienced the crash myself but noticed a few of my players would crash on join and that's where I got this log from. I've removed the script since but i'll try to take a look into it when I have time. |
Ok I've tried with my fork on Murder (latest version). |
Latest gmod update mention this line:
Might be a fix to this. |
As of latest gmod update, this happened again. I feel like it's the code running too soon. -Lua Stack Traces- |
-Lua Stack Traces-
Client
0. GetBonePosition - [C]:-1
Server
Lua Interface = NULL
MenuSystem
Not in Lua call OR Lua has panicked
The text was updated successfully, but these errors were encountered: