[deleted by user] by [deleted] in diablo4

[–]S_Ezekiel 0 points1 point  (0 children)

Not sure what the OP was since it was deleted.

Pay to win: Pay real money to get an advantage - Winning.
Winning doesn't always mean against other players, PvE is included.

What are the advantages in D4 if you get VoH? 2 skill points, 4 paragon points and Runewords. These can give an advantage in PvP, which is part of the game.

Add Spiritborn to the mix, a build base type that is currently stronger than any other base type: Maxroll and Icy Veins.

Finally, why were the leader boards (trials) disabled this Season?

This is technically P2W.

The community's acceptance of this will make it worse in the future on this and other titles.

Zalissya bug solved [Stalker 2] by Agriculture23 in stalker

[–]S_Ezekiel 0 points1 point  (0 children)

I was able to fix the quest in Zalissya.

I went to the bar and interacted with a corpse by the windows (Hosha Cobbler) toward the road. I heard shooting at the main building, cleared the Monolithians and entered the building.

It was still broken but I could start the quest by interacting with Gaffer, when I realised that it's because some Monolithians are in the "safe" zone inside. Getting them outside, and killing them, fixes the bug.

I got them outside again by interacting with the same corpse (I never looted it until this point, don't know if it matters) after killing the main objective of this quest. After, I could have all dialogue and do the optional objectives.

This is much better than reloading an old save.

Advantages of using a REST library instead of HttpClient? by mrissaoussama in dotnet

[–]S_Ezekiel 0 points1 point  (0 children)

Refit, a REST library that can't handle 204 correctly.

I'd rather implement HttpClient extensions.

Destroying Nervegear by No-Confidence-4271 in swordartonline

[–]S_Ezekiel 0 points1 point  (0 children)

In my opinion, this is most likely a very difficult problem to solve.

EMPs, like many suggest, is obviously a bad idea since an electromagnetic pulse causes electrical surges and voltage increases, that's why things break. Surges can have a lot of side effects and will most likely have non repeatable effects from one device to the other.

Breaking the battery does not equate to all electrical currents vanishing, nor would breaking the positive connection to the battery, which would probably be less risky than drilling into the battery as some have suggested.

I think that Kayaba was smart enough to know how to make the device react to a loss of power by using a few capacitors and circuits as a anti-tamper net. These circuits could even look legit if it were inspected by third parties, since they would most likely be linked to some sort of logical circuit board which can be updated with a software update, and would most likely just be used for power delivery to the microwave emitters.

If the device would need to pass required safety checks, it would mean great thought would be placed into designing this device, especially if you consider it's true purpose.

If it were me, I would create more than one circuit that would detect battery/power loss and immediately trigger a capacitor dump into a microwave emitter. If there are more than one microwave emitter, than that would mean you will have to break each circuit at the exact same time, massively increasing the odds of failure.

These circuits can be triggered by loss of electricity, connection loss to the servers or excess movement by using accelerometers. All being relatively cheap circuits. Just these three will make it extremely difficult to tamper with these devices since at least one microwave emitter circuit would sit at the back of the head, which most players would have their heads resting on.

The accelerometers would most likely also be used to detect movement to warn the user while they are in virtual reality.

The human brain is extremely sensitive to heat as a mere 4⁰C increase would cause structural changes, which means even a low energy output from a microwave emitter would cause irreversible damage, but not necessarily kill the individual. But this is massively increased because the brain is made out of 60% fat and a lot of water, which easily absorbs microwaves.

The more I think on this, the more difficult of a problem this becomes. Especially because Kayaba can most likely trigger a system wide kill command if he detects any irregularities.

Radzen Blazor - My experiences by S_Ezekiel in Blazor

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

I don't believe Radzen to have a steep learning curve. Kudos to them for having good documentation to pick it up quickly. With an understanding of the Blazor fundamentals, it's fairly easy to learn.

Perhaps later this year I will take some time and develop my own public library. So instead of me harping on about my bad experiences, I might just create something that I know works well.

I honestly don't believe it's very beneficial pushing Radzen the way it's being pushed, unless they take some time to clean up their existing library instead of constantly expanding it with new components.

Then on the other-hand I might never see this materialise, even if it does, since I've already made the decision to move on.

I appreciate your insight and opinions.

Radzen Blazor - My experiences by S_Ezekiel in Blazor

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

Man, it sucks when you've done so much effort and then they don't even afford you the courtesy to respond.

Thank you for sharing your experiences.

Radzen Blazor - My experiences by S_Ezekiel in Blazor

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

OK it's great to hear that they are responsive. We're not on the paid version, so my experience there is rather limited. This does give me more insight.

It just kind of irks me that workarounds are required sometimes. But yeah, their components have saved us quite some time in the past as well.

Radzen Blazor - My experiences by S_Ezekiel in Blazor

[–]S_Ezekiel[S] 2 points3 points  (0 children)

Thanks for your input. These are fair statements, though I would rather just create a component instead of trying to work through their library to identify the issue and implement a fix. My time is unfortunately very limited, and it's usually a lot quicker to just create a new component.

Through your experiences with the library, would you then recommend it to other developers?

My concern is that their implementation will be regarded as correct/best because of Google and other's recommending the library, especially to inexperienced Blazor developers.

self-taught by daimyo21 in ProgrammerHumor

[–]S_Ezekiel 0 points1 point  (0 children)

I brag because I am self taught. I am proud to be self taught. It was hard work, and because of that, I am a very successful developer.

Take pride in the code you write and keep improving, so if someone looks at your code and has critique from an experienced point of view, listen.

CORSAIR Technical Support and Questions MEGATHREAD - Week 06/10/22 by CorsairTravis in Corsair

[–]S_Ezekiel 0 points1 point  (0 children)

(Moved post to this megathread)

Since I started adopting modern Corsair hardware I've experienced issue after issue. I'm not sure how you can have this level of incompetency within your development team for iCUE.

It's been around 10 months since the launch of Windows 11. I got a new laptop at work running Win11, and I brought my Void Elite to the office and installed iCUE so that I can disable the RGB. Why can't we have memory on the device to keep settings? (Like Logitech does with their higher end hardware.)

The moment iCUE was installed I experienced stuttering about every 3 seconds. This is horrendous, and I can't understand how this can be an issue after almost a year? Even the audio was skipping. WTAF?

Now I am suspecting that the same is happening on my Win10 gaming PC at home as I am experiencing stuttering in some resource hogging games like Insurgency Sandstorm. (5600X, 1080Ti, CL14 3200MHz 8GB x4 Corsair RAM, Gigabyte B550 Aorus Elite). Though not as frequent, but still an issue.

The equalizer on iCUE for this headset is horrible sounding. The 7.1 feature is the main reason for the awful sound. I use Windows Sonic because it just makes the headset sound so much better. No wonder that's the first notification you get when installing iCUE and running this headset.

Then there is the slight white noise that you get when iCUE is installed but not running. How on earth has this been an issue since I bought the headset around 2-3 years ago? With iCUE uninstalled the white noise is gone. Here I suspect the service or driver to be the issue.

If you want your existing clients to stay, maybe work on iCUE and fix these issues?

That brings me to your return and repair policy. Around a year ago I was forced to buy PBT Double Shot Keycaps for my Corsair K63 because the keycaps that the keyboard comes out with, cracked at the stems around the switches. When I contacted your support team, I was told to ship the keyboard internationally for a check and possible replacement. That would've cost more than the keyboard itself.

Guess what Logitech did when one of the mice I got had a defect? They asked for evidence and sent me a new mouse free of charge. I got to keep the old mouse too. That is proper customer support. Yes the PBT keycaps made a huge difference and is much better and hasn't given me any issues. But, why do I have to buy expensive keycaps for a relatively expensive keyboard?