安装 Steam
登录
|
语言
繁體中文（繁体中文）
日本語（日语）
한국어（韩语）
ไทย（泰语）
български（保加利亚语）
Čeština（捷克语）
Dansk（丹麦语）
Deutsch（德语）
English（英语）
Español-España（西班牙语 - 西班牙）
Español - Latinoamérica（西班牙语 - 拉丁美洲）
Ελληνικά（希腊语）
Français（法语）
Italiano（意大利语）
Bahasa Indonesia（印度尼西亚语）
Magyar（匈牙利语）
Nederlands（荷兰语）
Norsk（挪威语）
Polski（波兰语）
Português（葡萄牙语 - 葡萄牙）
Português-Brasil（葡萄牙语 - 巴西）
Română（罗马尼亚语）
Русский（俄语）
Suomi（芬兰语）
Svenska（瑞典语）
Türkçe（土耳其语）
Tiếng Việt（越南语）
Українська（乌克兰语）
报告翻译问题
讨论规则及指引
举报此帖
~30-50% matches have one or two players who got disconnected and have to re-login to the game. Ffs it's obvious game's problem, client or server side. I also got disconnect 1 time per 50-70 matches while any other online game works fine and without any problems, even games with p2p multiplayer.
If "A" have some regular problem when "B", 'C", "D", "E", "F", etc don't have this problem, it mean that it's "A" fault.
I don't know how their servers works, I don't know how client syncs matches, but I know that I never saw regular disconnect problem in any other online games (I tried literally dozens in my life).
I think this disconnections is a bug. Server or client side. And HiRez knows about it but it's requers too much work to fix this. And like it always happens - you fix "x" but you break "y", maybe fixing this bug is almost impossible with current engine and all mechanics and stuff in it.
So, in order to keep tracking of which machines are loading the data accurately and consistently, it's possible that some machines are so busy loading the data for the map/game/models, that they don't respond to the server by saying "yes, I've loaded the data and ready to play", therefore, causing a timeout.
The server may still be waiting to see if the client can reconnect, but at that point in time (during the loading screen) the client will still be busy loading the data and not know to 'reconnect'.
So, it could be a catch-22 in that the machines that can't handle loading the data in a reasonable time (which for a lot of us, is still TOO DAMN LONG), it gives up and essentially forgets about that client, leading to a bot having to be loaded once the game is in match mode.
The reason a person that DC'd during loading can't reconnect (or reconnects as a spectator) is AGAIN linked to the fact that:
a) due to crashing during the load sequence, the client never got the details of which server to connect to for the match. So they just can't reconnect.
b) For those that return as spectators, I'd guess it's due to the fact the machine took so long to reconnect, it doesn't allow the client to connect as a player, but just gives them spectator access instead.
Therefore, I think that the main issue for these DC issues is down to PC performance (or lack, thereof).
Yes, I can imagine that things could have worked better previously, but we don't know what they've added to the game (perhaps to enhance the graphic quality, etc.) in the patches for the last 3-6 months where the DC issues have increased. We also don't know what MS has done with Win 10 that could have seriously affected game performance (such as fixes for Spectre or Meltdown that have caused CPU's to essentially run slower).
For those of us with moderately ok PC's (5 years old, and wasn't leading edge at the time) and perhaps having SSD's (a HUGE benefit!!!!), you could be absolutely fine and play the game without issues. Once again, this is NOT Hi-Rez's fault or problem. Get a PC that can run the game.
its a free game what do u expect?
p.s - not every f2p game is tf2, cheers
Battlerite, LoL, Dota 2, tons of f2p shooters. All working fine without players who getting dc during loading.
@Nefser
I think same more or less but still it is HiRez's fault. I don't mind to wait 30 seconds or so to wain somebody load, the problem is in a client and how it's work I'm sure.
Any match where I had to reconnect (one crash, graphics bug 3 times where I restarted on my own), i just reconnected fine.
Again, this is down to THE PLAYERS PC, and NOT due an issue with Hi-Rez.
If you crash during the loading screen, I don't think the client (i.e., your PC) has the details to know which server instance to connect to for the match, thus leading you to never reconnect and getting deserter status.
If you crash during the match (as long as you've made it to the base before the match starts), if you HAVE A DECENT PC/CONNECTION, you can reconnect to the game.
I have never "NOT" been able to re-connect to a match that I DC'd from, either by a crash (only one 'code' crash error) or when I've had to restart my client. So based, on what I've seen how the client/server situation works in a variety of instances, with a reasonably capable machine, I'd really, really have to lay most of the issue at the feet of those with rather lower spec. machines.
I'm not blaming you or insulting you for having low-spec machines. But be reasonable about how things work/don't work, in regards to the capability (or lack, thereof) of your own PC.
most people get dc during loading and they reconnect without any problems. This problem is common and regular. Since 1st day ea-release. ~Half of my matches have such player. Half of these players from my team, most of them type "i'm here, sorry, got dc".
And you can read my comments to find out how often I got dc during loading. It's HiRez's fault on making game's engine. If other games can load all players properly (even if most of them have wait somebody with wooden pc) and Paladins can't - it's Hirez's fault.
No. It's NOT their fault. Please read my latest comments and let that sink in. Their servers can't necessarily cope with a lack of communication from your PC and makes decisions based on that lack of feedback.
Yes, perhaps this could be coded slightly differently, but then again, given that they're already allowing this game to be run on VERY low spec. PC's, I'm not surprised that they've tried to tighten things up by restricting the timeout.
I've never reconnected when having an issue at the loading screen. I'd love to hear from others that have.
Specifically "at the loading screen".
Champ selection - yes.
Match - yes.
Loading screen - no.
Hmmm. Yes. I think that's a cause of some of these "Sorry, I DC'd."
I have a theory that HiRez doesn't have enough playerbase to suit enough players so they spread these bots left and right. Prove me wrong.
I mean, sure, someone may disconnect but all I see is someone never loads and NEVER comes back. N_E_V_E_R.
when I play ranked matches and someone from my team got dc, he usualy say something like "I'm back, got dc". Most people comes back, in ranked always comes back. Your "theory" is far from reality, I think it's just a bad engine code.
Correct. As I've said numerous times, ANYONE that crashes as part of the loading section can NOT come back, as they don't have the details of the server where the match will be played.
Anyone that crashes in either Champ selection (and is able to re-load quick enough to connect while the selections are being made), or during/at the start of the match will be able to reconnect.
The biggest problem is people with machines that may be struggling to load the game/map/models and that's where the real issue lies. It's because these people can never re-join that we end up having to suffer with bots that play through the match.
Ok. But the engine code is unreal 3 engine code, which is not necessarily Hi-Rez code (or at least probably not all of it) and part of what 'they get' when they use the engine. However, depending on whatver else is going on during the loading screen (which causes machines to crash), I'd imagine it's linked to issues with that pc AND the game code, not the game code on its own (as otherwise we'd all have these problems, or at least have them on a regular basis).
Code that runs on 90-95% successfully, game after game after game is not really an issue and cannot be called "the problem" just because it doesn't work correctly or times out on the other 10% of machines. (Or whatever the %'s are). It MUST be far more related to the OS version, patches, qualtity, performance, configuration of those other 10% of machines - therefore NOT directly something that people should expect Hi-Rez to be able to 'fix'.
for example if I alt+tab during load game crashes. It was crashing like this two years ago and it keeps doing that.
today game crashed during champions selection, no idea why, never seen that bug before. So-o... Probably new bugs r to blame.