0 of 0
About this mod
My app is designed for calculating and optimizing builds to achieve a specific 3D Mark score. Currently, it supports single, dual and quad GPU builds!
- Permissions and credits
- Changelogs
My app is designed for calculating and optimizing builds to achieve a specific 3D Mark score. Currently, it supports single, dual and quad GPU builds!!
-Please note that it is in a very early stage of development, and I am working on it alone in my spare time.
How it works:
-The app calculates the best CPU/GPU combo to reach the target 3D Mark score.It currently supports single and dual GPU builds.
-It's an .exe file that comes with some .csv files.
-When you open the app, simply input your target score and click "CALCULATE."
-The app will display the five best builds for your score. I've included some builds that are slightly below the target score to allow for potential overclocking experimentation, but it also shows better-performing builds.
What to know before using it:
-The app doesn't account for RAM speeds and occupied slots. This means that if you use RAM with lower speeds than in the calculated build, your score may be lower than expected. Please aim for the best RAM configuration to achieve your desired goal. In the future, I intend to explore this issue, but it's quite challenging.
-In the Dual GPU build option, the app won't suggest configurations that are not compatible with dual GPU(like the skylake socket).
-The choice of the motherboard is up to you, assuming that you are capable of selecting the right one, considering factors like SLI, Crossfire, socket compatibility, etc.
-Calculations may take a few seconds to complete, and the program may appear unresponsive during this time.
-I won't be addressing overclocking in this app. All scores are based on stock CPU and GPU speeds.
Future plans:
-Adding support for 4 GPU builds. DONE
-Implementing a cost-effective system (the app will calculate the best builds while considering their cost).
-Finding a solution to account for different RAM speeds when calculating CPU scores (the app will suggest the best RAM to achieve optimal results, or a more budget-friendly RAM if it's a viable solution).
If you have any suggestions for additions or fixes, please feel free to let me know. :)
-Please note that it is in a very early stage of development, and I am working on it alone in my spare time.
How it works:
-The app calculates the best CPU/GPU combo to reach the target 3D Mark score.It currently supports single and dual GPU builds.
-It's an .exe file that comes with some .csv files.
-When you open the app, simply input your target score and click "CALCULATE."
-The app will display the five best builds for your score. I've included some builds that are slightly below the target score to allow for potential overclocking experimentation, but it also shows better-performing builds.
What to know before using it:
-The app doesn't account for RAM speeds and occupied slots. This means that if you use RAM with lower speeds than in the calculated build, your score may be lower than expected. Please aim for the best RAM configuration to achieve your desired goal. In the future, I intend to explore this issue, but it's quite challenging.
-In the Dual GPU build option, the app won't suggest configurations that are not compatible with dual GPU(like the skylake socket).
-The choice of the motherboard is up to you, assuming that you are capable of selecting the right one, considering factors like SLI, Crossfire, socket compatibility, etc.
-Calculations may take a few seconds to complete, and the program may appear unresponsive during this time.
-I won't be addressing overclocking in this app. All scores are based on stock CPU and GPU speeds.
Future plans:
-Adding support for 4 GPU builds. DONE
-Implementing a cost-effective system (the app will calculate the best builds while considering their cost).
-Finding a solution to account for different RAM speeds when calculating CPU scores (the app will suggest the best RAM to achieve optimal results, or a more budget-friendly RAM if it's a viable solution).
If you have any suggestions for additions or fixes, please feel free to let me know. :)