Posted August 18, 2019
Hi,
I have a question about Postal Classic and Uncut on Linux. I forgot there's Linux build available and I've tested the Windows 7 Ultimate one on my trashy laptop with Intel GM 965 Express integrated graphic chipset. It runs very smooth, even though it's terrible hardware. Postal 2 runs in maybe 10-15 FPS in 1024x768 while in fullscreen, which is 1280x800 (slightly bigger), due to probably shaders issue is unplayable. But I don't blame anyone, it is really strange and hard to get it working piece of hardware.
What exactly is required to run Postal 1 on Linux? I have Xubuntu 18.04.03, 4GB DDR3 RAM, Intel Core 2 Duo T5750 (2 cores, 2GHz per core, 2 threads). And yeah, it's dual boot with the mentioned Win7 Ultimate. Running start.sh in a terminal outputs: "Running Postal: Classic and Uncut" and ends the process instantly. It doesn't appear in the Task Manager because it closes so fast that it cannot be tracked having the fastest available refresh rate chosen. Maybe top could do this work when set to probe processes really fast, like every milisecond for a single second.
Do you have any ideas what might be wrong?
I have a question about Postal Classic and Uncut on Linux. I forgot there's Linux build available and I've tested the Windows 7 Ultimate one on my trashy laptop with Intel GM 965 Express integrated graphic chipset. It runs very smooth, even though it's terrible hardware. Postal 2 runs in maybe 10-15 FPS in 1024x768 while in fullscreen, which is 1280x800 (slightly bigger), due to probably shaders issue is unplayable. But I don't blame anyone, it is really strange and hard to get it working piece of hardware.
What exactly is required to run Postal 1 on Linux? I have Xubuntu 18.04.03, 4GB DDR3 RAM, Intel Core 2 Duo T5750 (2 cores, 2GHz per core, 2 threads). And yeah, it's dual boot with the mentioned Win7 Ultimate. Running start.sh in a terminal outputs: "Running Postal: Classic and Uncut" and ends the process instantly. It doesn't appear in the Task Manager because it closes so fast that it cannot be tracked having the fastest available refresh rate chosen. Maybe top could do this work when set to probe processes really fast, like every milisecond for a single second.
Do you have any ideas what might be wrong?
No posts in this topic were marked as the solution yet. If you can help, add your reply