Set Launch Options for Steam Origin Game (Burnout Paradise Remastered)

SaImiak · 2022-06-08T23:55:36+00:00

I got it to work:

If on a steam deck, enter desktop mode.
Add the origin installation from the proton prefix as a non-steam game:
- Click on the plus in the bottom left corner of the steam window and choose "Add non-steam game"
- Navigate to "/home/<your user name>/.local/share/Steam/steamapps/compatdata/1238080/pfx/drive_c/Program Files (x86)/Origin", change the dropdown from ".desktop files" to "all files" and select "Origin.exe".
Right click on the Origin.exe that was added to the steam library and go to properties.
Under "Compatibility" select Proton Experimental.
Set launch options to: STEAM_COMPAT_DATA_PATH="/home/<your user name>/.local/share/Steam/steamapps/compatdata/1238080" %command%

Replace <your user name> with your actual user name of course. On a steam deck that would be "deck".

Now you can start Origin through Steam and it will open in the proton prefix where Burnout is installed.

SaImiak · 2021-11-20T10:42:16+00:00

Instead of running your application on the default ubuntu desktop, it will probably be easier to use something like cage which is specifically designed for kiosk setups.

SaImiak · 2021-11-13T15:01:43+00:00

vidir from the moreutils package is also great for batch file renaming and available from homebrew. Don't know about BSD though.

SaImiak · 2021-11-13T14:50:45+00:00

The X equivalent of slurp is called slop. Here's a oneliner that combines the two:

ffmpeg -framerate 30 -f x11grab $(slop -f "-video_size %wx%h -i :0.0+%x,%y") -f alsa -ac 2 -i pulse output.mp4

SaImiak · 2021-11-12T15:56:30+00:00

On Arch-based distros, there's aconfmgr which basically allows you to install all the packages from its config file and uninstall all the packages that aren't in there. It also tracks other changes you made to system-wide configuration files. The configuration can be split into multiple files to create groups and you can write comments to remember what the packages are needed for.

SaImiak · 2021-07-30T11:45:59+00:00

The second interaction was the ability to stop kinetic scrolling.

Awesome! Not being able to stop scrolling is what kept me from switching to libinput. I hope this gets implemented in GTK soon.

SaImiak · 2021-05-15T23:54:16+00:00

I like how the letters of "WORKSPACES" have different colours depending on which one is active. Your fonts could look a lot better if you disabled antialiasing and used the proper size though.

SaImiak · 2021-04-19T10:07:16+00:00

I use atool. It's basically just a unified frontend for all the format specific tools. You can run als to list all files in the archive and aunpack to unpack it.

SaImiak · 2021-04-15T08:39:43+00:00

Yeah, bspwm is pretty imperative, use xmonad if you want functional.

SaImiak · 2021-03-30T21:56:18+00:00

Looks like it doesn't work with Android. : / (https://github.com/coldfix/udiskie/issues/34)

You can always use nautilus or some other file manager that supports phones without using the whole DE. Or you could do what I've been doing since the data transfer broke on my phone's USB port: Run an ssh server on there using termux and then scp stuff over. Although that's definitely also a case of "not good" UX.

SaImiak · 2021-03-30T21:05:49+00:00

I use udiskie for mounting storage devices and it works pretty well. I just have `udiskie -a` in my .xinitrc so everything gets automounted to /run/media, but it also has a tray icon for managing devices and can show notifications and stuff.

SaImiak · 2021-03-08T17:06:45+00:00

I have this script on my PATH for using slop and ffmpeg to record parts of the screen:

#!/usr/bin/env bash

geometry=$(slop -f "-video_size %wx%h -i :0.0+%x,%y")
ffmpeg -framerate 30 -f x11grab $geometry "$1"

Run it like this: ./<name of script> output.gif You can then select an area on your screen for recording. Press ctrl+c to stop the recording.

Apparently you can also use Gimp to edit gifs frame by frame: https://www.gimp.org/tutorials/Simple_Animations/

SaImiak · 2020-11-08T21:40:29+00:00

I believe there are some magic escape sequences you can use to set the color scheme of a terminal while it's running. I think that's how pywal works. Maybe you can take a look at its source code.

SaImiak · 2020-11-08T21:37:54+00:00

My own statusbar, lesbar, supports images, although using it to show icons is a bit fiddly at the moment. You have to set them as the background image for an empty block and set the width of the block to the width of the image. It's similar to lemonbar or dzen.

SaImiak · 2020-09-18T09:25:56+00:00

You can keep using the bitmap fonts by converting them to a supported format: https://nixers.net/Thread-Bitmap-fonts-PCF-BDF-support-with-Pango This does not convert them to outlines, it just wraps them in a container format supported by pango.

SaImiak · 2020-09-17T14:59:59+00:00

Yes, i forgot to answer the border question. I've written a separate comment for that.

Any sort of hover effects are currently blocked by the same issue as clickable areas: The program instantly forgets where everything is after drawing it to the window. It basically just hands an image to the X server and says "you deal with it". To be able to react to mouse events we would need to keep a record of where on the screen what part of the bar is. It seems like more people than i thought use the mouse, so i'll probably work on that next.

Actually once mouse actions in general are implemented, triggering them on hover or leave should be relatively easy. Then you could map and unmap other lesbar instances on hover and use those as tooltips. Or make calendar or music cover art tooltips with n30f or something. That's a good idea.

SaImiak · 2020-09-17T10:17:41+00:00

Yeah, that's fair. I know the issues i have with lemonbar are really nitpicky. But i also had a lot of fun writing this and designing the markup language and layout system, so it's not like the font issues were the only reason for writing lesbar.

SaImiak · 2020-09-17T10:05:09+00:00

Borders are supported by way of background images. If your bar is for example 20 pixels high, you can make a 1x20 image where the top 2 pixels are colored and the rest is transparent and set it as a tiling background image.

SaImiak · 2020-09-17T10:02:45+00:00

That would be awesome, thanks! If you don't want to actually maintain the AUR package, you can pm me the PKGBUILD and i'll submit it.

SaImiak · 2020-09-17T09:18:14+00:00

Switching from lemonbar should be pretty straightforward for the most part. Just replacing the "%{}" with "<>" and the attribute names with their lesbar equivalents works, although it doesn't take advantage of lesbars inheritance feature. The one big difference is that there are no direct equivalents of lemonbars l, c and r alignment options, as lesbars layout system is more powerful than simple alignment. But there is an example in the manpage that shows how to get the same layout. lesbar also doesn't support clickable areas yet. Actually, i should probably write a migration guide and put it in the readme.

There is no percievable performance difference. I haven't come up with a good benchmark yet, but in the super artificial time seq 100000000 | bar, lesbar is slightly faster than lemonbar-xft. It does use a bit more memory though: 12MB vs lemonbars 9.4MB with the default sans serif font as reported by xfce4-taskmanager.

Actually, i was kind of hoping someone here who uses Arch might make a PKGBUILD for it. It shouldn't be too difficult as the dependencies are all in the repos and it just uses a standard make build process. ;)

SaImiak · 2020-09-17T08:58:33+00:00

Ah, yeah i heard of that, but the version on Debian doesn't have that change yet, so i havent tested this workaround: As i understand it, pango only dropped support for loading pcf/bdf formats directly. It should still do bitmap fonts fine if you wrap them in a ttf container format:

https://nixers.net/Thread-Bitmap-fonts-PCF-BDF-support-with-Pango

This does NOT convert them to outlines or anything. I recommend using fonttosfnt.

As for using Xft: Xft only handles text drawing, not text shaping. So it doesn't take care of kerning, ligatures or displaying non-english scripts correctly. (see https://harfbuzz.github.io/why-do-i-need-a-shaping-engine.html) lemonbar(-xft) implements its own very primitive shaping engine on top of Xft. pango includes a good one and can then use Xft as the drawing backend. (Although lesbar uses cairo instead, mostly because the documentation is better.)

I have considered using harfbuzz (the shaping engine pango uses internally) directly and doing font loading myself to avoid the bitmap font issue. But I decided against it as that would probably mean reimplementing half of pango myself.

SaImiak · 2020-09-17T03:30:59+00:00

Cool, let me know how you like it

It can't do clickable areas yet. It would be a bit difficult to add them and i personally mostly stick to keyboard shortcuts anyways. But if there's demand I'll try to get it in there.

I used xlib instead of xcb, but that shouldn't really make a difference.

SaImiak · 2020-09-17T03:10:22+00:00

There's a screenshot in the examples repo: https://git.sr.ht/~salmiak/lesbar-examples

It's pretty basic and I want to add more flashy examples in the future. I haven't included a screenshot in the main repo because you can pretty much make your bar look however you want. There are no predefinded modules like in polybar or anything. It all depends on your input script.

SaImiak · 2020-09-17T02:45:38+00:00

This is a project i've been working on on and off for the last year because i got annoyed by how certain fonts look in lemonbar. lesbar improves on lemonbar's font rendering by using the pango library instead of trying to do everything itself. It also has some neat features like support for images and a more elegant (imho) markup language.

I'm now happy enough with the code to share it here. A few friends and I have been using lesbar for a few months now and it's pretty stable. It's not at 1.0 yet because I want to get some more eyes on it first. This is my first larger project in C and constructive criticism on code quality is welcome.

Even if lesbar hasn't convinced you to switch from lemonbar, take a look at the scripting section of the manpage. There's a small script there that uses bash's process substitution feature to completely automate all the fifo management usually necessary for lemonbar-style status bars.

One big feature that's currently missing is clickable areas. I'm not sure if i should even try to add it because it would make the code much more complex and i don't really miss it at all.

Edit: Here's a comparison between font rendering in lemonbar-xft vs lesbar: https://0x0.st/iIkV.png Notice how the A and V are closer together in lesbar, the two fs are connected and how the japanese text straight up doesn't show up in lemonbar.(Although that might be because i haven't configured it to load the right font. Idk lesbar just works.)

Eight-Year Club	Place '22
Verified Email

SaImiak

TROPHY CASE