3Dm11 Low combined score fix ?
Benchmark/ OC d. 23. april. 2012, skrevet af Gripen90
Vist: 4855 gange.
Gripen90
#0
Er der nogen der ved om der er kommet en "work-around" eller speciel indstilling til 3dmark11 så man kan komme ud over den den low combined score bug der er til nogle SLi setups ?
Mine scores er ok iflg "target results" for de andre del-scores.
http://3dmark.com/healthcheck/...
Min combined score ved at gå fra Forceware 280,26 til 296,10 gav ca. 300point, men når lige at ligge under 6000point alligevel i combined.
Gammel score http://3dmark.com/3dm11/325305...
Ny score http://3dmark.com/3dm11/325305...
Jeg har den seneste 3dm11 patch inde.
Hvis noget kender "fixet" vil det være lækkert 😛
Tråden blev redigeret 1 gang, sidst af Gripen90 d. 23-04-2012 17:22:13.
Mine scores er ok iflg "target results" for de andre del-scores.
http://3dmark.com/healthcheck/...
Min combined score ved at gå fra Forceware 280,26 til 296,10 gav ca. 300point, men når lige at ligge under 6000point alligevel i combined.
Gammel score http://3dmark.com/3dm11/325305...
Ny score http://3dmark.com/3dm11/325305...
Jeg har den seneste 3dm11 patch inde.
Hvis noget kender "fixet" vil det være lækkert 😛
Tråden blev redigeret 1 gang, sidst af Gripen90 d. 23-04-2012 17:22:13.
det bare en ny standart så vi køber nyt udstyr :-p
#2
#0 Meget mærkeligt:S
Den gang jeg havde 2 stk GTX 580 + 920 lavet mine ca 8900.
http://3dmark.com/3dm11/165587...
Nu ved jeg ikke om din CPU var bedre end end 920, men min for en del bedre CPU score, tror vidst det er din CPU der halter.
Svaret blev redigeret 2 gange, sidst af NicklasAPJ d. 23-04-2012 19:15:42.
Den gang jeg havde 2 stk GTX 580 + 920 lavet mine ca 8900.
http://3dmark.com/3dm11/165587...
Nu ved jeg ikke om din CPU var bedre end end 920, men min for en del bedre CPU score, tror vidst det er din CPU der halter.
Svaret blev redigeret 2 gange, sidst af NicklasAPJ d. 23-04-2012 19:15:42.
nej det virker jo lige så godt som den gang han fik en større score 😀 det fordi de sætter kravne op på deres 3Dmark ..
Jeg ved ikke om det har interresse, men mit system yden 10558 point med 1 stk 680GTX i 5.0GHz 2600k
#4 det jo også det jeg mener du har det nyeste udstyr derfor score du mere nu 🙂 det derfor de laver patch hehe
#6
din CPU kan ikke levere nok power til dine 3 kort
men ud over det er din graphics score da ok at stock at være
men ud over det er din graphics score da ok at stock at være
#7
Det skyldes ikke den brugte CPU for andre systemer med selv Core i7 980x CPU'er oplever det samme.
Problemet er mest gældende ved mere end 2 grafikkort:
Iflg Futuremark.
This is a known issue.
Either disable the dedicated PhysX card or disable "legacy nvidia multi gpu detection" using SystemInfo diagnostic tool (details about the tool here:
http://www.yougamers.com/forum... - ignore the rest, just run the diag tool and change the config by unticking the bottom left box (legacy nvidia multi gpu) and apply that)
The issue is that...
- The "official new way of detecting SLI setups" fails on far too many SLI systems. Original SystemInfo that shipped with 3DMark 11 does it like this and SLI configurations just hung before Test 6. So we had to revert it back to the "legacy" method.
- The "legacy way of detecting SLI setups" works, but it can't tell normal SLI from SLI that is in Single GPU mode (from NVIDIA control panel) or Multi-GPU config that has dedicated PhysX card.
- Test 6 (combined) load changes with the number of GPUs. In order to properly render the scene with multi-GPU, each GPU must have a copy of the GPU physics simulation running on it (using Bullet/DirectCompute) - otherwise the physics code would have to shuffle data between GPUs and that would slow things down horribly. Hence the benchmark needs to know how many GPUs you have.
- If Test 6 gets wrong number of GPUs (in your case, I guess it gets "3"), the number of DirectCompute simulations running is larger than the number of GPUs actually rendering the scene, causing notable performance loss.
The situation is not ideal, but luckily scenarios where multiple NVIDIA GPUs are present without all being part of a SLI config (2x/3x/4x SLI) are very very rare and there is a workaround. Hopefully one day NVIDIA SLI detection API (the new method) starts to work reliably so SystemInfo can switch to it and it can then detect also a config like this and figure out the number of GPUs that are going to be actively rendering the scene.
Jeg oplever det samme, at sidste test "hænger" ved loadscreen i ca 2min. og så går testen i gang. Dvs et eller andet med genkendelse af GFX'ne fejler.
Problemet er mest gældende ved mere end 2 grafikkort:
Iflg Futuremark.
This is a known issue.
Either disable the dedicated PhysX card or disable "legacy nvidia multi gpu detection" using SystemInfo diagnostic tool (details about the tool here:
http://www.yougamers.com/forum... - ignore the rest, just run the diag tool and change the config by unticking the bottom left box (legacy nvidia multi gpu) and apply that)
The issue is that...
- The "official new way of detecting SLI setups" fails on far too many SLI systems. Original SystemInfo that shipped with 3DMark 11 does it like this and SLI configurations just hung before Test 6. So we had to revert it back to the "legacy" method.
- The "legacy way of detecting SLI setups" works, but it can't tell normal SLI from SLI that is in Single GPU mode (from NVIDIA control panel) or Multi-GPU config that has dedicated PhysX card.
- Test 6 (combined) load changes with the number of GPUs. In order to properly render the scene with multi-GPU, each GPU must have a copy of the GPU physics simulation running on it (using Bullet/DirectCompute) - otherwise the physics code would have to shuffle data between GPUs and that would slow things down horribly. Hence the benchmark needs to know how many GPUs you have.
- If Test 6 gets wrong number of GPUs (in your case, I guess it gets "3"), the number of DirectCompute simulations running is larger than the number of GPUs actually rendering the scene, causing notable performance loss.
The situation is not ideal, but luckily scenarios where multiple NVIDIA GPUs are present without all being part of a SLI config (2x/3x/4x SLI) are very very rare and there is a workaround. Hopefully one day NVIDIA SLI detection API (the new method) starts to work reliably so SystemInfo can switch to it and it can then detect also a config like this and figure out the number of GPUs that are going to be actively rendering the scene.
Jeg oplever det samme, at sidste test "hænger" ved loadscreen i ca 2min. og så går testen i gang. Dvs et eller andet med genkendelse af GFX'ne fejler.
#8
Men kan så ikke få deres "fix" til at ændre på noget 😕
#10
Kan så fortælle efter platform skifte at der er rigelig CPU power til kortene, men for PC'er med 3+ GPU'er så er der stadig intet fix fra futuremark ej hellere med seneste sysinfo update. Der er så få med 3gfx så et fix er ikke på top prioriteten. Man kan forbedre scoren ved OC, men med rette support vil scoren være bedre selv OCet eller ej.