Skip Navigation

Posts
2
Comments
39
Joined
11 mo. ago

  • It's not an RPG but how about Lollipop Chainsaw?

    It has hordes of enemies you can slaughter (which provides a certain kind of relaxation, to be fair) as a pretty girl who possibly looks like you maybe, and you can see boobs.

    I never actually played the game (although I'm interested in playing it) but it was the first thing that popped into my mind.

  • Just wanted to add a couple of things: the game is Street Fighter 3rd Strike, where you can die due to chip damage. What this means is that even if you block special moves (like Justin's Chun-li did) they still do damage, the aforementioned chip damage.

    So Daigo Umehara, the Ken player, had no option other than parry or he would lose the game and Justin Wong, the Chun-li player, would advance to grand finals. Parrying in 3rd Strike is done by inputting forward as opposed to blocking which is done by inputting back. More specifically you have to press forward in a 10 frame window. Since 60 frames equal a second, you have a window of 1/6th of a second to input it and you also cannot hold forward, otherwise you won't be able to use parry for the next 23 frames.

    So if Daigo had held forward to parry the remaining hits of Chun-li's attack, he'd die from chip damage (I think). What he did instead was manually parrying every single hit of the attack AND he also parried the attack in the air, which is even harder to do because in the air the frame window is halved (so you have a 5 frame window, or 0,5/6th of a second if my math doesn't fail me), which doubles the difficulty.

    And just to add to this: Daigo had actually done it in a match before but it wasn't recorded. Also, the number 37 was chosen at random to make it seem as if there were a lot more hype moments like this. Also also Justin Wong, aside from being one of the best fighting game players of all time, has always been (as far as I know) a cool sport about this, even encouraging people online to do the Daigo parry whenever he plays 3rd Strike just so players (the ones who know how to do it at least) can sort of be a Daigo for a moment.

    If you want to know more, I suggest this video: https://yewtu.be/watch?v=36m-teYaQmE

    P.S.: Daigo would go on to lose in the grand finals. But nobody cares about that, to be honest. I don't even know who won it.

  • One of the most iconic moments in video game history.

  • Hell March! The Red Alert 2 version is the best one to me, maybe because it was the first I heard or because it just feels punchier.

  • Okay, what's the biggest and most active gamer community on Matrix?

    As far as I know, https://friendlylinuxplayers.org/ . I'm sure it's not as active as whatever Discord communities you're in but it's fairly active and actually friendly.

  • I use mkinitcpio. You mean regenerating the initramfs? If so, yeah I've done that a few times without much success. I suppose reinstalling the bootloader could be an option but I've tried using a live ISO from another distro (Ubuntu) and the problem still manifested itself. But it is something to keep in mind, so thanks.

    Anyway, so far it seems to be a faulty PCIe slot, so I changed the GPU to another slot and things seem to be working fine. But I'll wait until tomorrow to do a final edit to my post.

  • PieFed isn't letting me edit the OP due to an unexpected error. The errors keep piling up, haha! [EDIT: It's fixed now!]

    Just wanted to thank all of you wonderful people for all the help you've given me. I love each and everyone of you (even the ones who skimmed through my post :p). A user on the other thread I created in the Arch Linux community suggested I add the nomedeset parameter, with which I managed to boot into the system. I updated it and installed linux-lts along with linux-lts-headers. Adjusted /boot/loader/entries/arch_linux.conf to switch to the lts kernel by default and rebooted the PC. Unfortunately, didn't work but I got logs! Here's the relevant part, I think:

       
        
    mai 03 11:04:23 arch kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0xffffffff  
    mai 03 11:04:23 arch kernel: amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x2000000, error code: 0xffffffff  
    mai 03 11:04:23 arch kernel: [drm:resource_construct [amdgpu]] *ERROR* DC: unexpected audio fuse!  
    mai 03 11:04:23 arch kernel: [drm] Display Core v3.2.316 initialized on DCE 12.0  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: [drm] Timeout wait for RLC serdes 0,0  
    mai 03 11:04:23 arch kernel: [drm] kiq ring mec 2 pipe 1 q 0  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110)  
    mai 03 11:04:23 arch kernel: [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed  
    mai 03 11:04:23 arch kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v9_0> failed -110  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu_device_ip_init failed  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU init  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device.  
      
      

    I did a search and it seems like it's the GPU's fault due to the ring errors. I think. I remembered I have an old nvidia GPU laying around so I'm going to try to reseat the current GPU and, if that doesn't work, try the old one. Not sure if I have to uninstall the amd drivers or if it's ok to have both the amd and nvidia drivers installed. If that doesn't work, I'm going to go through all the other suggestions y'all gave me to try and pinpoint the problem.

    Again, thank you so much!

  • debug nomedeset

    It worked! I managed to boot into the system. Updated it and installed linux-lts along with linux-lts-headers. Adjusted /boot/loader/entries/arch_linux.conf to switch to the lts kernel by default and rebooted the PC. Unfortunately, didn't work but I got logs! Here's the relevant part, I think:

       
        
    mai 03 11:04:23 arch kernel: amdgpu: [powerplay] Failed message: 0xe, input parameter: 0x0, error code: 0xffffffff  
    mai 03 11:04:23 arch kernel: amdgpu: [powerplay] Failed message: 0x4, input parameter: 0x2000000, error code: 0xffffffff  
    mai 03 11:04:23 arch kernel: [drm:resource_construct [amdgpu]] *ERROR* DC: unexpected audio fuse!  
    mai 03 11:04:23 arch kernel: [drm] Display Core v3.2.316 initialized on DCE 12.0  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm] *ERROR* No EDID read.  
    mai 03 11:04:23 arch kernel: [drm] Timeout wait for RLC serdes 0,0  
    mai 03 11:04:23 arch kernel: [drm] kiq ring mec 2 pipe 1 q 0  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: [drm:amdgpu_ring_test_helper [amdgpu]] *ERROR* ring kiq_0.2.1.0 test failed (-110)  
    mai 03 11:04:23 arch kernel: [drm:amdgpu_gfx_enable_kcq [amdgpu]] *ERROR* KCQ enable failed  
    mai 03 11:04:23 arch kernel: [drm:amdgpu_device_init.cold [amdgpu]] *ERROR* hw_init of IP block <gfx_v9_0> failed -110  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu_device_ip_init failed  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: Fatal error during GPU init  
    mai 03 11:04:23 arch kernel: amdgpu 0000:0a:00.0: amdgpu: amdgpu: finishing device.  
      
      

    I did a search and it seems like it's the GPU's fault due to the ring errors. I think. I remembered I have an old nvidia GPU laying around so I'm going to try to reseat the current GPU and, if that doesn't work, try the old one. Not sure if I have to uninstall the amd drivers or if it's ok to have both the amd and nvidia drivers installed.

    EDIT in case you missed it: So, I changed the GPU to a different PCIe slot and everything's working fine so far. I'm not celebrating just yet because when this first happened a few months ago, I'd hard reset the PC and everything would work fine. But if I shut it down and let it pass like 12 hours before I'd power it on again, the problem would reappear. So I'm just basically waiting for tomorrow now.

  • I tried adding the kernel parameter mentioned in that thread but it didn't work. But thank you anyway!

  • Regarding your edit: no, I haven't tried that, but I will keep those suggestions in mind, thanks!

  • Yep, has to be for the future, unfortunately, can't access my Arch system in any way right now, even with a live iso :(. But thanks!

  • No, I had to use the latest one. Nope, tried the Ubuntu live ISO but it also didn't work.

  • Those are all good tips, thanks! Will do that tomorrow and report back.

  • Linux @lemmy.ml

    System freezes at boot and I'm not sure if it's a software or hardware problem

    Arch Linux @lemmy.ml

    System freezes at boot and I'm not sure if it's a software or hardware problem

  • I mostly play fighting games nowadays and I think people can learn a lot about mental self-improvement by playing them online. Namely:

    • The main one for me: how to accept losses and learn from them. Losing/making mistakes is not the end of the world but an opportunity to learn from, grow and get better. Losing gives you experience if only on what not to do in a given situation
    • Not expecting short-term improvement and that you'll get better at something overnight. Be patient, understand and accept that on some days you'll be at the top of your game and on others you can't even think straight. Think in medium-to-long term
    • Sometimes losing/making a lot of mistakes will get you mad. And that's okay. Take a breather if you can.
    • Not comparing yourself to others and let yourself get discouraged. Everyone has their own rhythm. Maybe you'll need to work harder than others on some things. But that's just how it is sometimes. Keep at it and you'll eventually see improvements.
  • First of all, thank you for doing these, more original content is always welcome and appreciated! I really like your writing style and that the subjects you cover are just things you find interesting, whether they're related or not. Like you said, it's more of a old gaming blog style, which is cool.

    I also played the shit out of Abuse back in the day but never finished it, so thanks for the excuse to give it another go. Although I did find the 15 fps limit added to the charm of the game, so to speak. But I'll try this new version.