Limelight Forums

No, keeps happening afaik

I just had a new crash, this was a weird one:
I searched for an apple in the Q-menu, placed it on someones head and were going to shoot the apple, as SOON as I hit the firebutton, the MILLISECOND, I got the same crash to desktop with no warning.

Here is a video showing 30 secs prior.,
https://youtu.be/nJuasvZ3qOU

It's coz limelight is poorly optimised and unstable

It just happened to me once again, while I was typing a /pm in my towtruck.
Only had a 25-propped dupe out.

I hate to be the negative nancy but this will likely be an issue for at least a month

Hmm okay, keep us updated please.

Updated about what?
It keeps happening and we keep getting asked for updates and status, but are anyone actually doing anything about this?
Does any devs look into this, in the logs where the time-outs are?

It makes it almost unplayable, as if I build a lot I will crash atleast 3-4 times within a 2-3 hour session, which doesn't give me too much of a motivation to play.

I don't want to be the negative nancy again but crashes are 95% out of dev control. The 5% is the rare lua panic and similar mistakes, most of it is just source being almost as old as me. LL devs don't have the PDB (lets them see what the MDMP actually means basically) to fix the problem.

All we can do is wait on Facepunch (at the end of the day it's their game). When you crash, the follow the instructions here:
https://wiki.garrysmod.com/page/Crash_Reporting

If you do not, it is not likely to get fixed.

Hello there Williyvodka, I dont know if I'll be much of help but I used to crash alot on a similar community and what helped me was to type in -autoconfig in my launch options.

Here is a gif to show you how to do it;

Does it still prevent you from crashing, Eclipze?
I haven't tried the command, but I still keep crashing and sometimes get "Out of memory".

I feel it's rather unrealistic that this is locally on my machine, as this is the only server this has happened on and several friends of mine and members has also had this issue on this server only.
I have a feeling that it happened much rarely on the evocity-map tho