Lordmonkus

http://store.steampowered.com/app/208140/

No, it's a pay game. I haven't tried Endless Space but I have played Endless Legend which is their fantasy based 4X game and it's pretty cool.

Looks pretty cool, have you played Endless Space ? Plus Endless Space 2 is coming soon as well and that looks really good.

If you cannot run the balanced bsnes core use the core updater in Retroarch to download the Snes9x core you are looking for.

Yeah probably a good idea

I have not tried any Mame emulation on Android at all but I believe that the Android version of Mame is different from the mainline version. But I really have no idea about that.

It's the same as any other system, you just need the correct bios (the Mess bios work), and your games need to be in cue + bin format.

Yeah. As far as emulation goes the CPU is the driving factor behind the speed. The video card only comes in when you take shaders and resolution scaling into account and even then you don't need anything too amazing. I am using an older Radeon 7850 in an emulation computer which just has 1 gig of ddr5 and it is great for it.

Yeah for a pure emulation system both cards are very much overkill.

If it's a low profile card and would fit it might be a good deal. But otherwise the new 1050s have been announced at 109$ and 159$ which would be better. From what I could find on the 780 it's not low profile.

Version 6.12 - Released October 18, 2016 - New Premium Feature: Added custom marquee support to Big Box for arcade cabinets - New Premium Feature: Added proper multi-monitor support to Big Box - Improvement: Significantly reduced pop-in for images in LaunchBox - Improvement: Added a Producers tab to the About dialog for our amazing Patreon contributors - Fixed: Voice recognition commands specific to Big Box were complaining about not being in Big Box (bug was introduced in 6.11) - Fixed: Images were not retained when renaming games (introduced in a recent version) - Fixed: LaunchBox (not Big Box) was causing LEDBlinky to fire a list change and a game select command after a game started running - Fixed: AutoHotkey was working properly for events, but not for executing commands on startup of emulators, etc. - Removed: The import and export to zip file features were removed as they are no longer necessary when switching platforms between different LaunchBox installations; now it's as simple as just copying the platform's XML file and media files between installations

Umm, calm down. We cannot tell you where to locate roms.

Forgot about that.

You can just reimport all your games and it will skip the games already in your library.

Right click a game and click edit, then in the the edit screen click the download images and media button on the bottom right and it will pull from the database.

You could either rescrape the games or if you have downloaded the media you can just just drop it in the appropriate folders and refresh the images in Launchbox and they will appear.

There's no easy option to hide once they are imported but during the import phase you can tell Launchbox not to import clones. Otherwise you will just have to go through your Mame list and remove the clones you don't want manually.

For anyone new to Retroarch and looking for a great place to start here is your best place. https://www.reddit.com/r/RetroArch/comments/57z1rp/retroarch_faq/

Glad you got it sorted out.

Not sure if this will be of any help to you or not but I found this with a quick search. http://forum.arcadecontrols.com/index.php?topic=150889.0

Ok I am not too up on Time Traveler itself but if you are going through Daphne itself but you find out how to make a bat file for a game by doing this. Open your DaphneLoader.exe click the Configure button and go to the Advanced tab. The bottom drop down menu "Display command line", set this to Enabled, click apply and ok. Now when you start that game it is going to popup with a bunch of text, select it all and copy. The game will launch but just exit back out. I have done this for several Daphne games to generate batch files and they all work. Here is the batch file I have for Dragon's Lair daphne.exe lair vldp -framefile H:\Emulation\Roms\Daphne\vldp\lair\lair.txt -blend -ignore_aspect_ratio -blank_searches -precache -min_seek_delay 1000 -seek_frames_per_ms 20 -homedir H:\Emulation\Roms\Daphne -fastboot -bank 0 11011001 -bank 1 00100111 -nocrc -noissues -noserversend -sound_buffer 2048 -fullscreen -x 1600 -y 1200

look in your batch file for the parameter -fullscreen

Roms themselves change usually because they maybe were improperly dumped previously and even though they worked they weren't right. Then someone does a proper dump of a game and because arcade rom dumps are different than cartridge dumps you now have more files in the zip file. In the case of the latest version of Mame (178) the Capcom CPS2 roms have a .key file which is an encryption rom that was on the arcade boards. And because Mame aims for accurate 1:1 emulation they wanted to emulate these chips so now we have to have the roms with these .key files.

A user by the name of Brunnis over on the Retroarch forums has done a lot of work testing and improving input lag. He started out testing to see why Snes always had higher levels of lag compared to other emulators and if it could be improved. He finally posted a write up on settings to use to reduce it as much as you can in Retroarch itself, here is the forum post for it. Start at the beginning of the thread which is quite long and technical if you want to know more. http://libretro.com/forums/showthread.php?t=5428&page=36&p=49145&viewfull=1#post49145 Here is the copy and paste of the post he made. All of this information is from Brunnis and he gets all the credit for it, I am simply pasting it here. Linux Important: Run RetroArch from an X-less terminal. This requires a working DRM video driver, which most modern systems appear to have. See https://github.com/libretro/RetroArch/wiki/KMS-mode Important #2: You may get performance issues unless you set your CPU to max frequency. This is because the CPU's power management thinks the CPU is idle enough to be downclocked. In Ubuntu, you can run sudo cpufreq-set -g performance to do this. You may want to put this in a startup script. In retroarch.cfg set: video_driver = "gl" video_vsync = true video_threaded = false video_max_swapchain_images = 2 video_frame_delay = See description further down Windows In retroarch.cfg set: video_driver = "gl" video_vsync = true video_threaded = false video_fullscreen = true video_windowed_fullscreen = false video_hard_sync = true video_frame_delay = See description further down Note on video_max_swapchain_images setting When using the OpenGL ("gl") video driver, this setting switches between using two or three buffers for rendering. Without going into details, a setting of 3 allows the emulator to run ahead and prepare the next frame before the current one has even been shown. This improves performance (i.e. makes framerate hiccups less likely), especially on slow hardware, but increases input lag by one whole frame in the general case. So, the general rule is to use a setting of 2 if the system can handle it. It will shave off one frame of input lag compared to the default setting of 3. Please also note that a setting of 2 forces vsync on. Note on video_frame_delay setting This setting delays the running of the emulator by the specified number of milliseconds. This sounds bad, but actually improves input lag, since it pushes the input polling and rendering closer to when the frame will actually be displayed. For example, setting video_frame_delay = 10 shaves off 10 ms of input lag. The general rule here is to use the highest value possible that doesn't cause framerate or audio issues. This is highly system dependent. The faster your system is and the less demanding the emulator is, the higher you can push this setting. On my Core i7-6700K, I can put this setting at 12-13 ms when using snes9x2010, but not nearly as high when using bsnes-mercury-balanced. Please note that the frame delay value can't be higher than a frame period (which is 16.67 ms at 60 Hz). I believe the GUI caps this setting to a maximum value of 15. I would also advice to play with this setting last. It takes a bit of trial and error to find a good setting, and unless you're willing to make per game settings, you might not be able to find a setting that works well in all situations while still giving a worthwile improvement. A general note on GPU drivers Input lag can vary depending on GPU driver, so it's not possible to guarantee a certain input lag without testing the particular combination of hardware and GPU driver. For example, I have measured different input lag when just upgrading from one GPU driver version to another. Currently, my safest bet for low input lag would be to use Linux in KMS/DRM mode with the above mentioned settings. Note on Raspberry Pi The Raspberry Pi is sort of a special case. In general, it's too slow to use anything other than the default value for video_frame_delay (which is 0). Also, unless you're using the experimental open source OpenGL driver, the video_max_swapchain_images setting has no effect. In retroarch.cfg set: video_driver = "dispmanx" ("gl" if you require 3D acceleration or shaders. Will add one frame of input lag compared to dispmanx driver.) video_vsync = true video_threaded = false video_frame_delay = 0 The settings above are what's recommended for all of those using the default Raspberry Pi GPU driver. I have some comments coming up regarding the experimental OpenGL driver. Regarding accuracy vs input lag There's no real correlation between the two, except that accuracy usually comes with a performance penalty (i.e. frame rendering times increase). This, in turn, makes it less likely that you can use video_max_swapchain_images = 2 and high video_frame_delay numbers. I'd choose the emulator(s) I prefer/need for the games I play and then tweak the above mentioned settings to their optimal values. UPDATE: Version 1.6.0 of Retroarch added in a new input driver, RawInput which reduces input latency even further. This setting is in the Settings > Driver > Input Driver, set this to Raw,

Yeah give the balanced core a whirl, it's not so hard on the CPU requirements. And if Doom is your only issue then you are doing well.