What's the worst PC you managed to get modern TF2 running on?
I recently was given a 2008 PC with some Intel Quad Q8300 and after putting an old graphics card on it it could actually run TF2 from linux, even with just 2GB of DDR2 RAM !
Even before installing a fps config it rarely dropped below 100 fps on Legacy OpenGL... crazy.
https://i.imgur.com/JeVnSv2.jpeg
What's the worst PC you managed to get modern TF2 running on?
I recently was given a 2008 PC with some Intel Quad Q8300 and after putting an old graphics card on it it could actually run TF2 from linux, even with just 2GB of DDR2 RAM !
Even before installing a fps config it rarely dropped below 100 fps on Legacy OpenGL... crazy.
[img]https://i.imgur.com/JeVnSv2.jpeg[/img]
my shit computer blyat. fuck my frames. every game i pley lag. fucking computer
my shit computer blyat. fuck my frames. every game i pley lag. fucking computer
my old family computer ran on windows 98, had viruses from a sketchy wizard 101 download link, and took minutes to load a single tab of chrome, and it got like a solid 5 fps on completely low settings, actually unplayable but somehow launchable LMFAO
my old family computer ran on windows 98, had viruses from a sketchy wizard 101 download link, and took minutes to load a single tab of chrome, and it got like a solid 5 fps on completely low settings, actually unplayable but somehow launchable LMFAO
I might have a winner. I have a Acer Aspire One AOA150X netbook from 2008 with a Intel Atom N270 and 1GB DDR2. Here is an Imgur album of my experiments with it in 2018 plus a picture from today.
https://imgur.com/a/9IZmioP
I don't have all of the details because this was years ago. The benchmarks were within 1-3 FPS, but in practice it didn't matter because the actual experience was seconds per frame. When staring at a wall on itemtest it showed signs of life by pushing hundreds of FPS.
I used a stripped-down sketchy version of Windows 7. I definitely must have known at the time that Linux would theoretically be way better for this sort of thing but I must have had my reasons for not using it. If I were to take a guess it would probably have something to do with Windows being net better overall for the ancient integrated graphics by using DirectX instead of OpenGL. Or just that the OpenGL Linux version wouldn't launch at all.
I think mastercoms told me to disable multicore rendering or something equally unheard of. I tried some other software as well.
Team Fortress Classic: Not much better. It could simply be that running an operating system and a 3D application at the same time is simply too much to ask for the poor single-core 3W CPU.
Retail Half-Life 2: I recall this being a single-digit FPS but technically a moving picture unlike TF2. Wall-stares also technically gave me smooth motion.
DUSK: Despite the pseudo-N64 graphics it is in fact a game running on a modern game engine and therefore unusable. It did launch though.
NES emulation: To give no credit at all, I was surprised to see an NES game run at full speed. Mario still wasn't any fun because of the keyboard ghosting.
Steam dropped support for 32-bit hardware so I'm not sure if I could revisit this experiment if I wanted to, but if anyone has any further optimizations I would be down to try to break the 4FPS barrier.
I might have a winner. I have a Acer Aspire One AOA150X netbook from 2008 with a Intel Atom N270 and 1GB DDR2. Here is an Imgur album of my experiments with it in 2018 plus a picture from today.
https://imgur.com/a/9IZmioP
I don't have all of the details because this was years ago. The benchmarks were within 1-3 FPS, but in practice it didn't matter because the actual experience was seconds per frame. When staring at a wall on itemtest it showed signs of life by pushing hundreds of FPS.
I used a stripped-down sketchy version of Windows 7. I definitely must have known at the time that Linux would theoretically be way better for this sort of thing but I must have had my reasons for not using it. If I were to take a guess it would probably have something to do with Windows being net better overall for the ancient integrated graphics by using DirectX instead of OpenGL. Or just that the OpenGL Linux version wouldn't launch at all.
I think mastercoms told me to disable multicore rendering or something equally unheard of. I tried some other software as well.
[u]Team Fortress Classic[/u]: Not much better. It could simply be that running an operating system and a 3D application at the same time is simply too much to ask for the poor single-core 3W CPU.
[u]Retail Half-Life 2[/u]: I recall this being a single-digit FPS but technically a moving picture unlike TF2. Wall-stares also technically gave me smooth motion.
[u]DUSK[/u]: Despite the pseudo-N64 graphics it is in fact a game running on a modern game engine and therefore unusable. It did launch though.
[u]NES emulation[/u]: To give no credit at all, I was surprised to see an NES game run at full speed. Mario still wasn't any fun because of the keyboard ghosting.
Steam dropped support for 32-bit hardware so I'm not sure if I could revisit this experiment if I wanted to, but if anyone has any further optimizations I would be down to try to break the 4FPS barrier.
EnzoDBwindows 98
just learnt that steam supported win98 at some point during TF2's life
jzplrAcer Aspire One AOA150X netbook from 2008
its crazy that it could even launch TF2 lol, those netbooks were underpowered when they came out already
One thing i remember playing in craptops is you'd get awful stutter because the FPS would drop below your tickrate, so you'd have to set a lower tickrate to avoid it
https://images.steamusercontent.com/ugc/849345464519735582/7567C8F00C156EA035639166E3A62CC5224D67E0/?imw=5000&imh=5000&ima=fit&impolicy=Letterbox&imcolor=%23000000&letterbox=false
[quote=EnzoDB]windows 98[/quote]
just learnt that steam supported win98 at some point during TF2's life
[quote=jzplr]Acer Aspire One AOA150X netbook from 2008[/quote]
its crazy that it could even launch TF2 lol, those netbooks were underpowered when they came out already
One thing i remember playing in craptops is you'd get awful stutter because the FPS would drop below your tickrate, so you'd have to set a lower tickrate to avoid it
[img]https://images.steamusercontent.com/ugc/849345464519735582/7567C8F00C156EA035639166E3A62CC5224D67E0/?imw=5000&imh=5000&ima=fit&impolicy=Letterbox&imcolor=%23000000&letterbox=false[/img]