4 ms·

It's orders of magnitude more powerful than machines that can run Doom or Quake. The ports you have tried must be terrible.

foxfluff 5y ago
Or misconfigured? Graphics drivers and configuration would be the first suspect.
- regularfry 5y ago
  I wonder about this too, particularly with what effects it might be having on the browser performance. It feels noticeably worse than a browser on an equivalent phone.
  - foxfluff 5y ago
    Even with everything configured right, the browsing experience can be stuttery. From a performance / resource usage perspective, the web is an absolute disaster today.
    - regularfry 5y ago
      Well, yes. But making relative comparisons is still useful. And I'm not just thinking about the open web: one of the most common use cases I've got for my pi 400 is as a front-end to the octoprint instances I've got running on other pi's in the house. It's just not quite as slick on the 400 as it should be.
- petercooper 5y ago
  When I first got my 400, I set it up to run on my 4K monitor at an appropriate resolution for such a monitor and.. it was super slow. The mouse pointer lagged, everything was terrible. After changing to 1920x1080 it was smooth as butter 60Hz even using the browser, so I think something is definitely going on in terms of drivers.
dusted 5y ago
Is this your personal experience, what did you do to get them to run well ? I literally just installed the official operating system, following the official instructions and installed both pieces of software from the official package repositories.
- foxfluff 5y ago
  I haven't tried the official OS but with Alpine I had to enable a DT overlay (IIRC vc4-fkms-v3d) and install the relevant mesa driver (probably mesa-dri-vc4) to get X performance to a level where it's not absolute misery. Some other tweaks were required too to support my screen resolution. For Quake3, you may have to change the renderer to opengl1 or try q3lite. See https://forums.raspberrypi.com/viewtopic.php?t=247841 https://forums.raspberrypi.com/viewtopic.php?t=247841 (I have not tried Q3 myself but I know it can run, it even runs on RPi1. There are videos on youtube)
- bawolff 5y ago
  If a game from 1993 designed for 4 mb of ram and a 12 Mhz CPU is struggling on your 4gb ram 2 Ghz cpu, something must be amiss...
  - dpflug 5y ago
    The source ports are more recent, and no longer designed for 4mb of RAM and 12Mhz.
  - wang_li 5y ago
    It depends deeply on what version of doom the poster is talking about. Dhewm3 (source port of Doom 3) runs at 7 FPS on my RPi 4. The original Doom should run perfectly fine. The 2016 version of Doom is unlikely to run with any degree of playability.
    - yoz-y 5y ago
      Intriguing. I always though that when people talk about running doom it 100% of time meant Doom 1 and 2.
dpflug 5y ago
Not necessarily terrible, just not best for that device. gzDoom is fairly resource heavy, but it's had a load of bells and whistles added. Odamex would be more likely to run, and Crispy Doom is basically guaranteed.

foxfluff 5y ago

Or misconfigured? Graphics drivers and configuration would be the first suspect.

regularfry 5y ago
I wonder about this too, particularly with what effects it might be having on the browser performance. It feels noticeably worse than a browser on an equivalent phone.
- foxfluff 5y ago
  Even with everything configured right, the browsing experience can be stuttery. From a performance / resource usage perspective, the web is an absolute disaster today.
  - regularfry 5y ago
    Well, yes. But making relative comparisons is still useful. And I'm not just thinking about the open web: one of the most common use cases I've got for my pi 400 is as a front-end to the octoprint instances I've got running on other pi's in the house. It's just not quite as slick on the 400 as it should be.
petercooper 5y ago
When I first got my 400, I set it up to run on my 4K monitor at an appropriate resolution for such a monitor and.. it was super slow. The mouse pointer lagged, everything was terrible. After changing to 1920x1080 it was smooth as butter 60Hz even using the browser, so I think something is definitely going on in terms of drivers.

dusted 5y ago

Is this your personal experience, what did you do to get them to run well ? I literally just installed the official operating system, following the official instructions and installed both pieces of software from the official package repositories.

foxfluff 5y ago
I haven't tried the official OS but with Alpine I had to enable a DT overlay (IIRC vc4-fkms-v3d) and install the relevant mesa driver (probably mesa-dri-vc4) to get X performance to a level where it's not absolute misery. Some other tweaks were required too to support my screen resolution. For Quake3, you may have to change the renderer to opengl1 or try q3lite. See https://forums.raspberrypi.com/viewtopic.php?t=247841 https://forums.raspberrypi.com/viewtopic.php?t=247841 (I have not tried Q3 myself but I know it can run, it even runs on RPi1. There are videos on youtube)
bawolff 5y ago
If a game from 1993 designed for 4 mb of ram and a 12 Mhz CPU is struggling on your 4gb ram 2 Ghz cpu, something must be amiss...
- dpflug 5y ago
  The source ports are more recent, and no longer designed for 4mb of RAM and 12Mhz.
- wang_li 5y ago
  It depends deeply on what version of doom the poster is talking about. Dhewm3 (source port of Doom 3) runs at 7 FPS on my RPi 4. The original Doom should run perfectly fine. The 2016 version of Doom is unlikely to run with any degree of playability.
  - yoz-y 5y ago
    Intriguing. I always though that when people talk about running doom it 100% of time meant Doom 1 and 2.

dpflug 5y ago

Not necessarily terrible, just not best for that device. gzDoom is fairly resource heavy, but it's had a load of bells and whistles added. Odamex would be more likely to run, and Crispy Doom is basically guaranteed.