Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Performance issues #17251

Janevski opened this issue Oct 19, 2019 · 2 comments


Copy link

@Janevski Janevski commented Oct 19, 2019

Issue Summary

The performance using the latest appimages (playtest-20190825), is far worse than the last deb archive build (Release 20180307).
I get 10-20 fps at best during a skirmish game on the latest playtest appimage and the ingame clock lags, while on the last stable deb release there is no fps counter, but the pefromance is through the roof - very smooth and nice.
If i enable graphing, i see that a lot of time is lost during rendering - the red graph line.
The rest is low.

On a more powerful pc, such as something with an Intel i5 the issue is not noticeable.

Disclaimer: The only occasion when a (Release 20180307) might start to chop is from empty ore mines via bot ore truck pathfinders, or a bot trying to find you and you are on an island.
But that's a completely different topic.

System Information

  • Operating System: Ubuntu 16.04.2
  • .NET / Mono Version: 4.2.1 (Debian
  • OpenRA Version: playtest-20190825 (appimage) bad vs Release 20180307 (.deb archive) good
  • Mod: Red Alert
  • CPU: AMD Athlon(tm) II X4 620 Processor 4x2600MHz 2MB L2 cache
  • RAM: 6GB DDR2
  • GPU: Palit GF8400GS 512M DDR2 64B CRT DVI HDMI

Additional Information:

  • Steps to reproduce

    1. install the game
    2. play skirmish vs a bot
    3. check the fps, or check the system ingame clock vs real time stopwatch
  • Logs

  • OpenRA Replays
  • Screenshots & Videos

This comment has been minimized.

Copy link

@reaperrr reaperrr commented Oct 19, 2019

I suspect the 8400GS might not like some of the changes we made to our renderer, I doubt that the issue is CPU-side.


This comment has been minimized.

Copy link

@GraionDilach GraionDilach commented Oct 19, 2019

Bleed already got the OpenGL2 to OpenGL3 bump - that might have fixed this already.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
3 participants
You can’t perform that action at this time.