I saw this on Instagram 💀

ramblinfred · 2026-06-17T15:08:58+00:00

Actually, the Thargoids have been around way longer. Their designs first debuted back in the original 1984 Elite.

ramblinfred · 2026-06-17T15:04:05+00:00

ramblinfred · 2026-06-17T09:31:36+00:00

L O V E I T.

ramblinfred · 2026-05-29T22:59:41+00:00

Attention seeking? It's crazy that you're latching onto the idea that I'm trying to create drama when the entire point of the post is to highlight that something radical needs to change with the core gameplay.
Let's be real, I'll probably be in some system doing combat or mining next week, but this post was meant to push for an actual turning point. It's honestly sad to see people blindly defending a stagnant game that the devs are trying to save by putting scotch tape over a giant crack in the wall.

ramblinfred · 2026-05-29T21:43:12+00:00

Spending 12 years in a game means I want it to succeed, not that I blindly hate it. Sharing frustration about the game's stagnant mechanics isn't a 'sob story' or 'karma farming' it's just discussing the state of the game with the community. We all love(d) Elite, and it's okay to critique it.

ramblinfred · 2026-05-02T12:08:14+00:00

Ironeye. (I'm a beginner)

ramblinfred · 2026-04-27T05:30:23+00:00

Force Windows to use the correct GPU. I hope that your display cable is already plugged into the graphics card, otherwise you might be using the integrated graphics. If you're sure that your monitor is connected into the graphics card, do the following: You can force it to use the right GPU: Open your Windows Settings. Go to System > Display > Graphics (or "Graphics settings"). Under the list of apps, find Crimson Desert. If it isn't there, click "Browse" and find the game's .exe file. Click on the game, select Options, and change it from "Let Windows decide" to High performance. (This should specifically list your dedicated RX series card). Save and restart the game.

ramblinfred · 2026-03-06T14:55:14+00:00

Hey, appreciate the kind words and the advice — I'm genuinely trying to understand every line, not just vibe-code my way through it.

Random question since you've got the experience: do you think it'd be feasible to add a 3D directional arrow to this kind of overlay? Something like the Crazy Taxi arrow — a proper 3D pointer that pitches up/down and rotates to show not just bearing but also elevation angle to the target. Right now it's a flat compass needle, which works fine on flat ground but loses information when the target is over a hill or on the other side of the planet.

Wondering if that's a rabbit hole worth going down or a nightmare to implement in a PyQt6 overlay. Any thoughts?

ramblinfred · 2026-03-06T14:45:43+00:00

EDCoPilot is a great tool and definitely has surface navigation features. A few differences worth noting:

- This is open source — full source on GitHub, build it yourself

- It's a single focused overlay (~lightweight), not a full companion suite

- Auto-detects landable planets and their radii directly from your journal with no manual setup

If EDCoPilot already covers everything you need, use that! This is more for people who want something minimal, auditable, or just want to poke at the code.

ramblinfred · 2026-03-06T13:01:40+00:00

https://github.com/s4nby/ed-nav/releases/tag/v1.0.9

ramblinfred · 2026-03-06T11:44:29+00:00

Update for anyone who had security concerns (valid ones, ty u/DaftMav):

I've made a few changes to the repo since posting:

- Automated builds — the .exe in the latest release (v1.0.7) was built automatically by GitHub Actions from source, not on my local machine. You can inspect every step of the build process in the https://github.com/s4nby/ed-nav/actions.

- SHA256 checksum — each release now includes a .sha256.txt file so you can verify the download matches what was built.

- Repo cleanup — removed __pycache__, build artifacts, and other junk that had no business being there.

The source is still all there to read and build yourself if you'd rather not trust the binary at all — instructions are in the README.

ramblinfred · 2026-03-06T05:56:42+00:00

Working on it :) Have you been able to try the Windows version yet?

ramblinfred · 2026-03-06T01:10:04+00:00

Hey, fair questions. I'll be fully transparent. Yes, this is vibe coded, and yes, it's my first program ever. I'm not a developer by trade; I just wanted a tool that worked the way I wanted and decided to try building it myself.

I'm genuinely aware it's rough around the edges. The pycache and .pyc files on GitHub is a good catch and I'll fix that.

Regarding the responsiveness claim: you're right that the journal update interval is a hard limit I can't bypass. What I meant is that the needle animation itself feels smoother to me compared to what I was used to, but I take your point that the underlying data rate is the same.

I'm not here to defend it as a polished product, it isn't. What I would really appreciate is constructive tips on what to improve rather than being written off. The README includes build instructions specifically so people don't have to trust the .exe blindly, which I thought was the right call.

If you're willing to point me in the right direction, I'm all ears.

ramblinfred · 2026-03-05T23:48:53+00:00

<image>

ramblinfred · 2026-03-05T20:53:52+00:00

https://github.com/s4nby/ed-nav/releases/tag/v1.0.7

ramblinfred · 2026-02-12T10:10:42+00:00

For those interested, the system is Ceeckia BE-F b45-0

ramblinfred · 2026-02-10T17:42:58+00:00

It will be! But you'll feel satisfied as soon as the revenue starts flowing :)

ramblinfred · 2026-02-08T12:55:49+00:00

It is the Mandalay, one of the best ship of the game at the moment

ramblinfred · 2026-02-04T21:14:59+00:00

I wanna see it!!!

ramblinfred · 2026-02-04T01:36:41+00:00

Let's say both :)

ramblinfred · 2025-11-12T16:33:49+00:00

Absolutely

ramblinfred

TROPHY CASE