[a / b / c / d / e / f / g / gif / h / hr / k / m / o / p / r / s / t / u / v / vg / vr / w / wg] [i / ic] [r9k / s4s / vip / qa] [cm / hm / lgbt / y] [3 / aco / adv / an / asp / bant / biz / cgl / ck / co / diy / fa / fit / gd / hc / his / int / jp / lit / mlp / mu / n / news / out / po / pol / qst / sci / soc / sp / tg / toy / trv / tv / vp / wsg / wsr / x] [Settings] [Search] [Mobile] [Home]
Board
Settings Mobile Home
/3/ - 3DCG


Thread archived.
You cannot reply anymore.



File: raytracing.png (68 KB, 446x171)
68 KB
68 KB PNG
>>
Ray tracing isn't a meme but rtx is.
>>
>>695635
"normies discover things that others used the last 30 years for work, film at 11"
>>
>>695789
FPBP
Until there is a decent open RT framework raytracing will be a meme feature for the most part like VR. In 5 years, devs will suddenly start to notice additional gameplay possible with RT and from then on it's gonna be fairly standard.
>>
>>695791
And why is it 'normies' should know about stuff like that?
What's really facepalm inducing after long years and having become quite technically literate is year after year see the same steady
stream of newcomers spitting field-specific lingo left and right while pretending to be all knowledgeable.

Echoing this or that sentiment about something they heard some guru state in a video and now take any chance they can to assert this one fact they know and believe to be very true.
If I had a cent for every time I overheard some hack teaching a junior with authoritative certainty while being dead wrong I'd have several dollars in the bank by now.

Having an air of superiority about yourself because of niche knowledge in a narrow field is a form douchebaggery to rid yourself of.
>>
>>695814
BLAST-PROCESSING
>>
>>695814
all insecure people are like that and you just happen to be on the internet where insecure people like to hang out.
>>
painful to read
>>>/g/72545647



Delete Post: [File Only] Style:
[Disable Mobile View / Use Desktop Site]

[Enable Mobile View / Use Mobile Site]

All trademarks and copyrights on this page are owned by their respective parties. Images uploaded are the responsibility of the Poster. Comments are owned by the Poster.