
2.55 Client crash after connect
#1
OFFLINE
Posted 23 May 2014 - 09:33 AM

#2
OFFLINE
Posted 23 May 2014 - 11:11 AM

I think these are unrelated so I split the topic. I assume there is no crash info based on the previous report. Do you have a lot of custom sounds and maps on your server. There are some limitations that are more severe for 2.55 clients than 2.60 clients.
#3
OFFLINE
Posted 23 May 2014 - 12:25 PM

Thank you. No, there is no information about crash. Nothing in etconsole.log even nothing in silent_crash.log. I've done all those experiments, I spoke about, on my home server (just basic install => no custom sounds no maps). I've just installed silent on my home server and set the dl link to FDL we're using for our public server. Than I connected my HS and boom. That was also why I started thinking that there could be some problem in our FDL. But I've changed my mind. There cannot be anything wrong, it's just space for files with fast link, isn't it?
#4
OFFLINE
Posted 23 May 2014 - 12:56 PM

Have you tested with your home server setup that possible AV programs don't cause issues?
#5
OFFLINE
Posted 23 May 2014 - 02:57 PM

#6
OFFLINE
Posted 23 May 2014 - 03:07 PM

It could cerainly be related to the OpenGL. Yes, I meant AntiVirus. Also, I meant if it would affect the client but I didn't want to suggest you disabling it before connecting to an unknown server. However, if the 2.60 works fine in the same computer, it doesn't seem very likely that drivers would be the cause for you. The r_softwareGL 0 just ensures that you can't emulate OpenGL but you must have a GPU capable for it and the drivers. However, very often in Windows, I assume Windows because of the 2.55 version you are using, low level failures such as drivers and hardware generate BSOD and not such a clean exit.
#7
OFFLINE
Posted 24 May 2014 - 01:51 PM

#8
OFFLINE
Posted 24 May 2014 - 02:55 PM

If you make a default install on your server, without even any custom maps, does it work then?
#9
OFFLINE
Posted 24 May 2014 - 03:15 PM

#10
OFFLINE
Posted 24 May 2014 - 05:51 PM

If you make a default install on your server, without even any custom maps, does it work then?
Hmm, I could try this but I need to wait until nobody is on the server and it may take some time.
What is your server binary? Do you have any of these: pak1.pk3, pak2.pk3 or mp_bin.pk3 inside your etmain folder of your ET server installation?
No, I've removed all of those because clients with 2.55 wouldn't be able to connect. And this crash happens after a few seconds of being in game.
#11
OFFLINE
Posted 25 May 2014 - 05:03 PM

Just to make it clear on this case. The reason why the silent_crash.txt file is empty is because the mod file has been wiped out already. The exception handler is in that binary. I.e. the execution was not in silent mod binary when it happened. Based on the original thread this was posted, the game does not go all the way to the desktop, which indicates the engine encounters an issue it can't resolve and it has to close the game. However, even still this could be happening because of programmatic errors, less likely though, because some of the ET default utility functions have their own ways to handle bad input data. Console logs should provide enough information to recognize such cases.
#12
OFFLINE
Posted 03 June 2014 - 09:15 AM

Hello I'm back, here is my console output if it help somehow:
logfile opened on Tue Jun 03 10:56:10 2014
#13
OFFLINE
Posted 08 June 2014 - 11:00 AM

One more thing. I've tried some things before my 2.55 crashes and I've found out strange thing. After downloading server packs and after entering the world, I typed cvar_restart to my console. Then my WolfET again crashed after a few seconds but the crash window wasn't empty. There were notification about missing packs. Exactly, there were information, that the pack I removed before I launched the game, is missing even though I downloaded this pack during the ingame DL. So this made me thinking. Is it possible that game doesn't load pack or doesn't load it properly although they're download from server? Could this be the case of this crash? How could I fix that from server side? The fact that if I restart game and connect the server again then this crash doesn't occur supports this my speculation.
#14
OFFLINE
Posted 08 June 2014 - 12:10 PM

It sounds like the issue is in 2.55 client. I doubt there are things that can be done to prevent it. Luckily, it happens only when players download the packs so on subsequent times, they don't have problems. One thing you can do is to instruct players to update their clients.
#15
OFFLINE
Posted 09 June 2014 - 09:10 AM

#16
OFFLINE
Posted 09 June 2014 - 07:05 PM

There is no method for executing commands in the client. Only option for such a thing would be a custom menu, but that would not get executed unless the user opens the menu and clicks some button.
0 user(s) are reading this topic
0 members, 0 guests, 0 anonymous users