Keen:Performance Advice: Difference between revisions

From Medieval Engineers Wiki
Jump to navigation Jump to search
(Initial layout)
 
mNo edit summary
 
(7 intermediate revisions by the same user not shown)
Line 1: Line 1:
{{SEO|image_url=http://www.medievalengineerswiki.com/images/b/b7/KeenLogoBig.png|description=Medieval Engineers tries to not limit how complex worlds you can create. At certain points you will probably reach the memory limit of your system and won’t be able to add more objects, but that’s the only limit we imposed.}}
{{Keen:OCH}}
Medieval Engineers tries to not limit how complex worlds you can create. At certain points you will probably reach the memory limit of your system and won’t be able to add more objects, but that’s the only limit we imposed.
Medieval Engineers tries to not limit how complex worlds you can create. At certain points you will probably reach the memory limit of your system and won’t be able to add more objects, but that’s the only limit we imposed.


Line 24: Line 28:
Medieval Engineers is undergoing frequent optimizations and the performance will only get better. Nevertheless, the performance will always depend on complexity.
Medieval Engineers is undergoing frequent optimizations and the performance will only get better. Nevertheless, the performance will always depend on complexity.


[http://test.medievalengineers.com/about/system-requirements Check the System Requirements]
[http://medievalengineers.com/about/system-requirements Check the System Requirements]
[[Category:Keen_Help]]
[[Category:Keen_Help]]

Latest revision as of 12:51, 7 July 2018



Medieval Engineers tries to not limit how complex worlds you can create. At certain points you will probably reach the memory limit of your system and won’t be able to add more objects, but that’s the only limit we imposed.


We need you to understand that performance depends on the complexity of your world and the configuration of your computer. Simple worlds run smoothly even on low-end computers, but a more complex world with rich object interactions could overload even high-end computers.


Performance means how smooth the game runs. It is defined by FPS (frames per second) as well. The higher the FPS rating, the smoother the game runs. 60 FPS is great, 30 is good and even 20 is OK. If the game gets below 20, you will start feeling the delay. FPS doesn’t impact the physics simulation. FPS influences only your experience and perceived smoothness.


We can’t say where the line between a simple and a complex world is drawn. Please use your judgment and experiment a lot.


The basic rule is: more objects require more computations and more memory.


To help you understand what impacts the performance, we can provide the following advice:

  • If you are playing on slower computer use the empty world scenario. This scenario starts with less customization of the planet which will use less memory and processing to start with.
  • Set vegetation view distance to near. This will affect how many trees and plants are rendered which will have a direct impact on FPS.
  • Lowering shadow and textures quality will also help you get better performance.
  • As last but not least you can always lower your resolution which will make your game more fluent. But remember to use only recommended resolutions (marked by ***).


Medieval Engineers is undergoing frequent optimizations and the performance will only get better. Nevertheless, the performance will always depend on complexity.

Check the System Requirements