From 1bee2cd08380c9bb7dff7daf027f5a819df58b7e Mon Sep 17 00:00:00 2001 From: Luke Kenneth Casson Leighton Date: Wed, 9 Oct 2019 07:52:17 +0100 Subject: [PATCH] clarify --- updates/020_2019aug28_intriguing_ideas.mdwn | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/updates/020_2019aug28_intriguing_ideas.mdwn b/updates/020_2019aug28_intriguing_ideas.mdwn index 87005ec..d5e8e7e 100644 --- a/updates/020_2019aug28_intriguing_ideas.mdwn +++ b/updates/020_2019aug28_intriguing_ideas.mdwn @@ -22,12 +22,12 @@ things are slowly changing due to ongoing multi-man-year reverse-engineering efforts, 3D driver source code is often proprietary as well. -At the BoF, one attendee described how they are implementing -*transparent* shader algorithms. Most shader hardware provides -triangle algorithms that asume a solid surface. Using such hardware -for transparent shaders is a two-pass process which clearly comes with -an inherent *100%* performance penalty. If, on the other hand, they had -some input into a new 3D core, one that was designed to be flexible... +At the BoF, one attendee described how they are implementing *transparent* +shader algorithms. Most shader hardware provides fixed-function triangle +algorithms that asume a solid surface. Using such hardware for transparent +shaders is a two-pass process which clearly comes with an inherent *100%* +performance penalty. If, on the other hand, they had some input into a +new 3D core, one that was designed to be flexible... The level of interest was sufficiently high that Atif is reaching out to people (including our team) to set up an Open 3D Graphics -- 2.30.2