You thought they were done with the Vulkan API? Think again. To mark Vulkan 1.0 being 2236 days old (give or take), a brand new extension has been revealed. This is an absolute game changer, there's no other way to frame this.
Presenting: VK_FOOL_printed_surface
Developed by Joshua Ashton and Liam Middlebrook, who are both involved in many Linux related things, Liam handled the majority of the specification work, while Josh handled the CUPS layer implementation.
Okay, so what does it do? They say it's the "newest innovation in the cross section of the Printed Media and Vulkan ecosystems" and their hype around it is definitely warranted. This extension allows you to print frames, in Vulkan. That's right, printing for everyone and high ink rates too!
You can print frames in Vulkan now! No longer are the days of yore when a frame would only last until the next vkQueuePresent() landed. Now you can cherish your favorite frames and have them last forever. Hang up your new family heirloom on the wall, or put them in a time-capsule for generations to come.
"Bringing Vulkan to the workplace"
Of course the full Vulkan specification sheet has been upgraded for this new extension too, and it answers a lot of burning questions like:
4) Printers are inherently complex devices which are not yet fully understood by humanity, does the current set of error codes available in Vulkan allow for implementations to adequately express the various states of disarray encountered when a print is not successful?
RESOLVED: To the best of our ability we have introduced new Vulkan error codes which should help implementations express the complex state of printers. This list is likely not exhaustive and may be expanded in a future extension.
7) Why would someone want to see a printed frame?
RESOLVED: This is a stupid question. For thousands of years humanity has pursued artistic passion and looked to immortalize their creations. This pursuit obviously extends to the printed frame.
21) Will the extension support tearing?
RESOLVED: No. The printed surface will only support perfect prints. Tearing is left to the end-user.
Is this a joke? What's going on? You decide. Only the smartest will be able to figure it out.
This can't possibly be real though right? See for yourself:
Direct Link
"Please consider the environment before printing this extension."
Time to get a faster printer so I can see my game being printed in real time.I dunno, I find about 6–12 sheets per day gives me that classic "newspaper" feel. Back when life was more relaxed and people were less hurried, y'know? Why, back in my day…
At least 25 sheets per second!!!
Last edited by Philadelphus on 4 April 2022 at 6:33 pm UTC
Time to get a faster printer so I can see my game being printed in real time.I dunno, I find about 6–12 sheets per day gives me that classic "newspaper" feel. Back with life was more relaxed and people were less hurried, y'know? Why, back in my day…
At least 25 sheets per second!!!
You whippersnapper you! Back in my day...
Yes, yes, I know, the ink was still fresh on Gutenberg's type and you were lucky if you were able to illuminate one manuscript page a day…Time to get a faster printer so I can see my game being printed in real time.I dunno, I find about 6–12 sheets per day gives me that classic "newspaper" feel. Back with life was more relaxed and people were less hurried, y'know? Why, back in my day…
At least 25 sheets per second!!!
You whippersnapper you! Back in my day...
Yes, yes, I know, the ink was still fresh on Gutenberg's type and you were lucky if you were able to illuminate one manuscript page a day…Time to get a faster printer so I can see my game being printed in real time.I dunno, I find about 6–12 sheets per day gives me that classic "newspaper" feel. Back with life was more relaxed and people were less hurried, y'know? Why, back in my day…
At least 25 sheets per second!!!
You whippersnapper you! Back in my day...
The human eye can't see more than one manuscript page a day anyhow.
Just the right rate for a literary experience.
See more from me