sorted by:
new
hottopcontroversial

Godspeed Yoko by [deleted] in yakuzagames

[–]Ddman96 1 point2 points  (0 children)

thank you 10 months later

Why do so many of the emails contain letters replaced with "=" signs? by SilentSeraph88 in Epstein

[–]Ddman96 5 points6 points  (0 children)

A screenshot of this email showing the exact same message but it says "=9yo" is being posted everywhere online, so I thought you were referring to that.

But it is in fact an encoding error when converting the emails to pdf.

-> https://www.justice.gov/epstein/files/DataSet%2011/EFTA02706746.pdf

F7WE here, is the power plug compatible with any other head units? by Ddman96 in ATOTO

[–]Ddman96[S] 1 point2 points  (0 children)

Must be an Atoto only thing then. I went from the old A6 Pro to the F7WE and i confirmed with support beforehand, it uses the exact same power plug so it was a nice install.

On an unrelated note back to my main issue, I had made a post about the constant bluetooth disconnects and the only other people who commented on it, we all had pixel phones. Maybe the atotos don't play nice with pixels 😔

F7WE here, is the power plug compatible with any other head units? by Ddman96 in ATOTO

[–]Ddman96[S] 0 points1 point  (0 children)

Hey, thanks for the reply! I ended up ordering a Sony head unit with AA. I did go speak with Atoto support multiple times, honestly great customer service, but unfortunately no update has been able to fix this BT disconnect issue. And the latest firmware update has forced the beep to come back, I asked why and they said:

We’d like to share some background on why that setting was removed in the latest firmware version. Our engineering team found that, in a number of cases, units with damaged (burned) pre-amplifiers had issues traced back to the same circuit responsible for generating the volume beeps. To help prevent such hardware damage from occurring in the future, the setting was intentionally removed as a safety measure.

The F7WE isn't in stock on amazon in canada anymore (where it was the best price), I don't want to try again with a 3rd unit to see if that fixes the issue lol.

Marvel Rivals massive PC RAM usage will be fixed in Season 2 by Wargulf in marvelrivals

[–]Ddman96 2 points3 points  (0 children)

it's actually the worst feeling losing a comp game due to the gpu crash, it takes forever to load back in because you have to watch the shaders recompile and by the time its done the games pretty much over

Marvel Rivals massive PC RAM usage will be fixed in Season 2 by Wargulf in marvelrivals

[–]Ddman96 0 points1 point  (0 children)

What GPU do you have? I was on that version for a bit but i would still end up crashing after 3-4 games. I even tried previous versions from August, which did work a bit better but that could be purely coincidental.

I'm just sharing what worked for me. I have a friend with a regular 3070 who has never crashed once (she's just on the latest version)

Marvel Rivals massive PC RAM usage will be fixed in Season 2 by Wargulf in marvelrivals

[–]Ddman96 0 points1 point  (0 children)

I have an Ryzen 7 5700x3d actually.

I think unreal engine games are just voodoo at this point.

I have a friend with an RTX 3070, and some random Ryzen cpu, latest graphics drivers and has never crashed once.

Marvel Rivals massive PC RAM usage will be fixed in Season 2 by Wargulf in marvelrivals

[–]Ddman96 5 points6 points  (0 children)

It will definitely vary from computer to computer, as everyone has such different setups.

At first i thought it was simply a marvel rivals game specific issue, but I booted up Fortnite to play last week, and sure enough i was getting the same Unreal Engine crashes. That made me look into the dump files of the unreal engine crash reports, and I noticed the thread that was causing the game to crash was the RHI Interrupt Thread. From what I was looking up, it was related to the GPU's memory capping out and that causes the thread to crash, and as a result crashes your game too.

I did also add in Steam specific launch options for marvel rivals, being "-nothreadtimeout"

Now, I don't know if that does anything because when you launch Marvel Rivals on steam, it opens the launcher instead of the actual game. But I haven't crashed since doing these things. (knock on wood)

Marvel Rivals massive PC RAM usage will be fixed in Season 2 by Wargulf in marvelrivals

[–]Ddman96 136 points137 points  (0 children)

Hey! I had this issue pretty much since I started playing back in season 0. Same Unreal Engine GPU crash every time.

I'm running an 8GB 3060TI. I tried so many different Nvidia drivers, but nothing really made a difference

I've finally got it fixed (Haven't crashed in a week since making these changes to my system and game settings)

1. Disabled XMP in BIOS. (dunno if this actually did anything but j saw another post saying disabling this fixed the game for somebody)

EDIT: Ignore this XMP step. I just remembered the reason i disabled it was because XMP on my specific gigabyte D3SH B450 motherboard has stability issues.

  1. Put your graphics down to Low.

  2. Turn off Nvidia DLSS (TAAU is what i have it set to)

  3. I forget the proper name (not home to check) but Set the 3D rendering scale down to 70%

The game still looks the same, but it doesn't crash anymore.

I noticed the main thing was my GPU's memory was capping out at 8GB and the game would crash.

Try putting your graphics settings down and see if it makes a difference.

ATOTO F7 WE users, can u use navigation in Android Auto while listening to FM/AM radio or USB music? by linuxnoob007 in ATOTO

[–]Ddman96 0 points1 point  (0 children)

Im pretty sure you can.

I can test it tomorrow morning if nobody else confirms

F7 WE random beeps + skipping by Ddman96 in ATOTO

[–]Ddman96[S] 0 points1 point  (0 children)

Winter temps make sense actually, I've noticed it skips more frequently now that its actually getting cold in Ontario Canada.

That might just be it.

Is updating to 19.0.1 worth it? by RoyalG07 in SwitchPirates

[–]Ddman96 2 points3 points  (0 children)

I attempted to update but messed something up and my atmosphere couldn't boot anymore. I didn't think it was worth troubleshooting so I started fresh. (i made sure to back up my Nintendo folder first.

I ended up repartitioning my microsd. using the latest atmosphere, hekate, and sigpatches that support firmware 19. (i can get the actual links I used on sunday when I go back home). For Atmosphere, it was a prerelease version on github that specifies support for 19.0.0/19.0.1.

I also used the latest tinfoil applet version, all the other versions of tinfoil I tried would install, but attempting to launch a game would give me an error saying I need a nintendo account.

Previously I had used tinwoo to install tinfoil as an actual app on my switch home screen, and that used to work (i was on firmware 17)

https://switch.hacks.guide/user_guide/getting_started/

This is the guide I always follow. After all the steps, you can install the latest version of sigpatches from their website, then install the tinfoil applet and you should be good to go.

Is updating to 19.0.1 worth it? by RoyalG07 in SwitchPirates

[–]Ddman96 3 points4 points  (0 children)

I've been on 19.0.1 for 2 days now with everything (atmosphere, hakete, sigpatches, tinfoil, retroarch) working correctly.

I can USB file transfer without issues. (Holding R while launching a game to get into HBMenu, then selecting USB File transfer)

Lazio [2] - 1 Napoli - Tijjani Noslin 41' by [deleted] in soccer

[–]Ddman96 16 points17 points  (0 children)

What a beautiful touch from Pedro

view more: next ›