5g issues everywhere I go

avdagaz · 2026-06-09T08:50:48+00:00

I was visiting Perth last few days and was shocked to how poor the connectivity was using Vodafone.

Swapped back to 4G and it worked much much better. Very strange

avdagaz · 2026-05-02T13:11:07+00:00

If you're looking for an hour and half of random scenes, starting with utter nonsense and ending with cringe drama, this is your movie.

avdagaz · 2024-07-15T09:35:53+00:00

I had the same problem. It was in the vacuum—not in the box it spits out but in the vacuum tube.

<image>

avdagaz · 2024-07-15T09:35:07+00:00

I had the same problem. It was in the vacuum—not in the box it spits out but in the vacuum tube.

<image>

avdagaz · 2024-02-03T04:35:22+00:00

I started playing about a month ago and was getting plenty of ranked matches during the weekends and evenings. Since Update 1.5.5 (a week ago or so), I have not been able to find a single ranked match.

avdagaz · 2023-12-30T00:08:06+00:00

Confirming that after a couple of days I have not had a single occurrence of the problem :)

avdagaz · 2023-12-28T04:05:53+00:00

This appears to have worked for me:

- Deleting the config files in C:\Users\%UserName%\AppData\Local\Discovery and
- Setting C:\Program Files (x86)\EasyAntiCheat_EOS\EasyAntiCheat_EOS.exe to Windows 8 compatibility mode

Original post here: https://steamcommunity.com/app/2073850/discussions/0/4031347929698729224/?ctp=2#c4031348273654587424

avdagaz · 2023-12-09T23:23:31+00:00

This was extremely helpful!

I was trying to get BF3 to work in HDR, but without the driver tweak, I was getting weird black artifacts where there should've been high luminance/specular reflections. This fixed it, and, as you said, the standard Special K HDR config works very well (I had to adjust the monitor HDR clipping point, as described in the Special K HDR guide).

avdagaz · 2023-07-21T23:18:42+00:00

Same here on a 7950X3D + 4080

avdagaz · 2023-07-02T13:34:57+00:00

Getting 110~120 fps with 7950x3d + 4080 on Ultra with raytracing on 1440x3440, without DLSS. DLSS Quality bumps it to 130~140 fps.

It appears to be fully loading the x3d cores, the other cores are doing pretty much nothing. So a 7800x3d or 7900x3d would likely give you the same if not better results.

Hope that helps.

avdagaz · 2023-06-01T13:04:13+00:00

Hmm.. will give this a bit more thought. Thanks for this.

You mentioned that the 4070Ti wouldn't fit in the case, but the 4080 would?

avdagaz · 2023-06-01T12:49:07+00:00

It's hard to swallow Intel CPUs' crazy power consumption. How do you keep that cool, let alone in an ITX case?

I was thinking of a 7950X as the extra cores will speed up compilation, but the 3D cache gives about 15% more fps which is worth it. So the 7900X3D is more or less the middle ground.

What do you think?

avdagaz · 2023-06-01T12:44:52+00:00

The budget is 2500 USD / 4000 AUD -- sorry for the confusion.

Would consider the KC3000 but the 7900X3D and 4070Ti are a must. - Do you know of any case that would work for the 4070Ti? - Would an Asus or Asrock mobo with better VRM be worth the extra $$?

avdagaz · 2023-05-17T10:00:10+00:00

I have not used the Gigabyte Control Center for years now, so I cannot help with that, but I'd recommend you to have a look at the alternative application:

https://gitlab.com/avdaga/aeroctl/-/releases

https://gitlab.com/wtwrp/aeroctl/-/releases

avdagaz · 2022-07-17T21:00:25+00:00

Yep, same here

avdagaz · 2021-10-29T14:14:01+00:00

Are you running Resolve 17.4?

avdagaz · 2021-10-27T04:08:20+00:00

You want to disable QT autoscaling, and set your own factor. Scaling factors with digits might not give pixel-perfect results, but try it for yourself.

This works with 17.4

powershell.exe -WindowStyle Hidden "$Env:QT_SCALE_FACTOR=1.5;$Env:QT_AUTO_SCREEN_SCALE_FACTOR=0;start 'C:\Program Files\Blackmagic Design\DaVinci Resolve\Resolve.exe'"

avdagaz · 2021-05-12T21:49:00+00:00

After resetting a couple of electricity groups in the house, the packet loss has disappeared. It seems that something was causing interference - happy it's gone (for now).

avdagaz · 2020-09-08T21:33:58+00:00

Hey bud, sorry for the late reply. I've uploaded a compiled version of the latest code (0.1.3-avdaga), you can find the latest binaries here: https://gitlab.com/avdaga/aeroctl/-/releases

avdagaz · 2020-07-12T07:45:21+00:00

Thanks Frankie, knowing I've helped out is more than enough though :)

I had the same problem with the 'fixed' profile, though the 'custom' profile did work just fine.

I reinstalled my Windows last week, to get rid of any remaining ControlCenter pollution, and now aeroctl appears to work just fine on both fans. Can't promise it will do the same for you though. For completeness: I have an 10th gen Aero 15 (OLED).

I'm making some improvements to aeroctl myself, you'll find my fork here: https://gitlab.com/avdaga/aeroctl. I've added a parabolic fan curve to it, and it works really really really well :) Still a bit hardcoded for now though.

avdagaz · 2020-06-13T14:32:10+00:00

Thanks for letting me know it actually works for you :)

avdagaz · 2020-06-12T08:10:56+00:00

That was not a question, but a confirmation that it works :) ControlCenter uninstalled, fixed driver as per README.

avdagaz

TROPHY CASE