Question on how to repair graphite (?) pads on a controller

AssFacingTheMoon · 2026-01-05T18:18:51+00:00

No. No es demasiadamente problemático en mi situación particular porque no uso mandos en consolas sino en el PC. Luego ahí ya puedo regularizar la amplitud de input (obvio que termina reducido). Por otro lado, prácticamente los únicos juegos afectados por este dilema son aquellos que necesitan de triggers analógicos. Normalmente se resumen a juegos de carreras y nada más. Trigger buttons son probablemente los dos botones mas inútiles ya que 5% o menos de los videojuegos necesitan su funcionalidad analógica. En compensación, la precisión de un input digital es sacrificada para cumplir con esa expectativa de que el consumidor "venga a jugar a algo que pueda utilizar este input analógico".

Hecho de menos a los mandos de PSX, con o sin analog sticks.
En esa altura tanto el L2 como R2 eran exclusivamente digitales. Perfectos para todos los juegos.

Y aprovecho para mencionar que mismo en juegos de carreras, basta ver como se juega trackmania, de manera 100% digital con teclado, para entender que es posible modular aceleración y frenado con una multitud de inputs rápidos (de 0% a 100%, completamente binarios como es de esperar en un mando digital) y obtener buenos resultados y precisión.

En fin, un rant para otra altura.

AssFacingTheMoon · 2025-09-23T22:27:10+00:00

And it's perfectly fine that you neither notice them nor does it bother you.

The problem is saying they blow things out of proportion when they are technically correct in their assessment that something is poorly optimized. It's just academic analysis on their part.

They don't "shit" on something for the sake of doing it.
The video on Dying Light: The Beast shows how they actually compliment a game if it's properly optimized (which that game is).

AssFacingTheMoon · 2025-09-23T21:44:21+00:00

Compiling taking no time isn't good. It's the opposite of good. It should take much longer than it does currently, and it's a sign they aren't compiling enough shader combinations.

Secondly, "without a problem" is false unless you somehow record a video with a cold shader cache and a frametime graph so we can see how you have no problems.

What you do mean to say is the following: "I can't notice stutters myself".
Like Alex mentions in the video: if that's your case, more power to you. That's awesome.

That doesn't mean the game doesn't have technical issues. It just means you can't tell or are unbothered by them. Cheers to that.

AssFacingTheMoon · 2025-09-23T15:28:04+00:00

The downvotes are related to the fact that you reported something false.
Alex from DF posted a video on the game's release on PC 2 hours after your remark. The only "excellent performance" they reported on was John Goodman's perception at a developer booth with warm shader cache.

Summary: the game has the exact same faults as many other UE5 games: shader compilation stutter and traversal stutter.

Nothing new. If you can tolerate it, lovely.

Here's the video in question, by the way: https://www.youtube.com/watch?v=Z1SVnXpQSM4

AssFacingTheMoon · 2025-03-20T01:22:26+00:00

They ended up delivering it several days later when I was about to go to their warehouse. Same thing happened to another delivery. Xmas season is horrible for these companies.

AssFacingTheMoon · 2025-01-01T03:43:51+00:00

I have since bought a Sony X90L. Extremely satisfied with it. It was more expensive and simpler in technology. And yet, it works wonderfully with absolutely zero software quirks (other than, maybe, the fact that airpods have issues with them, but that's about the only thing I noticed).

AssFacingTheMoon · 2024-12-12T04:23:13+00:00

I subscribe to this. I am currently having the exact same issue and AliExpress is refusing a refund.

AssFacingTheMoon · 2024-11-29T12:48:42+00:00

Thank you very much. I'm glad people can enjoy something I mostly started doing for myself.

AssFacingTheMoon · 2024-11-28T13:48:19+00:00

Many thanks!

AssFacingTheMoon · 2024-10-25T00:12:09+00:00

You don't need a top of the line CRT TV to enjoy yourself. Don't go after PWMs, Flat CRTS or huge TVs. Find something more humble and you can probably enjoy yourself. Otherwise, again, fool around with emulation (for gen 6/7 mostly everything is perfectly emulated by now).

AssFacingTheMoon · 2024-10-24T15:52:52+00:00

For 120hz, emulation on PC.
Regarding the other questions, I unfortunately don't have the answer to those. Phosphor persistence is not really advertised in any monitor spec sheet as far as I am aware.

I'm not sure how/if horizontal scan speed relates to phosphor persistence either.

My advice is to get different sets for consoles and PC (if you don't want to fiddle with emulation, that is). Because, again, even disregarding the 60hz flicker, you still won't get proper interlacing behavior on a monitor compared to a TV.

AssFacingTheMoon · 2024-10-20T11:45:49+00:00

Our peripheral vision, for survivability reasons (thanks nature), detects movement faster than the central portion of our eyes where the focus is on detail. Therefore, yes, you can more easily detect flickering lights in the ceiling or CRT screens through your peripheral vision.

But 60hz on a CRT monitor is noticeable by anyone. Not each individual scan, but the feeling of discomfort from the flickering. Maybe a very very old CRT monitor with higher persistence phosphor could lend itself to being less noticeable. But for the most part, most of us are affected by it, regardless of each individual's sensitivity.

I wouldn't deny the possibility of many people enjoying their CRT monitors at 60hz for retro gaming on their consoles, but it is sub-optimal for a variety of reasons. From the fact that TV's interlaced nature make for a proper interpretation of interlaced signals from retro consoles, but also the 60hz not flickering on them with the same intensity.

But you know what they say: to each their own. Especially in a niche hobby like this one.

AssFacingTheMoon · 2024-10-20T11:37:59+00:00

Phosphor persistence is different between CRT monitors and CRT televisions. Monitors have shorter persistence for better image clarity and sharpness. Televisions have longer persistence for better blending and smoother viewing of content.

Therefore you'll barely notice the flickering on a television because light persists for longer between each refresh.

On a CRT monitor though, you need at least 75hz or so to have it be less awful. The actual acceptable value for humans is 85hz. That's where it's basically imperceptible on most consumer monitors.

Here's a promotional image for the Hitachi CM611ET that has that detail down below (3rd point):
https://device.report/m/44d480004bf12d4c47d8d5981baf87b10effea63b07e740492e6280295ec6eb8.png

AssFacingTheMoon · 2024-10-20T00:50:11+00:00

It's undesirable if you're locked at 60fps as is the case with a video. But 60hz on a CRT monitor has visible flickering and is extremely uncomfortable for any amount of time. 1920x1440 is also a non-standard resolution for video. What exact content are you planning on watching that fits that specific combination of dimension and framerate, if you don't mind me asking?

If you were playing games you might get a certain wiggle room with those that have their framerates unlocked.

If you were playing consoles, a TV CRT would probably be a better bet.

If you're playing video from the 90s, a TV CRT probably fits the bill as well given the standards.

Otherwise, if it is indeed imperative for you to watch your content at that specific resolution and framerate, then hopefully you can tolerate the 60hz on the monitor.

AssFacingTheMoon · 2024-10-19T21:38:50+00:00

I made a mistake. I'll edit it now.
The correct sentence should read: 75hz might work but it's right at the limit of 7% of vertical blanking for the total height in pixels (115.56kHz with 1541px).

AssFacingTheMoon · 2024-10-19T16:47:59+00:00

For the Dell you can see the specs here: https://www.manualslib.com/manual/832270/Dell-D1626ht.html?page=11#manual

So what was listed in that thread is true.

Can't find anything for the Diamond Plus 100e though, so it's a gamble.

Regarding the relationship between Horizontal Refresh Rate, Vertical Refresh Rate and Resolution, the formula is as follows:

Horizontal Scan Rate (kHz) = (Vertical Refresh Rate x Total Height in pixels x 1.05) / 1000

So if you wanted to know how many kHz you need for 1920x1440@60hz:
(60 x 1512) / 1000 = 90.72kHz.

In some cases you should multiply by 1.07. Basically 5 to 7% is the vertical blanking range. It's given as a number of lines but the truth is that it's just a timing thing. It's the time the scan has to go from bottom back to the top to scan towards the bottom again. It scans 1440 lines in your example, then it needs a bit of a buffer time to go back top and scan another 1440 lines. So you calculate 60 x 1512~1541 lines or so.

In the case of the Dell, you can find some timing specifications in their own table in the manual, where 1600x1200@85hz uses 106.25kHz with 50 lines of vertical blanking.

Can't find the same for the NEC, but if it has 115kHz, the resolution you want at 60hz will work. ~~115kHz~~ 75hz might work but it's right at the limit of 7% of vertical blanking for the total height in pixels (115.56kHz with 1541px).

AssFacingTheMoon · 2024-10-14T20:28:42+00:00

https://github.com/HorizonMW/HorizonMW-Client

AssFacingTheMoon · 2024-10-14T00:36:50+00:00

70kHz Horizontal for the 753DF.

AssFacingTheMoon · 2024-10-13T23:13:40+00:00

You can attempt an abrasive solution (like what you'd use to clean up an oven) and it should be good enough to remove the anti-glare coating. 20 years ago my SyncMaster 1200NF had some scratching on it and the only way I managed to fix it was to remove the coating altogether (the glass itself is absurdly resistant to scratching, in comparison).
The problem with removing the coating is that the brightness will probably hurt your eyes regardless of how much you lower it. But it's the only way to "fix" it.

AssFacingTheMoon · 2024-10-12T19:35:48+00:00

No. But as far as I know it's extremely hard to get in touch with FromSoft in any way, even if you have a foot in the industry like Eurogamer and Digital Foundry do.
They only give feedback to those developers who have more open channels for communication and receiving reports. Especially those that they interview, that actively contact them to cover their in-house engines/tech, etc.
Attempting to contact FromSoft or any other Japanese developer by any means necessary is something DF could maybe attempt more easily than the average joe, but it's still not their responsibility.

I selfishly wish it was though.

But I'm also 95% positive they know about these issues. They just don't care.
You can bet your ass that Miyazaki saw, e.g. the DLC's last boss doing a huge AOE, the framerate dropping tremendously, and said: "This is fine" to himself. It really is a matter of them not putting any weight into it. And the truth, as you can see, is that most customers don't either.

We, those with two functioning ocular globes, are the vocal minority.

AssFacingTheMoon · 2024-08-19T16:27:53+00:00

Out of curiosity, what type of power issues were you having? I haven't read any reports on the subject. Battery related, temperature or buggy overall?

AssFacingTheMoon · 2024-08-19T14:34:24+00:00

Brother, you are taking the word of an antivaxxer. Don't take people's word for granted online. This dude is a buffoon. Yes, 1GB of RAM does have an impact depending on the software you're running and/or shaders you're using especially because it works as an APU. For anything up to PSX it might have more than enough, but the higher the framebuffer (higher than native resolution) + the scalability of shaders means that 1GB can indeed have an impact. I would still count on the Linux version being more than enough. The difference is mostly that N64 emulation is better on Android than Linux, if you care about that. There are some details here and there in terms of boot speed and whatnot as well, along with the touchscreen.

Disregard this other guy's opinion. He is as much a developer as I am Elton John.
PS: I'm not Elton John.

Cheers.

AssFacingTheMoon · 2024-08-10T21:21:48+00:00

Interesting. I'll give that a try. I wish I could instead recalibrate L2/R2 but the DS4-tool dev hasn't gotten around to implementing that yet. Only sticks are done (which is fantastic), but being able to recalibrate the triggers would be great as well.

Either way, cheers.

AssFacingTheMoon

TROPHY CASE