Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

RetroArch 1.6.3 "Disk Image Append" restarts core Windows 10 #5254

Closed
mangopipeline opened this issue Aug 6, 2017 · 3 comments
Closed

RetroArch 1.6.3 "Disk Image Append" restarts core Windows 10 #5254

mangopipeline opened this issue Aug 6, 2017 · 3 comments

Comments

@mangopipeline
Copy link

First and foremost consider this:

  • Only RetroArch bugs should be filed here. Not core bugs or game bugs
  • This is not a forum or a help section, this is strictly developer oriented

Description

When using the Disk Image Append in the XMB menu
when i select the new image to append, RetroArch Reloads the Core

Description of the bug

I'm testing a multi cd sega 32x game.
when prompt to insert a different disk i run the following steps
1)press f1
2)go to core disk options
3)run Disk Cycle Tray Status
4)Resume emulation
5)press f1 again
6)try to change Disk Index (message list 1/1 images)
7)press Disk Image Append and browse to .cue file
8)when a double click on the new image

retro arch restarts the core from the beginning.

Expected behavior

after step 7 retroArch would allow me to change the Disk Image Index Close the try and resume emulation.

Actual behavior

Retro Arch Start From the begining...

Steps to reproduce the bug

1)press f1
2)go to core disk options
3)run Disk Cycle Tray Status
4)Resume emulation
5)press f1 again
6)try to change Disk Index (message list 1/1 images)
7)press Disk Image Append and browse to .cue file
8)when a double click on the new image

Environment information

  • OS: Windows 10
  • Compiler: [In case you are running local builds]
  • using PicoDrive 1.91
@mangopipeline
Copy link
Author

I went back and tested a few different retro arch versions....
seems like 1.3.6 64 bit works like a charm....

@RobLoach
Copy link
Member

Perhaps 366c73f ?

@mangopipeline
Copy link
Author

this seems to fix in 1.6.7 thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants