|
Notes |
|
|
|
Some of them should be just info message colored in green - that is game is acting correctly.
Some of them, however, indicate to serious issues with engine deign, just like
battleGetAllObstacles called when no battle!
Still, issues that do not cause game to behave incorrectly should be painted in another color than red (Magenta?) not to confuse user. |
|
|
|
(0004141)
|
|
Ivan
|
|
2013-11-24 18:38
|
|
>> Cannot find player 255info!
Can you describe when this one happens?
>> Ended handling connection
>> Our socket has been closed.
Should be green'ed |
|
|
|
|
I have a similar error.
vcmi 0.97.
backtrace:
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
Cannot get object with id 1117. Object was removed.
const PlayerState* CGameInfoCallback::getPlayer(PlayerColor, bool) const: Cannot find player 255info!
Error! Hero 1117 (Ãàëòðàí) has no army!
Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 0x7ffff4b7d700 (LWP 2237)]
0x00000039fd166c8c in CPathfinder::evaluateAccessibility(TerrainTile const*) const () from /usr/lib64/vcmi/libvcmi.so
(gdb) bt
#0 0x00000039fd166c8c in CPathfinder::evaluateAccessibility(TerrainTile const*) const () from /usr/lib64/vcmi/libvcmi.so
#1 0x00000039fd166efb in CPathfinder::initializeGraph() () from /usr/lib64/vcmi/libvcmi.so
0000002 0x00000039fd1685b5 in CPathfinder::calculatePaths() () from /usr/lib64/vcmi/libvcmi.so
0000003 0x00000039fd168cc7 in CGameState::calculatePaths(CGHeroInstance const*, CPathsInfo&) () from /usr/lib64/vcmi/libvcmi.so
0000004 0x000000000053b18f in CClient::getPathsInfo(CGHeroInstance const*) ()
0000005 0x00007fffe4d1df75 in VCAI::isAccessibleForHero(int3 const&, HeroPtr, bool) const () from /usr/lib64/vcmi/AI/libVCAI.so
0000006 0x00007fffe4d3b4c3 in VCAI::wander(HeroPtr) () from /usr/lib64/vcmi/AI/libVCAI.so
0000007 0x00007fffe4d3bf7f in VCAI::performTypicalActions() () from /usr/lib64/vcmi/AI/libVCAI.so
0000008 0x00007fffe4d44aa3 in VCAI::makeTurnInternal() () from /usr/lib64/vcmi/AI/libVCAI.so
0000009 0x00007fffe4d452c2 in VCAI::makeTurn() () from /usr/lib64/vcmi/AI/libVCAI.so
0000010 0x00000039fdc0d98a in thread_proxy () from /lib64/libboost_thread.so.1.55.0
0000011 0x000000336fa0752a in start_thread () from /lib64/libpthread.so.0
0000012 0x000000336f70079d in clone () from /lib64/libc.so.6
|
|
|
|
|
|
The issue with removed object is a serious gameplay problem. AI is not allowed to access objects it cannot see, but also should never try to do so - this already caused some crash bugs. |
|
|
|
|
>> const PlayerState *CGameInfoCallback::getPlayer(PlayerColor, bool) const: Cannot find player 255info!
I think I already handled this one, but could miss some cases.
|
|
|
|
|
This is a very interesting ticket! I've been doing autoskip for a long time and have seen hundreds of error messages.
I'm wondering which are the worst in terms of rating or something. And could provide saves with these errors |
|
|
|
(0008552)
|
|
krs
|
|
2023-04-12 16:40
|
|
Latest development not even warning messages.
Can be closed. Reopen on individual cases if needed. This is 2013! |
|
|
|
|
|
what about message from server? Is it empty? doesnt spam? I just dont know. |
|
|
|
|
|
@krs green message still exist ^ ) |
|
Cannot get object with id . Object was removed.rar (1,072,052) 2022-03-19 20:53
121.png (1,393,706) 2023-05-06 06:53