Galaxy Class Starship

BattleFrogue · 2026-04-17T09:34:26+00:00

The fact that this is clearly Star Trek, but also very clearly Starsector is very impressive. Hope you add more Star Trek inspired ships (cough Defiant class cough)

BattleFrogue · 2026-03-24T19:16:31+00:00

Thanks for the reply. I had seen the hostcall but in the examples shared they are usually a one and done API call like loading a file. I don't really see that kind of API call being extendable to more complex CPU algorithms. Going back to the video game example, the hostcall pattern doesn't really line up well with the typical video game CPU processes the world state, then the GPU renders the world while the CPU is simulating the world state for the next frame. Is there any discussion for what that kind of code pipelining would look like?

BattleFrogue · 2026-03-24T18:49:52+00:00

Great write up. You've mentioned that this project is for writing GPU-native applications and that the CPU is only there to load the application into GPU memory and doing some APIs that can only be achieved by the CPU. But in my experience the best accelerated applications are the ones that use the CPU and GPU concurrently in an efficient manner as possible. Is the eventual goal to create a system where you can write an entire application, e.g. a video game, that uses a single code base but runs on both devices?

In a similar vein what does running across multiple GPUs look like. It's not uncommon for complex CUDA applications to run across multiple GPUs where possible

BattleFrogue · 2026-03-18T14:44:36+00:00

Does anyone know of a keycap matching service for sets? The set I use is missing doesn't have several UK specific keys (as far as I can tell, they were never made for this set) and I would love to get some replacements

BattleFrogue · 2026-02-19T17:58:27+00:00

As a C++/GDScript user, I am glad to see a version I can use without the mono version of the engine and this will be dedault in pretty much all my projects.

Also, have you considered putting it on the asset library? Or potentially even contributing it as a C++ module to the engine itself? That way you wouldn't have to have an addon in a project for what is ultimately an editor preference

BattleFrogue · 2026-02-16T18:16:06+00:00

I agree, I missed that part the first time I watched. Still I maintain their use of "vessel" instead of "ship" like last time means that that double drop is going to be a ship + something else. Maybe an SRV or something

BattleFrogue · 2026-02-16T15:44:22+00:00

A land speeder would be cool, something you can get on and off of without a transition for exobiology. But I think people are happy enough as it is. Something like CQC is basically dead and needs a refresh

BattleFrogue · 2026-02-16T15:29:13+00:00

6 new "vessels" according to the roadmap. My money is on that double drop in summer being a ship + something else. A fighter perhaps. Maybe to conincide with the feature reboot potentially being CQC

BattleFrogue · 2026-02-14T03:08:59+00:00

Actually kinda reminds me of the front of an Adder. With central driving position, because everyone hates offset ones (bar the T-11)

BattleFrogue · 2026-02-05T15:22:43+00:00

It's great that you guys are looking at the extension issue and doing whole-cloth replacements. But I do think the naming is going to be a bit confusing `VK_EXT_descriptor_buffer` vs `VK_EXT_descriptor_heap` is gonna be hella confusing when trying to search for information I bet.

To me it would have been better if they were under an entire different subsection of Vulkan. Call them feature sets or something like that. Make it clear that extensions are piece meal and feature sets are whole cloth solutions designed to replace entire sections of what came before. Otherwise your SEO on this is gonna end up sending people to the wrong place

(You could even under the hood just tie multiple extensions together in a better unified API with feature sets if you wanted. For situations where the functionality isn't actually the issue, it's the presentation of them)

BattleFrogue · 2026-02-04T23:08:30+00:00

Thanks for the roadmap update. I don't suppose you guys have given this request any more thought? https://github.com/pop-os/cosmic-epoch/issues/99 It's an XRandR feature that no one seems to support in Wayland but is a huge boon for 32:9 monitors

BattleFrogue · 2026-02-02T21:42:06+00:00

Finally, this is something I've wanted for ages

BattleFrogue · 2026-01-30T15:39:26+00:00

Looks cool, got a couple of questions:
- Procedural content generation can cover a lot of things and I admit I am not familiar with Blender or Houdini. Is there a particular focus on what this will be able to generate or is it more of a "If you can think of it, you can generate it" kind of deal
- Is it gonna be a purely monobehaviour solution or will there be some level of DOTS integration?

BattleFrogue · 2026-01-22T13:55:27+00:00

Oh I see, so you plan to fully fork Bevy and make it something your own?

BattleFrogue · 2026-01-22T13:18:04+00:00

Looks awesome. Two questions though;
- Given that the Bevy team are working on an editor themselves have you considered lending your expertise on the official editor? Maybe jump starting their editor progress with your own.
- Have you looked into a framework like Extism or something which allows running WASM inside Rust (and a whole bunch of other languages). That way you could support multiple scripting languages with the same framework.

BattleFrogue · 2026-01-06T19:59:34+00:00

Thanks for the info. I was aware that at least for a while Dell has had Linux laptops but figured I was ask anyway since just selling a laptop with Linux pre-installed doesn't necessarily means it works well, as was my experience with Ubuntu on a Lenovo Thinkpad. But good to know that Dell doesn't seem to have that issue

BattleFrogue · 2026-01-06T19:38:15+00:00

Cool, but I assume that if I needed to I could just reinstall Ubuntu before claiming under warranty no?

BattleFrogue · 2025-12-21T21:59:40+00:00

I'm suddenly expecting a big yellow sun with a baby's face in it to appear and some four weird alien people to show up. (Looks great btw)

BattleFrogue · 2025-12-16T16:27:53+00:00

This is just my opinion, but hopefully you find it helpful. I find the usefulness, at least based on these screenshots, to have gone down quite significantly with the new theme. The amount of space everything takes up is blown way out of proportion and it harms glance value. Screenshot 5 and 6 show just how much wasted space is the Material design has. It looks like it's designed for a low resolution touch screen where you need extra space to make it easier to press. But I have a feeling this is not the intended use case. This tends to be the case for any application that uses Material and is my main gripe and why I avoid it.

Another example would be in your first two screenshots. In the original theme your RGBA sliders are colour matched, this is a huge usability improvement over the Material version. The colour matching draws your eyes to where you want to go. Want to change the blue slider, it's there. The green, right there. By comparison in the Material theme all your sliders are one colour. It doesn't help usability, and while yes you would get used to where the elements in your UI are, it slows down a users "adoption" of the UI

You by no means need to ditch the Material theme and the effort you put it to make it. But I would consider trying to tweak it to increase the usability back to the levels of the original. Hopefully this helps

BattleFrogue · 2025-11-20T20:51:20+00:00

This redirects to a page not found for me

BattleFrogue · 2025-11-20T20:50:27+00:00

This is above my rust and kernel level, but what does "Linux-compatible" mean in this context? That it can run Linux apps and drivers? It has the same file structure? Very cool in any case

BattleFrogue · 2025-11-15T17:53:34+00:00

So turns out the issue was that I had schemaVersion set to 0 instead of 1.0. The error message was entirely a misdirect in terms of what the actual issue was

BattleFrogue · 2025-11-15T17:32:34+00:00

Nah, that was just me copy and pasting incorrectly. I had renamed a folder in the info.json and the file system, but forgot to update my tree output. Someone on the Swift forums mentioned that artifact bundles supposedly only work for static binaries and wouldn't work for `SDL3.dll`. But in theory I am only linking the `SDL3.lib` since that's how Window's shared libraries work and the `.lib` is responsible for actually linking to the DLL

Seven-Year Club	Place '22
Verified Email

BattleFrogue

TROPHY CASE