Winkelpagina
Avorion
Alles Discussies Screenshots Beeldmateriaal Uitzendingen Video's Workshop Nieuws Gidsen Recensies
Avorion >  Workshop > Workshop van LM13 > [2.5.2+] Xavorion: Combat AI > Discussies
[2.5.2+] Xavorion: Combat AI
Beschrijving Discussies1 Opmerkingen105 Wijzigingen
Koinzell || Souza 4 jul 2023 om 16:39
New bug ?
Hello there LM13, starting a new one here cause

after the last update it keeps sendind this error in the log from the dedicated server

2023-07-05 01-25-47| Starting thread [Stacktrace Sender]...
2023-07-05 01-25-47| Started thread [Stacktrace Sender] with id 140610157659904
2023-07-05 01-25-49| create save work for sector (-131:186), 0x7fe21344c440, entities: 164
2023-07-05 01-25-49| Player Arrax moved to sector (-140:182)from (-131:186) server time taken for change: 0ms
2023-07-05 01-25-49| saving sector (-131:186)
2023-07-05 01-25-49| sector (-131:186) saved to "galaxy/Avorion/sectors/-131_186"
2023-07-05 01-25-51| create save work for sector (-140:182), 0x7fe2a0001da0, entities: 598
2023-07-05 01-25-51| saving sector (-140:182)
2023-07-05 01-25-51| sector (-140:182) saved to "galaxy/Avorion/sectors/-140_182"
2023-07-05 01-25-59| [CheckAttackedEntity] New target sent via RPC
2023-07-05 01-25-59| T: 140610711316224
2023-07-05 01-25-59| Object: N2cp13ServerScriptsE
2023-07-05 01-25-59| Execution Context (inner to outer):
2023-07-05 01-25-59| #0: XAIComponent.updateServer /home/container/galaxy/Avorion/workshop/content/445220/2918443067/data/scripts/ShipXAI/XAIComponent.lua
2023-07-05 01-25-59|
2023-07-05 01-25-59| Error calling Player:invokeFunction: Calling script located in (-134:178), player in (-140:182). Cannot interact with scripts of a player in another sector. Use invokeFactionFunction() or runFactionCode() for that functionality.
2023-07-05 01-25-59|
2023-07-05 01-25-59| stack traceback:
2023-07-05 01-25-59| [C]:-1: in function invokeFunction
2023-07-05 01-25-59| /home/container/galaxy/Avorion/workshop/content/445220/2992808971/data/scripts/ShipXAI/Plugins/CombatAI.lua:149: in function NotifyCombatHUD
2023-07-05 01-25-59| /home/container/galaxy/Avorion/workshop/content/445220/2992808971/data/scripts/ShipXAI/Plugins/CombatAI.lua:116: in function CheckAttackedEntity
2023-07-05 01-25-59| /home/container/galaxy/Avorion/workshop/content/445220/2992808971/data/scripts/ShipXAI/Plugins/CombatAI.lua:286: in function _Update
2023-07-05 01-25-59| /home/container/galaxy/Avorion/workshop/content/445220/2918443067/data/scripts/ShipXAI/XAIComponent.lua:507: in function ?
2023-07-05 01-25-59|
2023-07-05 01-25-59| Starting thread [Stacktrace Sender]...
2023-07-05 01-25-59| Started thread [Stacktrace Sender] with id 140610157659904
2023-07-05 01-25-59| Script "/home/container/galaxy/Avorion/workshop/content/445220/2918443067/data/scripts/ShipXAI/XAIComponent.lua" or one of its requirements is not in its original state, skipping sending of stack trace.
2023-07-05 01-26-15| [CheckAttackedEntity] New target sent via RPC
2023-07-05 01-26-15| T: 140610702923520
2023-07-05 01-26-15| Object: N2cp13ServerScriptsE
2023-07-05 01-26-15| Execution Context (inner to outer):
2023-07-05 01-26-15| #0: XAIComponent.updateServer /home/container/galaxy/Avorion/workshop/content/445220/2918443067/data/scripts/ShipXAI/XAIComponent.lua
2023-07-05 01-26-15|
2023-07-05 01-26-15| Error calling Player:invokeFunction: Calling script located in (-134:178), player in (-140:182). Cannot interact with scripts of a player in another sector. Use invokeFactionFunction() or runFactionCode() for that functionality.
2023-07-05 01-26-15|
2023-07-05 01-26-15| stack traceback:
2023-07-05 01-26-15| [C]:-1: in function invokeFunction
2023-07-05 01-26-15| /home/container/galaxy/Avorion/workshop/content/445220/2992808971/data/scripts/ShipXAI/Plugins/CombatAI.lua:149: in function NotifyCombatHUD
2023-07-05 01-26-15| /home/container/galaxy/Avorion/workshop/content/445220/2992808971/data/scripts/ShipXAI/Plugins/CombatAI.lua:116: in function CheckAttackedEntity
2023-07-05 01-26-15| /home/container/galaxy/Avorion/workshop/content/445220/2992808971/data/scripts/ShipXAI/Plugins/CombatAI.lua:286: in function _Update
2023-07-05 01-26-15| /home/container/galaxy/Avorion/workshop/content/445220/2918443067/data/scripts/ShipXAI/XAIComponent.lua:507: in function ?
< >
1-6 van 6 reacties weergegeven
LM13  [ontwikkelaar] 7 jul 2023 om 0:37 
Thanks, I see you have a line in logs that is not supposed to be there anymore - meaning I need to bump version numbers to force update on dedicated servers.
#1
Koinzell || Souza 10 jul 2023 om 16:38 
Sup LM13, howdy ?? any ETA on that update ? not here to pressure you or anything, just that it seens those lines in the log seems to be affecting server performance.
#2
LM13  [ontwikkelaar] 10 jul 2023 om 16:42 
Origineel geplaatst door Koinzell || Souza:
Sup LM13, howdy ?? any ETA on that update ? not here to pressure you or anything, just that it seens those lines in the log seems to be affecting server performance.

Sorry for not replying. Are you still getting that error? All modules should have received an update and version number bump to force that on servers.
#3
Koinzell || Souza 11 jul 2023 om 10:59 
Worry not LM13, and yea i'm still getting the message, there is something that causes it to start showing up, server lags while it is looping that message, and then after a while it stops.
i noticed that it happens more when lots of ships are fighting, i was doing rift missions these days and it happened several times. i'll link one of the smaller logs, from 12hours ago. it shows those messages.

https://drive.google.com/file/d/1GgnRLqbQ79yUB2groiHG53QH08jgh3Rb/view?usp=sharing
#4
LM13  [ontwikkelaar] 11 jul 2023 om 11:11 
Thank you for that log.
I am 100% sure now that for some reason, your server is using old version of mods.

A line in logs still exists:

"[CheckAttackedEntity] New target sent via RPC"

And that one was commented out some time ago along with a fix for that error. It should not appear in logs at all, meaning that a fix for that error is not present on your server.

I have no idea how mod updates work on dedicated servers, so I really can't guide you through this. The dumb thing is that log claims that it has checked workshop items at startup.

Maybe a server-side mods folder needs to be manually removed?
#5
Koinzell || Souza 12 jul 2023 om 6:27 
That sounds like a plausible solution, i'll try doing that
i'll update you if anything changes!
#6
< >
1-6 van 6 reacties weergegeven
Per pagina: 1530 50