# Initialize memory (rev:3.63, ctm:196Mhz, cpuclk:147Mhz detected) INFO: GL_ARB_get_texture_sub_image is available
INFO: GL_ARB_texture_barrier is available INFO: GL_ARB_shader_image_load_store is available INFO: GL_ARB_draw_buffers_blend is available INFO: GL_EXT_texture_filter_anisotropic is available IsoFile open ok: C:\Users\Bazooka\Desktop\Raw Danger\rd typeA.iso Patches: No CRC found, using 00000000 instead. (GameDB) 9708 games on record (loaded in 138ms) AVXīinding GS: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\GSdx32-AVX.dllīinding PAD: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\LilyPad.dllīinding SPU2: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\Spu2-X.dllīinding CDVD: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\cdvdGigaherz.dllīinding USB: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\USBnull.dllīinding FW: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\FWnull.dllīinding DEV9: C:\Users\Bazooka\Downloads\pcsx2-v1.5.-g42b5161-windows-x86\plugins\DEV9null.dll Vendor/Model = GenuineIntel (stepping 07)ĬPU speed = 3.299 ghz (4 logical threads)
Operating System = Microsoft Windows 7 Service Pack 1 (build 7601), 64-bitĬPU name = Intel(R) Core(TM) i5-2500K CPU 3.30GHz
I was looking for any advice to see if it would be possible to avoid such a crash on PCSX2 so that I can study these lines. Just activating this feature seems to lower the in-game FPS to 15 while maintaining game speed, so I think it might be a viable hypothesis. My working hypothesis is that these markers aren't culled behind walls at all, so if you activate them while looking at the corner of the area you should be fine, but otherwise it will cause a crash because you're looking at too many of them. I've been trying to document and explain these markings but having too many of them visible seems to crash the game. Not in an illegal sort of way, but a memory poking sort of way that causes a crash that wouldn't happen otherwise.īasically, for the first demo build of Raw Danger I had found an integer which could be changed to 1, which would activate all sorts of unexplained debug markings, example shown here: So, disclaimer above all disclaimers: what I'm trying to do here isn't exactly legitimate.
0 kommentar(er)
