SLI Celestia
Posted: 06.09.2006, 18:52
Hi, there,
After testing a lot of profiles to get Celestia take advantage of SLI, I have come to a kind of sweet spot to ensure that both GPUs are working.
Here is the code to add to your "nvapps.xml" file in /windows/system32/
Just copy/past the patch into nvapps.xml. Then, open the Nvidia control panel and browse to "New Application". Pick any item, change its value to whatever, change it back to the exact initial value and save. The CP is dumb. It will read from the nvapps.xml file but will save the settings to the registry only when you have saved changes. The CP does not read the registry! ... and to add to the confusion, the driver does read the settings from the registry, not from nvapps!
This shows that SLI is activated to display the highest possible quality:
Celestia is CPU-bound. SLI will kick in only for the highest quality rendering when asked to push as many pixels as possible.
Enjoy
After testing a lot of profiles to get Celestia take advantage of SLI, I have come to a kind of sweet spot to ensure that both GPUs are working.
Here is the code to add to your "nvapps.xml" file in /windows/system32/
Code: Select all
<PROFILE Label="New Application">
<APPLICATION Label="celestia.exe"/>
<PROPERTY Label="aa_default" Value="10000018"/>
<PROPERTY Label="gamma_correct_aa" Value="0"/>
<PROPERTY Label="af_default" Value="10000010"/>
<PROPERTY Label="vsync_default" Value="8416747"/>
<PROPERTY Label="triple_buffering" Value="1"/>
<PROPERTY Label="multichip_ogl_options" Value="10"/>
<PROPERTY Label="d3d_negative_lod_bias_status" Value="0"/>
<PROPERTY Label="conformant_texture_clamp" Value="0"/>
<PROPERTY Label="ogl_version" Value="3157554"/>
<PROPERTY Label="ogl_extension" Value="0"/>
<PROPERTY Label="dyn_tiling_mode" Value="0"/>
<PROPERTY Label="multi_mon_config" Value="0"/>
<PROPERTY Label="sli_aa" Value="29060797"/>
<PROPERTY Label="sli_afr" Value="51621661"/>
</PROFILE>
Just copy/past the patch into nvapps.xml. Then, open the Nvidia control panel and browse to "New Application". Pick any item, change its value to whatever, change it back to the exact initial value and save. The CP is dumb. It will read from the nvapps.xml file but will save the settings to the registry only when you have saved changes. The CP does not read the registry! ... and to add to the confusion, the driver does read the settings from the registry, not from nvapps!
This shows that SLI is activated to display the highest possible quality:
Celestia is CPU-bound. SLI will kick in only for the highest quality rendering when asked to push as many pixels as possible.
Enjoy