/vr/ - Retro Games

>>9128693
That image shows a difference between bilinear and nearest scaling more than anything.

You run into a mis-sized image for your display if you just use nearest + integer, however. You can cheat this by using nearest up to a certain level and then bilinear past it, and it will naturally look like Integer yet at a proper size. The pixels will be so softly rounded that you won't notice that it's not truly pixellated. RA has a shader preset called "sharp bilinear" that's just this, more things should have it.

>>3517767
pic related, probably

>>3517775
puss isn't necessary, nips are mainly for references as to where to cover up stuff

>>3029012
>original rgb
No, you have fucked up the scaling (pic related).

>>2890901
Why is integer ratio so hard for you idiots to understand? Look how shit the dithering is in your first image. Nearest neighbor is unfairly considered ugly because people keep doing it wrong.

>>2888379
Integer ratio you fucking retard

>>2852561
The left pic is doubly incorrect. Not only is the aspect ratio wrong, but also it is using non-integer ratio nearest neighbor scaling.

>>2852570
The only uncommon things are the CRT and the parallel port controller. And even without them latency is very good.

>>2775151
>>2775154
>most got rejected
Good, because you fucked up the scaling. And if you really want it at a non-integer ratio size, first scale it nearest-neighbor to a high integer ratio, and then scale it down with Lanczos or whatever resampling filter you like.

>>2772473
>>2772486
What is so hard about integer ratio scaling? It looks crap because it is scaled wrong.

>>1929626

Yes, nearest neighbor is always optimal no matter what.......

>>1181676
Image clearly demonstrates what you're doing wrong.

>>884309