Jump to content

skullyi

Platinum Member
  • Posts

    6
  • Joined

  • Last visited

About skullyi

Profile Information

  • Location
    South Wales

skullyi's Achievements

Rookie

Rookie (2/14)

  • First Post Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later
  • One Year In

Recent Badges

0

Reputation

  1. Just wanted to drop an update from my side since I'm experiencing this also - updated to 2.0.60 and the bug is still present.
  2. Haven't seen this reported on the forum (if it has apologies for the double post) Noticed the HS button in HyperHQ doesn't work if HyperSpin is installed in a different location other than C:\HyperSpin - seems to be a hardcoded location rather than taking the variable from install where you define HS install location - or possibly not handling spaces in the folder names correctly "i.e. C:\HyperSpin 2" Has been the same for prior builds too so evidently a bug. Attached logs and log output screenshot all-logs.zip
  3. Noticing this behaviour across numerous systems and roms that have the same releases on different systems - roms from other systems are showing up in libraries (i.e. dreamcast games showing in playstation or gameboy) with the paths for the directories to said roms - causes a bit of a nightmare for loading them as the emulators are expecting the current system format and it seems to load the top rom in the path list. This is on latest release (2.0.54)
  4. Retroarch has a built in "AI" translator service that can be run for non native languages (https://docs.libretro.com/guides/ai-service/) - would be nice to see this as a globally controlled setting to facilitate on/off/manual mode functionality.
  5. Just as additional info - appears to only affect uncompressed roms.
  6. Not sure if this is expected behaviour (I wouldn't expect it to be) Seems that HyperHQ can't scan roms that are nested within a folder (i.e. PlayStation -> game rom folder -> rom files), but if I add each of them manually then they'll add to the system list. I don't see this as expected behaviour so is this a bug? - attached logs just in case there's some deeper error The below has been observed on a fresh install of HS2 *Update* - bug still present in HS 2.0.60 all-logs.zip
×
×
  • Create New...