You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I discovered that I can actually run both Glide64 and Glide64mk2. It appears that specifying a plugin name will attempt to match a plugin by name. Specifying mupen64plus-video-glide64 was matching mupen64plus-video-glide64mk2.so. If I specify the 'full' name as mupen64plus-video-glide64.so with the .so extension, it properly loads Glide64. Here are the current reward values for the two hard-coded races I have at the moment:
I discovered that I can actually run both Glide64 and Glide64mk2. It appears that specifying a plugin name will attempt to match a plugin by name. Specifying
mupen64plus-video-glide64
was matchingmupen64plus-video-glide64mk2.so
. If I specify the 'full' name asmupen64plus-video-glide64.so
with the.so
extension, it properly loads Glide64. Here are the current reward values for the two hard-coded races I have at the moment:Still need to look into the discrepancy in the values. Why do they differ when the action sequence and progression through the race is the same?
Originally posted by @bzier in #53 (comment)
The text was updated successfully, but these errors were encountered: