04-18-2024, 06:27 AM -
Follow~up: The situation from my previous post persists from the last time that I mentioned this back in August; as of March 026 of this year, I am now under the impression that the PPU~based Unmapped Memory crash that happens when everybody gets on the Green is because of how RPCS3 is now reading or decoding either the Costume Data or the Club Models, this only ever happens when using any of the regular gear that is available through general play (even the Present Uniforms that are enforced on Augusta National) and the crash amazingly will never occur when playing on Augusta National (1934) with the 1934 Clothing and Wooden Clubs.
Every other course, regardless of if it is On~Disc or DLC, will trigger this error once everybody ends up on the Green of any hole, there is an incredibly rare chance that you will be able to complete a hole without crashing but there is zero certainty that you will make it through a full round without it happening on the Green somewhere; we at least know that this issue started up on a build from no earlier than August 03 or 04 of 2023 during then~major updates to the PPU Decoder and wishfully with this information on hand we will finally figure out what is crashing the game as it switches over to when somebody goes up to putt.
An updated logue from Build 16347 of the Master Build is provided below, as well as footage from an earlier revision of Master from April 010, the test logue and footage were both done with the PPU Decoder on LLVM but the crash on the Green will also happen on Interpreter (Static) regardless of config; the same hardware combo as usual (Ryzen 5950X, 04x016 GB of DDR IV at 3200 (CL 016), and Radeon VII) is used here, now with a Matured Unit of the Ryzen 5950X following an RMA of my previous unit (my older 5950X was manufactured on Week 024 of 2021 and had a core on one of its CCDs die on December 028 of last year; the Matured Unit I got from the RMA was made during Week 046 of 2022 and began its use here on March 02), it's nice to get back to testing after this involuntary hiatus and this is a good way to return. (:
~ Tiger Woods PGA Tour '14 (MHE): RPCS3 Data Logue for Build 16347 (Mediafire)
~ Tiger Woods PGA Tour '14 (MHE): Crash on the Green Exhibition (No Crash on Augusta National (1934) ~ Hole 01 with Classic Gear)
~ Tiger Woods PGA Tour '14 (MHE): Crash on the Green Exhibition (Crash on Augusta National (1934) and Atlanta Athletic Club with Present Gear)
When replicating the crash, there are two possible Error Lines I have come across that you will get when it transitions to a player on the Green; they are listed below for reference, note that 0x00023614 is the more common of the errors and consistently showed beginning in the tests dating back to August.
~ F {PPU[0x100000e] Thread (threaded_main) [0x00023614]} VM: Access violation reading location 0x0 (unmapped memory)
~ F {PPU[0x100000e] Thread (threaded_main) [0x000d88fc]} VM: Access violation reading location 0x0 (unmapped memory)
Another detail to note when watching the footage: Sometime in the past few months, all builds and editions of PGA Tour '14 started to have this inexplicably big and bright yet translucent White Box when the Scorebug is not present in the Upper Left corner, I intentionally used Reshade in the test footage to make sure that it is viewable and even when running without it this will still happen, doesn't matter if you are running OpenGL or Vulkan; this particular graphical issue was not present back in August, but it is worth looking into since it doesn't happen on native hardware and wasn't ever apparent until at least late last year, very interesting how this title fluctuates with improvements and breaks but it's been a good analysis piece up to now.
Every other course, regardless of if it is On~Disc or DLC, will trigger this error once everybody ends up on the Green of any hole, there is an incredibly rare chance that you will be able to complete a hole without crashing but there is zero certainty that you will make it through a full round without it happening on the Green somewhere; we at least know that this issue started up on a build from no earlier than August 03 or 04 of 2023 during then~major updates to the PPU Decoder and wishfully with this information on hand we will finally figure out what is crashing the game as it switches over to when somebody goes up to putt.
An updated logue from Build 16347 of the Master Build is provided below, as well as footage from an earlier revision of Master from April 010, the test logue and footage were both done with the PPU Decoder on LLVM but the crash on the Green will also happen on Interpreter (Static) regardless of config; the same hardware combo as usual (Ryzen 5950X, 04x016 GB of DDR IV at 3200 (CL 016), and Radeon VII) is used here, now with a Matured Unit of the Ryzen 5950X following an RMA of my previous unit (my older 5950X was manufactured on Week 024 of 2021 and had a core on one of its CCDs die on December 028 of last year; the Matured Unit I got from the RMA was made during Week 046 of 2022 and began its use here on March 02), it's nice to get back to testing after this involuntary hiatus and this is a good way to return. (:
~ Tiger Woods PGA Tour '14 (MHE): RPCS3 Data Logue for Build 16347 (Mediafire)
~ Tiger Woods PGA Tour '14 (MHE): Crash on the Green Exhibition (No Crash on Augusta National (1934) ~ Hole 01 with Classic Gear)
~ Tiger Woods PGA Tour '14 (MHE): Crash on the Green Exhibition (Crash on Augusta National (1934) and Atlanta Athletic Club with Present Gear)
When replicating the crash, there are two possible Error Lines I have come across that you will get when it transitions to a player on the Green; they are listed below for reference, note that 0x00023614 is the more common of the errors and consistently showed beginning in the tests dating back to August.
~ F {PPU[0x100000e] Thread (threaded_main) [0x00023614]} VM: Access violation reading location 0x0 (unmapped memory)
~ F {PPU[0x100000e] Thread (threaded_main) [0x000d88fc]} VM: Access violation reading location 0x0 (unmapped memory)
Another detail to note when watching the footage: Sometime in the past few months, all builds and editions of PGA Tour '14 started to have this inexplicably big and bright yet translucent White Box when the Scorebug is not present in the Upper Left corner, I intentionally used Reshade in the test footage to make sure that it is viewable and even when running without it this will still happen, doesn't matter if you are running OpenGL or Vulkan; this particular graphical issue was not present back in August, but it is worth looking into since it doesn't happen on native hardware and wasn't ever apparent until at least late last year, very interesting how this title fluctuates with improvements and breaks but it's been a good analysis piece up to now.