One way you could do it is to get an Capture Card (like an Elgato) and then Record it from your PC Screen.

@justcarp Please don't reply to 3 years old topics. Open a separate topic and ask your question, referencing this topic if needed.

Thank you very much

@spiky
Well thanks for trying anyhow! I have it working on dosbox on my laptop, no issue what so ever. Must be some config in my Pi's dosbox that won't allow it to work. Will need to continue research, thanks!

@jonnykesh sorry, But i need help, is there something i can do or should i just flash a new one.

I have just released a post about the virtual COM port of the GamepadBlock. I hope that answers your questions! You can find it at https://blog.petrockblock.com/2017/11/11/using-virtual-com-port-gamepadblock/

@askalangly deleting retroarch.cfgs and the back up isn't the right thing to do. we don't use retroarch defaults, which is what you'll end up using if you delete everything.

please fill out https://retropie.org.uk/forum/topic/3/read-this-first

@lamaman1971 Thanks for sharing. Definitely share your feedback on bezels, filters and the like with the community - there are plenty of people here in search for the perfect set up as well, so the more the merrier!

Cheers.

Wow, it looks awesome.

Figured I'd share the error I was getting. Firstly, you need to be using Python 3+ for the version of ansible.

sudo pip install ansible

Downloading/unpacking ansible Downloading ansible-2.4.1.0.tar.gz (6.7MB): 6.7MB downloaded Running setup.py (path:/tmp/pip-build-f2xlqxxd/ansible/setup.py) egg_info for package ansible no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' Requirement already satisfied (use --upgrade to upgrade): jinja2 in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): PyYAML in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): paramiko in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): cryptography in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): setuptools in /usr/local/lib/python3.4/dist-packages (from ansible) Requirement already satisfied (use --upgrade to upgrade): idna>=2.1 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Requirement already satisfied (use --upgrade to upgrade): asn1crypto>=0.21.0 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Requirement already satisfied (use --upgrade to upgrade): six>=1.4.1 in /usr/local/lib/python3.4/dist-packages (from cryptography->ansible) Installing collected packages: ansible Running setup.py install for ansible changing mode of build/scripts-3.4/ansible from 644 to 755 changing mode of build/scripts-3.4/ansible-playbook from 644 to 755 changing mode of build/scripts-3.4/ansible-pull from 644 to 755 changing mode of build/scripts-3.4/ansible-doc from 644 to 755 changing mode of build/scripts-3.4/ansible-galaxy from 644 to 755 changing mode of build/scripts-3.4/ansible-console from 644 to 755 changing mode of build/scripts-3.4/ansible-connection from 644 to 755 changing mode of build/scripts-3.4/ansible-vault from 644 to 755 no previously-included directories found matching 'ticket_stubs' no previously-included directories found matching 'hacking' changing mode of /usr/local/bin/ansible to 755 changing mode of /usr/local/bin/ansible-doc to 755 changing mode of /usr/local/bin/ansible-galaxy to 755 changing mode of /usr/local/bin/ansible-connection to 755 changing mode of /usr/local/bin/ansible-console to 755 changing mode of /usr/local/bin/ansible-inventory to 755 changing mode of /usr/local/bin/ansible-vault to 755 changing mode of /usr/local/bin/ansible-playbook to 755 changing mode of /usr/local/bin/ansible-config to 755 changing mode of /usr/local/bin/ansible-pull to 755 Could not find .egg-info directory in install record for ansible Successfully installed ansible Cleaning up...

Looks good so far, but...

ansible --version

ERROR! Unexpected Exception, this is probably a bug: unsupported operand type(s) for %: 'bytes' and 'bytes' the full traceback was: Traceback (most recent call last): File "/usr/local/bin/ansible", line 85, in <module> mycli = getattr(__import__("ansible.cli.%s" % sub, fromlist=[myclass]), myclass) File "/usr/local/lib/python3.4/dist-packages/ansible/cli/__init__.py", line 38, in <module> from ansible.inventory.manager import InventoryManager File "/usr/local/lib/python3.4/dist-packages/ansible/inventory/manager.py", line 44, in <module> IGNORED_EXTS = [b'%s$' % to_bytes(re.escape(x)) for x in C.INVENTORY_IGNORE_EXTS] File "/usr/local/lib/python3.4/dist-packages/ansible/inventory/manager.py", line 44, in <listcomp> IGNORED_EXTS = [b'%s$' % to_bytes(re.escape(x)) for x in C.INVENTORY_IGNORE_EXTS] TypeError: unsupported operand type(s) for %: 'bytes' and 'bytes'

Ok according to a post I've found, apparently I need to put both in /opt/retropie/configs/all/retroarch.cfg and /opt/retropie/configs/snes/retroarch.cfg

but I still have the problem. Do I really need to add it inside each retroarch.cfg emulator ?

Pi is very demanding on the power supply.
If the voltage is below 5.2V, turbo mode is disabled
PI will operate at a reduced frequency in throttling mode.
Some SNES games, even on an optimized driver under the SNES2002 AWS, will slow down.

avoid warnings=2 fixit problem

I was looking for a solution for ages. I found this page to be helpful.

https://askubuntu.com/questions/344863/ssh-new-connection-begins-to-hang-not-reject-or-terminate-after-a-day-or-so-on

By switching to netcat it now works without a problem.

fixed switching hdmi group and mode to one i wrote in original post.

I used the free trial to play championship manager 01/02 on my phone. While it worked and loaded the game... I wasn't a fan. If my phone screen locked I would lose my progress, had to constantly save. Had errors too.

Even if it worked properly I didn't think it was near worth the cost. If the guy had gone down the open source route I reckon he'd have had a far better end product by now.

Ultimately I'm sure there will be a product that does that in time.

Also while it may be useful to have access to something like this along with retropie, it shouldnt be him cashing in on retropies brand. That feels wrong on every level, especially when in my opinion his end product is nowhere near the level it needs to be.

After using ClrMamePro and updating my ROM set... and finding out that i didn't have to go through all of that....
i already had the correct ROM set version. All i had to do was copy over dkong.zip and then ReStart EmulationStation.
Donkey Kong showed up and played just fine after that. Thanks for all the Great Advice.!!!!!
Later, David, ThunderBoyDavid

Just put some decent kits together, create PDF/video guides on how to install Retropie, how to put ROMs on the system and all the other basics.
Don't forget to use homebrews for examples and mention that using ROMs of games you don't own, or BIOS of systems you don't own is illegal.
Give credit to RetroPie/homebrew developers.

Doing this I think you are in the clear.