More or less copy/cross-posting this from descent2.de, but it could be useful here as well. Gives better suggestions/information than I could.
Here's a few hints what you can do if D2X-XL runs too slowly for you. Basically the hints boil down to three categories:
Decrease memory usage
- Decrease memory usage
- Decrease the burden put on the lighting system
- Decrease usage of computationally intensive effects
Decrease the burden on the lighting systemThis category actually might be split in two subdivions: Decrease the number of light sources, and decrease the number of \"entities\" (vertices) to be lit.
- Don't use the highest texture quality for hires textures, the second highest quality really is good enough and only requires 1/4 of the texture memory.
- Depending on the number of light sources, texture space for lightmaps can become pretty big. Usually \"medium\" lightmap quality is good enough and requires way less memory.
- Another way to decrease texture memory usage is to set \"-model_quality 2\" in d2x.ini.
Decrease usage of computationally intensive effectsMost of these are related to using effects based on D2X-XL's particle system.
- turn on hardware object lighting
- limit light sources/object to 8
- turn off powerups being light sources (that will result in only powerups that might emit light - like energy sparks or shield orbs - actually emitting light)
- Set \"-fix_models 1\" and \"-alt_models 1\" in d2x.ini, as this will make D2X-XL use optimized models of the standard robots with way less faces and vertices.
- Use per vertex lighting combined with lightmaps. That usually looks almost as good as per pixel lighting and is much, much faster. If your hardware has problems with handling the lightmaps, fall back to pure per vertex lighting.
- Only use the weakest mesh improvement, or turn it completely off. Mesh improvement creates a lot more vertices, and with a lot of light sources around (like shots or powerups), can slow the lighting calculation down significantly.
- If this still isn't good enough, turn of high res models and 3D powerups and use the high res sprites for the latter instead (they still look great).
- Explosion shrapnel really can kill the frame rate. Turn it off.
- Particle light trails are also very expensive to render. Choose solid light trails instead, they look almost as good.
- Turn off gatling smoke trails as these are also particle based (technically they are a particle trail like the one of lasers, they just don't emit light and are gray).
- Turn off explosion lightning effects, set the lightning quality to \"low\", the style to \"jaggy\" and turn off lightning plasma. Imo the lightning effects adding most to the game are \"damage lightnings\" (the blue static discharges creeping over a robot when it is severely damaged) and the omega lightnings. Lightnings usually also add a lot of light sources that need to be handled on top of what is already there.
- Highest corona quality will only be fast enough on good gfx hardware, as it does some more or less advanced render buffer and shader stuff (I found it to work well on ATI Radeon X850 XT and X1900 XT).
- Turn off real-time shadows. They may look cool, but are somewhat costly to render (and make people fire at the shadows instead the robots anyway ... )
- If you have a multicore CPU, turn on multithreading. This will mostly avoid framerates dropping too much when creating effects that cost a lot of CPU power.
On my system (dual core Athlon 4400, Radeon X1900 XT w/ 256 MB VRAM), I can turn on most of the stuff above and hardly ever experience lag. So contrary to what some might say, you don't need the latest high end machine to enjoy most of D2X-XL's goodness.