<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Hardware Accelerated Neural Block Texture Compression with Cooperative Vectors · HackerPapers discussions</title><link>https://hackerpaper.kaipfister.de/p/2506.06040/</link><description>Collected HN comments and submissions linking this paper.</description><language>en</language><lastBuildDate>Mon, 02 Nov 2026 11:16:22 GMT</lastBuildDate><atom:link href="https://hackerpaper.kaipfister.de/p/2506.06040/feed.xml" rel="self" type="application/rss+xml" /><item><title>Hardware Accelerated Neural Block Texture Compression with Cooperative Vectors — mentioned by cubefox</title><link>https://news.ycombinator.com/item?id=45158024</link><guid isPermaLink="false">urn:hackerpapers:mention:2506.06040:45158024</guid><pubDate>Sun, 07 Sep 2025 13:34:12 GMT</pubDate><description>&lt;p&gt;The more efficient versions compress the entire material stack in one, to exploit inherent redundancies, including albedo, normals, roughness etc. The main problem, as far as I can tell, is the increased GPU performance cost compared to block compression. Though recent research shows some versions are already pretty manageable on modern GPUs with ML acceleration: https://arxiv.org/abs/2506.06040 They cite 0.55ms per frame at 1080p on a recent Intel GPU. The budget for one frame at 60 FPS is 16.7ms, so the performance cost would be 3.3% of that. Though higher resolutions would be more…&lt;/p&gt;&lt;p&gt;&lt;a href="https://hackerpaper.kaipfister.de/p/2506.06040/"&gt;Paper and discussion history&lt;/a&gt;. A mention is not an endorsement.&lt;/p&gt;</description><category>cs.GR</category></item></channel></rss>
