I bought a 3C509TP recently to put in my 486; the only issue I had was dirty contacts in the ISA slot. After I sorted that out, it worked perfectly.

You can draw single pixels. I'm not sure where whoever told you that got it from.

And create single-pixel images. My most used application of Paint by far is creating single-pixel PNG files to work around the fact that "solid color" is not an option for lock/login screen backgrounds.

But can you resize without antialiasing, and does pasting trigger antialiasing?

There's this https://www.windowsphoneinfo.com/threads/why-does-resizing-m... (made confusing by the next person talking about Paint 3D, a different application) and this https://learn.microsoft.com/en-us/answers/questions/3991946/... (made confusing by the person being an artist and talking in peanut butter metaphors).

There's some suggestion there that shapes (including lines) are separate entities from pixels. Wikipedia references a now-deleted answers.microsoft.com version of the first question https://web.archive.org/web/20250203164656/https://answers.m... with a couple of people saying that resize is useless. Wiki also says "re-copied" images blur, which is why I wondered if that meant pasting. Also this: https://learn.microsoft.com/en-us/answers/questions/5673783/... a complaint that the tool for drawing pixels doesn't indicate exactly which pixel it will draw to.

I can't reproduce any of those issues. When drawing the indicator snaps to a pixel, so it's perfectly clear where it's going. When I draw a line, it's pixel-perfect when moving the control points, likewise after it finalises. And when I copy a section of the image and paste it back in, it's pixel-perfect as I move and when I finalise. There doesn't seem to be a true resize; all I seem to be able to do is change the size of the canvas, which doesn't add any kind of aliasing.

But I've only used the program for less than 5 minutes, so maybe it's configured differently?

Yes, resizing within Paint preserves pixel-level color. I just resized a single pixel dot to about 14x25 without aliasing.

I don't know why you are so concerned, but it's incredibly easy to test these questions if you really want to know.

I've been using Turbo Pascal and Turbo Assembler on real vintage hardware in my attempt to do the Roguelike Tutorial. I'm still getting to the point of finishing part 1 because I decided to go hard mode and use the graphics coprocessor to draw 16x16 tiles instead of text mode.

You don't want to simulate the god-awful flicker my CRT has at 60Hz.

The hysteresis of the phosphor makes this a non-issue in reality. 60Hz looks great on a CRT when the input is a game console or VCR from the era.

Maybe you mean screen tearing, bad deinterlacing, etc. caused by software running on a PC?

No, I mean the screen noticeably flickers when displaying a static image at 60Hz progressive.

I mean... are you bobbing and weaving your head while rolling your tongue or what?

I get that CRTs aren't perfect, but I'm not sure how else to reproduce what you're calling "flicker".

perhaps was 60hz interlaced. I had memories of my first CRT monitor only allowing to do 1024x768 in interlaced and doing a very obvious flickering. But was flicker free at 800x600 and lower resolutions.

You can increase the refresh rate until it goes away. I don't think anyone notices flicker at 80Hz or so.

Yeah, there's no visible flicker at 70Hz or higher.

My CRT did 1024x768@85 just fine.

The flicker is fine, especially with 240p and 480p.

You do want to simulate it, because it's the only way to preserve the original motion quality of games designed around a fixed 60 fps frame rate without changing the gameplay or adding latency.

Yup, definitely the Rust users who are toxic. Totally not the people going into every thread about Rust to tell everyone about how toxic Rust users are. Nope.

> Totally not the people going into every thread about Rust to tell everyone about how...

That's the kind of straw man I was talking about. Aggressive downvoting and being butthurt about the slightest criticism; that's not normal in other communities at all.

But it is true, you see way more comments complaining about "the toxic Rust community" than said toxic community itself. At some point it just becomes annoying and tiring...

In terms of "finished" projects, I wrote a program that generated new, empty, histories for Crusader Kings II. It could create new cultures, religions, and titles, and did a simple simulation of them spreading over the map.

I also wrote a server-side plugin for Assetto Corsa that monitored track limits, and could integrate into the program the league I was in used to find the pace of drivers for when we needed multiple servers.

In terms of "finished" meaning "I stopped working on it", I did write a compiler for a static concatinative language.

They're a long-time anti-Rust zealot. This is the sort of nonsense they've been coming out with for years.