Dolphin Progress Report: December 2019 and January 2020
dolphin-emu.org
dolphin-emu.org
The binary compatibility has documented limitations. As https://docs.microsoft.com/en-us/cpp/porting/binary-compat-2... explains, "The Redistributable your app uses has a similar binary-compatibility restriction. When you mix binaries built by different supported versions of the toolset, the Redistributable version must be at least as new as the latest toolset used by any app component." This allowed us to add VCRUNTIME140_1.dll as part of the "FrameHandler4" work that the compiler back-end team did. This decreases the size of exception handling info on x64 for compiled programs, sometimes significantly.
(I work on the Visual C++ team, on the STL. We regularly build Dolphin with our development toolset to prevent shipping compiler/library regressions, and to provide advance notice of source-breaking changes. I've had to report a couple of breaking changes to Dolphin and have been astounded at their prompt fixes - they are a wonderful team!)
Can't find more about this by Googling around... anyone knows what the crude message was and where it was hidden?
[0] https://tcrf.net/Meet_the_Robinsons_(GameCube)#Dev_Message
Previously they've had to deal with a piece of code that is designed only to work with the gamecube's L2 cache, and crashes emulators that don't emulate the cache layers close enough. Which emulators rarely do as it's prohibitively expensive; you're looking at somewhere between an order of magnitude and two lower perf. This code doesn't do anything in the good case, and doesn't have any reason to exist except to be an anti-emulation check.
Do you mean on nightly?
If you visited the url, it was just a hit counter. I found out about it on Sony's PS2 registered developer forum. Someone had put the disc through the PS2 "Performance Analyzer"[1] and had a peek at the VRAM. When I hit it site it was in the low hundreds. A few months later it was in the low thousands. A few months after that it was gone. konami.co.jp apparently isn't even a thing anymore.
[1]http://lukasz.dk/mirror/research-scea/research/pdfs/GDC2003_...
Is it because of some patents? Anyone knows?
One could reasonably assume that the sponsor of the work would have access to the patent on very favorable terms. Some details at [1].
[1] https://twitter.com/trav_downs/status/1202863930210734080
We have this problem with CPU manufacturers stating that something is supported, when it is instead emulated (hello checks on CPUID). Disk drives acknowledge writes before they actually write the data to the disk (hello layers of unreliable fsyncs). Network cards claim that packet have been shipped while they never left the circular buffer (hello bufferbloat).
Please HW manufacturers, stop lying to us.
Thanks for all the enjoyable reads!
I honestly thought every game would just be playable directly from a disc, but I guess this one was too large for a single disc.