• 0 Posts
  • 15 Comments
Joined 3 years ago
cake
Cake day: June 15th, 2023

help-circle

  • 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…






  • 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.)






  • I haven’t looked at the schematics, so I am not certain which connection exactly would be needed. I only know that the Reform Mainboard and the Reform CM4 adapter don’t expose any way of writing to the eMMC other than booting the system first. The problem here is that the Banana Pi CM4 boot process first looks for a bootloader in eMMC, and only if it cannot find one there, tries the SD card. So, if one flashes a bootloader that gets recognized by the firmware, but that later fails to boot, one is stuck…

    The I/O board on the other hand allows to connect to the CM4 via USB, and there is a weird, but supposedly working, procedure to erase the data in eMMC.

    In any case, I now have a spare CM4 I/O board lying around, and if I ever choose to upgrade my Reform to the Rockchip SoM (or something even faster), I can then still use the CM4 as a small standalone PC.


  • At least in my case, the default OS came on an SD Card, and both, the M.2 SSD (which I had ordered together with the laptop) and the eMMC were empty. The manual contains a section about moving the OS to eMMC, so I guess that’s their default setup.

    (In my case there’s an additional thing though: For the Banana Pi CM4 SoM the installation of u-boot into eMMC is officially not supported, as one would need a CM4 I/O board to erase it again, if anything goes wrong. I installed it there anyhow, and it’s working for me, but I did buy the I/O board beforehand as a precaution.)


  • I am curious how much work it will be to modify that Ubuntu image to fully work on the Reform. The audio chip and some other peripherals are on the mainboard, and need to be included in the device tree for the kernel to pick them up, so I would expect that at least some modifications of the image are needed.

    It might already be enough to grab the device tree from the MNT gitlab, compile it, and put it in the boot partition for stuff to work. (You will likely also want to install the reform-tools - either from their gitlab or from their repository. They include a kernel module that is needed to get battery readout and to power off the laptop on shutdown.)

    What helped me a lot while setting up the system was that I kept the SD card with the official (Debian Unstable) image around - every time something didn’t work, I could boot it up and check how the official image does it.