Description of Bug: Lua effects are stacking up and allegedly not being killed properly.
How to replicate: Have the whole server fire their weapon on hostiles.
How to replicate: Have the whole server fire their weapon on hostiles.
Lua effects not being killed properly (Possibly heavy lag inducing)
- Thread starter SynergyJohn
- Start date
A ton of other people were getting it as well, along with a lot of people saying they were getting the errors in general
Hello good sirs,
So I had previously looked into this so I can give some insight though obviously I'm not a gmod expert like others.
When we had first moved over ARCCW there was an issue with the lrb_tracer where it wasn't being killed properly.
This had ultimately caused a lua effect loop which made things like NPCs not have tracers etc for client side.
In addition to the above, clients are expected to have Much Lower FPS to someone that has joined the server as it effects are client side.
So re-joining the server will remove these effects.
As a request Synergy and to any other players.
If they get this within console can you please do the following:
Open Console `
Type FProfiler
Top Left - Start Profiling
Run for 10 seconds
Stop Profiling and then click on "Total Time in MS"
This should indicate what is taking up the most resources on your client.
An example can be shown below where I had identified that the LRB_tracer was not being deleted properly.
This was fixed a while back.
Hopefully this helps in trying to identify this issue.
So I had previously looked into this so I can give some insight though obviously I'm not a gmod expert like others.
When we had first moved over ARCCW there was an issue with the lrb_tracer where it wasn't being killed properly.
This had ultimately caused a lua effect loop which made things like NPCs not have tracers etc for client side.
In addition to the above, clients are expected to have Much Lower FPS to someone that has joined the server as it effects are client side.
So re-joining the server will remove these effects.
As a request Synergy and to any other players.
If they get this within console can you please do the following:
Open Console `
Type FProfiler
Top Left - Start Profiling
Run for 10 seconds
Stop Profiling and then click on "Total Time in MS"
This should indicate what is taking up the most resources on your client.
An example can be shown below where I had identified that the LRB_tracer was not being deleted properly.
This was fixed a while back.
Hopefully this helps in trying to identify this issue.
Heya, so Wooloo was getting lua errors as well that were the same as mine, so I had him run the profiler (since I wasn't getting them in a timely manner) and this was the result (Image attached)
In addition the function details do not appear when you click on it, and it just remains empty. (Second insert)
And upon printing details to console, this is the result
