开源软件名称（OpenSource Name）：

开源软件地址(OpenSource Url)：

开源编程语言(OpenSource Language)：

开源软件介绍(OpenSource Introduction)：

1. Disclaimer

This is an educational project. Although the project started as a learning exercise on the Irrlicht Engine, it has kind of turned into an OpenGL one instead due to limitations and issues with Irrlicht (most likely caused by my limited experience with graphics programming). Turns out working directly with OpenGL is not as hard as I thought. For more information on the project's license, check LICENSE.

2. What is this project all about?

This projects aims to reproduce the background functionality of Wallpaper Engine on Linux systems. Simple as that.

3. What is Wallpaper Engine?

Wallpaper Engine is a software designed by Kristjan Skutta that provides live wallpaper functionality to Windows Systems, allowing It's users to animate their own backgrounds and sharing their own creations. You can find more about it on their Steam page.

4. Compilation requirements

linux-wallpaperengine

• OpenGL 2.1 support
• CMake
• LZ4
• ZLIB
• SDL
• FFmpeg
• X11 (with libxxf86vm)
• Xrandr
• GLFW3
• GLM
• GLEW
• GLUT
• FreeImage

5. How to use

5.1. Pre-requirements

In order to properly use this software you'll need to own an actual copy of the Windows version of Wallpaper Engine (which you can buy on the Steam Page), as it contains some basic assets on which most of the backgrounds are based on.

The only way to get those assets is to install the Windows version through Steam. Luckily you don't really need a Windows installation for that. Using the Linux Steam client is enough to download the files we need. Note you may need to check "Enable Steam Play for all other titles" in the Steam Play section of Steam's settings if you haven't already. Also note that the software cannot actually be launched through Steam Play (Proton), but the setting is required for Steam to download the software.

5.2. Extracting the assets

The automatic way doesn't require of anything extra, as long as Wallpaper Engine is installed in Steam the software should automatically detect where the assets are.

5.2.1. Extracting the assets manually

In the off-case where the software doesn't automatically detect the correct path, the assets can be extracted manually. Once Wallpaper Engine is downloaded, open the installation folder (Right-Click the application in Steam -> Manage -> Browse local files). Here you'll see the main folders of Wallpaper Engine. The folder we're interested in is the one named "assets".

The assets folder itself must be copied to the same folder where the binary lives.

5.3. Getting the sources

You can download a zipped version of the repository here: https://github.com/Almamu/linux-wallpaperengine/archive/refs/heads/main.zip

You can also clone the repository using git like this:

git clone [email protected]:Almamu/linux-wallpaperengine.git

Or using the HTTPS method if you haven't set up SSH:

https://github.com/Almamu/linux-wallpaperengine.git

5.4. Compilation steps

The project is built on CMake as build engine. First we need to create the directory where the build will be stored and get into it:

mkdir build
cd build

Once the folder is created and we're in it, CMake has to generate the actual Makefiles. This can be done this way:

cmake ..

Take a closer look at the CMake output, if you miss any library CMake will report the missing libraries so you can install them either trough your package manager or manually in your system.

Finally we can compile the project to generate the actual executable

make

REMEMBER: The assets folder has to be in the same folder as the executable

5.5. Running a background

5.5.1. Running a background from Steam

Just like with the assets, the software can automatically detect where the subscribed backgrounds are stored. To get started, search in the workshop for whatever background you want to use and click the "+Subscribe" button. This should download the background in the steam directory.

To actually use the background you'll need to know the workshop's ID. This can be obtained right-clicking anywhere in the background's page -> "Copy Page URL". You can paste this URL anywhere, it will look something like this:

https://steamcommunity.com/sharedfiles/filedetails/?id=1845706469&searchtext=portal+3

Where 1845706469 is the wallpaper's ID. You can use this ID to run wallengine:

./wallengine 1845706469

5.5.2. Running a background in a different folder

For the situations where the software cannot detect where the backgrounds are stored, you can specify a full path to it, like so:

./wallengine /home/almamu/Development/backgrounds/1845706469/

5.5.2. Running in a window (Default)

By default the app will load the backgrounds in a window so you can preview them:

./wallengine /home/almamu/Development/backgrounds/1845706469/

Where /home/almamu/Development/backgrounds/1845706469/ is the background's path.

5.5.3. Running as a screen's background

Only screens configured with the XRandr extension are supported. To specify the screen names (as reported from xrandr tool) just use the --screen-root switch. You can specify multiple screens at the same time, for example:

./wallengine --screen-root HDMI-1 --screen-root DVI-D-1 /home/almamu/Development/backgrounds/1845706469/

IMPORTANT: Right now this doesn't work if there is anything drawing to the background (like a compositor, nautilus, etc)

5.5.4. Limiting FPS

To reduce the performance hit to your system you can reduce (or increase) the FPS limit with the switch --fps, especially useful for laptops:

./wallengine --fps 30

6. Example background

This was the first background to even be compatible with the software. And It's not 100% compatible yet. Both textures and shaders are properly loaded, but there are still particles missing.

1845706469

In similar fashion to the example background, this one represents the progress of the program. It leverages FBOs (targets), and multiple-effects over objects.

7. Special thanks

• RePKG for the information on texture flags
• RenderDoc for the so helpful OpenGL debugging tool that simplified finding issues on the new OpenGL code. Seriously this tool ROCKS