Jump to content


Elite Member
  • Content count

  • Joined

  • Last visited

  • Days Won


RIP-Felix last won the day on December 20 2017

RIP-Felix had the most liked content!

Community Reputation

200 Excellent

About RIP-Felix

  • Rank
    Most Appropriate Profile Pic

Profile Information

  • Gender
  • Location

Recent Profile Visitors

1339 profile views
  1. Well that's the thing. It disproportionately affects older CPUs. The older (within the last 10 years - the relevant ones) are affected more than the newer faster models. So yeah, there is perhaps a fear factor there, but I think it's driven more out of necessity than coercion. Tests show that the patch doesn't seem to as noticeable in normal user scenarios as was initially feared (Browsing internet, gaming, and file management). Where it becomes noticeable is when the CPU is usually operating near 100%, like in servers or data centers. I wonder about video encoding. That one gets me as it's the primary reason I bought a fast CPU (Intel i7-4790K). It already takes a buttload of time to encode mp4 home movies in hitfilm.
  2. Battle Damage - Unofficial Star Wars Hype Thread

    Just saw it last weekend and was expecting it to be worse. I saw "Wonder" before TLJ and was expecting it to be the better movie of the two, but enjoyed both.
  3. Aparantly, it's a huge vulnerability. Intel cpu users are vulnerable from the internet, regardless of settings. AMD is vulnerable from local access, so hackers would need physical access to your computer. The exploit was discovered by a professional hacking service that brings them to the attention of the companies it affects. From what I gather, it has not yet hit the nefarious hacking community yet, but they will start attacking the fix once they get a look at what it does (revealing the exploit itself). So until Intel, ARM, and AMD fix their physical CPU architecture, this will continue to be a security risk requiring regular OS level updates to keep ahead of the hackers. So, expect a 5-30% performance hit for current CPU's. The new architecture is going to be 5% faster without any advances in technology, other than fixing the flaw. So annoying.
  4. Meanwhile, AMD eagerly awaits the increase in market share. Nothing more satisfying than your competition doing your job for you.
  5. SEGA Saturn Cracked, Better emulation coming soon!

    You should watch the video. Yes he did make a chip that plugs into the expansion port, but figured out exactly how the CD sub-system worked (2:30). Essentially there is a CPU that controls that system and he was able to dump it's rom. No one was able to do this previously. Saturn is particularly hard because of the way it works and emulation efforts in the past were a trial/error process. This contribution to the available information will allow emulator devs to make cycle accurate emulation. He only started the project in 2013 and recently finished (like in the last year or two). He is getting close to releasing prototype boards that will allow you to load roms on your Saturn. However, he has been sharing his findings with emulator devs, who should be releasing updates with real improvements as they figure out how to implement these findings in software (19:16)! So I think this is news, at least it was to me.
  6. NEStalgia Project (Mini NESpi)

    Yeah, but the files actually have to no special characters (The *.gen, *.sfrom, and etc). Most romsets have alternate dumps, hacks, and regions inside of an archive (Goodsets do anyway). I already went through and extracted the US region verified working dumps, those signified with "(USA) [!]". I placed them in a separate folder when I wanted to pair down the full set to the to IGN top 100. This makes finding a good game much easier;) It was a lot of work, but thus are the ones I included on the SD card (once I got them renamed correctly). I managed to get the L2/R2 momentary press issue sorted. It was pressing L1 and R1. L1/2 and R1/2 are registering as the same buttons respectively. So instead of L2 (Select item) or R2 (Select weapon) it was pressing L1 (Scope) and R1 (nothing, since I couldn't select a weapon). I swapped them in settings and that works, but I can't use L1 and R1 because of it. Also, the left analog stick is just cloning the D-pad. It's not analog at all, retroarch settings doesn't change that. The Wii classic controller works better, but I need to do more testing...
  7. NEStalgia Project (Mini NESpi)

    Yup, the "\(" escapes the ( command and tells it to literally look for an open parentheses. Same with "\]". I wasted a whole day watching youtube videos trying to figure that out!!! Eventually I managed to whip the romnames into shape. Probably took me more time than it would have to rename them one by one! (breaths deeply)...
  8. NEStalgia Project (Mini NESpi)

    Yes, I can see the usefulness. It's just masked by the throbbing pain in my neck! Trouble in SNEStalgia The 8BitDo SF30 pro controller isn't perfectly recognized in retroarch on the SNESC yet! R3/L3 and the right analog stick do not bind (are not seen). Everything else is seen. All the regular cores work fine without these controls (NES, SNES, Genesis, Atari 2600, and GB/GBA are the ones I've tested so far). However, PS1 and N64 won't work properly without them. For PS1 I'm using pcsx_rearmed_neon. R3/L3 and the right analog stick are not recognized, so no ape escape! Also, in Metal Gear Solid, L1/L2 act like a momentary switch. It doesn't see me holding the button down, which won't allow me to select weapons/items. It just equips the scope. So PS1 games are unplayable with this controller. Mupen64 is even worse. In addition to the buttons retroarch won't bind, the emu itself doesn't respond to the left analog stick or D-pad, even though they are bound in retroarch. Since there is no emulation station or frontend with the SNESC, it makes troubleshooting these things out of my league. There most likely needs to be a core update to modify the controller driver (wherever it's located). I'm using "_km_pcsx_rearmed_neon_12_16_17.hmod" for the PSX core, but I'm not sure that's where the retroarch controller drivers are stored. These cores get installed on the SNESC using Hakchi1, an unforgiving process. Assuming the driver is in the *.hmod, I would need to edit it and hack around inside of it (Linux coding). YUK!!!
  9. NEStalgia Project (Mini NESpi)

    Speaking of coding... HELP!!! The USB-HOST MOD that I'm using requires that no special characters be in the romname. My Goodset roms have Parentheses, exclamation points, and hyphens (Battletoads & Double Dragon - The Ultimate Team (U) [!].nes for example). In order for it to be loaded from the USB drive, it needs to be renamed to Battletoads & Double Dragon_The Ultimate Team.nes. I could do this rom by rom, but it would take forever. So I downloaded a bulk renaming tool (RegexRenamer, but I'm not married to it). However it uses general expressions to match patterns and rename. I have no idea how to get it to remove just the special characters. I've already spent too much time watching youtube videos trying to figure it out, to no avail. How do I remove "(U)" and "(!)" without changing anything else? How do I replace "-" with underscores? EDIT: I Found the following to work: (.\(.*\]) That searches for "space(" + any number of characters followed by "]". That removes "space(U) [!]" After renaming, I'm left with "Battletoads & Double Dragon - The Ultimate Team.nes". The last thing left is to remove are the hyphens; (.-.) That matches "space-space". In the replace bar I put an underscore. It thus becomes "Battletoads & Double Dragon_The Ultimate Team.nes" after renaming again.
  10. NEStalgia Project (Mini NESpi)

    SNEStalgia update Apparently the SNES classic edition can now have a USB/SD storage device added. You can solder in an SD card (Invasive) or use a micro USB On-The-Go Adapter to extend the storage. The alteration is less user friendly and bugs are still being worked out, but now the sky's the limit for it's library. I'm going to add PS1 to it. From what I understand it's hardware is slightly more impressive than the raspberry Pi 3. So it should be able to swing more (N64?). I like the interface better than emulation station, the save state manager and rewind feature specifically, but it doesn't offer the flexibility RPi does. Regardless, this is a huge leap forward. It's really giving NEStalgia the old Na-Na-Nuh-Boo-Boo-I-Hold-Your-Face-In-Doo_Doo! It can't emulate the cartridge, and never will. So there's that. They are really fighting for Daddy's attention.
  11. NEStalgia Project (Mini NESpi)

    Yeah, that seems doable. I'll probably put this project off for a while, I'm just not feeling it right now. Nice tool however. Thanks for the tip! Defiantly on my to-do list.
  12. NEStalgia Project (Mini NESpi)

    Yeah, I read through the walk-through. It's pretty strait forward, albeit tedious, I'm just hesitant to edit my run on start and end scripts. NEStalgia uses them to automate the cartridge emulation function. I might be able to get it to work in addition to the modified script I already have, but each time the changes add up and later make figuring out what you did harder. SD image backups will thus be necessary. My bigger concern is that I don't have a dedicated controller. I routinely pair the Wii U pro, SF30/NES30 pro, and PS3 controllers to other devices (GameEX HTPC, Arcade Cab, SNES classic edition, and original SNES/NES/PS3). I'm not sure that the Bluetooth ID or linux assignments will always be the same when resyncing to the Pi. I've had this problem on windows, even with wired controllers. I have a bunch of different adapters, but the USB port you plug it into has to be the same or the event ID changes; I often have to redo all the keymaps in GameEX, MAME, Emulators, and etc. because I can never remember which port it was plugged into. The only solution I've found it to mark the ports or leave the adapter in permanently. I wish there was a way to instruct the computer to recognize the adapter and assign it a static event ID, regardless of which USB port it was plugged into. Maybe there is, but I've revisited this issue may times and came up empty each time. That's the biggest advantage of retroarch IMO. One controller map applies to every system. So you just have to do it once. However, it always has to be recognized as the same controller. Wired is one thing, wireless has been a mixed bag in my experience. The last thing I want to do is have to repeat that tedious process each time I pair the controller because Emulation station recognized it as "Gampad 8" instead of "Gamepad 6", even though they are both the same "SF30 pro gampad". Sorry your suggestion is bringing up some Personal Computer Stress Disorder (PCSD). I've been through some loosing battles with my arcade cab, and this is bringing me back there. EDIT:
  13. NEStalgia Project (Mini NESpi)

    Yikes, my Profile pic says it all! Well...ummm...yeah, that's that's the intense linux muck around session I was hoping to avoid. I can see why you've been putting it off. I've had rumble working in ePSXe on windows. I use ePSXeCutor to create shortcuts with per game settings which are launched by GameEX. Then I manage disc switching with @nullPointer's Switch disc. That works fine, but takes forever to setup correctly. Then if some path or video driver changes, you have to start all over. I've been needing to redo my setup since I last upgraded my video card, but have been pitting off because of what a PITA it is. RetroPi makes PS1 simpler. PSX2PSP simplifies multi disc games and retroarch makes disc swapping easy. EmulationStation automates the controller profiles for easy setup. Why for Pete's sake is the only thing lacking Force Feedback? It's frustrating. It seems like it would be such a simple thing, but just isn't. It was so close to being the perfect solution for PS1 emulation! Sigh...I guess nothing is perfect. Oh well.
  14. NEStalgia Project (Mini NESpi)

    I'm starting to think some of the issues of the PSX emulator not working are related to some configuration exception in retroarch, not the controller. The reason is because none of my controllers will control PS1 now. With all the testing/setting up I was doing with a Wii U pro, PS3, and the 8BitDo controllers I think something got confused. I need to reset the PS1 configuration file and retry. It was working great with my Wii U Pro controller (No rumble though) now it isn't. So I'm skeptical that my results for the Switch mode above are accurate. I think it was just the first appearance of this issue, which has now spread to the rest of my controllers. I have no idea why, so I just need to find the config file and reset it. I'm not sure where to start. EDIT: Well I got the controllers working again (PS3 - using this Mayflash adapter, SF30 Pro, NES30 Pro, and Wii U Pro). They all work together fine, but the rumble still won't work on any of them. The PS3 controller uses the Mayflash adapter on it's x-input setting and is recognized as a "Microsoft X-box 360 controller". On windows this allows rumble support, but only one controller per wireless adapter. On it's D-input setting the adapter allows 4x PS3 controllers to pair simultaneously, but no rumble - again on windows. I wanted to see if it would work similarly in Retropi. It does recognize the controller and all buttons fine. Since the adapter handles the sync, the pi has no problem with it. The adapter automatically pairs the controllers Bluetooth ID, the Pi just sees the adapter as a USB controller. Re-pairing is no issue whatsoever. If I use the controller elsewhere (PS3, arcade cab, HTPC) all I have to do to re-sync with the pi is plug the PS3 controller into the adapter, and adapter into the Pi. No messing around with Bluetooth drivers! Now the lack of rumble no matter what I've tried is weird. The SF30 pro has rumble and vibrates once upon each sucessful sync with the pi. So I know it works. The Wii U Pro had force feedback, but I haven't felt anything. The PS3 controller has force feedback, but it doesn't rumble either. I have the rumble option in retroarch enabled, but that doesn't do anything. I have the rumble enabled in game (If that matters). What else can I try? I did find a guide that enables the Force Feedback in the driver for the Pantherlord/Greenasia USB PS1/2 Dualshock adapters. I do have one of these adapters and some controllers. The rumble is supposed to be weaker since the Pi can only supply 5v instead of the 7.5v OEM. However that guide is...um...daunting. I hate linux. I'd like to avoid compiling kernels manually if possible. Regardless, this is not exactly what I'm looking for anyway. What I'm trying to find out is why rumble isn't working for any controller I've tried.