Dahrkael @dahrkael@fosstodon.org

compiled and ran re3 on my laptop and pinephone both running @manjarolinux
on the laptop it runs so much better than the Proton version! but sadly on the pinephone there seems to be some opengl and wayland issues and nothing gets rendered (it doesnt crash though).

got my first Wireshark dissector working fine and fast. now I need to figure out how the conversation API works for the second one to work properly

trying to write a Wireshark dissector. very confusing C API for newcomers with a so mewhat lacking documentation.
but i'm slowly progressing regardless

next on my ToDo list: a Wireshark dissector. noone told my I was gonna do so many and varied things to get the game running again!

before Microsofts purchase, Github "explore" section was great to find new interesting stuff, now it sucks so bad it feels like YouTube recommendations.

I find the LilyGO TTGO T-Watch a very interesting piece of hardware, specially as a standalone thing compared to the PineTime.
I wish I had time to mess with this kind of projects

immediate mode UIs are great but have their own set of issues

back from holidays, back to code

I went crazy for a couple hours trying to understand why my renderer wasnt working. it ended up being the data coming from the file with the wrong endianess, goddamit

@futureisfoss depends on your interests

added some autogenerated cpp files with gigantic dictionaries of game data. now instead of 20 seconds it takes 4 minutes to compile.

unsurprisingly Windows scheduler became even worst and trying to sleep a thread for 33ms is impossible in my Ryzen. 46+ms always, if asked for 16ms its 75% of the time 30ms, 25% 16ms.
I read I have to set the affinity of each thread for this to work but whats the point of the scheduler then?

so my visibility and subscription system works fine, can see other players when in range and start receiving movement updates.
another important milestone achieved

I came up with a subscriber system to keep track of which players require network updates when some entity changes its state. not the best thing in the world but for now it seems to work ok without wasting extra memory.