CalcProgrammer1

joined 3 years ago
MODERATOR OF
[–] CalcProgrammer1@lemmy.ml 106 points 1 day ago (9 children)

Honestly, not even mad. Sucks for the victims, but we need hackers poking holes in kernel anticheats. Show the game companies that kernel anticheat is a waste of effort and maybe this horrific plague of gaming will die off.

[–] CalcProgrammer1@lemmy.ml 3 points 1 week ago

If Bungie is behind it I have zero interest without even knowing what it is. Destiny 2 was an OK game, but its god awful anticheat bans Linux users. That is a sure-fire way to make me pretend your game doesn't exist. Client side anticheat is a plague. Do it properly on the server side.

[–] CalcProgrammer1@lemmy.ml 86 points 1 week ago (10 children)

Until any competing store releases a Linux client, I can't really argue against Steam. They are a gatekeeper and almost a monopoly, but they're also the most benevolent and pro-consumer gatekeeper that we have in the PC gaming distribution space. As long as all the competition continue to be Windows-only and, in some cases, actively work against Linux users, I don't want Valve's digital fiefdom to fall.

[–] CalcProgrammer1@lemmy.ml 5 points 2 weeks ago* (last edited 2 weeks ago) (1 children)

I've been experimenting with both of these and recently wrote up a guide for installing FEX on postmarketOS (as I am testing it on my phone and tablet) but the steps should work for Pi as well.

https://wiki.postmarketos.org/wiki/Steam

I also just made a video tutorial/demo on YouTube. I ran Half Life 2 and Tomb Raider (2013). I'm not sure how capable the Pi 4 GPU is in comparison to the Adreno GPUs I tested.

https://youtube.com/watch?v=EuOX2L_yNqI

[–] CalcProgrammer1@lemmy.ml 4 points 2 weeks ago (3 children)

Box86/64 and FEX can both run Steam on ARM. Lighter games should be playable on RPi4 and 5.

[–] CalcProgrammer1@lemmy.ml 8 points 2 weeks ago

APIs can be complex too. Look at how much stuff the Win32 API provides from all the kernel calls, defined data structures/types, libraries, etc. I would venture a guess that if you documented the Win32 API including all the needed system libraries to make something like Wine, it would also be 850 pages long. The fact remains that a documented prototype for a software implementation is free to reimplement but a documented prototype for a hardware implementation requires a license. This makes no sense from a fairness perspective. I'm fine with ARM not giving away their fully developed IP cores which are actual implementations of the ARM instruction set, but locking third parties from making their own compatible designs without a license is horribly anticompetitive. I wish standards organizations still had power. Letting corporations own de-facto "standards" is awful for everyone.

[–] CalcProgrammer1@lemmy.ml 22 points 2 weeks ago (1 children)

In the mobile Linux scene, Qualcomm chips are some of the best supported ones. I don't love everything Qualcomm does, but the Snapdragon 845 makes for a great Linux phone and has open source drivers for most of the stack (little thanks to Qualcomm themselves).

[–] CalcProgrammer1@lemmy.ml 48 points 2 weeks ago

RISC V is just an open standard set of instructions and their encodings. It is not expected nor required for implementations of RISC V to be open sourced, but if they do make a RISC V chip they don't have to pay anyone to have that privilege and the chip will be compatible with other RISC V chips because it is an open and standardized instruction set. That's the point. Qualcomm pays ARM to make their own chip designs that implement the ARM instruction set, they aren't paying for off the shelf ARM designs like most ARM chip companies do.

[–] CalcProgrammer1@lemmy.ml 241 points 2 weeks ago* (last edited 2 weeks ago) (18 children)

Hopefully Qualcomm takes the hint and takes this opportunity to develop a high performance RISC V core. Don't just give the extortionists more money, break free and use an open standard. Instruction sets shouldn't even require licensing to begin with if APIs aren't copyrightable. Why is it OK to make your own implentation of any software API (see Oracle vs. Google on the Java API, Wine implementing the Windows API, etc) but not OK to do the same thing with an instruction set (which is just a hardware API). Why is writing an ARM or x86 emulator fine but not making your own chip? Why are FPGA emulator systems legal if instruction sets are protected? It makes no sense.

The other acceptable outcome here is a Qualcomm vs. ARM lawsuit that sets a precedence that instruction sets are not protected. If they want to copyright their own cores and sell the core design fine, but Qualcomm is making their own in house designs here.

 

I did a video tutorial and demonstration showing the Steam, FEX Emulator, and Distrobox setup I documented on the postmarketOS wiki here:

https://wiki.postmarketos.org/wiki/Steam

I go through the setup process for the Ubuntu container, FEX emulator, Steam, and then install and test two games - Half Life 2: Lost Coast and Tomb Raider (2013) to demonstrate gaming performance on an ARM device (in this case a Xiaomi Pad 5 Pro with Qualcomm Snapdragon 870 chip).

[–] CalcProgrammer1@lemmy.ml 6 points 3 weeks ago

Except the one platform that actually matters, Linux. My girlfriend got me into this game and it's the only game I have to keep a Windows installation around for. It doesn't run on the Steam Deck, so it's the only multiplayer game I play where I would even contemplate having to play it on Switch. I hate Epic Games.

 

I managed to get Steam installed on my OnePlus 6T and Xiaomi Pad 5 Pro, both running postmarketOS, using Distrobox to create an Ubuntu 24.04 container and then installing FEX-Emu inside of it. I wrote up a guide on the postmarketOS wiki on how to do it, some issues I ran into, some tips on how to get around those issues, and a list of games I've tested. Feel free to expand upon this list if you try it out. Older games such as Half Life 2 are quite playable, especially if your device supports keyboard and mouse input. I have not yet tested using a controller.

[–] CalcProgrammer1@lemmy.ml 5 points 1 month ago

The name Unity just needs to be avoided. I get the well intentioned meaning behind the word, but it has been the name of three major controversial/disastrous products in semi-recent history - Ubuntu Unity Desktop, Assassin's Creed: Unity, and the Unity Engine.

[–] CalcProgrammer1@lemmy.ml 4 points 1 month ago

Leave it on, but turn off the monitor. I have it set up as a GitLab runner for some projects and also want to be able to SSH/SFTP in to access files, run updates, etc.

 

I have added support for system-wide plugin installations in Linux for the upcoming 1.0 release. The plugin files can be installed system-wide to the /usr/lib/openrgb/plugins path, which allows them to be provided by distribution packages rather than manually downloading them.

I have created AUR packages for the following plugins and they have been picked up by the Chaotic AUR repository if you want binary builds.

  • openrgb-plugin-e131-receiver-git
  • openrgb-plugin-effects-git
  • openrgb-plugin-hardware-sync-git
  • openrgb-plugin-visual-map-git

I plan to update the rest of the plugins on https://gitlab.com/OpenRGBDevelopers and get them into the AUR as well before 1.0 releases. Until that happens, you will need to use the openrgb-git AUR package to utilize these new plugin packages. The current 0.9 release in the main repository does not support system-wide plugin installation.

 

I made a 3D printed, Arduino-powered desk fan based around a 120mm Corsair QL120 ARGB fan after seeing Noctua's desk fan. I wanted something similar but with RGB. It is based around CorsairLightingProtocol so it syncs with OpenRGB but also has a knob to adjust fan speed and LED brightness directly. I made a video showing it off but if you prefer to read about it, I have project documentation and files (code, assembly instructions, and 3D models) on GitLab here:

https://gitlab.com/CalcProgrammer1/OpenRGBDeskFan

The 3D models are also on Thingiverse:

https://www.thingiverse.com/thing:6655697

1
submitted 1 year ago* (last edited 1 year ago) by CalcProgrammer1@lemmy.ml to c/openrgb@lemmy.ml
 

#OpenRGB 0.9 has been released! Check it out at https://openrgb.org! The full release notes are available on GitLab here:

https://gitlab.com/CalcProgrammer1/OpenRGB/-/releases/release_0.9

 

This is not news, just wanted to pin the most recent release here on Lemmy. It released on November 28, 2022. The next release, 0.9, is still being worked on but as always you can try the latest pipeline build at https://openrgb.org/#pl for the latest supported devices and features.

 

I made this video discussing my thoughts on the OpenPleb initiative by Wendell of Level1Techs and Steve of Gamers Nexus. As the developer of OpenRGB, the OpenPleb initiative, which aims to work with hardware vendors to open up documentation for proprietary protocols used for consumer PC hardware, could be a massive boon for OpenRGB development as at the moment almost everything we add is reverse engineered. Having access to protocol documentation would improve the quality of our code and the efficiency in which we can release it.

For reference, I'd recommend watching Steve's original video here:

https://www.youtube.com/watch?v=bKOtvOqa_vM&t=0s

I posted this on /r/hardware because Steve's video got a lot of traction there, but I wasn't necessarily happy about posting on Reddit, so here it is for Lemmy.

view more: next ›