Deixo aqui alguns tópicos muito bons para a configuração do FSX
Eu ainda não os fiz, mas testem vocês e deixem aqui o feedback
http://www.forum.aerosoft.com/index.php?showtopic=30796
http://forums1.avsim.net/index.php?showtopic=281538
http://www.simforums.com/forums/forum_p ... ?TID=29041"
[Desactualizado] Dicas Para Melhorar o Desempenho do FSX
Moderadores: Comandante, ATC
Regras do Fórum
Coloquem apenas tópicos e posts com qualidade (truques e dicas), para que todos possam lêr e aprender.
Coloquem apenas tópicos e posts com qualidade (truques e dicas), para que todos possam lêr e aprender.
-
- 1º Oficial
- Mensagens: 97
- Registado: quarta fev 10, 2010 5:49 pm
-
- 1º Oficial
- Mensagens: 97
- Registado: quarta fev 10, 2010 5:49 pm
Re: Dicas para Melhorar o desempenho do FSX
Adicionei estas duas linhas ao config e posso-vos dizer que notei grandes diferenças
[BufferPools]
UsePools=0
(note that PoolSize is ignored if UsePools equals 0. Use 1 if you experience crashes )
When you see 'toggle' values (1 or 0) it means ON/OFF - UsePools its an ON / OFF value (1 or 0)
PoolSize its a 'size' value (in bytes) If you 'DISABLE' the pools, you will get increased
performance, AND ALSO, instability if you don't 'balance' your components and sliders
apropiately, in case of instability, then simply DO use pools by changing the value of UsePools
to 1 and 'adjust' PoolSize. BE CAREFUL (and forget everything you have been told about this value)
it does NOT use video memory, PERIOD. it uses SYSTEM memory, because its a special type of pool
called Explicit Vertex buffer which DOESN'T GO INTO VIDEO MEMORY unless they have A VERY SPECIFIC FLAG
(and they don't) more info here: http://msdn.microsoft.com/en-us/library/ff539490.aspx
you can also do your own tests and see how 'increasing' PoolSize affects the size of the fsx.exe process proportionally.
[GRAPHICS]
HIGHMEMFIX=1
Fixes errors with texture addressing modes in WDDM1.0 and 1.1 when using a lot of video memory
The HIGHMEMFIX=1 you see above, fixes a bug in the FSX engine on how it handles texture addressing modes (Wrap,Clamp) and initial render states on single pass shaders, it will completely prevent textures, buildings and entire cockpits from dissapearing! this 'bug' is triggered when there is a high video memory usage situation. so, enjoy this is my way of giving to a community that has given me so much over the years.
[BufferPools]
UsePools=0
(note that PoolSize is ignored if UsePools equals 0. Use 1 if you experience crashes )
When you see 'toggle' values (1 or 0) it means ON/OFF - UsePools its an ON / OFF value (1 or 0)
PoolSize its a 'size' value (in bytes) If you 'DISABLE' the pools, you will get increased
performance, AND ALSO, instability if you don't 'balance' your components and sliders
apropiately, in case of instability, then simply DO use pools by changing the value of UsePools
to 1 and 'adjust' PoolSize. BE CAREFUL (and forget everything you have been told about this value)
it does NOT use video memory, PERIOD. it uses SYSTEM memory, because its a special type of pool
called Explicit Vertex buffer which DOESN'T GO INTO VIDEO MEMORY unless they have A VERY SPECIFIC FLAG
(and they don't) more info here: http://msdn.microsoft.com/en-us/library/ff539490.aspx
you can also do your own tests and see how 'increasing' PoolSize affects the size of the fsx.exe process proportionally.
[GRAPHICS]
HIGHMEMFIX=1
Fixes errors with texture addressing modes in WDDM1.0 and 1.1 when using a lot of video memory
The HIGHMEMFIX=1 you see above, fixes a bug in the FSX engine on how it handles texture addressing modes (Wrap,Clamp) and initial render states on single pass shaders, it will completely prevent textures, buildings and entire cockpits from dissapearing! this 'bug' is triggered when there is a high video memory usage situation. so, enjoy this is my way of giving to a community that has given me so much over the years.