User Tools
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revision Both sides next revision | ||
|
general:faqs_users [2008-01-03 20:24] Carsten Updated FPS FAQ |
general:faqs_users [2008-01-03 20:40] Carsten Revised some phrases. |
||
|---|---|---|---|
| Line 85: | Line 85: | ||
| Here is a list of options and suggestions that might help with the performance. You may simply try them out, and see what works best for your system. However, please note that most of these options //will buy you faster rendering at the cost of decreased image quality//. | Here is a list of options and suggestions that might help with the performance. You may simply try them out, and see what works best for your system. However, please note that most of these options //will buy you faster rendering at the cost of decreased image quality//. | ||
| - | * **Vertical synchronization enabled.** People frequently report that their frame-rate seems to be "capped" or limited to 60 or 30 (or another multiple of 15) FPS. This is usually because //vertical synchronization// is enabled for your graphics board. Please see the Wikipedia article at [[wp>Vertical_synchronization]] for more details. \\ Find the related setting in the control panel of your graphics driver to disable the "v-sync". Your graphics driver and board will then render the frames without the v-sync delay, which in turn increases the FPS. | + | * **Vertical synchronization.** People frequently report that their frame-rate seems to be capped to 60 or 30 (or another multiple of 15) FPS. This is usually because //vertical synchronization// is enabled for your graphics board. Please see the Wikipedia article at [[wp>Vertical_synchronization]] for technical details on the matter. \\ Find the related setting in the control panel of your graphics driver to disable the vertical synchronization. Your graphics driver and board will then render the frames without the delay inherent to vertical synchronization, which in turn increases the FPS. |
| * **Video memory and texture size.** If your graphics board has too little video memory to store all the textures simultaneously that Ca3DE needs for rendering a single frame, the FPS usually suffers significantly. In this case you can set a lower texture quality in the initial Options dialog. \\ This effectively scales all textures down to not exceed a maximum size, and therefore improves the chances that they all fit into video RAM simultaneously. Another option is to add physical memory to your graphics board. 128 MB normally work well, 256 MB are even better and can store the textures even in maximum resolution. | * **Video memory and texture size.** If your graphics board has too little video memory to store all the textures simultaneously that Ca3DE needs for rendering a single frame, the FPS usually suffers significantly. In this case you can set a lower texture quality in the initial Options dialog. \\ This effectively scales all textures down to not exceed a maximum size, and therefore improves the chances that they all fit into video RAM simultaneously. Another option is to add physical memory to your graphics board. 128 MB normally work well, 256 MB are even better and can store the textures even in maximum resolution. | ||
| * **Display resolution.** The default display resolution of Ca3DE is 1024*768. That setting has been proven a good compromise between image quality and frame-rate, but you might decrease it within the console in order to increase the frame-rate. Reducing to 800*600 or even to 640*480 helps a lot. | * **Display resolution.** The default display resolution of Ca3DE is 1024*768. That setting has been proven a good compromise between image quality and frame-rate, but you might decrease it within the console in order to increase the frame-rate. Reducing to 800*600 or even to 640*480 helps a lot. | ||
| - | * **Pixel fill-rate.** A common reason for low FPS is that dynamic lighting and shadows consume a //very high pixel fill-rate//. Besides reducing the display resolution as mentioned above, an effective way to improve FPS in this case is to turn dynamic lighting and shadow effects entirely off. \\ One way to achieve this is to set the ''cl_maxLights'' console variable to ''0''. This can be achieved in the game console or by putting the statement<code lua>cl_maxLights=0;</code> into your ''config.lua'' file. \\ When Ca3DE is run from the command-line, it is also possible to specify a renderer DLL that makes use of less graphics features. For example, you might try the OpenGL 1.2 renderer in order to increase the FPS:<code>C:\...\Projects\Ca3D-Engine> Ca3DE.exe -clRenderer ..\Libs\build\win32\vc8\release\MaterialSystem\RendererOpenGL12.dll</code> | + | * **Pixel fill-rate.** A common reason for low FPS is that dynamic lighting and shadows consume a //very high pixel fill-rate//. Besides reducing the display resolution as mentioned above, an effective way to improve FPS in this case is to turn dynamic lighting and shadow effects entirely off. \\ One way to achieve this is to set the ''cl_maxLights'' console variable to ''0''. This can be done in the game console or by putting the statement<code lua>cl_maxLights=0;</code> into your ''config.lua'' file. \\ When Ca3DE is run from the command-line, it is also possible to specify a renderer DLL that makes use of less graphics features. For example, you might try the OpenGL 1.2 renderer in order to increase the FPS:<code>C:\...\Projects\Ca3D-Engine> Ca3DE.exe -clRenderer ..\Libs\build\win32\vc8\release\MaterialSystem\RendererOpenGL12.dll</code> |
general/faqs_users.txt ยท Last modified: 2015-05-18 22:09 (external edit)