u/rowenarrow

Looks nice.

It looks great! And the skills learned along the way I am sure inspire taking on other challenges

Congratulations and I am excited for you. Studying for the length you did is a story in itself and I hope both you and your friend are proud of what you did in the time you did it. I first got my Net+ in 2009-2010 and let me tell you with some purposeful study and growth you can maintain it and never take the exam again. So welcome to the team!!!

o7

I just need it to last one more class to finish my degree, lol.

Alt biomes gonna be cray from this

A source aggregator. I primarily use the audio feature to generate podcast-like explanations of my weekly readings for school. Basically went through my masters program barely reading anything and had it read to me in a manner I am more likely to retain or receive the important parts. Additionally I use it to query contracts and large files.

The panel and wings sync being dummy proof would be fantastic.

Thank you my friend.

What is that hex code though?

High demand, global supply chain is inflated and restricted in part due to some orange guy stirring things up.

If you ordered multiple items then if all aren't available to ship then the order is held until all items are available. Not sure if this is your circumstance but good to know.

I am happy for you but am disappointed because I ordered min in Oct 2025 and no update.

## Issue Summary: Thrustmaster SOL-R2 Base Button Mapping Behavior (Buttons 31-34 / 41-44)

### Initial Problem

When attempting to map the Thrustmaster SOL-R2 HOSAS setup to separate vJoy devices using Joystick Gremlin, base buttons `31–34` and `41–44` appear locked to specific physical hardware sides:

* Buttons `31–34` only register data through the physical Left Stick.

* Buttons `41–44` only register data through the physical Right Stick.

When trying to map these inputs as standard digital buttons in Joystick Gremlin to cross-pollinate them across different virtual containers, the expected button activations do not trigger.

### Technical Findings

1. **Asymmetric Hardware Mapping:** The SOL-R2 firmware splits the central/base button controls down the middle. They do not duplicate across devices; they are uniquely assigned to individual stick hardware IDs at the Windows driver level.

2. **HAT Switch Representation (The Root Cause):** Despite being labeled as distinct buttons (`31-34` and `41-44`) in some Thrustmaster documentation, the Windows driver actually reports these cluster buttons as **POV/HAT switch directions** rather than standard digital button presses. Because they are sending axis-style HAT packets, traditional "Button Remap" actions in Joystick Gremlin fail to capture the inputs.

3. **Verification and Visibility:** To confirm that the physical buttons are actively sending signals, you must have the **raw physical hardware device selected in the Joystick Gremlin Input Viewer**. When pressing the physical buttons while viewing the hardware tab, you will see the HAT directions light up instead of digital buttons.

---

### Fix Action / Solution

To successfully route these buttons across virtual devices in Joystick Gremlin, they must be mapped using the **Hat** container logic instead of the standard button layout.

#### Step-by-Step Configuration Guide

1. **Verify Raw Input:** Open Joystick Gremlin's **Input Viewer**, ensure your raw physical hardware device is selected, and press the buttons to confirm the HAT directions are actively lighting up.

2. **Locate the Input in Profile:** Go back to the main profile setup and select the physical device tab (e.g., Right Stick for 41-44).

3. **Navigate to Hats:** Scroll past the standard button list down to the **Hat** section.

4. **Expand Directions:** Expand the corresponding Hat container (e.g., `Hat 2`) to expose the discrete **Up, Down, Left, and Right** nodes.

5. **Apply Remap Actions:**

   * Select a direction (e.g., *Up*, which physically corresponds to button 41).

   * Set the Action to **Remap**.

   * Choose your target virtual device (e.g., `vJoy 1` or `vJoy 2`).

   * Map it to a standard digital **Button** ID of your choice.

6. **Repeat:** Do this for all remaining directions on both sticks.

7. **Activate Profile:** Ensure the profile is actively running (Green gamepad icon) to verify the virtual cross-mapping in the Input Viewer.

Agreed, I use Notebook LM as a educational informing and summarizing tool. It is often the starting point and useful for brainstorming. Then I take the work done there and refine using ChatGPT or Gemini

Good to hear and looks like a fun upgrade to make

I do it in canva or using nano 🍌

It is tough to say I would say plan to go native and using JSG. I am dealing with a button mapping issue JSG and vJoy with the SOL-R2 and it just leaves me feeling defeated that I can't fix it.

It is nice

Okay so here is my unsolicited input. I hope this is a guest house or you will always be the only person there because between you and that 3D printer sound is going to bounce all over the place and others down below will annoy you. I used to have my office in a space similar to and the moment I had a woman staying over or with me it was quickly revealed I would have to do something different.

Thank you for sharing the website says it is in maint for days now.

So clean

I am about at this place.

How is the stability for you? I find that the wood shelf’s are the way to go but it is so hard to get ones