Исправлено: ошибка WarFrame 10054

Содержание

Код ошибки 10054 ammyy admin как исправить

IPv6 (Интернет-протокол версии 6) является последней версией стандарта IP. Интернет-протокол – это протокол связи, который используется для обеспечения механизма идентификации и определения местоположения компьютеров в сетях и маршрутизации веб-трафика через Интернет. Warframe лучше связывается с IPV6. Включив этот протокол в игре, Windows и ваш роутер могут решить проблему.

Решение 3. Обновите сетевые настройки Windows

Если сетевые настройки вашей системы Windows повреждены или не оптимальны для Warframe, то это может вызвать текущую ошибку Warframe. В этом случае изменение / сброс этих настроек может решить проблему.

ipconfig / renew (пропустите, если вы используете статический IP).

Решение 4. Используйте Google DNS

DNS-сервер используется для перевода названия веб-сайта в IP-адрес их хостов. Если у вашего DNS-сервера возникают проблемы с запросом серверов Warframe, игра может выдать ошибку 10054. В этом случае использование DNS-сервера Google может решить эту проблему.

Решение 5. Создайте новую учетную запись WarFrame

Текущая ошибка Warframe может произойти из-за проблемы с вашей учетной записью. Вы можете проверить это, создав другую учетную запись Warframe. Но имейте в виду, что пользователю разрешено иметь несколько учетных записей, но ему запрещено торговать, дарить подарки или взаимодействовать между счетами. Если он это сделает, DE заблокирует оба своих аккаунта.

Решение 6. Отключите UPnP и NAT-PMP в настройках игры

В игре могут быть разные параметры, которые могут вызвать обсуждаемую проблему. Изменение этих параметров может решить проблему.

Решение 7. Используйте статический IP-адрес в маршрутизаторе

Обычно схема IP домашней сети поддерживается автоматически с использованием DHCP. У этого есть свои преимущества, но связь Warframe использует IP-адрес вашего ПК, который может автоматически изменяться DHCP и, таким образом, вызывать проблему. В этом случае установка статического IP-адреса для вашего ПК может решить проблему.

Решение 8. Отключите UPnP / NAT-PMP / Strict NAT в маршрутизаторе

Универсальный Plug and Play (UPnP) – это сетевой протокол, который позволяет подключать проводные / беспроводные соединения к Интернету с минимальной конфигурацией. Но из-за открытого характера этого протокола у Warframe есть проблемы со связью при использовании этого протокола. Отключение UPnP может решить проблему, с которой вы сейчас столкнулись.

Решение 9. Используйте Regedit для отключения TCP / IP

Протокол управления передачей по интернет-протоколу, обычно известный как TCP / IP, представляет собой набор правил, которые используются для соединения различных систем через Интернет. Если связанные с ним записи реестра Windows повреждены, то Warframe может выдать обсуждаемую ошибку. В этом случае отключение разделов реестра Windows, относящихся к TCP / IP вашего компьютера, может решить эту проблему.

HKEY_LOCAL_MACHINE SYSTEM CurrentControlSet Services Tcpip Parameters

Решение 10. Измените настройки вашего маршрутизатора

Если настройки вашего маршрутизатора не настроены должным образом для Warframe, то Warframe может выдать текущую обсуждаемую ошибку. В этом случае изменение этих настроек может решить проблему. Проблема может быть вызвана межсетевым экраном вашего маршрутизатора, включенным QoS, отключенной DMZ

Если у вас все еще есть проблемы, то проблема может быть вызвана настройками NAT вашего маршрутизатора. NAT играет важную роль в переназначении пространства IP-адресов. Возможно, ваши настройки протокола NAT не настроены должным образом для Warframe и, следовательно, вызывают ошибку 10054. В этом случае настройка этих параметров может решить проблему.

Если у вас ничего не получилось, попробуйте остаться в региональном чате, если это не решено. Также вам следует обратиться к вашему провайдеру для решения проблемы. Если вы используете любую форму мобильного интернета, то, возможно, ваш трафик направляется через APN, так как эти интернет-провайдеры используют APN. Но эти APN запрещены NAT (изменение настроек NAT на вашем маршрутизаторе не повлияет на блокировку провайдера) и может вызвать проблему. Интернет-провайдер может предоставить вам APN, где NAT не запрещен (но обычно это не так).

Error 10054 1 in transporttcp2 readexact 2

This article will be useful for those using Ammyy Admin as well as other remote access application users as it contains general info on remote control software which can be applied while using similar remote access applications.

It happens quite often when Ammyy Admin users ask "What is the minimum Internet connection bandwidth that makes Ammyy Admin work ok?". Usually we give an answer like this "Ammyy Admin will work with any Internet bandwidth, but the better Internet is the faster Ammyy Admin works". However, it’s impossible to identify the minimum Internet connection speed required for comfort work because there is no any standard for "comfort work" and the meaning of this term may vary from person to person. Thus "comfort work" term used in this article is nothing more than my personal opinion on the matter and you may have your own different one.

Step 1: Connection speed test

Copy link Quote reply

Ratinod commented Mar 26, 2019

Godot version:
3.1 (March 13, 2019) and 3.0.6

OS/device including version:
Windows 10 x64
GeForce GTX 770/PCIe/SSE2

Issue description:
The game crashes after a while. The game window will freeze and then close, giving the error:
drivers/unix/net_socket_posix. cpp:190 – Socket error: 10054

Steps to reproduce:

This comment has been minimized.

Copy link Quote reply

qarmin commented Mar 26, 2019

I got this backtrace, when I opened all scenes at once:

This comment has been minimized.

Copy link Quote reply

qarmin commented Mar 26, 2019

Also sometimes error about missing function happens:

This comment has been minimized.

Copy link Quote reply

Chaosus commented Apr 2, 2019

Play until the error appears

Can you bisect this bug to – Run the game and its crash?

This comment has been minimized.

Copy link Quote reply

CEDoromal commented Apr 2, 2019

I previously encountered this error in my tilemap game.
For me, the fix was to load in the textures to the tilemap node.
Maybe you have a node with a property that is not properly loaded.

(I’m new to Godot so I’m not really the one to trust with this, but maybe I could help)

This comment has been minimized.

Copy link Quote reply

CEDoromal commented Apr 2, 2019 •

I think it has something to do with Winsock. And if it does, that means that the error is WSAECONNRESET (Error Code: 10054, see https://docs. microsoft. com/en-us/windows/desktop/winsock/windows-sockets-error-codes-2 for more info)

I don’t really know how and why Godot is using Winsock, but these stuffs are beyond my current knowledge.

(I haven’t reached college education yet. Don’t blame me for not understanding these. lol ? )

This comment has been minimized.

Copy link Quote reply

Zireael07 commented Apr 2, 2019

Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)

This comment has been minimized.

Copy link Quote reply

CEDoromal commented Apr 2, 2019

Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)

Well now I know why Godot is using Winsock. Thanks! ?

This comment has been minimized.

Copy link Quote reply

Zireael07 commented Apr 2, 2019

Most probably your project is doing something which causes the project itself to crash. badly named variables, recursive references, missing assets could all be the reason.

This comment has been minimized.

Copy link Quote reply

Ratinod commented Apr 2, 2019

Play until the error appears

Can you bisect this bug to – Run the game and its crash?

No. The game never crashed on launch. You need to play for a while until you get an error.

Most probably your project is doing something which causes the project itself to crash. badly named variables, recursive references, missing assets could all be the reason.

I am new to Godot. And this project was done strictly following the tutorial. Twice from scratch (on versions 3.0.6 and 3.1). And this problem occurred both times. The problem does not allow itself to be found (not an informative error without any specifics).

This comment has been minimized.

Copy link Quote reply

OlexiyKravchuk commented May 5, 2019

I have the same problem with my project in Godot_v3.1-stable_win64.

This comment has been minimized.

Copy link Quote reply

OlexiyKravchuk commented May 5, 2019 •

I completely deleted a lot of comments in which they hit lines like this – ("""some kind of code" value of the line "some kind of code""") and this helped, after this, such error stopped appearing. If there are relapses I will inform.

This comment has been minimized.

Copy link Quote reply

Hedre commented May 12, 2019

I have this problem too

This comment has been minimized.

Copy link Quote reply

ScepticDope commented May 13, 2019 •

Same error here, Windows 8.1 V3.1.1 Mono stable. After a reboot everything works fine again? I only get this on launch after messing around with 3D camera’s.

This comment has been minimized.

Copy link Quote reply

robertarnborg commented May 16, 2019 •

I am getting this error when changing scenes or reloading scenes sometimes ?

This comment has been minimized.

Copy link Quote reply

paacardoso commented May 16, 2019

I found out that disabling the debugger agent (in Project Settings/Mono/Debugger Agent/Wait For Debugger) will solve this issue.

This comment has been minimized.

Copy link Quote reply

hedgehog90 commented May 30, 2019

I get this error + crash when trying to debug Godot using vs code.

This comment has been minimized.

Copy link Quote reply

Obr00007576 commented Jun 2, 2019

This comment has been minimized.

Copy link Quote reply

Obr00007576 commented Jun 3, 2019

I’ve solved my problem. At the beggining I tried to use ‘export(packedscene) var scene’ to export the scene and then use function change_scene_to to get into another scene. The error occured in this way but when I tried to use change_scene with parameter of the path of the scene, everything was in order. So, I guess, the operation of export happens at the begginning of the programm and it is the first step. If the scenes are exported in circle just as what I said in the last comment, godot will stick on loading those scenes in dead circle. When it got the limit of memory or quantity of functions or anything else I’m not sure, godot got broken with this error because its debugger had been broken.

This comment has been minimized.

Copy link Quote reply

winston-yallow commented Jun 17, 2019 •

I have the same error message (only on windows, Linux seems to run smooth for me). I am not sure if it is caused by the same thing as the error message itself is not very descriptive. My project has only a few nodes. The only one with a script is a RigidBody with some _integrate_forces() things. The error consistently appears after the game ran for a few seconds (basically the error appears when the body reaches a "stable" position). My code was a small test for an idea I had (limiting the movement of a RigidBody onto a Curve3D. ). The code is far from perfect, however it should not make the engine crash.

If you think this is not related to this issue please let me know so I can create a separate issue. The error message itself does not really tell me what is wrong or why it appears.

Godot Version:
v3.2.dev. calinou.197b65f32

OS:
Windows 10 x64

Minimal reproduction project:
testing. zip

Code that enables the bug:

This comment has been minimized.

Copy link Quote reply

Zireael07 commented Jun 17, 2019

That doesn’t look like GDScript, nor C#. What language/bindings is that?

This comment has been minimized.

Copy link Quote reply

winston-yallow commented Jun 17, 2019

Do you mean my example? It is GDScript (using type annotations)

This comment has been minimized.

Copy link Quote reply

winston-yallow commented Jun 17, 2019

After further investigation I think the drivers/unix/net_socket_posix. cpp:190 – Socket error: 10054 error is only hiding another error which causes the game to crash. In my case I found an error in my code:

This comment has been minimized.

Copy link Quote reply

Klassix commented Jun 18, 2019 •

Hi iam currently doing the "Discovering Godot: Make Video Games in Python-like GDScript" on udemy. While trying around for an exercise ive also run into this bug. Heres the bugged project:

This comment has been minimized.

Copy link Quote reply

qarmin commented Aug 23, 2019

If you thinks it might be a Godot bug, then attach here a minimal project to reproduce it.

This comment has been minimized.

Copy link Quote reply

golddotasksquestions commented Aug 23, 2019 •

Only after shutting down and restarting Windows, Godot stopped crashing when I started to run my project.

This crashing behavior and error cost me way too much time though. I did not consider restart earlier, because I had no problem with Windows or other Window applications while the issue was present. I also had no problem working within the Godot editor while the crashing was occurring, as it only crashed the window in which I tried to run my project. Restarting Godot itself did not help.

After trying to run another Godot project which I did not touch that day with the same crash and error was it clear that I had to restart my system.

Even if this is not a Godot bug, the error message (as it is so often) could be a lot more informative about what is going on and how to solve the issue.

This comment has been minimized.

Copy link Quote reply

SarojKumar10 commented Aug 28, 2019

It happened to me when I deleted a material on which a model was depended on. Making the material with same name and extension fixed it.

This comment has been minimized.

Copy link Quote reply

akien-mga commented Oct 10, 2019 •

To everyone who reported issues in this thread apart from OP, please open your own issues.

This issue should have been renamed earlier but "Socket error: 10054" is NOT A BUG and this is also not a common denominator between the issues you are facing. It’s just a message from the debugger telling you that the debugger can’t connect anymore — because your game process crashed.

As such this issue is basically a collection of "my game can crash" comments, which you can easily imagine might have a thousand different causes for every single commenter here.

This issue should be solely about debugging the crash when playing the game in #27444 (comment), all other issues should have their own ticket with detailed steps to reproduce and reproduction project, otherwise they have no change to be fixed.

This comment has been minimized.

Copy link Quote reply

akien-mga commented Oct 10, 2019

@Ratinod I played the match3 game for a few minutes on Godot 3.2 alpha 1 and did not get any issue. Can you still reproduce the crash?

This comment has been minimized.

Copy link Quote reply

Toshiwoz commented Oct 10, 2019

@akien-mga, to my understanding what happens is what is mentioned here:

Socket error 10054 is because the debugger is using Winsock, and it’s disconnecting when the crash happens and/or it gets unexpected data. (Yes, I have had cases where the game runs perfectly IF I don’t touch the remote tree tab, then it crashes, because the debugger for some reason cannot handle it)
Based on this comment #27444 (comment)

So, if the debugger cannot handle the error, there’s no error message to look at. And, this way it becomes very hard to debug the issue. Meaning that it would become very hard to create a minimal reproduction project, as the CAUSE of the issue is unknown.

This issue should have been renamed earlier but "Socket error: 10054" is NOT A BUG
all other issues should have their own ticket with detailed steps to reproduce and reproduction project, otherwise they have no change to be fixed.

And this worries me, because I don’t know how to find the source of the problem, in other words it will become very hard to fix my specific issue. And given what you say it sounds like there will be no help from here.
I’ll delete my "spam" comment anyhow. (not this one)

This comment has been minimized.

Copy link Quote reply

akien-mga commented Oct 10, 2019 •

@Toshiwoz I didn’t mean that any comment was spam – but each comment stating that they have the "same" issue should actually be their own issue with detailed information on what issue you actually have.

So, if the debugger cannot handle the error, there’s no error message to look at. And, this way it becomes very hard to debug the issue. Meaning that it would become very hard to create a minimal reproduction project, as the CAUSE of the issue is unknown.

It’s not about the debugger not being able to handle the error. The game crashes (process killed), so the connection to the debugger is severed. The debugger notifies it and reports that.

The fact that there is no other error is not related to the debugger losing its connection.

Источники:

https://ddok. ru/ispravleno-oshibka-warframe-10054-appuals-com/

https://pcznatok. ru/kompjutery/error-10054-1-in-transporttcp2-readexact-2.html

Понравилась статья? Поделиться с друзьями:
Добавить комментарий

;-) :| :x :twisted: :smile: :shock: :sad: :roll: :razz: :oops: :o :mrgreen: :lol: :idea: :grin: :evil: :cry: :cool: :arrow: :???: :?: :!: