I have had no success running RetroArch through VirtualBox, the application suffering from a runtime error right from the start. Running it through Phoenix produced the same error. (I am running it through VirtualBox because, being under Linux, this is through it I would be going to play games).
Video acceleration was enabled from the VirtualBox software. bsnes is working right, but not the latest VirtualBox.
Consider posting here in the future if you have any insights, or success stories!
To make sure I’m following correctly: you’re using a Linux host with a virtualized Windows machine?
The next question would be about drivers and your physical hardware.
Oh, yes – exactly. A virtualized Windows-XP machine.
Guest drivers were installed. OpenGL was used, same thing than on bsnes. On the host, NVIDIA drivers are installed.
I have tried disabling the audio for RetroArch, and modifying other settings, but nothing has seemed to resolve the issue. I am going, however, to try one more time – I will report back if anything new is discovered.
EDIT: I have tried back again. Phoenix performed both latest-NES-core and redist updates.
“The application failed to initialize properly (0xc0150002). Click on OK to terminate the application.”
I think I have found the culprit. It seems Visual-C+±libraries runtime components have to be installed – I did not know about that.
EDIT: I am going to test back in the future using a powerful-enough computer equipped with integrated Intel graphics.
Unfortunately, I’m a bit out of my element in this situation. I suspect getting vsync working in the guest will be difficult, since it’s already difficult enough in the native system…
RetroArch runs natively in Linux. In fact, Themaister, the main developer, uses Linux as his main OS. Why are you doing this?
Well, actually I have built an “entertainment system,” which conceivably cannot, as a whole, be ported to Linux. Everything is working well under VirtualBox right now, though. except for a few minor hiccups to be solved.
No problems.
Remember that the problem, though, is not getting vsync to work as such, but to make both vsync and async work at the same time, without crackling, nor tearing.
Perhaps it is the specs of the computer that are not up to the job, or perhaps that is because of interference from the part of NVIDIA drivers. I am going to test back in the future using a powerful-enough computer equipped with integrated Intel graphics, which may well solve the issue at hand.