search

FrozenSand / UrbanTerror4

Official bug tracker for the game Urban Terror 4.x - www.urbanterror.info
77 stars 18 forks source link

New Version 4.3.3 #431

Closed alexptbg closed 6 years ago

alexptbg commented 6 years ago

Hi, After a fresh install of the new version (4.3.3) sometimes it freezes the game. Something that never happened before. Cpu: i5 8GBram / gtx1050 / win7pro/x64 / SSD disk, (video card is at 26ºC/cpu at 40ºC) What did you did with the game? I am playing the game for about 5 years and that never happened? Going back to the version 4.3.2.

Barbatos commented 6 years ago

Hi,

We'll need some more information to assist you. Please provide a demo showing such crash and upload your complete log file there once your game has crashed.

Thanks

bozzy-gh commented 6 years ago

4.3.3 crashes continuously on Windows, it sometimes lasts 2 or 3 minutes, sometimes 2 or 3 seconds. I've been trying to play on a server where almost all users on Windows are suffering this problem. Linux users seems to be ok. Tried to revert to 4.3.2 executable, but the problem persists. It's somewhere else, maybe on the VM (zUrT43_qvm.pk3). I don't know how to get a log of the crash, is there something (a debug option) I have to activate in order to get one?

Barbatos commented 6 years ago

You can launch the game using cmd.exe: cd C:\Location\of\the\UrbanTerror43\folder\ Quake3-UrT.exe +set logfile 1 +set developer 1

It should create a file named qconsole.log in your q3ut4, which will contain the crash information. Thanks!

Critofur commented 6 years ago

My game also crashes constantly since the update and has severe frame drops when it hasn't crashed yet

I use windows too

Barbatos commented 6 years ago

Guys, there is nothing we can do to help you if you don't provide log files. Please take a moment to generate them and upload them here!

bozzy-gh commented 6 years ago

qconsole.log

Here is my qconsole.log, but it seems to contain nothing strange at the end. Maybe because the "crash" is actually a freeze, audio loops and then Windows says "program stopped working" and asks if I want to terminate it or wait...

alexptbg commented 6 years ago

Yes. I cant provide a demo since the game freezes "program stopped working" . I have the 2 versions off the game at the moment. (In a separate 2 folders) So the version 4.3.2 everything it's ok. The version 4.3.3 freezes with audio loop, to exit the game have to press "crtl+alt+del" and close the "Task". Ill continue using the version 4.3.2 for now, but one of the servers that i play in using the latest server version and cant find it on version 4.3.2 only seeing the server at version 4.3.3. Waiting for some kind of a fix.

Thanks in advance. AlexPT.

Barbatos commented 6 years ago

Thanks for the log file. Does it happen on specific servers only? Could you guys also paste me your q3config.cfg files? Are you using in_mouse "1" or dmaHD_enable "1"? Do you use wireless keyboards or are several keyboards connected to your computer?

This issue could potentially be linked to https://github.com/FrozenSand/UrbanTerror4/issues/305 but we weren't able to reproduce it so far.

fperana commented 6 years ago

Does it happen on specific servers only?

No, it happens on all servers I've played on after upgrading to 4.3.3, but there seems to be a factor that strongly influences crashes: the number of plauyers on that server. Yesterday I were into a server with only another player, we played for about half an hour without problems. Then on another server (one that used to be very popular, but 'cause of these crashes a lot of users leaved...) we were in 4 or 5 players and crashes were quite rare (every 10-20 mins). On busy servers (10 or more users) it may crash in 5 seconds or maybe 1 or 2 minutes.

Could you guys also paste me your q3config.cfg files?

Yes, I'll do these evening or tomorrow.

Are you using in_mouse "1" or dmaHD_enable "1"?

I don't know, but I made no strange settings, I'm using quite default config (I'm not a hardcore player). You'll see in the config.

Do you use wireless keyboards or are several keyboards connected to your computer?

No, wired keyboard and mouse, only one of them.

This issue could potentially be linked to #305 but we weren't able to reproduce it so far.

It seems to be a widespread problem for Windows users, as I told before one of the servers I'm used to play in was quite always full, now rarely it gets more than 10-12 people playing, and most of them (me too) can play only for a couple of mins before a crash happens.

EDIT: I'm the same user as bozzy-gh, sorry, forgot to login with the right user, this is my work account.

Barbatos commented 6 years ago

Thank you for answering my questions. I look forward to seeing your config file. There must be some factor making it happen only for some players... I and others have played for at least a dozen of hours since the 4.3.3 release, on public and private servers, filled with 10 to 24 players and we've never crashed nor seen anyone complain about crashes.

Some more questions...

Are you playing on Windows 10? Windows 7? Windows XP ( :zipper_mouth_face: )? Did you update through the UrTUpdater or by downloading a zip/torrent file? From the official website? Do you use a custom/third party engine? Could you please run the Updater again which will check all your files and make sure that all of them are up to date and not corrupted?

bozzy-gh commented 6 years ago

I look forward to seeing your config file. There must be some factor making it happen only for some players..

I'll try to play with a default config file this or tomorrow evening.

Are you playing on Windows 10? Windows 7? Windows XP ( 🤐 )?

Windows 10 (64bit).

Did you update through the UrTUpdater or by downloading a zip/torrent file? From the official website? [...] Could you please run the Updater again which will check all your files and make sure that all of them are up to date and not corrupted?

Both by UrTUpdater (first attempt), then after experiencing some crashes I've downloaded the full 4.3.3 zip from the official website, I've extracted it on a new path and copied my config file from the old to the new path. It couldn't be something corrupted on my PC, both because of the fresh new install and because of all the other users experiencing the same crashes (freezes, to be precise).

Do you use a custom/third party engine?

No (actually never known of).

bozzy-gh commented 6 years ago

qconsole.log

Clean install, only thing changed in config is user name and screen resolution, nothing else. Still crashes exactly like before. Here's my config file and another log.

bozzy-gh commented 6 years ago

q3config.cfg.txt Ok, GIT didn't allowed the extension .cfg, here the renamed file ;)

bozzy-gh commented 6 years ago

News: I usually play in TD servers, this evening I've tried a well populated FFA server... no crashes at all for over an hour! This can narrow it down a little...

Barbatos commented 6 years ago

Thank you @bozzy-gh for your help.

We were able to replicate your issue yesterday on several crowded TDM servers on the Eagle map. We've also narrowed the issue down to the QVM and are currently investigating what in the QVM could cause this. I'll get back to you guys as soon as we have more information.

@bozzy-gh did you also crash on a specific map (Eagle) and game mode (TDM)?

Thanks!

bozzy-gh commented 6 years ago

did you also crash on a specific map (Eagle) and game mode (TDM)?

Yes, it seems from my tests (see my latest message) that playing on crowded FFA servers doesn't crash the game. I usually play in TDM mode and the server I experienced more problems is on Eagle 24/24, but I'm quite sure I got crashes on other maps also (don't remember which ones, maybe Abbey...).

Glad to see you're able to reproduce the problem, I know it's crucial for investigation 👍

bozzy-gh commented 6 years ago

Hi. Are there any news?

Barbatos commented 6 years ago

Hi,

Unfortunately, we're still looking into it. This issue is very hard to track down because of how randomly it happens. It also doesn't happen when running debug tools, making it even harder. We're doing everything we can to find and fix the issue ASAP. We've spent more than five evenings on this already and this is not over...

If you have any new information regarding the issue, please do not hesitate to post it here.

Core-Urbania commented 6 years ago

Hi, I am head-admin Core of the server |DN| Eagle 24/7. As you will understand, this problem is of high importance to us. I have 3 observations I like to share with you. Hopefully these observations provide hints to solve this problem.

  1. Linux and Mac users NEVER experienced problems. Neither in 4.3.2, nor in 4.3.3 Only Windows users crash on the Eagle map. In 4.3.3 Windows users crash as often as 3 times in 5 minutes. We note an increasing crash chance if the server is filling up with players. In short: the Eagle map has become unplayable for 4.3.3 players with Windows clients.
  2. In version 4.3.2 we had similar crash problems , but far less frequent. Mostly the crashes would occur during high-speed, jumping and shooting encounters. And yes, some players would crash more than others. The situation was certainly not good, but just bearable for most.
  3. Last week - as a test - I ran other maps on the same Eagle hardware. (Without touching the running B3 and echelon software) I ran the maps: Ramelle, Kingdom, Tunis, Toxic and intermodal_beta. Each for about an hour. NO crashes were reported during this testing period by our Windows players. So it seems to be an Eagle only problem.
bozzy-gh commented 6 years ago

Hi. Actually I'm one of the users who plays on |DN| Eagle 24/7. You're confirming what I've experienced and reported here: crash chance is directly proportional to number of players. I've found myself playing on your server for about half an hour without problems when we were in 3 or 4 total users. Then players started to arrive and crashes increased with them. About point 2, I've never had a crash in 4.3.2 or earlier in your server, but I'm just an occasional player (I'm there one or two hours a couple of days per week). I give you this info to emphasize the completely different experience I'm having between 4.3.2 (never crashed) and 4.3.3 (unplayable)... I think, but I could be wrong, that the crashes you've observed in 4.3.2 aren't correlated to the problems we're having in 4.3.3. About point 3, I'm not totally sure but when I was trying to understand what was going wrong after updating to 4.3.3, I played on various servers (always TDM) and I seem to remember I had a crash on the map Abbey... but my primary goal was to sort out if it was something with my installation or not, so maybe I've confused things a bit. If I'll experience crashes on other maps I'll report here promptly.

bozzy-gh commented 6 years ago

@Core-Urbania btw, couldn't you set your server to still accept connections with version 4.3.2 until the problem is solved?

Critofur commented 6 years ago

We've also narrowed the issue down to the QVM and are currently investigating what in the QVM could cause this.

On which repo is this code so we can speed up things?

I found plenty of repos when searching. The FrozenSand? The ioq3? The ioq3-for-UrbanTerror?

Barbatos commented 6 years ago

The game code is closed source.

highzone commented 6 years ago

Hello. I'm experiencing the same problem with the 4.3.3 .
I'm using windows 10 64 bit. (update from win7)

Intel Core I7-4770k Geforce GTX780 TI

I play most of the time in bomb mode. 90% the nexunity server. ( https://www.urbanterror.info/servers/91.121.183.25:27960/ ) I think it never happend to me in an other game mode.

I did the console save thing maybe it can help.
qconsole.log

This time the game crashed just after loading a map (paris) but it can happen any time for no reason with any map. For me the number of players don't look to be a cause of the crash.

I tried all compatibility modes (from xp to win8) and it still happen. I'm using avira free version as antivirus.

When it crash i have this window that appears and the only choice is to shut the program. crash_4_3_3

friendly. highzone.

danielepantaleone commented 6 years ago

I'm wondering if the FS team is considering a rollback to version 4.3.2. It's been 2 months now since this bug appeared and I believe it's a pretty hard/annoying one to track down.

Barbatos commented 6 years ago

We finally might have found and fixed the crash issue. We'll do some intensive testing in the next few days and release a 4.3.4 version as soon as the fix is confirmed. Thank you guys for your patience. 👍

Barbatos commented 6 years ago

This should be fixed in 4.3.4 ; fix will be confirmed in the upcoming release candidate.