Revision as of 17:28, 20 March 2021
Information about message (contribute ) This message has no documentation.
If you know where or how this message is used, you can help other translators by adding documentation to this message.
Message definition (Simple Config )
The first choice of the "configuration" menu.<br> <br> [[File:aide_pwcg_config.PNG|300px]] <br> <br> Setting the air, ground, AA, and CPU allocations to a low value results in the lightest possible mission.<br> This limits mission items that require a lot of processor power.<br><br> [[File:simple config.png|800px]]<br><br> '''Air Density :''' Unit Density Level, simplified performance customization - low, medium, high, advanced config for custom. Warning : Medium already consumes a lot of CPU.<br> <br> In general "medium" is meant to be the right answer, but there is a reason why these configs are tied to a campaign and not every campaign in PWCG.<br> Depending on the kind of campaign you are running you might want to emphasize one thing over the other.<br> For instance, if you was doing a ground attack campaign and probably a bomber campaign as well, you would set air activity to low and ground to high. You would keep CPU allowance at medium and would tend to leave structure at medium.<br> You would do this more because you don't want to be bothered so much with pesky fighters than for performance reasons.<br> Use Medium Air with Low CPU Allowance. That will put flights in the air than low while limiting bomber flights, which suck up a lot of CPU.<br> If you are flying a fighter campaign you might want to set ground activity to low to save CPU for more planes.<br> If you are flying a ground attack campaign, do the opposite - set air to low.<br> In the end it is planes that take up the majority of CPU cycles with bombers being the worst offenders. Some savings can be had by reducing ground units, but a truck is not nearly as AI intensive as a plane.<br>
The first choice of the "configuration" menu.<br>
<br>
[[File:aide_pwcg_config.PNG|300px]]
<br>
<br>
Setting the air, ground, AA, and CPU allocations to a low value results in the lightest possible mission.<br>
This limits mission items that require a lot of processor power.<br><br>
[[File:simple config.png|800px]]<br><br>
'''Air Density :''' Unit Density Level, simplified performance customization - low, medium, high, advanced config for custom. Warning : Medium already consumes a lot of CPU.<br>
<br>
In general "medium" is meant to be the right answer, but there is a reason why these configs are tied to a campaign and not every campaign in PWCG.<br>
Depending on the kind of campaign you are running you might want to emphasize one thing over the other.<br>
For instance, if you was doing a ground attack campaign and probably a bomber campaign as well, you would set air activity to low and ground to high. You would keep CPU allowance at medium and would tend to leave structure at medium.<br>
You would do this more because you don't want to be bothered so much with pesky fighters than for performance reasons.<br>
Use Medium Air with Low CPU Allowance. That will put flights in the air than low while limiting bomber flights, which suck up a lot of CPU.<br>
If you are flying a fighter campaign you might want to set ground activity to low to save CPU for more planes.<br>
If you are flying a ground attack campaign, do the opposite - set air to low.<br>
In the end it is planes that take up the majority of CPU cycles with bombers being the worst offenders. Some savings can be had by reducing ground units, but a truck is not nearly as AI intensive as a plane.<br>
Translation Le premier choix du menu "configuration". <br> <br> [[File:aide_pwcg_config.PNG|300px]] <br> <br> La définition des allocations air, sol, AA et CPU à une faible valeur se traduit par la mission la plus légère possible en ressource système. <br> Cela limite les éléments de mission qui nécessitent beaucoup de puissance de processeur. <br> Le premier choix du menu "configuration".
La définition des allocations air, sol, AA et CPU à une faible valeur se traduit par la mission la plus légère possible en ressource système.
Cela limite les éléments de mission qui nécessitent beaucoup de puissance de processeur.