#Async Loggers

2154 messages · Page 3 of 3 (latest)

past cairn
past cairn
past cairn
#

how has the experimental version done after a week of being out?

lone stone
#

Pretty flawlessly

#

After the fix for loadingscreen there hasn't been any problems

tawny fog
#
System.NullReferenceException: Object reference not set to an instance of an object
  at (wrapper managed-to-native) System.Object.wrapper_native_0000FFF272321E6F()
  at AsyncLoggers.Sqlite.SQLiteLoader.LoadSqliteLibrary () [0x0005c] in ./Preloader/src/Sqlite/SQLiteLoader.cs:63 ``` new version logs this error
grizzled jacinth
tawny fog
#

I never installed async loggers experimental 💀

#

only lobby control and Additional network

grizzled jacinth
#

Maybe try reinstalling it

#

Try uninstalling the mod, clearing unused cache and reinstall it

tawny fog
#

I tried but its still the same

grizzled jacinth
#

See if you have this

tawny fog
#

yes

#

i have

grizzled jacinth
#

Okay try deleting it then relaunching

#

it should redl it

tawny fog
#

its still the same

grizzled jacinth
#

Yeah I see it happening for me too

#

@past cairn Async Loggers' update is busted, Experimental was fine

grizzled jacinth
# tawny fog its still the same

Swapping to the Experimental build and deleting that file and launching should resolve it, something is borked with the Stable update

autumn pebble
#

The most recent version of Async Loggers consistently crashes the game if you exit it after having entered a lobby initially

lone stone
pure egret
#

and delete that file

autumn pebble
lone stone
#

But bertogim's mod stopped soundapi crashes on exit from happening

#

So probably will stop this too

#

Since it just terminates the process when you click it

past cairn
#

uh? all i did was download the dll from experimental, rename it and upload back 🤔

grizzled jacinth
grizzled jacinth
grizzled jacinth
# pure egret ill prob just downgrade for the time being

Just use the Experimental build like I said after deleting that file rather than rolling back Stable Async Loggers, I’ve used it for a couple months without issues. It’s strange it’s breaking tbh from a dll rename but I’m sure he’ll look into it

lone stone
#

didnt have an issue with crashing, though i use ForceQuit so i guess its now dual purpose to avoid asyncloggers and soundapi crashes?

grizzled jacinth
#

If you had Experimental dl the SQLite stuff the update works without prblems

#

It only explodes in fresh profiles or profiles that didn’t have it

#

Idk why

lone stone
#

oh ok

grizzled jacinth
#

Theoretically people could just dl Experimental let those files dl and swap back and it will all just work til Matty figures it out

#

But safer to just use Experimental because the profile will likely be shared snd if someone doesn’t have the SQLite stuff in their game directory it will just explode

lone stone
#

ok hold on

#

when does this crash happen

#

when exiting to main menu or exiting game?

#

if its the latter it does not affect me or my players at all

grizzled jacinth
#

Exiting game and it’s because with the Stable update AsyncLoggers appears to be dling corrupted files somehow when it dls the SQLite files

#

That or it just can’t read them

lone stone
#

alright awesome

#

another W for bertogim

#

though i also have sqlite logging off so idk if thatll help

grizzled jacinth
#

Good to see

#

https://thunderstore.io/c/lethal-company/p/mattymatty/AsyncLoggers_Experimental/ For people experiencing problems, swap to this version of Async Loggers and allow it to regen the folder it downloads here. If you're on Stable and got errors and crashes you'll need to go to your installed game directory and delete this folder and let Experimental redownload it, or simply create a seperate profile and launch the game with just Async Loggers Experimental as that should trigger it to redownload the sqlite files

grizzled jacinth
#

@past cairn Tested the new version on my tiny REPO pack since I reprod the issues with the update yesterday on that game and can confirm it's fixed, what did you change?

autumn pebble
#

Whus it's called?

past cairn
autumn pebble
#

ForceQuit, kill him (Lethal Company)

autumn pebble
past cairn
#

well yeah. when you force quit you skip all the remaining logs from being written to file/db/console

autumn pebble
#

Scratches head

#

Should I just install Experimental in the meantime then

#

Because logs r important

past cairn
#

does the current stable still have that issue? tilted_head

autumn pebble
#

Pluh

past cairn
#

v2.2.1 was busted for some reason while being a litteral reupload of Experimental

#

last evening i uploaded a recompiled version as v2.2.2 that should work fine

autumn pebble
#

Yeah nah just tested it /w Async disabled

#

Game didn't explode this time

past cairn
#

you can also toggle the shutdown behaviour in the config file:
Scheduler.Shutdown style

autumn pebble
#

Wat would that do?

past cairn
#

tell AsyncLoggers to not wait for logs on shutdown 😅

autumn pebble
#

...Would that prevent the crashing...?

grizzled jacinth
#

2.2.2 is fine

#

If you’re crashing still from using 2.2.1 have it redl the SQLite files

proper tundra
grizzled jacinth
autumn pebble
#

I can't find it in our modpack folder

grizzled jacinth
autumn pebble
#

Ah

autumn pebble
#

It still crashes, even after having gone through all the steps you listed

honest glacier
#

looks like you are having the same issue as me

#

this is from a profile with just asyncloggers and a couple butterystancakes mods.

#

game crashes upon pressing quit

#

almost certainly the same thing happening to samantha i think

lone stone
past cairn
#

😅

grizzled jacinth
#

I even tested installing the v2.2.2 version on REPO and it all worked fine

#

So weird

tawny fog
#

REPO?

grizzled jacinth
#

Well at least v2.2.3 resolves it

grizzled jacinth
# tawny fog REPO?

Yeah my REPO pack was where I reprod the v2.2.1 issues, because on my Lethal profile everything was fine since I had Experimental create the zip folder previously

raw shuttle
#

More like a-stink loggers

tawny fog
#

ah

#

I thought it was a repo in github

grizzled jacinth
#

Nah REPO as in the game

grizzled jacinth
#

Funny issues be funny

steady yacht
#

Yo does this mod work for V80?

tawny fog
#

yes

grizzled jacinth
#

@past cairn Just wanna let you know, you'll probably want to update this to disable DbLogging by default. Reason being is the new enemies in v81 spam so much when they exist that when Dblogging is on and logging the game lags very badly and drops frames pretty significantly, this was even after I excluded a lot of that logging with logwrapping. The second I turned off the DbLogging my game started to run much better overall again on v81

past cairn
#

that's very weird. the DBLogger like all the others in AsyncLoggers runs on a separate thread with a queue to decouple it from the main game thread. it should not affect performance and if it did the other loggers should too 🤔

grizzled jacinth
flat rune
#

isn't it because of stacktrace capture?

past cairn
#

the default for stackTraces is None tho

grizzled jacinth
#

They really should be relocated from Info logs to debug logs with just how much they spam

#

it is terrible

past cairn
#

that's not how the queue works. if logs come too fast they are simply discarded in favor of never affecting the main thread

#

also all vanilla logs ( or more precisely Unity logs ) don't have a log level distiction, so they are all treated as Message i belive 🤔

grizzled jacinth
#

Ah hmmmm

past cairn
#

as Diffoz said: do you have the stacktrace setting to a non-default value?

grizzled jacinth
#

No I had it default

past cairn
grizzled jacinth
#

So my only other best guess remains my first one in that maybe it's not liking Proton and Linux too well

past cairn
#

ehh proton might not like native windows calls. that's entirely possible

grizzled jacinth
#

Prolly, I do know Linux does have native sqlite stuff but I dunno if Async Loggers could make use of that lol

past cairn
#

if that's the case it might affect other low-level mods too

#

it'd be very hard to detect if we're running on proton and somehow escape the proton sandbox to run native linux commands 🤔

grizzled jacinth
#

Yeah definitely

past cairn
#

i might instead add an option to use an external "proper" db, but the users of my DbLogger are already so few and the ones on linux are even less 😅

#

unless you were actively using the db. turning it off should not matter

grizzled jacinth
#

Yeah I haven't actively needed to use it in a while, modding has gotten much more stable since the days I had to peruse it a ton thankfully lmao

#

I remember when I used to have to check it every other session

#

😅

past cairn
#

@flat rune were you the one that had to deal with the disk space issues on Proton?

flat rune
#

yep

past cairn
#

do you see the same issues lunxara has then? or maybe you don't use AsyncLoggers 😅

flat rune
#

I'm pretty sure that I had some performance drop when db logger is enabled, so on our modpack I always disabled it

#

but I currently don't use linux on my main pc, so I can't test it rn

past cairn
flat rune
#

on linux, on windows i think it's fine, but I just never tested

grizzled jacinth
#

Yeah some way of using the native version that comes preinstalled would prolly help lol

#

But idk if it's feasible

#

The lag likely comes from the windows stuff since the mod will use the Windows version of SQLite

regal saffron
#

Can I suppress this type of log? There are many of them in loglines, I don't know exactly what they mean, hence my question

past cairn
#

you can.
if you want you can suppress all of them, but i doubt they come from the vanilla game

#

and AsyncLoggers can only suppress the vanilla ones.

it's probably worth to ask the dev of whatever mod is throwning them to fix it

regal saffron
#

How do I find out which mod it is? I don't understand code, I only know that the class name is "GameNetcodeStuff.PlayerControllerB"

past cairn
#

oh if it's from PlayerControllerB then it can indeed be suppressed