EVEGames

@Nanochess, Glad to see this thread is still chuggin'. I recently installed CoolCV on a Raspberry Pi Zero W for the first time, and while I got it fully up and running, controller mapped properly, still it runs a bit laggy. It starts with sound slightly stuttering and it seems to get progressively worse with time while playing a game. Just wondering if there are any tips or tricks to squeeze additional performance out of CoolCV. I have not yet gone as far as to overclock my Pi, I want to save that as a last resort. Any tips from the creator? Thanks again for all you do with CoolCV! -Dave

@theborga, I think this is your key... cd /dev/inputjstest js0 ...you're now in testing mode. press each button and d-pad direction on your controller, one at a time. It will show you, in real-time, which button or axis you are pressing. Write them all down. ctrl-c to exit out of the test. apply your newfound controller mapping knowledge to your coolcv_mapping file as shown above, and set your key bindings however you want. . . . ...but instead of testing "js0", in your case you probably want to test "js1" for your second joystick. To be sure, you can list all your connected input devices by going to: cd /dev/input , and running: ls -lah It will probably show that you have one "js0" joystick and one "js1" joystick connected. If so, run: jstest js1 , and figure out your keybindings for that second joystick. Then edit coolcv_mapping.txt and map the controls to your js1 joystick. Hope that works for you. -Dave

Just popping in to drop some respect and maybe help some CoolCV-via-RetroPie newbies like myself. First, hats off to Nanochess for creating CoolCV and releasing it into the wild, and thanks for helping me get past my setup issues! Also, thanks to the posters on this thread, I read all 16 pages worth, and it got me past all my remaining questions and issues, especially groovy978, mckafka99 and intvdave. Special thanks to paulace50 for requesting the 2-keypress mapping feature, allowing CoolCV to conform to the RetroPie 2-finger saute (Select+Start to exit any emulator). Lastly, if I am not stepping on any toes, I'd like to distill some of the the key points that I gleaned from this thread into a step-by-step how-to, specifically geared toward current RetroPie owners, who have already installed and updated CoolCV through the RetroPie Setup GUI, but who found, like I did, that you cannot (as of this writing) obtain the VERY LATEST version of the emulator through the automated method. So if you want to manually install the very latest version of CoolCV, which allows for the aforementioned 2-finger salute, this is for you. Note 1, these instructions are very Windows-centric, I have no idea how well they translate to Mac. Note 2, you will be executing commands manually from the command line on your Pi. if this frightens you in the least bit, stop right here and consider sticking to the CoolCV that you already have working... Note 3, If Linux frightens you but you're going to proceed anyway, I suggest making a backup of your SD card just in case you screw something up. 1) Obtain "coolcv_v0.6.4_all.zip" (or newer) from Nanochess's original post in this thread. 2) Unzip that file to a temp folder, read the included readme (coolcv.txt), and consider throwing a few bucks Nano's way via PayPal, see the bottom of the readme for details. Pro Tip: If you're a Windows user like me, the text in coolcv.txt will look jumbled in Notepad. Obtain a copy of Notepad++ (it's free). It's also great for editing xml files - very useful for a Pi user. 3) From your temp folder where you unzipped the files, copy the "coolcv_pi" binary and drop it onto your Pi... Complete Noob Tip: This is how I do it, because I'm still a Raspberry Pi noob. There are surely better ways. 3a) Get your PC and Pi both running, get both connected to the internet on the same network. On the Pi, if you boot directly into EmulationStation (or AttractMode or whatever), you must exit to the command line. (For EmulationStation, simply hit F4. Not sure about AttractMode or MotionBlue, I haven't messed with them yet.) 3b) On the PC, open two Windows Explorer windows. First one, navigate to your temp folder. Second one, at the top, type in \\RETROPIE and hit enter. That should connect you to your Pi from your PC. This is called the "Samba Shares" method, and the instructions for PC and Mac can both be found here: https://github.com/retropie/retropie-setup/wiki/Transferring-Roms 3c) On the Retropie Windows Explorer window, navigate to the "splashscreens" folder. Why? Because it's a safe place to drop things without risking overwriting anything important. 3d) On the temp folder Windows Explorer window, Copy the "coolcv_pi" binary. On the Retropie Explorer window, paste that file into the splashscreens folder. 4) Switch over to your Raspberry Pi, which should already be running and should be on the Linux command line. Execute the following commands. cd /home/pi/RetroPie/splashscreens (this is where you dropped the updated version of the coolcv_pi binary) chmod 777 coolcv_pi (change permissions, make it executable) sudo chown root coolcv_pi (owner needs to be set to root) sudo chown :root coolcv_pi (group needs to be set to root) cd /opt/retropie/emulators/coolcv/coolcv (I don't know why my coolcv folder has a folder called coolcv... you might not have that second coolcv folder) sudo mv coolcv_pi coolcv_pi_orig (Make a backup copy of the original coolcv_pi binary, called coolcv_pi_orig, so you can revert back to it if needed) sudo mv /home/pi/RetroPie/splashscreens/coolcv_pi . (Move the updated coolcv_pi binary from your splashscreens folder to your coolcv folder) 5) Validate. Run this command from the current folder (your coolcv folder): ls -ltr If all went well, your listing should look SOMETHING like this: total 708 -rwxrwxrwx 1 root root 352054 Aug 23 2015 coolcv_pi_orig -rwxrwxrwx 1 root root 358692 Aug 23 2015 coolcv_pi -rw-r--r-- 1 root root 11971 Nov 27 2015 coolcv.txt Don't concern yourself with matching the dates or the byte counts, concern yourself only with the filenames, the permissions, and the owner and group of the files. If your filenames, permissions, and owner and group look right, you have successfully replaced the old coolcv_pi binary with the updated one. At this point, you have not yet altered your CoolCV controller mapping to use the two-finger salute, but before doing that, you should test to see that Coleco still works within EmulationStation. Run the command "sudo reboot", navigate to ColecoVision, and launch a game which you know worked previously. If the game does not run, you get an error, or you get a blank screen, exit to the command line, cd /opt/retropie/emulators/coolcv/coolcv, mv coolcv_pi coolcv_pi_new, mv coolcv_pi_orig coolcv_pi. You're back to normal. If the game DOES run, now you're ready to edit your CoolCV mapping. exit to the command line. cd /opt/retropie/configs/coleco sudo nano coolcv_mapping.txt ...you're now in the nano text editor. use the arrow keys to navigate down and find the mapping for "key_exit". It probably looks something like this: key_exit key1073741939 change it to something like this: key_exit key1073741939 joy0_4 joy0_5 ...at least, that's what Select and Start are mapped to on my SNES controller, joy0_4 and joy0_5. You will have to figure out what your correct button mappings are for your controller. press ctrl-x to Exit, enter Y to save, and hit enter to complete the save. Run the command "sudo reboot", navigate to ColecoVision, and launch a game which you know worked previously. Press Select and Start to exit the game. If it didn't work, exit the old way, get back to the command line, and do the following to determine your controller's button mappings: cd /dev/input jstest js0 ...you're now in testing mode. press each button and d-pad direction on your controller, one at a time. It will show you, in real-time, which button or axis you are pressing. Write them all down. ctrl-c to exit out of the test. apply your newfound controller mapping knowledge to your coolcv_mapping file as shown above, and set your key bindings however you want. By no means did I intend on writing anywhere near that much in this post. But I hope it helps someone. Please feel free to edit and improve. Thanks, -Dave