![]() ![]() ![]() I should really change my versioning naming convention. You can consider the 200327 to be a solid check point to work from. In Hexen, once you get the ability to fly, you will probably need the light bar, since we’ve run out of keys fo fly up and down.Īny more hot fixes I make I will provide instructions and files for fixing them yourself, in addition to uploading a new image that has the hot fixes applied. Shift Select/Start = scroll items left/right You might not even like my config, since I have it set to a gameshell without a light bar.ī(south) = Jump (if available) or centre view It’s not actually essential at all, since you can just configure it yourself. Since it’s identical to the file posted above, if you’ve already downloaded and installed build 200327, you can just update if with that file. chocolate-doom.zipĪnd done! Build 200328 is exactly the same as 200327, just providing a tiny hot fix to include a config file for the chocolate doom/heretic/hexen/strife wrappers. Here’s some super rough configs I just whipped up. The config file is located in /home/cpi/.chocolate-doom/ if you ever wanted to back it up or anything. No need to work out key codes/hex values, or editing of the config files. You can input each key one at a time till you have something that works. It’s located in: /usr/games/chocolate-doom-setup /usr/games/chocolate-heretic-setup /usr/games/chocolate-hexen-setup /usr/games/chocolate-strife-setup ![]() On another note, you can edit the doom/heretic/hexen/strife config on the gameshell, executing the configs via the dinguxcommander in utilities. So having someone who can help spot when I make silly mistakes is greatly appreciated! It happens. Sometimes, things I do in one card get lost along the way, going between them. My testing involves 3 gameshell images: Card1: a 32GB card that I mess around with test things and break things to find things that work (it gets wiped a lot), Card 2: a stock 16GB card that I apply the findings I make on Card 1 and base all of my clean images on, and ensure works, and Card 3: a 128GB day to day image filled with test roms, to ensure that most games run, and that incremental updates can be successfully applied. I’ll need to write an older image to a spare card to extract my previous config files and post them up. To be honest, I’ve actually been using zdoom to run most of my WADS lately, so didn’t actually check to see if it was working. Somewhere along the line it got wiped! Possibly, while doing the buster update! At least that’s how I thought I had it set up. This is to have something useable on a gameshell without a lightbar setup. You’re doing me a huge favour doing this! It means a lot that you keep checking every day!Īs for the fire key, I have currently mapped it to “snes X”, ie the North action key. Thanks to you actually! I’ve honesty wanted to have someone who’s willing to help me test out everything. It’s the same build number, since it’s just a slight revision of something that is trivial to fix. I’m assuming by the sound of things, you know how the nfig works.Įdit: Aaaaand it’s uploaded. Let me know if you need any assistance with replacing the contents of the nfig files. Thanks for testing it thoroughly to find these! I’ll upload a new version to include these changes. SO_URL=ttps:///nightly/linux/armv7-neon-hf/latest/picodrive_libretro.so.zip ROM_SO=/home/cpi/.config/retroarch/cores/picodrive_libretro.so Here’s a fix: ROM=/home/cpi/games/MegaDrive ROM_SO=/home/cpi/.config/retroarch/cores/mednafen_wswan_libretro.soĪnd ha! While making the PCSX Retroarch core, I used the PicoDrive nfig as my template, but evidently got mixed up which one was the source and destination! That would explain why it happened like that! I copy pasted the nfig from the GBA as a template. Thank goodness, it’s just the title that was wrong. Thank you so much for thoroughly checking this! These are things I honestly overlooked! ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |