Search
Results (3)
- Emulator Issues #13516 (New): Unhandled excep ... ormatted timestamp on savestate file scanning
- **What's the problem? Describe what went wr ... e), then it's anyone's guess what's going to trigger it again. Even the quit dialog after pressin ... er<char,500,std::allocator<char>>>,char,std::chrono::duration<__int64,std::ratio<1,1>>>::format_ ... er<char,500,std::allocator<char>>>,char,std::chrono::duration<__int64,std::ratio<1,1>>>::on_loc_ ... C++ DolphinD.exe!fmt::v10::detail::parse_chrono_format<char,fmt::v10::detail::tm_writer<std: ... er<char,500,std::allocator<char>>>,char,std::chrono::duration<__int64,std::ratio<1,1>>> &>(const ... er<char,500,std::allocator<char>>>,char,std::chrono::duration<__int64,std::ratio<1,1>>> & handle ... format_context<fmt::v10::appender,char>,std::chrono::duration<__int64,std::ratio<1,1>>>(const tm ... t<fmt::v10::appender,char> & ctx, const std::...
- Emulator Issues #13491 (New): Game Randomly C ... MG1 or SMG2 as a custom level using romhacks)
- **Game Name?** Super Mario Galaxy, Super M ... _1::unique_lock<std::__1::mutex>&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 100 ... _1::unique_lock<std::__1::mutex>&, std::__1::chrono::time_point<std::__1::chrono::system_clock, std::__1::chrono::duration<long long, std::__1::ratio<1l, 100 ... long, std::__1::ratio<1l, 1000l>>(std::__1::chrono::duration<long long, std::__1::ratio<1l, 100 ... _1::unique_lock<std::__1::mutex>&, std::__1::chrono::duration<long long, std::__1::ratio<1l, 100 ... long, std::__1::ratio<1l, 1000l>>(std::__1::chrono::duration<long long, std::__1::ratio<1l, 100 ... c std::__1::this_thread::sleep_for(std::__1::chrono...
- Emulator Issues #12898 (Questionable): Dolphi ... i remotes do not respond to pointing controls
- **Game Name?** WarioWare: Smooth Moves -> ... efiles, savestates)** [Anything else here]