Bugs with chat, lifeforms and so on
Resistor
Russia Join Date: 2014-08-01 Member: 197747Members
Russia Join Date: 2014-08-01 Member: 197747Members
Faced some bugs:
1) my messages in chat appear appear only after several minutes
2) can't buy anything in armory/prototype
3) can't take any lifeform or upgrade (actually, I managed to take gorge once right after joining to a team)
-was not able to build anything by being gorge
4) can't log out from hive/command station
5) some console commands do not work (j1, j2, sv_status...); disconnect and quit are still working
6) can't vote for shuffle or rtv (standard vote with f1/f2 still works)
7) can't request a medpack or ammo
8) f4 also is not operable
Have this issue on every server, regardless of mods (ns2+, combat, competitive).
Besides named problems everything looks fine.
Also, everything works in sandbox mode.
NS2.exe is added to exceptions in windows firewall, unsubscribed from all mods.
Uninstall (according to this thread ) did not help.
Below there are links for "tech support" and demo (forgot to type something in chat, can rewrite if necessary).
tech support
demo
small demonstration of some bugs on youtube
Waiting for advice.
1) my messages in chat appear appear only after several minutes
2) can't buy anything in armory/prototype
3) can't take any lifeform or upgrade (actually, I managed to take gorge once right after joining to a team)
-was not able to build anything by being gorge
4) can't log out from hive/command station
5) some console commands do not work (j1, j2, sv_status...); disconnect and quit are still working
6) can't vote for shuffle or rtv (standard vote with f1/f2 still works)
7) can't request a medpack or ammo
8) f4 also is not operable
Have this issue on every server, regardless of mods (ns2+, combat, competitive).
Besides named problems everything looks fine.
Also, everything works in sandbox mode.
NS2.exe is added to exceptions in windows firewall, unsubscribed from all mods.
Uninstall (according to this thread ) did not help.
Below there are links for "tech support" and demo (forgot to type something in chat, can rewrite if necessary).
tech support
demo
small demonstration of some bugs on youtube
Waiting for advice.
Comments
Aliens
Chat
For the last video:
0:13 - attempt to write test message-1
0:48 - attempt to write test message-2
2:55 - attempts to ping map, request heal, taunt, chuckle
3:21 - test message-1 appears
4:56 - test message-2 appears, ping, chucke (at the same time)
Usually can't use them though (but, once I managed to get almost all upragdes for one kill).
Internet provider and router were the same.
Tomorrow will try connecting to internet directly, without router.
Can you reproduce the problem within 5 minutes max using net_log 3 please?
Made 2 logs, for marines and for aliens.
Don't know if there is any sense in making videos. Made it just in case.
Server with "pregame" mod, marines. Needed pregame to demonstrate bug with armory. Recorded until chat message appeared. (log_rines_pregame)
Server without any mods, aliens (log_aliens)
Please tell if you need any other information.
Thanks for help.
Unrelated, but you should be running DX9 fullscreen, not DX11.
Could you open command prompt in windows and do a trace route? :
To start the command prompt in Windows-8 or 8.1, press the key combination [Win-Logo]+[R], then simply type the command cmd and confirm that with [ENTER] or by pressing the button [OK]!
Now type : tracert 82.199.102.133:27045
When it's done press the "PRINT SCRN" Button on your keyboard to take a picture of the results and then upload that picture here. (ctrl + V in Paint or something)
+++ WER0 +++:
Êîíòåéíåð îøèáêè , òèï 0
Èìÿ ñîáûòèÿ: MpTelemetry
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.5.218.0
P5: Çàùèòíèê Windows (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 58e1f776-4e4a-11e4-83ff-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 96
Õýøèðîâàííûé êîíòåéíåð:
+++ WER1 +++:
Êîíòåéíåð îøèáêè , òèï 0
Èìÿ ñîáûòèÿ: MpTelemetry
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.5.218.0
P5: Çàùèòíèê Windows (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 58e1f776-4e4a-11e4-83ff-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 4100
Õýøèðîâàííûé êîíòåéíåð:
+++ WER2 +++:
Êîíòåéíåð îøèáêè , òèï 0
Èìÿ ñîáûòèÿ: RADAR_PRE_LEAK_WOW64
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: AI.exe
P2: 0.0.0.0
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
C:\Users\Resistor\AppData\Local\Temp\RDRCE10.tmp\empty.txt
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 509cf17c-4df9-11e4-83fd-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 96
Õýøèðîâàííûé êîíòåéíåð:
+++ WER3 +++:
Êîíòåéíåð îøèáêè 94602595211, òèï 5
Èìÿ ñîáûòèÿ: RADAR_PRE_LEAK_WOW64
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: nightmare.exe
P2: 1.0.15664.0
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
C:\Users\Resistor\AppData\Local\Temp\RDR2AFC.tmp\empty.txt
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 5d2f1239-4cab-11e4-83f7-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 0
Õýøèðîâàííûé êîíòåéíåð: c553776e49268d0b81c8028f25e41948
+++ WER4 +++:
Êîíòåéíåð îøèáêè 94597990899, òèï 5
Èìÿ ñîáûòèÿ: RADAR_PRE_LEAK_64
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: EndlessLegend.exe
P2: 4.5.4.31047
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
C:\Users\Resistor\AppData\Local\Temp\RDR4090.tmp\empty.txt
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: dedbe5fe-4bc2-11e4-83f3-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 0
Õýøèðîâàííûé êîíòåéíåð: 970cbb09879d5f6afe8ba6acd318c047
+++ WER5 +++:
Êîíòåéíåð îøèáêè -751049027, òèï 5
Èìÿ ñîáûòèÿ: AEAPPINVW8
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: e386efc7-4b04-11e4-83f0-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 0
Õýøèðîâàííûé êîíòåéíåð: dbd94bb9bcc526682a050bf66e2816ab
+++ WER6 +++:
Êîíòåéíåð îøèáêè 73538366796, òèï 1
Èìÿ ñîáûòèÿ: APPCRASH
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: rogame.exe
P2: 0.0.0.0
P3: 541ca1b0
P4: rogame.exe
P5: 0.0.0.0
P6: 541ca1b0
P7: c0000005
P8: 00068cb0
P9:
P10:
Âëîæåííûå ôàéëû:
C:\Users\Resistor\AppData\Local\Temp\WER7DF3.tmp.WERInternalMetadata.xml
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
C:\Users\Resistor\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_rogame.exe_e6112037c3d360e951f17a1068ce91bd3761c1_a7fd97bc_0a3c846c
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 42312c44-4aeb-11e4-83ed-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 1
Õýøèðîâàííûé êîíòåéíåð: 9a2b17afc53b21c0c2b538e2b10d7c4c
+++ WER7 +++:
Êîíòåéíåð îøèáêè 94529420440, òèï 5
Èìÿ ñîáûòèÿ: RADAR_PRE_LEAK_WOW64
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: ss2013.exe
P2: 4.3.4.31067
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
C:\Users\Resistor\AppData\Local\Temp\RDR2A9E.tmp\empty.txt
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 69633c74-492e-11e4-83e4-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 0
Õýøèðîâàííûé êîíòåéíåð: 1e5d7037ca3ca5221cb6850c0e46e759
+++ WER8 +++:
Êîíòåéíåð îøèáêè -751049027, òèï 5
Èìÿ ñîáûòèÿ: AEAPPINVW8
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: 05282136-48a5-11e4-83df-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 0
Õýøèðîâàííûé êîíòåéíåð: dbd94bb9bcc526682a050bf66e2816ab
+++ WER9 +++:
Êîíòåéíåð îøèáêè -751049027, òèï 5
Èìÿ ñîáûòèÿ: AEAPPINVW8
Îòêëèê: Íåò äàííûõ
Èäåíòèôèêàòîð CAB: 0
Ñèãíàòóðà ïðîáëåìû:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Âëîæåííûå ôàéëû:
Ýòè ôàéëû ìîæíî íàéòè çäåñü:
Ñèìâîë àíàëèçà:
Ïîâòîðíûé ïîèñê ðåøåíèÿ: 0
Èäåíòèôèêàòîð îò÷åòà: ca1ac5d7-48a4-11e4-83df-e06995a3699c
Ñîñòîÿíèå îò÷åòà: 0
Õýøèðîâàííûé êîíòåéíåð: dbd94bb9bcc526682a050bf66e2816ab
Also is EVERYTHING delayed or just text?
+++ WER0 +++:
Контейнер ошибки , тип 0
Имя события: MpTelemetry
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.5.218.0
P5: Защитник Windows (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Вложенные файлы:
Эти файлы можно найти здесь:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 58e1f776-4e4a-11e4-83ff-e06995a3699c
Состояние отчета: 96
Хэшированный контейнер:
+++ WER1 +++:
Контейнер ошибки , тип 0
Имя события: MpTelemetry
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.5.218.0
P5: Защитник Windows (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Вложенные файлы:
Эти файлы можно найти здесь:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 58e1f776-4e4a-11e4-83ff-e06995a3699c
Состояние отчета: 4100
Хэшированный контейнер:
+++ WER2 +++:
Контейнер ошибки , тип 0
Имя события: RADAR_PRE_LEAK_WOW64
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: AI.exe
P2: 0.0.0.0
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
C:\Users\Resistor\AppData\Local\Temp\RDRCE10.tmp\empty.txt
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 509cf17c-4df9-11e4-83fd-e06995a3699c
Состояние отчета: 96
Хэшированный контейнер:
+++ WER3 +++:
Контейнер ошибки 94602595211, тип 5
Имя события: RADAR_PRE_LEAK_WOW64
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: nightmare.exe
P2: 1.0.15664.0
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
C:\Users\Resistor\AppData\Local\Temp\RDR2AFC.tmp\empty.txt
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 5d2f1239-4cab-11e4-83f7-e06995a3699c
Состояние отчета: 0
Хэшированный контейнер: c553776e49268d0b81c8028f25e41948
+++ WER4 +++:
Контейнер ошибки 94597990899, тип 5
Имя события: RADAR_PRE_LEAK_64
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: EndlessLegend.exe
P2: 4.5.4.31047
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
C:\Users\Resistor\AppData\Local\Temp\RDR4090.tmp\empty.txt
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: dedbe5fe-4bc2-11e4-83f3-e06995a3699c
Состояние отчета: 0
Хэшированный контейнер: 970cbb09879d5f6afe8ba6acd318c047
+++ WER5 +++:
Контейнер ошибки -751049027, тип 5
Имя события: AEAPPINVW8
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: e386efc7-4b04-11e4-83f0-e06995a3699c
Состояние отчета: 0
Хэшированный контейнер: dbd94bb9bcc526682a050bf66e2816ab
+++ WER6 +++:
Контейнер ошибки 73538366796, тип 1
Имя события: APPCRASH
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: rogame.exe
P2: 0.0.0.0
P3: 541ca1b0
P4: rogame.exe
P5: 0.0.0.0
P6: 541ca1b0
P7: c0000005
P8: 00068cb0
P9:
P10:
Вложенные файлы:
C:\Users\Resistor\AppData\Local\Temp\WER7DF3.tmp.WERInternalMetadata.xml
Эти файлы можно найти здесь:
C:\Users\Resistor\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_rogame.exe_e6112037c3d360e951f17a1068ce91bd3761c1_a7fd97bc_0a3c846c
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 42312c44-4aeb-11e4-83ed-e06995a3699c
Состояние отчета: 1
Хэшированный контейнер: 9a2b17afc53b21c0c2b538e2b10d7c4c
+++ WER7 +++:
Контейнер ошибки 94529420440, тип 5
Имя события: RADAR_PRE_LEAK_WOW64
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: ss2013.exe
P2: 4.3.4.31067
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
C:\Users\Resistor\AppData\Local\Temp\RDR2A9E.tmp\empty.txt
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 69633c74-492e-11e4-83e4-e06995a3699c
Состояние отчета: 0
Хэшированный контейнер: 1e5d7037ca3ca5221cb6850c0e46e759
+++ WER8 +++:
Контейнер ошибки -751049027, тип 5
Имя события: AEAPPINVW8
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: 05282136-48a5-11e4-83df-e06995a3699c
Состояние отчета: 0
Хэшированный контейнер: dbd94bb9bcc526682a050bf66e2816ab
+++ WER9 +++:
Контейнер ошибки -751049027, тип 5
Имя события: AEAPPINVW8
Отклик: Нет данных
Идентификатор CAB: 0
Сигнатура проблемы:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Вложенные файлы:
Эти файлы можно найти здесь:
Символ анализа:
Повторный поиск решения: 0
Идентификатор отчета: ca1ac5d7-48a4-11e4-83df-e06995a3699c
Состояние отчета: 0
Хэшированный контейнер: dbd94bb9bcc526682a050bf66e2816ab
+++ WER0 +++:
Error container , type 0
Event name: MpTelemetry
Responce: no data
CAB descriptor/identifier: 0
Problem signature:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.5.218.0
P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Attached files:
These files can be bound here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d
Symbol/character analysis:
Repeated search for solution Повторный поиск решения: 0
Report identifier : 58e1f776-4e4a-11e4-83ff-e06995a3699c
Report status: 96
Hash container:
+++ WER1 +++:
Error container , type 0
Event name: MpTelemetry
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: 2152759308
P2: unspecified
P3: ScanFile
P4: 4.5.218.0
P5: Windows Defender (77BDAF73-B396-481F-9042-AD358843EC24)
P6: unspecified
P7: unspecified
P8:
P9:
P10:
Attached files:
These files can be found here:
C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: 58e1f776-4e4a-11e4-83ff-e06995a3699c
Report status: 4100
Hash container:
+++ WER2 +++:
Error container , type 0
Event name: RADAR_PRE_LEAK_WOW64
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: AI.exe
P2: 0.0.0.0
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\Resistor\AppData\Local\Temp\RDRCE10.tmp\empty.txt
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: 509cf17c-4df9-11e4-83fd-e06995a3699c
Report status: 96
Hash container:
+++ WER3 +++:
Error contaner 94602595211, type 5
Event name: RADAR_PRE_LEAK_WOW64
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: nightmare.exe
P2: 1.0.15664.0
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\Resistor\AppData\Local\Temp\RDR2AFC.tmp\empty.txt
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: 5d2f1239-4cab-11e4-83f7-e06995a3699c
Report status: 0
Hash container: c553776e49268d0b81c8028f25e41948
+++ WER4 +++:
Error contaner 94597990899, type 5
Event name: RADAR_PRE_LEAK_64
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: EndlessLegend.exe
P2: 4.5.4.31047
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\Resistor\AppData\Local\Temp\RDR4090.tmp\empty.txt
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: dedbe5fe-4bc2-11e4-83f3-e06995a3699c
Report status: 0
Hash container: 970cbb09879d5f6afe8ba6acd318c047
+++ WER5 +++:
Error contaner -751049027, type 5
Event name: AEAPPINVW8
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Attached files:
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: e386efc7-4b04-11e4-83f0-e06995a3699c
Report status: 0
Hash container: dbd94bb9bcc526682a050bf66e2816ab
+++ WER6 +++:
Error contaner 73538366796, type 1
Event name: APPCRASH
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: rogame.exe
P2: 0.0.0.0
P3: 541ca1b0
P4: rogame.exe
P5: 0.0.0.0
P6: 541ca1b0
P7: c0000005
P8: 00068cb0
P9:
P10:
Attached files:
C:\Users\Resistor\AppData\Local\Temp\WER7DF3.tmp.WERInternalMetadata.xml
These files can be found here:
C:\Users\Resistor\AppData\Local\Microsoft\Windows\WER\ReportArchive\AppCrash_rogame.exe_e6112037c3d360e951f17a1068ce91bd3761c1_a7fd97bc_0a3c846c
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: 42312c44-4aeb-11e4-83ed-e06995a3699c
Report status: 1
Hash container: 9a2b17afc53b21c0c2b538e2b10d7c4c
+++ WER7 +++:
Error contaner 94529420440, type 5
Event name: RADAR_PRE_LEAK_WOW64
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: ss2013.exe
P2: 4.3.4.31067
P3: 6.3.9600.2.0.0
P4:
P5:
P6:
P7:
P8:
P9:
P10:
Attached files:
C:\Users\Resistor\AppData\Local\Temp\RDR2A9E.tmp\empty.txt
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: 69633c74-492e-11e4-83e4-e06995a3699c
Report status: 0
Hash container: 1e5d7037ca3ca5221cb6850c0e46e759
+++ WER8 +++:
Error container -751049027, type 5
Event name: AEAPPINVW8
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Attached files:
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: 05282136-48a5-11e4-83df-e06995a3699c
Report status: 0
Hash container: dbd94bb9bcc526682a050bf66e2816ab
+++ WER9 +++:
Error container -751049027, type 5
Event name: AEAPPINVW8
Respond: No data
CAB descriptor/identifier: 0
Problem signature:
P1: 48
P2: 2
P3: 6.3.0.0
P4: 1049
P5: 35
P6:
P7:
P8:
P9:
P10:
Attached files:
These files can be found here:
Symbol/character analysis:
Repeated search for solution: 0
Report identifier: ca1ac5d7-48a4-11e4-83df-e06995a3699c
Report status: 0
Hash container: dbd94bb9bcc526682a050bf66e2816ab
All I can tell about this report, that all .exe are of games:
AI.exe - Alien Isolation
EndlessLegend.exe - Endless legend
rogame.exe - Red Orchestra 2
ss2013.exe - Surgeon Simulator 2013
nightmare.exe - Endless nighmares (or something like that)
Can attach files like "C:\ProgramData\Microsoft\Windows\WER\ReportQueue\NonCritical_2152759308_f7d740a5f1a5e2768b51f2db4859bdfc2ecc978f_00000000_07b51e7d" if necessary (there are "report.wer" files)
Since I tried to launch NS on other computer and had the same bugs - problem is not in Windows.
Everything except shots, movement, voice chat. They work fine.
Text, taunts, j1/j2, go to ready room, ping map are delayed. Armory and evolution don't seem to work at all.
P.S. Yesterday tried to connect internet directly (without router) - same bugs.
It gives some weird errors in your log. WHile I am unsure what it does exactly, it has somethint to do with fonts. Try to deinstall that program first.
I did notice most are games indeed.
But if multiple computers experience the same issue its indeed far less likely its windows, unless you run the same software on them all.
I'll record my own log to compare with these results, I have real 100 Mbit/s so packet loss should not be a problem. At least at the ISP's zone of responsibility.
1) Check your network cable and (in case of ADSL) the line parameters. Flood ping may also reveal the packet loss.
2) Try any other multiplayer game which has the ability to log the network events. You need a UDP-based protocol because TCP resends packets transparently (so most of RTS/TBS aren't suitable for the task). Probably a Source game would fit? Like CS:GO, Team Fortress or even the dreaded Dota 2. I'm not familiar with that engine so you should look for the info about the network logging. If you'll have the same packet loss there, well, bad luck. Call your ISP and try to explain them that what they do is wrong.
3) Install leenooks, for example Ubuntu. This would require installing the proprietary NVIDIA driver as well. This would sort out if any Windows-related issues like an incompatible AV software or other games are involved. Personally, I don't believe it will help but if you're out of options...
1) Not ADSL. You mean check it physically? It's fine then. Or I should check opened ports or something?
2) Other games seem to work fine.
As far as I understand CS: GO uses UDP ingame. Didn't manage to make a proper log, still it's obvious that no packages lost (loss and choke = 0).
Don't know which protocol uses UE3, no packages lost in UT3 and RO2.
As you said, since the problem appeared suddenly and on several PCs it must be ISP's fail. Will try contacting it.
I found it odd many of his earlier traces did not show the same loss which could indicate software specific, but does also not say it is.. It could very well be router related.
I decided to wait on diggin in the network as so many variables exist without any real logging.
* It could be a modem setting. For this he needs to look into his modem and report them all, including modem model number.
* Could be as silly as any network switch, port, hub, router, printer or card set to 10Mb and not 100Mb on its connection.
* Could be full duplex vs not.
* Could be outdated drivers.
* Could be outdated modem firmware.
* Could be a dying switch.
The list goes on. Although personally I would start in the modem with things like firewall and flood detection.
Sometimes cable modems also contain basic routing features.
Also if its in the code it is odd so few people experience the issue as a whole. I wont deny it can be the code though.. one should never exclude options beforehand.
Lets assume @rkfg is onto something because all those resends are indeed not supposed to be.
I checked a log again, its all reliable resends which indicated the udp (unreliable) is fine. So its something with the tcp sends.
Which makes it all the more odd.. usually UDP buggers out..hmm..
You don't normally resend udp packages since it usually contains data that is already too old to be used if resent. The protocol itself doesn't contain this feature and for the reason given earlier I'm not sure if ns2 does that.
I may be a IT person but my knowhow in networking and network protocols is more standard then advanced.
On the side note, realtime protocols like those in action games (like NS2) should only resend non-realtime data like menu opening or team joining. Anything that is going here and how (movement, firing) can be dropped and interpolated by server. Otherwise you'll get mixed game states from present and past which is harmful and useless at the very least. I don't believe something as basic as this is plaguing the NS2 network code.
As for the reliable resends, I suppose it means the proto tries to transparently recover from the packet loss so it means "our reliable send was not confirmed by the receiving side so we're resending the packets to keep the proto reliable". That's the whole point of RUDP, I can't think up a situation where the game code should resend the reliable data (thus already received and confirmed). Other than waste bandwidth and increase the latency which is kinda what's happening but it shouldn't happen. Maybe some CDT member with the engine code access will clear this up by looking at the code that prints this message. I'm currently out of ideas.
As for the whole cable thingy. Over here we have no RJ-45 plugs from isp.
Your ISP supplies either ADSL/SDSL, Coax or Fibre. On that connection comes a ISP shipped modem or modem/router.
Now that of course has Rj-45.
Hence the confusion.
"sending unreliable" doesn't mean anything important really.
Here is a quick snippet from my own log to a server i always play on without issue, during a moment where there was zero issues:
[ 64.584] 162.255.138.35 Client: Processing unreliable 166
[ 64.584] 162.255.138.35 Client: Started receiving a new packet of 216 bytes
[ 64.605] 162.255.138.35 Client: Sending unreliable 167
[ 64.616] 162.255.138.35 Client: Processing unreliable 167
[ 64.616] 162.255.138.35 Client: Started receiving a new packet of 213 bytes
[ 64.648] 162.255.138.35 Client: Sending unreliable 168
[ 64.681] 162.255.138.35 Client: Processing unreliable 168
[ 64.681] 162.255.138.35 Client: Started receiving a new packet of 216 bytes
[ 64.691] 162.255.138.35 Client: Sending unreliable 169
[ 64.734] 162.255.138.35 Client: Processing unreliable 169
[ 64.735] 162.255.138.35 Client: Started receiving a new packet of 215 bytes
[ 64.735] 162.255.138.35 Client: Sending unreliable 170
[ 64.778] 162.255.138.35 Client: Processing unreliable 170
[ 64.778] 162.255.138.35 Client: Started receiving a new packet of 214 bytes
[ 64.778] 162.255.138.35 Client: Sending unreliable 171
[ 64.820] 162.255.138.35 Client: Sending unreliable 172
[ 64.832] 162.255.138.35 Client: Processing unreliable 171
[ 64.832] 162.255.138.35 Client: Started receiving a new packet of 217 bytes
[ 64.864] 162.255.138.35 Client: Sending unreliable 173
If you already bypassed the router.. are you using a modem?? (asking because of what rkfg said)
If so, what model? And have you checked the error logs immediately after having these issues?
Seems really odd that your PC is able to connect to that IP address just fine but in game you are running into issues..
As rkfg already said, I just have a cable with RJ45, no other peripherals required just to connect to net. (of course on the attic there is provider's network switch)
Anyway, now everything is fine.
Don't know what happened. There was a shutdown nearby (several houses lost connection), perhaps repair works also had some effect on my connection.
Obviously, problem was in ISP.
p.s. rkfg : I know, that's why I said as much in my first sentence.