OculusKiller VS revive

It's the shitty oculus software, I use oculus killer for this exact reason, just make sure you follow the instructions and of course, use at your own risk

Here https://github.com/LibreQuest/OculusKiller/releases/tag/v1.2.0

UMM BepInEx Oculus Killer to make my wire linked quest 2 launch in steam vr with some other perks The VR mod itself (I use 0.9 in the recording but a newer version was released) The mod that makes announcers possible Serial Designation J from Murder Drones as my announcer

If you are using oculus install this: https://github.com/LibreQuest/OculusKiller It Removes the oculus dash which saves you a decent bit of performance (doesn't affect anything other than not being able to play your Oculus Store games) I use it myself and its saved around 200-300mb of ram (On Rift CV1).

For 3 there is the OculousKiller thing. It bypasses the Dashboard launcher entirely. https://github.com/LibreQuest/OculusKiller

Meta Killer

As for free stuff you can try, there's stuff you can mess with using Oculus debug tool (there's plenty of posts in this sub about it) and OculusKiller is worth a shot (it disables the Oculus dash and boots you straight to steamvr)

Initially the experience was very shitty. The Oculus's Dash that launches store and games freezes hard! When launching SteamVR tho it is very much OK until you press Oculus button. So the solution was to bypass Dash entirely! :D I've used this tool to do it: https://github.com/LibreQuest/OculusKiller. This uses SteamVR as main environment right when you use the Oculus link or Air instead of original oculus Dash. (Installation is easy and reversible). The Oculus App on the WIN 4 itself is still accessible and can be used to reduce refresh rate to 72HZ and set resolution scale to something like 0.7.

I completely disabled the oculus dash because it sucked so much using this modified version of the oculusdash.exe.

The v1.3.4 of revive, the fast, configurable, extensible, flexible, and beautiful linter for Go, is available.

I would suggest checking out something like revive to improve the code. For instance you use an errors.New(fmt.Sprintf(... when you can just use fmt.Errorf(... to simplify it. I am not saying obey everything but there are some good lints included that can even catch bugs (for instance misusing errors.Is or errors.As or general equality).

Linting and static analysis: https://revive.run/

For people using this linter (like me) https://github.com/mgechev/revive

Been using https://github.com/mgechev/revive in all my projects.

The day after, I talked about the Hacktoberfest to Salvador (architect colleague and my technical/career unofficial mentor). He is known for contributing to revive a Golang linter. We decided that I could contribute by solving these 3 issues (2 new rules and add a docker image to the release). Since this moment, I have been coding every available hour I had. It felt so reviving to spend time coding on new projects, rewarding to solve issues for people actually using the tool. Here are all my contributions.

While golint may be deprecated it has been brought back as revive. You can also enable in golangci-lint.

This release adds support for revive, a ~6x faster, stricter, configurable, extensible, and beautiful drop-in replacement for golint.