My wife is looking for a portable device primarily for modeling in Blender and optionally for drawing in Krita. So we looking for something with a GNU/Linux support from manufacturer.

We considered https://www.tuxedocomputers.com/en/TUXEDO-InfinityFlex-14-Gen1, it looks nice, but maybe you have other suggestions? Do you have experience with convertibles, how convenient is to draw on them?

We also considered https://earth.starlabs.systems/pages/starlite for drawing and a separate device for Blender, but having two devices might not be convenient...

cross-posted from: https://lemmy.ml/post/22613952

> I just wanted a pocketable device, so I decided to pick Mini over 5. > > Originally, I wanted to order the white color but ended up choosing the black one because it makes the bezels and pillar boxes blend into the case. It also looks like a small SteamDeck 😅 > > When I'm not programming, I'm playing GTA III on it and earning RetroAchievements 😃 > > !With SteamDeck > > !GTA III

cross-posted from: https://lemmy.ml/post/22613952

> I just wanted a pocketable device, so I decided to pick Mini over 5. > > Originally, I wanted to order the white color but ended up choosing the black one because it makes the bezels and pillar boxes blend into the case. It also looks like a small SteamDeck 😅 > > When I'm not programming, I'm playing GTA III on it and earning RetroAchievements 😃 > > !With SteamDeck > > !GTA III

I just wanted a pocketable device, so I decided to pick Mini over 5.

Originally, I wanted to order the white color but ended up choosing the black one because it makes the bezels and pillar boxes blend into the case. It also looks like a small SteamDeck 😅

When I'm not programming, I'm playing GTA III on it and earning RetroAchievements 😃

!With SteamDeck

!GTA III

I've been working on bevy_replicon for the last two weeks. That's the networking library we use for the game.

Originally, I planned to make a small change to include the number of updates in the message (needed for prediction) but ended up completely reworking the serialization 😅 Typical me. This change improves message packaging. For example, in our statistics test, we use only 16 bytes for a test message instead of 33!

Okay, it's finally time to go back to the original change I wanted to make 😄

It's a crate for dynamic and contextual input mappings for Bevy, inspired by Unreal Engine Enhanced Input.

While porting my game, I made many improvements. Actually using the crate gave me a better perspective 😅

Here's a quick showcase from my game. Smooth movement now automatically done by built-in LerpDelta modifier.

Also notice how pressing Esc cancels object spawning first due to the context priority.

Pressed keys displayed via screenkey app.

📜Full changelog 📦bevy_enhanced_input

It's a crate for dynamic and contextual input mappings for Bevy, inspired by Unreal Engine Enhanced Input.

While porting my game, I made many improvements. Actually using the crate gave me a better perspective 😅

Here's a quick showcase from my game. Smooth movement now automatically done by built-in LerpDelta modifier.

Also notice how pressing Esc cancels object spawning first due to the context priority.

Pressed keys displayed via screenkey app.

I also refined controls and added proper gamepad support. But touchscreen is still required due to missing UI navigation in Bevy. And I need to add cursor control with sticks 😅

Now I planning to implement some important features for bevy_replicon.

📜Full changelog 📦bevy_enhanced_input

Migrating my game to bevy_enhanced_input and making some tweaks to the crate. I'll do another release once I finish.

Had to rewrite some game logic to adapt it to the observer pattern. Working with young engines like Bevy means constant rewrites 😭

But I love the power of ECS, everything is so decoupled. Combined with Rust’s strict type system, it makes the rewriting process a lot smoother. I think the engine has great potential!

It's an app for translating and speaking text using Mozhi.

We've added automatic selection for the fastest instance and fixed some bugs.

My next plan is to port it to Qt6. I try to get to it during my winter vacation. I'm just currently focused on a FOSS life simulation game. If anyone wants to help with the migration, PRs are welcome!

Works both on desktops and mobile Linux. Here is a screenshot of the app running on my PinePhone Pro:

!screenshot

It's a crate for dynamic and contextual input mappings for Bevy, inspired by Unreal Engine Enhanced Input.

I really like the UE approach and decided to bring it to Bevy.

Despite being the first release, it's packed with features:

• Map inputs from various sources (keyboard, gamepad, etc.) to gameplay actions like Jump, Move, or Attack.
• Assign actions to different contexts like OnFoot or InCar, which are regular components.
• Activate or deactivate contexts by simply adding or removing components.
• Control how actions accumulate input from sources and consume it.
• Layer multiple contexts on a single entity, controlled by priority.
• Apply modifiers to inputs, such as dead zones, inversion, scaling, etc., or create custom modifiers by implementing a trait.
• Assign conditions for how and when an action is triggered, like "hold", "tap", "chord", etc. You can also create custom conditions, such as "on the ground".
• React on actions with observers.

I've implemented everything from UE and even added some extras. The crate also has ~90% test coverage.

📦bevy_enhanced_replicon

It's a crate for dynamic and contextual input mappings for Bevy, inspired by Unreal Engine Enhanced Input.

I really like the UE approach and decided to bring it to Bevy.

Despite being the first release, it's packed with features:

• Map inputs from various sources (keyboard, gamepad, etc.) to gameplay actions like Jump, Move, or Attack.
• Assign actions to different contexts like OnFoot or InCar, which are regular components.
• Activate or deactivate contexts by simply adding or removing components.
• Control how actions accumulate input from sources and consume it.
• Layer multiple contexts on a single entity, controlled by priority.
• Apply modifiers to inputs, such as dead zones, inversion, scaling, etc., or create custom modifiers by implementing a trait.
• Assign conditions for how and when an action is triggered, like "hold", "tap", "chord", etc. You can also create custom conditions, such as "on the ground".
• React on actions with observers.

I've implemented everything from UE and even added some extras. The crate also has ~90% test coverage.

📦bevy_enhanced_replicon

It's a crate for dynamic and contextual input mappings for Bevy, inspired by Unreal Engine Enhanced Input.

I really like the UE approach and decided to bring it to Bevy.

Despite being the first release, it's packed with features:

• Map inputs from various sources (keyboard, gamepad, etc.) to gameplay actions like Jump, Move, or Attack.
• Assign actions to different contexts like OnFoot or InCar, which are regular components.
• Activate or deactivate contexts by simply adding or removing components.
• Control how actions accumulate input from sources and consume it.
• Layer multiple contexts on a single entity, controlled by priority.
• Apply modifiers to inputs, such as dead zones, inversion, scaling, etc., or create custom modifiers by implementing a trait.
• Assign conditions for how and when an action is triggered, like "hold", "tap", "chord", etc. You can also create custom conditions, such as "on the ground".
• React on actions with observers.

I've implemented everything from UE and even added some extras. The crate also has ~90% test coverage.

Finally released! Next up, I'll be migrating the game to use it. After it I will need to implement some requested features for bevy_replicon.

📦bevy_enhanced_input

Over the past two weeks, I have been working on an input management plugin.

LWIM crate is good, but I wanted to try a different approach inspired by the Unreal Engine Enhanced Input.

If you have never used it, I explained the approach in the README, where you can also find a link to UE's documentation.

I finished the implementation and added examples, but I still need to write tests and improve the documentation. Planning to release it soon and continue focusing on the game :)

https://github.com/projectharmonia/bevy_enhanced_input

I'm working on a life simulation game with the working title Project Harmonia and would like to share my progress.

I migrated navigation from oxidized_navigation to vleue_navigator.

It uses the novel Polyanya algorithm instead of the classical A*.

I faced a few issues during the migration, but the author helped me resolve them all. He even dumped the navmesh of the house I built in the game and created a test named after the project 😅

I also implemented skipping points that the agent has projected past to prevent jitter when multiple points are close to each other.

It uses the novel Polyanya algorithm instead of the classical A*.

I faced a few issues during the migration, but the author helped me resolve them all. He even dumped the navmesh of the house I built in the game and created a test named after the project 😅

I also implemented skipping points that the agent has projected past to prevent jitter when multiple points are close to each other.

This week, I was fixing bugs (there were a lot!) and refactoring.

I finally migrated the game's physics from XPBD to Avian. The migration was seamless since we're only using it for picking, collision checking, and navigation for now 😅

It's worth noting that I also switched from Avian's global Position component to Bevy's relative Transform, as the global Position breaks when there are multiple cities.

The progress is incredible!

I working on a life simulation game with a working title Project Harmonia.

I’ve finally added the ability to edit and remove previously spawned walls, along with an undo/redo system.

Implementing the undo/redo was a bit challenging. If a command spawns or despawns an entity, it needs to be tracked to update the history with the correct ID. Additionally, since the game is networked, I had to introduce the concept of pending history commands. These commands are only added to the history after server confirmation.

I’ve finally added the ability to edit and remove previously spawned walls, along with an undo/redo system.

Implementing the undo/redo was a bit challenging. If a command spawns or despawns an entity, it needs to be tracked to update the history with the correct ID. Additionally, since the game is networked, I had to introduce the concept of pending history commands. These commands are only added to the history after server confirmation.