Hey devs something is very strange with performance please take a look at this

Página na loja

Dead Rising 3

Tudo Discussões Capturas de tela Artes Transmissões Vídeos Notícias Guias Análises

Dead Rising 3 > Discussões gerais > Detalhes do tópico

The doctor is in possui Dead Rising 3

6/set./2014 às 5:15

Hey devs something is very strange with performance please take a look at this

ok so ive been getting horrible framerate

y cpu/gpu are poorly utilized over 50% idle!

so took some interesting screenshots using msi afterburner 4.0.0

http://imgur.com/rsEFbZE.jpg
http://imgur.com/WW5WKjs.jpg
http://imgur.com/wNSFSJ7.jpg
http://imgur.com/RpcaDjq.jpg

the screenshots show

my gpu is never above 50%

and my cpu cores are never above 50%

and im getting horrible framerate

and im not going to disk

and im not running something else

so what is holding back my framerate?

that is interesting question...

if u want i can run it in amd cpu/gpu profiler and see what is going on inside

to me it looks like it threads stalling on themselves waiting for something

just so that you know

every setting that could be turned off is turned off

every setting that could be lowered is lowered to lowest value

including resolution, i mean everything!

and im running on

amd 1090t
ati 6870 1gb
16gb 1033 ddr3
128gb sata 3 ssd (system and game)
2tb 7200 rpm sata 3 (programs)
2tb 7200 rpm sata 3 (workspace)
windows 8.1 64-bit

Última edição por The doctor is in; 6/set./2014 às 5:19

< >

Exibindo comentários 1–14 de 14

The doctor is in possui Dead Rising 3

6/set./2014 às 6:25

ok i did some more testing and most of the time the cpu is doing

0 atidxx64.dll!AmdDxGsaFreeCompiledShader+0x4af9bd
1 atidxx64.dll!AmdDxGsaFreeCompiledShader+0x4afb28
2 atidxx64.dll!AmdDxGsaFreeCompiledShader+0x4c38e2
3 atidxx64.dll!XdxInitXopAdapterServices+0x1f344
4 atidxx64.dll!XdxInitXopAdapterServices+0x45dcf
5 atidxx64.dll!AmdDxExtCreate+0x63ef
6 atidxx64.dll!AmdDxExtCreate+0x6596
7 KERNEL32.DLL!BaseThreadInitThunk+0xd
8 ntdll.dll!RtlUserThreadStart+0x1d

why is game constantly doing the above in one of its thread? why is it spending most of its time doing this... couldnt it just cache it instead of constantly be creating it...

of the game 30% of my cpu usage about 50% of it was jut that thread doing the above

my gpu was also equally underutilized waiting i would guess on the above

of the long list of thread most are just waiting on object

0 ntdll.dll!ZwWaitForMultipleObjects+0xa
1 KERNELBASE.dll!WaitForMultipleObjectsEx+0xed
2 deadrising3.exe+0xe14fd9
3 KERNEL32.DLL!BaseThreadInitThunk+0xd
4 ntdll.dll!RtlUserThreadStart+0x1d

most of the time the game is waiting so cpu/gpu is not utilized much and what is is mostly free compiled shader

Última edição por The doctor is in; 6/set./2014 às 6:29

The doctor is in possui Dead Rising 3

6/set./2014 às 6:32

did some more playing around this time with process monitor and this is what i see its constantly just doing this

9:31:21.0508804 AM deadrising3.exe 2416 RegOpenKey HKLM\System\CurrentControlSet\Control\DeviceClasses\{ec87f1e3-c13b-4100-b5f7-8b84d54260cb} NAME NOT FOUND Desired Access: All Access

i mean honestly shy keep hitting the registry... read it and cache it

here is stack trace for it...

0 ntoskrnl.exe NtWaitForSingleObject + 0x7a6 0xfffff803509def46 C:\WINDOWS\system32\ntoskrnl.exe
1 ntoskrnl.exe SeOpenObjectAuditAlarmWithTransaction + 0x3832 0xfffff803509edb42 C:\WINDOWS\system32\ntoskrnl.exe
2 ntoskrnl.exe NtQueryInformationFile + 0x1218 0xfffff803509dd478 C:\WINDOWS\system32\ntoskrnl.exe
3 ntoskrnl.exe ObOpenObjectByName + 0x1e3 0xfffff803509dadd3 C:\WINDOWS\system32\ntoskrnl.exe
4 ntoskrnl.exe PsLookupProcessThreadByCid + 0x940 0xfffff80350a282b4 C:\WINDOWS\system32\ntoskrnl.exe
5 ntoskrnl.exe PsLookupProcessThreadByCid + 0x676 0xfffff80350a27fea C:\WINDOWS\system32\ntoskrnl.exe
6 ntoskrnl.exe setjmpex + 0x34b3 0xfffff803507604b3 C:\WINDOWS\system32\ntoskrnl.exe
7 ntoskrnl.exe KeSynchronizeExecution + 0x3010 0xfffff80350758900 C:\WINDOWS\system32\ntoskrnl.exe
8 ntoskrnl.exe RtlVolumeDeviceToDosName + 0x17db 0xfffff803509b80ff C:\WINDOWS\system32\ntoskrnl.exe
9 ntoskrnl.exe RtlVolumeDeviceToDosName + 0x1726 0xfffff803509b804a C:\WINDOWS\system32\ntoskrnl.exe
10 ntoskrnl.exe FsRtlAllocateExtraCreateParameter + 0x4fd3 0xfffff8035099b503 C:\WINDOWS\system32\ntoskrnl.exe
11 ntoskrnl.exe FsRtlAllocateExtraCreateParameter + 0x4e5d 0xfffff8035099b38d C:\WINDOWS\system32\ntoskrnl.exe
12 ntoskrnl.exe FsRtlAllocateExtraCreateParameter + 0x38f2 0xfffff80350999e22 C:\WINDOWS\system32\ntoskrnl.exe
13 ntoskrnl.exe FsRtlAllocateExtraCreateParameter + 0x1b8f 0xfffff803509980bf C:\WINDOWS\system32\ntoskrnl.exe
14 ntoskrnl.exe RtlEqualUnicodeString + 0xa79 0xfffff80350995241 C:\WINDOWS\system32\ntoskrnl.exe
15 ntoskrnl.exe SeQuerySessionIdToken + 0xd63 0xfffff803509a0a6f C:\WINDOWS\system32\ntoskrnl.exe
16 ntoskrnl.exe SeQuerySessionIdToken + 0xd05 0xfffff803509a0a11 C:\WINDOWS\system32\ntoskrnl.exe
17 ntoskrnl.exe ObReferenceObjectByHandleWithTag + 0x994 0xfffff803509e0374 C:\WINDOWS\system32\ntoskrnl.exe
18 ntoskrnl.exe NtDeviceIoControlFile + 0x56 0xfffff803509e1146 C:\WINDOWS\system32\ntoskrnl.exe
19 ntoskrnl.exe setjmpex + 0x34b3 0xfffff803507604b3 C:\WINDOWS\system32\ntoskrnl.exe
20 ntdll.dll NtDeviceIoControlFile + 0xa 0x7ffb3d0ead7a C:\WINDOWS\SYSTEM32\ntdll.dll
21 KERNELBASE.dll DeviceIoControl + 0x73 0x7ffb3a6736e3 C:\WINDOWS\system32\KERNELBASE.dll
22 KERNEL32.DLL DeviceIoControl + 0x80 0x7ffb3cf12470 C:\WINDOWS\system32\KERNEL32.DLL
23 CFGMGR32.dll CM_Get_Device_Interface_ListW + 0x11f 0x7ffb3a78f8df C:\WINDOWS\system32\CFGMGR32.dll
24 CFGMGR32.dll CM_Get_Device_Interface_ListW + 0x3a 0x7ffb3a78f7fa C:\WINDOWS\system32\CFGMGR32.dll
25 CFGMGR32.dll CM_Get_Device_Interface_List_ExW + 0x63 0x7ffb3a78fa43 C:\WINDOWS\system32\CFGMGR32.dll
26 DEVOBJ.dll DevObjGetClassDevs + 0x2ae 0x7ffb39221f9e C:\WINDOWS\SYSTEM32\DEVOBJ.dll
27 SETUPAPI.dll SetupDiGetClassDevsExW + 0x11e 0x7ffb3c9f58f2 C:\WINDOWS\system32\SETUPAPI.dll
28 SETUPAPI.dll SetupDiGetClassDevsW + 0x67 0x7ffb3c9f59c7 C:\WINDOWS\system32\SETUPAPI.dll
29 XINPUT1_3.dll XInputGetKeystroke + 0x4b6a 0x2e899a C:\WINDOWS\SYSTEM32\XINPUT1_3.dll
30 XINPUT1_3.dll XInputGetKeystroke + 0x28ec 0x2e671c C:\WINDOWS\SYSTEM32\XINPUT1_3.dll
31 XINPUT1_3.dll XInputGetKeystroke + 0x2f0f 0x2e6d3f C:\WINDOWS\SYSTEM32\XINPUT1_3.dll
32 XINPUT1_3.dll XInputGetKeystroke + 0x3168 0x2e6f98 C:\WINDOWS\SYSTEM32\XINPUT1_3.dll
33 XINPUT1_3.dll XInputGetKeystroke + 0x870 0x2e46a0 C:\WINDOWS\SYSTEM32\XINPUT1_3.dll
34 XINPUT1_3.dll XInputGetCapabilities + 0x1a4 0x2e3104 C:\WINDOWS\SYSTEM32\XINPUT1_3.dll
35 gameoverlayrenderer64.dll ValveHookScreenshots + 0x3333 0x7ffb2d241023 P:\Program Files (x86)\Steam\gameoverlayrenderer64.dll
36 deadrising3.exe deadrising3.exe + 0xd0b301 0x7ff653f5b301 P:\Program Files (x86)\Steam\steamapps\common\deadrising3\deadrising3.exe
37 deadrising3.exe deadrising3.exe + 0xcfdba5 0x7ff653f4dba5 P:\Program Files (x86)\Steam\steamapps\common\deadrising3\deadrising3.exe
38 KERNEL32.DLL BaseThreadInitThunk + 0xd 0x7ffb3cf116ad C:\WINDOWS\system32\KERNEL32.DLL
39 ntdll.dll RtlUserThreadStart + 0x1d 0x7ffb3d0c34a5 C:\WINDOWS\SYSTEM32\ntdll.dll

as u can see all those request mostly doing NtWaitForSingleObject cause its waste of time to keep reading registry...

Última edição por The doctor is in; 6/set./2014 às 6:34

You Kissed a Boy and Liked It 6/set./2014 às 6:34

I'm getting similar issue with my 7970 -- sluggish performance and underutilised hardware. I haven't tested it by the numbers, however...

What program are you using to assay the fps and processor usage?

Última edição por You Kissed a Boy and Liked It; 6/set./2014 às 6:35

KrautwagenTDI possui Dead Rising 3

6/set./2014 às 6:35

how did you get all of the data like that up in the corner. becuse i cant figure it out on the new msi afterburner 3.0

The doctor is in possui Dead Rising 3

6/set./2014 às 6:43

above i use process explorer and process monitor by microsoft

but i also have an array of developer tools including amd cpu/gpu profiler whick i will play with next...

the thing is most of the time the game is not running its just waiting... perhaps it they could cache some of the above values the framerate would increase bigtime since over 50% of the time the game waiting on nothing...

so someone who has access to source code who knows how to use profilers should run it for a little while and capture some stuff and resolve it.

ive also been using the latest msi afterburner 4.0.0 beta it collects a lot more info
http://www.guru3d.com/files-details/msi-afterburner-beta-download.html

i mean if i didnt have to call AmdDxExtCreate and i could cache it i would same for registory if i dont have to keep reading a value in the registry i dont , and i cant think of many values in registry that u have to keep reading.. most u can read and cache...

calls like that are very expensive and showever makes them and who ever is dependent on them are going to stall and it looks like that is what the game is doing one giant stall 50% of the time...

so u get horrible utilization of cpu/gpu and u really have to throw hardware at it to make a dent...

not caching values that could easily bre cached but are very expensive to get is sort of common mistake programmers make

Última edição por The doctor is in; 6/set./2014 às 6:50

Lt.Marlow

6/set./2014 às 6:49

With any luck this poor utilization at the moment could mean big performance gains after a patch and set of drivers are released.

The doctor is in possui Dead Rising 3

6/set./2014 às 6:51

the thing is for someone to fix they would have to take a look, run it with tools to see what is going on like profiler... im not sure this is something they are going to do. they didnt do it for xbox since i would subspect its the same code... im hoping they see the thread and it sort of helps them to see they should take a look hopefully with profiler...

fyrepony

6/set./2014 às 6:56

cap-♥♥♥♥ released this way it is, they have no intention to fix it, so im not gonna get another product from them again.

SiNiSTAR

6/set./2014 às 7:00

Same issues and I'm using a 6970. Changing from high to the lowest options possible doesn't change anything at all and my gpu is not fully used.

Escrito originalmente por Lt.Marlow:
With any luck this poor utilization at the moment could mean big performance gains after a patch and set of drivers are released.

I tought the same thing, let's hope it won't take too long for a patch and new drivers.
Also, I saw some small fps improvement from using catalyst 14.4 instead of 14.8 beta.

You Kissed a Boy and Liked It 6/set./2014 às 7:00

I just download MSI Afterburner and checked mine. I drove through oodles of deadites and the game runs so-so, but the GPU usage gets no higher than 33%.

I also noticed about half of the 8 CPU cores are idle or near idle...

EDIT:
I used Fraps to check the fps -- 15-32fps! lol... Crapclown >_>

Última edição por You Kissed a Boy and Liked It; 6/set./2014 às 7:15

#10

The doctor is in possui Dead Rising 3

6/set./2014 às 12:42

on my 1090t it using all 6 cores which makes sense since it creates a bunch of threads and the unless asked to run it on specific core os schedules them on one of the cores that has least utilization

Última edição por The doctor is in; 6/set./2014 às 12:43

#11

null

6/set./2014 às 19:40

this needs to be bumped, devs need to see this. Good work sir, though what an awful shame that a consumer has to find the source of your huge mistakes capcom.

#12