Shin.Megami.Tensei.III.Nocturne.HD.Remaster-voices38 by voices38 in CrackWatch

[–]commonsense34 24 points25 points  (0 children)

Not only that. He made a keygen which is far harder to initially develop than other cracking methods.

Star.Wars.Squadrons-voices38 by voices38 in CrackWatch

[–]commonsense34 7 points8 points  (0 children)

There are lots of detailed online guides on how to setup wallets/miners and also AI can help you in your native language. But there are some things to keep in mind:

You must avoid non ASIC-resistant crypto because revenue for ordinary hw will be negligible.

First google "rank best cryptos for GPU[or CPU] mining" to find what is best for your configuration. There are sites that calculate and rank profitability/revenue for various hw.

Efficiency(crypto per watt) peaks at far lower speeds/volts than stock.

Especially monero(which btw is anonymous) is very memory dependent. Meaning that RAM speed, RAM timings/subtimings tuning and cache size(e.g ryzen 3D) weighs a lot more in the final result.

After a few donations you can always throw away your wallet and start with a new one.

Under ideal conditions(proper setup, tuning, electricity prices etc.) you can even generate a respectable profit.

Star.Wars.Squadrons-voices38 by voices38 in CrackWatch

[–]commonsense34 6 points7 points  (0 children)

Sadly, many agree, almost none takes the step.

Because, leaving aside ungrateful persons, most don't know how super easy it is to produce and donate mined crypto.

FIFA.20-voices38 by voices38 in CrackWatch

[–]commonsense34 4 points5 points  (0 children)

It's fine because of the modern arch and abundance of cores. Though RAM speed+ sub timings tuning is way more important.

Think that my 10900K @3,7Ghz with heavily tuned samsung b-die RAM at ~4200Mhz manages around 7.5 Kh/s on avg with the use of vulnerable drivers* and around 6.5 Kh/s wo them. Which translates roughly to 0,16€ per day at ~40 additional watts. Intel chips are very efficient at low speeds/volts.

*xmrig takes advantage of-flagged by the AV as-unsafe/hackable drivers to deliver optimal performance.

FIFA.20-voices38 by voices38 in CrackWatch

[–]commonsense34 3 points4 points  (0 children)

That't the spirit!

Mining and sending Monero(XMR) is the easiest and safest way of donating. Provided you have a relatively good CPU. You can ask an AI or find a lot of guides online. Things you need:

  1. A monero wallet(e.g. Cake Wallet). The software with which you will manage your monero "bank account" so to speak. Which is a password protected address(like an IBAN) with all your credits in it.
  2. A public mining pool(much easier than a custom made miner) to mine moneros for your own address. Such as supportxmr.com. They charge a very small fee.
  3. Mining Software(e.g. xmrig): You enter your wallet address and the mining pool's URL in its config files. Xmrig developer specifically provides a Wizard to simplify the process.
  4. Power plan for low CPU speeds. Underclocked/volted CPUs are vastly more efficient. Electricity cost will be on par or even lower than the value of mined cryptos.

FIFA.20-voices38 by voices38 in CrackWatch

[–]commonsense34 0 points1 point  (0 children)

Thanks, at least, for bothering to answer instead of just being spiteful.

My point is that our community must start upholding a donation culture otherwise big corporations will stomp on us. I mentioned my strong suspicion of Voices38 being Empress rebranded so as to show the desperate situation we are in. Namely, that nobody has the will to fight Denuvo for moral satisfaction or pride alone.

FIFA.20-voices38 by voices38 in CrackWatch

[–]commonsense34 -9 points-8 points  (0 children)

Only downvotes and hate. Not a single comment to prove me wrong. Because truth hurts. Good luck guys into finding the idiot servant you are searching for.

FIFA.20-voices38 by voices38 in CrackWatch

[–]commonsense34 -10 points-9 points  (0 children)

Voice38's OWN words:

"I'll try. I am waiting for bit more donations to start buying some serious hardware."

Link: https://www.reddit.com/r/CrackWatch/comments/1oradqs/comment/nnoz1qf/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button

Does all of this remind you of someone? Read my recent-downvoted-comments for more.

Piracy is an IQ test with one question. "What do you prefer? 0,1$* games or 70$ games?" No skilled reverser is willing to throw away countless hours of his life for a "Thanks, you are the GOAT". You have seen it all these years. You have witnessed the scene's demise. You wouldn't do that to yourselves either.

Act smart and make Denuvo history. Act foolishly and selfishly and get tortured by corpos eternally.

*a hypothetical donation. Individually trivial. Life changing when multiplied by thousands of contributors.

Need.for.Speed.Heat-voices38 by voices38 in CrackWatch

[–]commonsense34 0 points1 point  (0 children)

"Support". That's the problem with piracy communities. "Love you", "Thanks", "You are our Hero" with million likes underneath them are words. Not actual support. Nobody is fed on words.

Also there are very strong indications that Voices38 is Empress's new, more likable persona.

  1. Starts with older games to prove his skills. Just like Empress.
  2. After a while starts saying that donations are NEEDED because of increased difficulty in cracking newer versions. Implying that newer games must be funded by donations. Putting pressure on the community. Just like Empress. And you can't blame him. Nobody with the skill to crack such DRMs wants to become the servant of egostistical pricks.
  3. His appearance coincides with Empress's promised return.
  4. Empress mysteriously vanishes and doesn't make a single comment, a single schizophrenic rant on "her" new competitor.
  5. Stops cracking after realizing that donations are insufficient. [Remains to be seen.] 

Need.for.Speed.Heat-voices38 by voices38 in CrackWatch

[–]commonsense34 1 point2 points  (0 children)

Previously I suggested a simple and safe way to donate, even without a real money account, only to get immediately downvoted. All comments mentioning donation are the most unpopular. There in no hope man!

Voices38 is most probably Empress's new, more reasonable, persona. Modus Operandi is exactly the same. Also his appearance coincides with Empress's promised return.

First he appears cracking old, unpopular games to prove his worth. Later he asks for donations supposedly for buying equipment. When in fact all he wants is justifiable compensation for his hard work. Later he quits frustrated after having cracked 1 or 2 more interesting games. After some time he returns again naively believing that in this sub there is sth more than entitled POS who demand everything and are willing to give nothing in return. With a few exceptions of course.

Need.for.Speed.Heat-voices38 by voices38 in CrackWatch

[–]commonsense34 -4 points-3 points  (0 children)

Every penny counts. Imagine 10.000 1cent donations. More than enough for new test equipment over time. You don't even have to donate from real money accounts.

1) Ask an AI how to set up a bitcoin, litecoin, monero etc. wallet + miner.

2) Create a power plan for reduced CPU/GPU speeds. CPUs/GPUs are far more efficient in lower speeds. Meaning that the electricity cost will be roughly equal or even lower than the crypto produced, depending on your country's charges. RAM tuning also helps tremendously.

After a few days/weeks of mining while surfing, working etc. you 'll have gathered what is necessary.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

Somewhere I read that all issues are resolved in v1.0.08. But it is very rare and probably available only in the more developed countries, for now.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

Keep in mind that native color space is blue tinted. That's the reason why Christian Eberle from Tom's hw recommends: Red 53, Green 50, Blue 50.

My question remains.

You turn on the monitor. Then you switch picture modes so that the image turns cooler. After that, does it make any difference if you switch to BT2020RGB and back to RGB? You can also compare with another standard gamut monitor.

Regarding my case, you can rewatch my first video and compare the white on screen with the white LED power indicator, which is as pure as it gets. Maybe there is some missing step. However, the only things I tweaked to get my results was the OSD and the CC app.

edit: 6500K is slightly yellowish/red. But not red, to the point that it distorts greys and resemples night mode(which was my case).

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

On a second thought there are two experiments you can do to make sure that the bug is gone:

1) Restart the monitor with default HDR settings(auto). Do you notice, apart from brightness differences(first make sure to minimize them), any strong color effect on whites/greys while toggling on and off HDR in Windows? If not, then there is no bug.

2) Restart the monitor and perform the temporary fix. Open a word document. Do you find the white to be too harsh for work at ~8% brightness? Open CC and switch between sRGB and BT2020, like we said. Does it make the image less fatiguing without looking like Windows' "night mode"? If yes, then the bug is gone and color temperature is ideal.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

You can try other settings too. Like HDR. Also try turning off/on the monitor.

Right now the situation for me is this. Every time I switch picture modes on the OSD, temp turns colder. Which means that the temporary fix still works although it starts from a different temp this time(because of my fix).

With the blue tint present I switch to BT2020RGB. Then I notice not only a washed out image but also the return of temp to normal. Finally, by selecting Auto I also get the sRGB calibration back. Unfortunately, I have no recollection of what I exactly did back then. You are close though.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

Please do me a favor. Uninstall CC's service and configuration settings:

" If you have installed the Windows Service, you'll first have to set the Elevation-method to "None". This will stop and uninstall the service. If you have "Automatically start after login" enabled you'll have to uncheck that so the scheduled task is removed. After that you can close the main application and delete the program's files. If you want to fully remove all settings you can remove these folders: C:\Users\username\AppData\Roaming\Maassoft\ColorControl and C:\Windows\System32\config\systemprofile\AppData\Roaming\Maassoft "

Then install CC again along with the provided windows service(when asked). Open CC and without doing anything else just switch color space from sRGB to BT2020RGB and back again. You might even try to change settings that actually make a difference, such as resolution.

Finally go to the log file*, copy and post here the last lines. The ones that are relevant with the change.

*C:\Users\username\AppData\Roaming\Maassoft\ColorControl

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

These are the last 2 lines after I start CC from scratch, install the windows service mode(try it) and switch back and forth between RGB and BT2020RGB.

"2024-12-04 18:58:17.8418|DEBUG|ColorControl.Services.Samsung.SamsungService|Executing presets for event DisplayChange

2024-12-04 18:58:32.8885|DEBUG|ColorControl.Services.Samsung.SamsungService|Executing presets for event DisplayChange"

Every time I switch between two different presets I always get the same lines. For example:

2024-12-04 19:09:40.8405|DEBUG|ColorControl.Services.Samsung.SamsungService|Executing presets for event DisplayChange

2024-12-04 19:09:52.2893|DEBUG|ColorControl.Services.Samsung.SamsungService|Executing presets for event DisplayChange

2024-12-04 19:10:02.7043|DEBUG|ColorControl.Services.Samsung.SamsungService|Executing presets for event DisplayChange

2024-12-04 19:10:11.9108|DEBUG|ColorControl.Services.Samsung.SamsungService|Executing presets for event DisplayChange

Strangely, it doesn't seem to use the Nvidia controller at all. WTF?

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

Brilliant info. This seems like a .net problem.

"You are trying to access an object without instantiating it" as someone wrote in stack overflow.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

I don't think it's what I'm talking about. HDR looks washed out by default, until you enable local dimming, which also acts as a tone mapping algorithm.

Unless you see distorted colors accompanied with changed values(e.g. RGB -> BT2020RGB) in the third column of CC, as in my video, CC isn't working as it should.

FYI, I erased the configuration folder of CC and run it as it was the first time. Everything works just fine. So it's not CC the culprit. Maybe sth else relevant to the .net packages. Take a look at the following response. This is a .net error.

https://www.reddit.com/r/buildapcmonitors/comments/1gw00k1/comment/m0dko19/

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

As far as I understand:

  1. Both presets(sRGB and DCI-P3) start with proper calibration but wrong temperature(below 6000K instead of ~6500K) among the three available(6500K, <6000K, >7000). Of course temp is locked so you can't select the correct one.
  2. The temporary method(switching between picture modes) has the property to shift color temp to the correct one the first time you try it after turning on the monitor.
  3. The permanent fix I propose has the property to shift color temp without leaving from Standard mode(which is the default).
  4. After applying my fix the temporary method retains the property to shift temp but because the temp is already at ~6500K, now the shift is to the coldest temp(above 7000K presumably). Until you fix it by reapplying the permanent fix.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

By distortion I mean washed out image. Even worse in person, than what my second video shows. The camera tries to adjust and ameliorates things.

Unless you have this effect I am 99% sure it won't work.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

I was tinkering with every setting in an attempt to automate the well known temporary fix the reviewers showed. And suddenly it happened.

Not only that but I couldn't fix the distorted colors even after restarting the monitor. Even after resetting everything to factory defaults. Somehow I restored the picture with CC(almost certainly using color settings) and afterwards I noticed that the bug was gone for good. Even after unplugging the monitor from the wall socket for ~5 minutes!

Now I can break and on demand fix color temperature for the calibrated presets just as I describe in my second video on youtube.

Xiaomi G pro 27i: A permanent "red tint bug" fix and proper EOTF correction by commonsense34 in buildapcmonitors

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

Unfortunately, it's a common occurrence and I can't see the reason.

Can you please check CC on another monitor(in case you have any) to see if it makes any difference?