#Any version above skytils 1.9.8 makes me lag

1 messages · Page 1 of 1 (latest)

soft bloom
#

i reported this before already a few versions ago but to no success
when i try to use any version newer than 1.9.8 i get stutters exactly like when your ram is full (but it is not full)
this happens in dungeons for me (i think nowhere else actually)
please comment if anyone has the same issue / i wanna know if this is actually JUST me

rancid dragon
#

yes

#

it's a feature

soft bloom
#

so you are having those specific lags as well?

rancid dragon
#

I don't personally, but a lot of other people do

soft bloom
#

i just deleted my old skytils config and that seemed to resolve the issue ? (not entirely sure yet) but had no lag for a few days now

#

though, fucking annoying setting everything up again

lone wolf
vagrant nexusBOT
#

Going to Crystal Hollows or joining Dungeons with a team, the game lags horribly, horribly bad.

Solo Dungeons and everywhere else is fine.

The lag in Dungeons with a team gets fixed instantly when WebSocket connection is eventually terminated from server-side.

Workaround is to disable WebSocket entirely by adding -Dskytils.websocketURL=localhost to JVM arguments at which point the mod will try to connect localhost through WS and will get IOException: Connection refused, the second error of "java.lang.IllegalStateException: Tried to send packet but session was null" will keep spamming but theres 0 lag.

The following error messages appear after the termination:

gg.skytils.ktx-coroutines.channels.ClosedReceiveChannelException: Channel was closed
at gg.skytils.ktx-coroutines.channels.BufferedChannel.getReceiveException(BufferedChannel.kt:1729) ~[BufferedChannel.class:?]

(Gets printed 1 time)

java.lang.IllegalStateException: Tried to send packet but session was null
at gg.skytils.skytilsws.client.WSClient.sendPacket(WSClient.kt:95) ~[WSClient.class:?]
at gg.skytils.skytilsmod.listeners.DungeonListener$onPacket$5.invokeSuspend(DungeonListener.kt:215) ~[DungeonListener$onPacket$5.class:?]

(Keeps getting printed, currently the count is at 700 for me, although the exception causes 0 lag when connection is closed, meanwhile while connection open and no errors in log it lags horribly, so its not the errors.)

lone wolf
lone wolf
rancid dragon
#

I don't why it lags so much for you, the performance for me is fine even with all the packets being sent and received

soft bloom
#

yea nah they did return eventually, it just doesn't lag sometimes and sometimes it does its so weird

#

but the start option did fix it (for now at least)

#

ty !

lone wolf
#

The "return to normal" "sometimes doesn't lag" "gets fixed sometimes by itself" is just the WS connection being terminated, so of course it won't lag after the connection is dropped because it never retries to connect again