[ / / / / / / / / / / / / / ] [ dir / animu / ausneets / kpop / leftpol / lit / tacos / vg / vichan ][Options][ watchlist ]

/tech/ - Technology

You can now write text to your AI-generated image at https://aiproto.com It is currently free to use for Proto members.
Email
Comment *
File
Select/drop/paste files here
Password (Randomized for file and post deletion; you may also set your own.)
* = required field[▶ Show post options & limits]
Confused? See the FAQ.
Expand all images

File (hide): 6ee38fc8c10c648⋯.png (344.59 KB, 940x264, 235:66, ClipboardImage.png) (h) (u)

[–]

 No.950397>>950427 >>950483 >>950504 >>950704 >>950843 [Watch Thread][Show All Posts]

New AA tech /g/amers

http://research.nvidia.com/publication/2018-08_Adaptive-Temporal-Antialiasing

We designed our method for compatibility with conventional game engines and to harness the strengths of TAA, while addressing its failures unequivocally and simply. The core idea is to run the base case of TAA on most pixels and then, rather than attempting to combat its failures with heuristics, output a conservative segmentation mask of where it will fail, and why. We then replace the complex heuristics of TAA at failure pixels with robust alternatives, adapting to the image content.

We implemented the ATAA algorithm in Unreal Engine 4 and gathered results using Windows 10 v1803, Microsoft DXR, the NVIDIA RTX enabled 398.11 driver, and an NVIDIA Titan V GPU. To demonstrate the image quality achievable with ATAA, Figure 3 shows a comparison of ATAA and other common antialiasing algorithms used in games, zoomed to challenging areas of the scene.

The No AA row demonstrates the baseline aliasing that is expected from a single raster sample per pixel. The FXAA and TAA rows are the standard implementations available in UE4. SSAA 4x is 4× supersampling. We show the segmentation mask and three variations of ATAA with 2, 4, and 8 rays per pixel. Since the drawbacks of standard TAA are difficult to capture in still images, and all images in Figure 3 come from a stable converged frame, the supplemental video provides a more faithful comparison between standard TAA and ATAA in practice, including motion artifacts.

On an NVIDIA Titan V GPU at 1920×1080 resolution, ATAA runs in 18.4ms at 8× supersampling, 9.3ms at 4× supersampling, and 4.6ms at 2× supersampling for the image in Figure 1. This includes the creation of the standard TAA result, our segmentation mask, and adaptive ray tracing (including 1 shadow ray per light per primary ray). For the view shown in Figure 3, 107,881 pixels are selected for adaptive ray tracing, representing 5.2% of the total image resolution.

The specific number of rays identified for antialiasing varies per frame according to the segmentation mask. In addition, the FXAA pass adds as much as 0.75ms when the whole frame is new, but in practice scales linearly down to 0 as fewer of the pixels are identified for FXAA in the mask. Under typical camera motion fewer than 5% of pixels are selected for FXAA. Our ATAA solution integrated successfully operates within the 33 millisecond frame budget for a typical UE4 frame across all settings. Operating within a total frame budget of 16ms, while also ray tracing 1spp shadows at screen resolution, is possible with the 2× and 4× ATAA variants. As DXR is an experimental feature of Windows 10 v1083, we are optimistic that performance will improve as the runtime and driver receive important release optimisations.

 No.950401

>/g/amers

This thread is going to hit bump limit, isn't it?


 No.950427>>950446 >>950705

File (hide): 2976a7c127938b8⋯.png (261.62 KB, 426x477, 142:159, 297.png) (h) (u)

>>950397 (OP)

>anti-aliasing

>not wanting raw, crisp pixels


 No.950446>>950448

File (hide): d9d4ede31b7e0e3⋯.png (177.08 KB, 755x352, 755:352, Untitled.png) (h) (u)

>>950427

Enjoy your reduced detail and flickering pixels.


 No.950448>>950449

File (hide): 0ce31d35e35d075⋯.png (5.24 KB, 384x272, 24:17, 4.png) (h) (u)

>>950446

Thx, I do.


 No.950449>>950475 >>950504

>>950448

Is there literally any pixel art game that has programmatic antialiasing?


 No.950475>>950476 >>950520

File (hide): 763ce2af2f1bb0b⋯.jpg (677.35 KB, 1972x984, 493:246, amiga-game-screenshots1.jpg) (h) (u)

>>950449

Maybe some modern indie games have that. But in every old game I played, any AA was simply drawn in by the artists, directly into the sprite frames or the background. No need to make it complicated and waste CPU cycles. And frankly, I think the old sprite games look and play much better than anything after the mid 90's (when 3D shit started being shoved into everything).


 No.950476>>950478 >>950580

>>950475

>implying you never played a pre-rendered game


 No.950478>>950481

File (hide): e9445f512845a44⋯.png (8.44 KB, 320x256, 5:4, Loom_1.png) (h) (u)

>>950476

Most of the 8-bit and Amiga games I played were just hand-drawn pixels. The rest were flat-shaded polygons, or even wireframe.

I guess some pre-rendered stuff was common in DOS for games like Doom though, but I thought you were talking about the game engine doing the antialiasing. Anyway I'm not a fan of FPS or games like Myst. I even stopped buying games altogether after Commodore went out of business.


 No.950481>>950485

>>950478

>pre-rendered

>Doom

>FPS

do you even know what you're talking about?


 No.950483

>>950397 (OP)

>The digital jew in action

Always improving the image, never bothering to work on the picture.


 No.950485>>950487

>>950481

Doom sprites were real models captured on camera, so in a way they're pre-rendered.

And I never liked the SNES. Never owned one, don't even collect its roms. The last console I bought was a Sega Genesis. Get it through you r head already: I DON'T LIKE YOUR FUCKING FANCY ASS GRPAHICS SHIT.


 No.950487>>950512 >>950580

>>950485

That's digitization or rotoscoping, depending on how they animated them.

I don't care about your preferences, I want you to stop being an embarrassment for /tech/ and start using the correct terms


 No.950504

File (hide): ece5cc8b9df1fb1⋯.jpeg (84.52 KB, 1024x1024, 1:1, polygon.jpeg) (h) (u)

>>950397 (OP)

>anti-aliasing

On a related note, I remember years ago reading about silhouette tessellation, where edge-detection is used to prioritize silhouettes of geometry for additional polygons (possibly actual 3D polygons, maybe some strange sort of 2D processing, but it looked natural with shading/textures/etc). The justification for this was the fact that the centers of objects (especially in the case of more modern shading techniques) are difficult to spot vertex boundaries and other polygonal artifacts in, whereas the outermost silhouettes of objects are the areas such artifacts are most visible in.

Has anything come of this? In a quick search just now, I see a lot of papers about something implemented as a shader in modern engines, but I can't see any wireframe images that indicate a reduction of polygons in the middle of objects and an increase in granularity toward the edges.

>>950449

Wouldn't that sort'a make it not pixel art by definition? The closest to AA you could come would be alpha channel support, allowing you to use baked-in AA (in addition to translucency) on each sprite. Earliest example that jumps to mind (though it's prerendered 3D) is Starcraft.


 No.950512

File (hide): 1e0953e11f37b48⋯.png (303.9 KB, 728x588, 26:21, bONgrZm.png) (h) (u)

>>950487

It was digitization, although not all Doom sprites were based off models. Several were hand-drawn.

Also everyone likes sucking Adrian Carmack's dick but the best models were made by Gregor Punchatz who only had a footnote in Doom history.

<muh gaymes


 No.950519

I have never cared for anti-aliasing and always seen it as a useless resource hog.


 No.950520>>950580 >>950583

>>950475

Turrican is a crappy game and you fucking know it.


 No.950580>>950613 >>950670

>>950487

Idiot with poor short-term memory, you wrote earlier >>950476

>implying you never played a pre-rendered game

Then you whip out some SNES title like it means something to me. All this time you're >implying I care about your retarded rendered graphics shit. Well I don't give a rat's ass, and never did. I stopped playing games when they moved away from hand-drawn sprites. The new games are nasty! I'd rather play Terry's collection of TempleOS games than any of that shit.

Also digitization will by its nature create anti-aliasing. Look at this fucking picture of a digitized girl. Zoom in closely so you can see the pixels. Now look at the countour between her skin and the blue wall. It's not a straight color, is it? No, some blue pixels are in that zone. Looks like you don't even know wtf you're talking about and should feel embarased!

>>950520

No, I don't fucking know it. I never played Turrican. Out of all those, I only played the top-left game (Lionheart).


 No.950583

>>950520

Don't a lot of Euros actually like Turrican though? Compared to Shadow of the Beast where they like its visuals but hate the game.


 No.950613>>950624

>>950580

False, very severe aliasing occurs in pixel-based cameras and scanners due to their discrete sensors, causing jaggies, moiré, and other artifacts, especially at higher magnification/lower resolution. While properly tuned software AA is the best way to deal with it, some newer devices, including most consumer-grade digital cameras, obviate this using crude optical blur filters in front of the sensors to add simple anti-aliasing:

https://web.archive.org/web/20070216052644/https://www.maxmax.com/hot_rod_visible.htm

As for your photo, I'm sure you're aware it's 8-bit, almost certainly scanned at a much higher resolution than appears onscreen, and the dithering is so severe that it leaves a 2-6 pixel fringe of dappled fuzz around every detail.


 No.950624>>950659

>>950613

Nigger wat even. The picture is 320x256 which is exactly the common Amiga resolution. And yeah it's 8-bit. How many fucking colors do you think an OCS Amiga can display at one time at that resolution (protip: it's a power of two and less than 64). This is exactly the picture as rendered by UAE. Now suck it, faggot.


 No.950659>>950665

>>950624

<scanned at a much higher resolution than appears onscreen

>exactly the common Amiga resolution

My point is both that the image as it appears onscreen is probably not at all like the raw file the dev's scanner probably produced, in that it was likely shrunk (usually inducing simple AA through bilinear oversampling), and that the final result onscreen is too severely dithered (not even 12-bit HAM!) for AA to be visible in the first place.


 No.950665>>950669

>>950659

Who says he's using a scanner that's making a high resolution file? That game is from 1988, and Newtek had this hardware already available for a couple years by then, where you can just capture at the exact resolution you want:

https://youtube.com/watch?v=rFqZvzcarrs


 No.950669

>>950665

I always scanned at least 2x the size I needed back then for the exact reason I just said (in addition to scanning at a higher depth to produce an optimum palette), besides which, as I said, that image is so badly dithered that whatever aliasing may have existed is unintelligible.


 No.950670

>>950580

>I'm a brainlet that doesn't understand what an example is.

You don't need to write me a wall of text to show how little you know about digital images.


 No.950693

>>>anything above 2ms for Anti-Aliasing

are you insane, its heavier than HBAO+, why the fuck would anyone use if you can just work a little more on your TAA solution and mix it with small amount MSAA with like 10x lower cost


 No.950704

>>950397 (OP)

>less than 60 fps in 2k resolution on Titan V

Wow what the fuck. I'll take my 16x MSAA thank you.


 No.950705

>>950427

It's a good point per se but in practice it only applies to games where you don't need to pick apart individual pixels on a 4k screen in order to identify your targets. I.e. when aliasing impacts object legibility negligibly then that's OK to have rough polygon edges. When you do shit like sniping people all the way across the map using ironsights, when your target is smaller than the ironsight front post, then anti-aliasing starts to matter.


 No.950808

Is there even a point to AA with our high resolution screens? I always turn it off and the difference is negligable.


 No.950843

>>950397 (OP)

>>>/g/

/g/et the fuck out

sage




[Return][Go to top][Catalog][Screencap][Nerve Center][Cancer][Update] ( Scroll to new posts) ( Auto) 5
29 replies | 9 images | Page ???
[Post a Reply]
[ / / / / / / / / / / / / / ] [ dir / animu / ausneets / kpop / leftpol / lit / tacos / vg / vichan ][ watchlist ]