

For 2) I’d also suggest to check out SDL. There are excellent SDL bindings for Rust, and it’s way less involved than dragging in a fully-featured game engine.


For 2) I’d also suggest to check out SDL. There are excellent SDL bindings for Rust, and it’s way less involved than dragging in a fully-featured game engine.


For $50 I’d get (afaict current prices):
This totals now $48.18. If you have an additional dollar to spare, I’d also recommend to get something to scratch that retro-gaming itch:
That’s now $50.91 in total.
Oh, sorry. I stand corrected then.
I’m willing to bet that it’s AI. It soft-contradicts itself quite often, emphasising that C++ is “Performance First”, but then also claiming stuff like “Rust achieves memory safety with zero runtime overhead”.
Edit: What I am trying to say is that I have seen text like this in LLM output quite often, if the LLM is mixing text from different sources in its training data.
Also, there is just wrong stuff in the text itself, not only in the conclusion. For instance the claim that Rust’s type system makes data races impossible. They are easier to avoid, but there is nothing stopping you from writing data races… Here, for instance, have a data race in safe Rust…


I’m new to both, FreeCAD and Blender, but what I’ve been doing up to now:


Oh, and a small follow-up:
I just asked my partner which gamepad feels “better”. She chose the Xbox Series X controller, so maybe my opinion isn’t the most objective one.


There are several small differences between the Xbox 360 and the Xbox Series X gamepad. No single point by itself would be a very big difference, but overall it sums up. I have both gamepads in front of me, and will try to make a comparison:
I think the last point - the feeling when using the buttons and especially the D-Pad - is the most important one for me. On the Xbox 360 gamepad the buttons feel like actual buttons. On the Xbox Series X gamepad they sound and feel like a fidget toy. Using the D-Pad on the Xbox Series X gamepad is really annoying, because of the noise it makes.


Just to toss this in: If all you need is to draw stuff to the screen, play audio, and handle input, you might have a good experience with using SDL or raylib. Those are “just” libraries and not fully featured engines, so they don’t come with advanced features like asset management or a ready-to-use level-editor.
I am not saying that those are a better option than a fully featured engine, just that, depending on what you are trying to achieve, they might be.


What annoys me is that previous generations of Xbox controllers had quite good build quality. The Xbox 360 controller was amazing in that regard, and the Xbox One controller was pretty decent too. The Xbox Series X controllers (and I am explicitly not excluding the “Elite” model) feel like cheap trash in comparison.


The worst part is that it is incredibly difficult (impossible?) to update the controller firmware on anything other than an Xbox or a Windows PC…
I’d go with different system acounts. That way their savegames are guaranteed to stay separate.
That’s because on PC most games just care about the system user when determining the savegame folder, and don’t care about steam accounts.
So, what I’d do is to:


Gamedev here: For non-indie projects it’s not up to the devs to decide which platforms get a native build. That decision is made by the publisher, and usually depends strongly on the estimated amount of extra work needed to make a native version. I agree with your statement, that if devs use ARM development PCs, they get a strong argument to convince publishers to pay for a native version, because porting costs will drop to near-zero.
However (there always is a “however”): Many devs cannot switch away from Windows. If one develops for PC only, it’s possible. If one targets other platforms too (think: game consoles), one is stuck with whatever development environment the manufacturers of those platforms support - what is typically Windows and Visual Studio. It is kind of a chicken-and-egg problem. Platform SDKs will be made available for other operating systems or processor architectures once enough gamedevs are using those. Gamedevs cannot yet use those because platform SDKs aren’t available for them…
It’s, to be honest, a frustrating experience… I personally would switch away from MSVC and Windows the moment I get an opportunity to. However, there never was an opportunity up to now… Our previous tech-director was pushing for Linux on dev machines - or rather: “let the devs use whatever they want, as long as it works” - but there never was an opportunity to switch, due to our games’ target platforms allowing only Windows for development…


I’ve never used Heroic, so I can’t say what to expect, but I’ve never had any issues downloading games via the GoG website.
Have you tried that? Maybe it’s faster?
Though, honestly, I think i might just be some outage on GoGs side. If the downloads via the website are slow too, it might be worth talking to their support.


That “Solid Snake Method” sounds a lot like the emacs doctor…
In case you don’t know what the emacs doctor is: It’s an easter-egg of the text-editor emacs (it is, however, mentioned in the manual). The doctor is a chatbot based on ELIZA, and meant to portrait a psychotherapist. Since it is a rather simple script, it is very limited in what it can do, and mostly just reformulates user input as questions.


For a typical desktop Linux 12 GiB should be fine.
It depends on what you do with the system, of course. If you regularly compile big and template-heavy C++ codebases, work with Blender,… then 12 GiB won’t be enough.
(What really surprised me was how much can still be done with just 4 GiB of memory. My laptop is currently limited to 4 GiB, and with some effort to set up a minimalist system it’s working surprisingly well. I barely ever hit the memory limit - actually only when compiling big template-heavy C++ codebases 😉.)


There was also an option to just install a Debian chroot on Android, with no virtualization in-between.
The app was called Lil’Debi, but isn’t maintained any more since 2018.


shocking and horrifying the player is kind of the whole point of the game
I disagree on the “shocking” part here. DDLC is psychological horror. It does have shocking moments, like the end of Act 1, but this is not the main point. It is way more about relationships than about shock moments. Sadly discussing that part of the game (the later acts…) is massive spoiler territory, so I’ll stop here.
The fact remains though, that it is a horror game, and if the end of Act 1 is already too much, then sorry, but it is only going to get worse. A lot worse. (Or, if you enjoy psychological horror: Better. A lot better.)


Yeah, I could imagine that it would need to be connected to a USB charger for that…
(I hope they make the suggested version with the eInk display. That way the image would persist even if the power runs out.)


Could be wireless. That would also explain the “battery” mentioned in the poll on shitter.
How big the performance hit is depends on the game. If the game logic itself is CPU-heavy, the performance hit will be big. If the game spends most of the CPU time in system-supplied libraries or isn’t CPU-heavy to begin with, it’s gonna be small.
The good news is that many VR titles aren’t CPU-heavy.