They were in-house but the local dev team were not working with them. Work force in that country was cheaper so i just got fired shortly after :)

Me maintaining an old codebase and implementing features for months before boss shows up one day and says the 60 remote workers have been working on an identical project which will be the one we actually use. Bruh wtf

Same at my new place, i tend to take a shorter lunch and leave earlier, i usually get into office at 8am or slightly before

This is indeed the appropriate reaction to being banned on counter strike. Joke aside you could just lock the entire functionality of adding an account to your family if someone got caught cheating though.

I mean, someone should get banned from cheating. I can see why this happen though, since the account playing does not own the game the account which has the game linked gets banned instead. If the account cheating has the game they are instead playing on their copy and that gets banned instead (i assume).

However the ban should be linked to the account and not the copy of the game. I do not understand why this isnt the case. Maybe because someone could just make a new account and link that to play on instead, therefor never having to buy more than one copy of the game while cheating.

This is very valid but in our case we dont really store any important data on the computer. We make digital timetable signs for bus stops and train stations, the computers we build and put inside are just a base image we flash onto the disk and set hostname and IP on. Then they all connect and set themselves up via our servers and pull any displayed data from our actual main servers.

In this case its sad that it didnt actually restart, that means our client has to drive out and deassemble the entire sign. But it seems to be a failing disk so it had to be replaced either way.

We did try that, it just have us Permission Denied

I would use the man pages but my working laptop uses Windows and since the system died i dont have any way to check them until I get home.

Thank you a lot for the answer though, that does explain a lot!

Pascal or camel case for code, snake case for files and screaming snake case for globals

Just started a new job last week. Ive been in the industry for 3 years so not completely junior but getting in to a new codebase is always rough. Especially when only 1 huge library file is documented, every component is cluttered af and most variables and parameter names are 1 character long.

Doesnt help that functions are 100 lines either when each the parameter names makes the logic incomprehensible.

Will update the original post but I solved it. Apparently there’s specific gamepad settings inside of Wootility under Settings > Gamepad. There you have to select what type of controller the software will emulate. I just took the recommended (Xbox Controller) and now it works as expected.

The keyboard itself is fine if I use regular mappings, however in the wootility software they provide (yes they have an official linux version) you can map controller inputs to your keys. So for example I can map (emulate) controller joystick left input to my A key to emulate the analog signal. These does not seem to register in-game. Other key inputs work fine.

Not related but I’ve had some dual booting issues aswell. Turns out that the drives mounted in Linux didn’t properly unmount on shutdown so when trying to access them on Windows they wouldn’t be accessible.

Just some info for anyone that might be having issues

This goes hard

What KDE/Kwin version do you use? Would be interesting to compare.

Edited the original post but might aswell comment it. I switched to GNOME (Wayland) and the FPS issue seems to be gone there. I ran the game with only the command line arguments “gamemoderun %command%” in steam and it seems to work properly. Very odd issue.

Launching it in GNOME (Wayland) seems to fix the issue. Very uncertain what this issue was but it seems to be related to KDE.

(Also I did not let the shaders compile, so not a shader issue)

Got gamescope working but the issue still persists. I’m gonna try launching in different DE aswell as letting shaders fully compile.

Good info, I will try this tomorrow and report back.

I had not seen this, but V-sync was off all the time :(