After that I've started each time, wait for 1 minute, and walk for 240 sec, press forward (W), at the end of the road - press backward (S) and so on. FPS was measured and recorded by FRAPS.
My conclusions:
- 32 vs 64 bit performance when fps settings is not specified in config (fps limiter is on, default) is practically the same, but 64 bit build in a simple/medium scenes gives much higher maximum FPS. Average FPS in both cases is about 62, which is comfortable. Minimum fps is below comfort level.
- Code: Select all
viewing_range_nodes_min = 70
wanted_fps = 75
fps_max = 120
32 vs 64 bit performance when fps_max = 1000 is specified in config is much higher. Average FPS for 32bit is 225 FPS and 209 FPS for 64bit, way above comfort level. Minimum fps is 103. This configuration gives much more smoother and better gameplay on simple/medium scenes, but could use a bit more computer power.
So if you have a good PC and ~60 FPS in minetest is not comfortable for you, you can get it much higher, by editing FPS settings and view distance, this will help a lot in noncomplex scenes, on a complex scenes difference will be much less. If you play on a big and complex servers, 64bit one is preferred and for me it gives much more smoother gameplay with better FPS even on "just test".
Right now I'm using this settings:
Your phone or window isn't wide enough to display the code box. If it's a phone, try rotating it to landscape mode.
System settings
Server: localhost
Seed: 7774474182753078898
Start point: 70.0 19.5 -0.8 (yaw = 180)
View distance: 70 nodes (fixed)
Wait on server before benchmark: 60 sec
Benchmark time: 240 sec (walk straight forward and back until time runs out)
OS: Windows 7 sp1
System: Core i3-2120, 8GB RAM, ATI Radeon HD 6870
Minetest config without fps settings
+
Spoiler
Minetest config with fps_max = 1000
+
Spoiler
Results
FPS over time
How it looks
Screenshot of the place - https://i.imgur.com/xlUAbIU.jpg
