#Validating - Expected behavior or issue ?

20 messages · Page 1 of 1 (latest)

brittle hazel
#

Also just seeing a few random errors.

These aren't always problematic, so I wanted to confirm with modAuthor before spending more time tracking down syntax issues or other problems.

2025-01-09T16:48:58 245.249 ERR XML loader: Loading and parsing 'blocks.xml' failed
2025-01-09T16:48:58 245.250 EXC Unknown mesh attribute 'blueprint' on block frameShapes:cube
2025-01-09T16:48:58 245.911 ERR XML loader: Loading and parsing 'progression.xml' failed
2025-01-09T16:48:58 245.913 EXC Requested value 'CombatStressMultiplier' was not found.
2025-01-09T16:48:59 246.598 ERR XML loader: Loading and parsing 'buffs.xml' failed
2025-01-09T16:48:59 246.603 EXC Requested value 'WeightCapacity' was not found.
2025-01-09T16:48:59 246.974 INF Loaded (local): misc in 0.12
2025-01-09T16:49:16 263.730 ERR XML loader: Loading and parsing 'items.xml' failed
2025-01-09T16:49:16 263.731 EXC Unknown block name 'wallTorchLightPlayer' in use_action!
2025-01-09T16:49:17 264.306 ERR XML loader: Loading and parsing 'item_modifiers.xml' failed
2025-01-09T16:49:17 264.308 EXC Requested value 'VitalityChangeOT' was not found.
2025-01-09T16:49:18 265.207 ERR XML loader: Loading and parsing 'entityclasses.xml' failed
2025-01-09T16:49:18 265.208 EXC Requested value 'AmbienceMultiplier' was not found.

fallow shell
brittle hazel
#

Playing single instance SP / Peer-to-Peer isn't feasible so I'm spinning this up on the current version of Dedi.

fallow shell
#

The effects of those XML errors may not be immediately prominent but the fact that there are several references unable to be reconciled is going to be bad news somewhere.

I do not know that there is any specific limitation with running AL on a server, FWIW. Can't say I've used/hosted one myself, though, so my helpfulness in that regard will be almost zero.

#

I think the most common cause of WalkerSim failing to execute is a missing libgdiplus package, but that is only relevant on a Linux server.

brittle hazel
#

I think I may have found the issue. I'll report back but it looks like mainline release on SteamDB for Windows Dedi may still be stuck on 1.1 (b14)

#

which is likely the cause.

#

I'll dig into it and report back shortly.

#

could just be my old tired eyes overlooked it.

fallow shell
#

Ah, yeah, if you're running 1.1 via whatever combination that'll almost certainly not work

vague ermine
#

everything appears to be in order in this thread coolChamp

brittle hazel
#

@vague ermine It's called 'pay closer attention to the numbers after the decimal for me 😛 . . pulling latest now, but I'm fairly confident this was a suppuku situation. But thats why another pair of eyes is always welcome. Thx 🙂

brittle hazel
#

Ok well - The majority of the issue is that the mainline release from steamDB is still 1.1 even tho the depot says v1.2 is 'gold' , it's still pushing 1.1 unless you select -beta v1.2 branch.

So, that's resolved with a little tweak to the bat .

Now the issue seems to be a silent disconnect on join, for an unknown reason. I've tried both enabling as well as disabling litenet and steamnetworking.

Server instance is on same network segment as the testClient, so it's odd.

I have a rebirth instance as well as a vanilla instance on that same box and testing both from the same client work fine. It's only the instance with Afterlife that throws this deserialize error.

//--2025-01-09T18:12:14 265.081 ERR NCSimple_Deserializer (cl=EOS_0002233e54d84918954010de541784c2, ch=0) Message: Parsed data size (257) does not match expected size (278) in NetPackagePlayerDisconnect
2025-01-09T18:12:14 265.091 EXC Parsed data size (257) does not match expected size (278) in NetPackagePlayerDisconnect//

I am going to call it quits on this for the night, but just wanted to add some more context in case anyone else comes here with an issue. At least they will know they aren't alone.

I'm going to spin up wireshark on a linux VM in that same segment just to see if anything looks peculiar on framing, MSS< etc. but its probably just something fucky with the map, the host, or some other rando issue. Doubt its mod code, but like i said, wanted to put this here just in case.

brittle hazel
#

--Update : Same error when a peer to peer connection is attempted.

Buddy tried to join me in an SP peer-2-peer game, and it kicked him with the same error message.

vague ermine
#

sorry I dont know what could be doing this ._.

#

at the very least I can say we havent done anything to differentiate the NetPackagePlayerDisconnect size

gaunt pollen
#

Do you have a full stacktrace?

#

Or maybe even client+server logs to compare?