DevLog 250529 — Remote Access and Blender Victory

After two years of setbacks and having to rebuild my desktop computer from scratch, I finally opened Blender on my MacBook. It is slow and not very clear, but it runs. This log also documents the setup of RustDesk for secure remote access between devices without paid software or static IPs.

Today I installed RustDesk on Ubuntu and successfully connected from my MacBook. I was able to control my Linux machine and verify that my graphics are working. More importantly, after all this time and effort, I reached a major milestone. Blender opened. For the first time since starting this entire journey, I have a working environment where I can launch 3D tools, test workflows, and start building the future I envisioned.

Setup Overview

Installed RustDesk using the .deb package:

sudo apt install ./rustdesk-1.4.0-x86_64.deb

Checked interfaces and IP addresses:

ip a

Quick local IP check:

hostname -I

Used RustDesk to connect remotely from:

user@000.00.00.0

Lessons Learned

• RustDesk is a capable and free alternative to commercial screen sharing apps
• The .deb install method is the easiest route
• LAN connections do not require a relay server
• Docker bridges show up in ip a output and can be ignored

Quick Recap

1. Boot the Ubuntu machine
2. Run ip a or hostname -I to get your address
3. Install RustDesk with sudo apt install ./rustdesk.deb
4. Launch with rustdesk & or from the GUI
5. Connect from another device using IP or ID

Blender Status

I opened Blender on my MacBook. It is not fast and not entirely stable, but it works. The program loads, responds, and renders. I can now officially say this setup is 3D capable. That opens the door for real animation and scene development using my own machine.

Next Steps

• Set RustDesk to launch on boot if I want unattended access
• Explore private relay setup for secure remote access outside the LAN
• Test Eevee and reduce samples to improve Blender performance

Here's a link: Arynwood Terminal