Federicrit Posted April 3 Posted April 3 (edited) It's been a while since I was able to play in 2.60b. I think it stopped working after a Win10 update, but I didn't really mind since I could still play from Legacy. Today I wanted to join Silent from the 2.60b client, so I reinstalled everything and used default config, but the problem persists. The main manu is fine, the server browser is fine, when I join any server (I tried non-FA as well), all the mod files download just fine, and the map gets downloaded fine also. Eventually it starts loading the map, but there it gets stuck, it freezes completely. Nothing happens for minutes. I have to manually close the game. I tried opening console before it freezes, but, when the loading map screen appears, the console closes. It doesn't seem to be generating any crash logs. I tried running in compatibility mode and as administrator. I'm using a low-end intel laptop at the moment. Any thoughts? I'll check tomorrow or so. Update 1: It seems I can only play in the 64-bit Legacy client, so I can only join Legacy servers. ET 2.60b and 32-bit Legacy don't work for me, not even in Legacy servers. Edited April 3 by Federicrit Quote
Gengis Posted April 3 Posted April 3 (edited) Your logfile is activated ? Ingame go with /logfile = 1 or set logfile "1" in your cfg. Your console will be saved and you can read it to see if there are any error messages. 32-bit Legacy should work. Silent1 uses ET Legacy v2.77 win-x86. I use W10 with the latest updates installed. I use ET Legacy v2.82.0 win-x86. It works fine for me. Gengis Edited April 3 by Gengis 2 Quote
kajto3 Posted April 3 Posted April 3 Have you tried creating a local server from your 2.60b and connecting to it? For example, create a shortcut to your etded.exe, run it with +map oasis parameter inside Target box, try to connect to localhost or 127.0.0.1 1 Quote
Federicrit Posted April 3 Author Posted April 3 (edited) 2 hours ago, Gengis said: Your logfile is activated ? Ingame go with /logfile = 1 or set logfile "1" in your cfg. Your console will be saved and you can read it to see if there are any error messages. Okay, I activated logfile in 2.60b and 32-bit ETL. 2.60b logfile: etconsole.log 32-bit ETL logfile: etconsole.log I only see "ERROR: Disconnected from server" in the 32-bit ETL logfile, but that only happens after I type "/disconnect" while map loading screen is stuck. I didn't find anything interesting in the 2.60b logfile. To clarify. 64-bit ETL works just fine. In 32-bit ETL I can't connect to servers, but if I'm connecting to a Legacy server, I can at least open console when the map loading screen gets stuck; if I try with a Silent server, it gets completely frozen. In 2.60b everything gets frozen during map loading screen. All versions and Windows 10 are updated. Another interesting thing is that 32-bit ETL seems to be inconsistent in main menu performance. Most of the times it works fine, just like the 64-bit version, but sometimes it gives me heavy lags, running at less than 1 fps, and the only solution I found was to close the game, and try again. Quite weird... None of these things happened a few months ago. 1 hour ago, kajto3 said: Have you tried creating a local server from your 2.60b and connecting to it? For example, create a shortcut to your etded.exe, run it with +map oasis parameter inside Target box, try to connect to localhost or 127.0.0.1 Okay, I managed to host a game both in 2.60b and in 32-bit ETL. I hosted both from Main Menu -> Host. Edited April 3 by Federicrit 1 Quote
kajto3 Posted April 4 Posted April 4 And you were able to play on that hosted server right? Creating a server from the main menu is slightly different than creating a local server on your PC and connecting to it from your regular client. So, let's host a server from your ETDED.exe (ET 2.60b), which will be more compatible with your ET 2.60b client. 1. You will need your default ET 2.60b directory with ETDED.exe inside of it (it should be there by default, unless you removed it). If you have a lot of files in etmain, it might be a good idea to create a new directory with only essential files, which are: pak0.pk3, mp_bin.pk3 and qagame_mp_x86.dll 2. Create a shortcut to ETDED.exe by right-clicking on it -> Create shortcut. 3. Right-click the shortcut, go to Properties, in the Target box (first from top) add a space after "path\to\your\etded.exe" and paste: +map oasis +set net_port 27960 4. When it starts, you can type the status cmd inside of it, it should show you the map name and an empty list of players. While it's running, you can test your 2.60b or ETL 32 bit clients with it. Just do /connect 127.0.0.1 from your game and you should be able join your own etmain mod server. I'm just curious if your game freezes because it's something on your PC or is it a problem with connecting to other servers 1 Quote
Federicrit Posted April 4 Author Posted April 4 3 hours ago, kajto3 said: And you were able to play on that hosted server right? Yes, I managed to play in that server in both 2.60b and 32-bit ETL. 3 hours ago, kajto3 said: So, let's host a server from your ETDED.exe Alright, I did that and the status cmd showed oasis and the empty list of players. I could also join to that server from both 2.60b and 32-bit ETL. And I could play just fine. However, in both clients it took quite a long time to connect, like more than 60 seconds in both clients. This also happened with my previous test when I connected to the server hosted from the main menu, both clients also. When I used to connect to Silent1 it would only take a few seconds. 1 Quote
kajto3 Posted April 5 Posted April 5 (edited) So there is something that slows your ET down wonder if you wait long enough, you'll be able to connect to a remote server eventually. Still, the fact that 64bit ETL works just fine is most interesting. Are you using any AV software? Do you install your ET/ETL on Onedrive or some other cloud storage? Your PC specs maybe? Tried with default/fresh config? Edited April 5 by kajto3 1 Quote
Federicrit Posted April 5 Author Posted April 5 1 hour ago, kajto3 said: wonder if you wait long enough, you'll be able to connect to a remote server eventually. I tried. I didn't test this 100%, but I think that in 2.60b, et.exe just freezes (task manager says that it isn't responding). Yet in 32-bit ETL it doesn't freeze completely. Yesterday I waited and it eventually kicked me to main menu with message "Server connection timed out". 1 hour ago, kajto3 said: Are you using any AV software? AV stands for audio-video? No, just Intel integrated graphics. 1 hour ago, kajto3 said: Do you install your ET/ETL on Onedrive or some other cloud storage? No, everything on local storage. 1 hour ago, kajto3 said: Your PC specs maybe? Probably, but this didn't happen a few months ago, which makes me think that it's a Windows 10 thing. Maybe they messed up the integrated graphics drivers or something. I'm actually going to test if I can join while disabling Windows Defender. Maybe it's blocking et thinking it's a virus or something. 1 hour ago, kajto3 said: Tried with default/fresh config? Yeah, I tried with default config, clean install and everything. I noticed that if I disable GL extensions in 2.60b, my main menu lags, giving me less than 1 fps (I don't know what GL extensions are or if it could be related to my issue, and I don't know if this would've happen before). Quote
kajto3 Posted April 5 Posted April 5 What I meant by AV was anti-virus. You mentioned Windows Defender, so yeah let's try with it disabled, but why only you would have this issue though... Also, I wasn't expecting "probably" as an answer for PC specs 😄 what I meant was your PC specification, like CPU, graphics etc 1 Quote
Solution Federicrit Posted April 5 Author Solution Posted April 5 Okay... It seems to be solved. But I don't really know how. Yesterday it didn't work. Today I directly tested while disabling Windows Defender and I managed to join! Then I re-enabled Windows Defender but I could still join. Both clients. I'm not really sure what happened. I'm thinking it was indeed some Windows 10 update related with Security and it was fixed automatically, or maybe disabling and re-enabling Windows Defender actually accomplished something. Anyways, it works now. See you in Silent, thanks a lot for the help <3 2 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.