Should this really be considered "intro" since it's removing handling of trap exceptions, which point to errors long before the game does anything else?
Specs: i7 5820K @ 4.4ghz | R9 Fury Tri - X | 16GB DDR4 2400mhz | Win 10 Pro
(03-31-2017, 06:19 AM)Nobbs66 Wrote: Should this really be considered "intro" since it's removing handling of trap exceptions, which point to errors long before the game does anything else?
Is there some sort of database on what all the errors (access violation reading XXXXXXX, invalid RSX method, etc.) mean?
(03-31-2017, 06:19 AM)Nobbs66 Wrote: Should this really be considered "intro" since it's removing handling of trap exceptions, which point to errors long before the game does anything else?
Is there some sort of database on what all the errors (access violation reading XXXXXXX, invalid RSX method, etc.) mean?
Er. It kinda already says what it means (I'd say that's the whole point of the log). You just need to know what an RSX method is for example.
E {SPU[0x2000004] Thread (highCellSpursKernel4)} SPU: [0x00a80] Function call without $LR
E {SPU[0x2000004] Thread (highCellSpursKernel4)} SPU: [0x00acc] Function call without $LR
E {PPU[0x1000005] Thread (fios mediathread 2) [0x0152eea8]} Stat: 'sys_fs_stat' failed with 0x80010006 : CELL_ENOENT [x14]