| Age | Commit message (Collapse) | Author |
|---|
|
Logo refresh for android, windows, and linux
|
|
Android: Adopt a new versionCode scheme
|
|
LillyJadeKatrin/retroachievements-challenge-popups
Add Messages for Challenges
|
|
|
|
Starting or ending a challenge now displays a popup naming and describing the challenge along with the active icon.
|
|
ScmRevGen: Set commits ahead to zero when on a tag
|
|
IOS/USB: Use Enum for Infinity Base Positions
|
|
Core/PatchEngine: Remove remnants of Speedhack system
|
|
|
|
|
|
LillyJadeKatrin/retroachievements-visual-improvements
RetroAchievements - Dialog Visual Improvements
|
|
|
|
|
|
|
|
|
|
All usages of this have been removed many years ago in cbe9c3e040a466bba410f025e026ed84f3f8b1c0
|
|
Fix warning on Android builder by returning bool instead of const bool.
|
|
|
|
Update Achievement List when Rich Presence Updates
|
|
|
|
|
|
This reverts commit 72cf2bdb87f09deff22e1085de3290126aa4ad05.
SYSCONF settings are getting cleared when they shouldn't be. Let's
revert the change until I get proper time to figure out why it's broken.
|
|
Whenever a request to update the Rich Presence comes in, typically every ten seconds, the Achievement Progress Widget will update the sort order of the achievements and all of their measured values.
|
|
|
|
|
|
|
|
LillyJadeKatrin/retroachievements-hardcore-state-changed
Decouple Hardcore from EmulationStateChanged
|
|
LillyJadeKatrin/retroachievements-start-session-bug
Add MemoryVerifier to AchievementManager Startup
|
|
dreamsyntax/advanced-cpu-clock-override-step-adjustment
DolphinQt: Adjust CPU Clock Override slider
|
|
DolphinQt: fix some warnings
|
|
Trim extra characters from measured progress
|
|
Fix cut off text in Achievements dialog
|
|
The measured_progress C string for achievements to display potentially contains junk data after the null terminator, which was rendering in the QString in the dialog. This trims those junk characters.
|
|
This causes Dual Core to lock up during the boot sequence, because it tries to wait for a not-yet-running GPU thread.
Fixes https://bugs.dolphin-emu.org/issues/13559
|
|
|
|
|
|
Also clean up signals a bit.
|
|
Clean up Core::GetState
|
|
IOS/USB Add 2 more Spaces for Disney Infinity figures
|
|
Vulkan: Update Vulkan headers, VulkanMemoryAllocator
|
|
rc_client calls the provided memory peeker asynchronously in the callback for starting a session, to validate/invalidate the memory used for achievements. Dolphin cannot access memory from any thread but host or CPU so this access has a small chance of being invalid. This commit adds a MemoryVerifier that the AchievementManager will use to perform this, before changing the peek method back to the original MemoryPeeker for normal operation.
|
|
|
|
|
|
Some pieces of code are calling IsRunning because there's some
particular action that only makes sense when emulation is running, for
instance showing the state of the emulated CPU. IsRunning is appropriate
to use for this. Then there are pieces of code that are calling
IsRunning because there's some particular thing they must avoid doing
e.g. when the CPU thread is running or IOS is running. IsRunning isn't
quite appropriate for this. Such code should also be checking for the
states Starting and Stopping. Keep in mind that:
* When the state is Starting, the state can asynchronously change to
Running at any time.
* When we try to stop the core, the state gets set to Stopping before we
take any action to actually stop things.
This commit adds a new method Core::IsUninitialized, and changes all
callers of IsRunning and GetState that look to me like they should be
changed.
|
|
Core::GetState reads from four different pieces of state: s_is_stopping,
s_hardware_initialized, s_is_booting, and CPUManager::IsStepping.
I'm keeping that last one as is for now because there's code in Dolphin
that sets it directly, but we can unify the other three to make things
easier to reason about.
This commit also gets rid of s_is_started. This was previously used in
Core::IsRunningAndStarted to ensure true wouldn't be returned until the
CPU thread was started, but it wasn't used in Core::GetState, so
Core::GetState would happily return State::Running after we had
initialized the hardware but before we had initialized the CPU thread.
As far as I know, there are no callers that have any real need to know
whether the boot process is currently initializing the hardware or the
CPU thread. Perhaps once upon a time there was a desire to make the
apploader debuggable, but a long time has passed without anyone stepping
up to implement it, and the way CBoot::RunApploader is implemented makes
it rather difficult. So this commit makes all the functions in Core.cpp
consider the core to still be starting until the CPU thread is started.
|
|
AudioCommon: release mutex explicitly to avoid -Wunused-result warning
|
|
CMake dependency fixes
|
|
This field was completely hiding the progress bar in dark mode without this.
|
|
When AchievementProgress::UpdateData(false) is called, it will now empty itself and reinsert all existing boxes, re-sorted into their current buckets, and call UpdateProgress on them all.
|
|
Rerendering the entire Achievements dialog every EmulationStateChanged signal is far too often when it turns out that signal fires multiple times to confirm game close, for example. This change results in only the settings changing on EmulationStateChanged, and having the Hardcore mode toggle (which DOES require redrawing the entire dialog) emit its own signal alongside EmulationStateChanged.
|
