« on: July 22, 2015, 11:46:20 AM »
This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.
Qt 5.5 brings you more solutions for even faster development workflows, a more powerful UI creation offering for keeping pace with market demands in multimedia and 3D user experiences, preliminary support for upcoming Windows 10 development, and more for connectivity. Plus, of course, improvements across the whole Qt framework.
New Features in Qt 5.5
- Improvements and enhancements to all major Qt modules, on all platforms
- All Windows builds are now automatically dynamic regarding OpenGL vs. ANGLE backends, no need to manually configure deployment anymore!
- Qt Bluetooth includes full support for Bluetooth Low Energy and is supported on Linux, Embedded Linux, Android, iOS
- Qt Canvas 3D module fully supported
- Qt 3D 2.0 introduced as technology preview
- Qt Location technology preview lets you integrate maps, geocoding, routing and places into your application. The included mapping backends are: Nokia HERE, OpenStreetMap and MapBox
- Qt Multimedia has support for GStreamer 1.0 enhancing the multimedia capabilities on Linux based systems. Also integration of video/camera to Qt Quick graphics is now easy.
- Qt WebEngine has been updated to Chromium version 40 and the public APIs have been extended, for instance with full integration to Qt WebChannelQt WebEngine has been updated to Chromium version 40 and the public APIs have been extended, for instance with full integration to Qt WebChannel
- TreeView control included in Qt Quick Controls
- Former “Qt Quick Enterprise Controls”, including different industrial gauges, dials and other controls, are now migrated into Qt Quick Controls and are also available for Qt Open Source users
- Full and official support for Red Hat Enterprise Linux 6.6
- Qt Creator 3.4
- Deprecating Qt WebKit, Qt Script and Qt Quick 1 modules.
Today we released a new Hotfix driver 353.49 that addresses the following issue:
Sony Vegas Pro crashes
Windows 10 installation issue introduced with previous 353.45 driver
In addition, this driver also includes the same fixes which were part of our previous 353.38 hotfix driver release:
Delays when starting or switching apps & games with GSYNC enabled
In my previous post I introduced ARB_shader_storage_buffer, an OpenGL 4.3 feature that is coming soon to Mesa and the Intel i965 driver. While that post focused on explaining the features introduced by the extension, in this post I’ll dive into some of the implementation aspects, for those who are curious about this kind of stuff. Be warned that some parts of this post will be specific to Intel hardware.
Another interesting thing we had to deal with are address alignments. UBOs work with layout std140. In this setup, elements in the UBO definition are aligned to 16-byte boundaries (the size of a vec4). It turns out that GPUs can usually optimize reads and writes to multiples of 16 bytes, so this makes sense, however, as I explained in my previous post, SSBOs also introduce a packed layout mode known as std430.
Intel hardware provides a number of messages that we can use through the Data Port interface to write to memory. Each message has different characteristics that makes it more suitable for certain scenarios, like the pixel mask I discussed before. For example, some of these messages have the capacity to write data in chunks of 16-bytes (that is, they write vec4 elements, or OWORDS in the language of the technical docs). One could think that these messages are great when you work with vector data types, however, they also introduce the problem of dealing with partial writes: what happens when you only write to an element of a vector? or to a buffer variable that is smaller than the size of a vector? what if you write columns in a row_major matrix? etc
In these scenarios, using these messages introduces the need to mask the writes because you need to disable the channels in the vec4 element that you don’t want to write. Of course, the hardware provides means to do this, we only need to set the writemask of the destination register of the message instruction to select the right channels.
AMD (NASDAQ: AMD) today announced the new AMD FirePro™ S9170 server GPU, the world’s first and fastest 32GB single-GPU server card for DGEMM heavy double-precision workloads1, with support for OpenCL™ 2.0. Based on the second-generation AMD Graphics Core Next (GCN) GPU architecture, this new addition to the AMD FirePro™ server GPU family is capable of delivering up to 5.24 TFLOPS of peak single precision compute performance while enabling full throughput double precision performance, providing up to 2.62 TFLOPS of peak double precision performance.
Designed with compute-intensive workflows in mind, the AMD FirePro S9170 server GPU is ideal for data center managers who oversee clusters within academic or government bodies, oil and gas industries, or deep neural network compute cluster development.
“AMD is recognized as an HPC industry innovator as the graphics provider with the top spot on the November 2014 Green500 List. Today the best GPU for compute just got better with the introduction of the AMD FirePro S9170 server GPU to complement AMD’s impressive array of server graphics offerings for high performance compute environments,” said Sean Burke, corporate vice president and general manager, AMD Professional Graphics group. “The AMD FirePro S9170 server GPU can accelerate complex workloads in scientific computing, data analytics, or seismic processing, wielding an industry-leading 32GB of memory. We designed the new offering for supercomputers to achieve massive compute performance while maximizing available power budgets.”
“There are some HPC workloads which require as much data as possible to stay resident on the device, and so the 32GB of memory provided by AMD FirePro S9170, the largest available on a single GPU, will enable the acceleration of scientific calculations that were previously impossible,” said Simon McIntosh-Smith, head of the Microelectronics Research Group at the University of Bristol. “For example, our new OpenCL version of the SNAP transport code from Los Alamos National Laboratory needs to keep as much data resident on the device as possible, and so the 32GB of memory will let us run problems of a much more interesting size faster than ever before. The large memory, combined with the 320GB/s memory bandwidth and double precision floating point performance, will make the AMD FirePro S9170 server GPU a ‘killer’ solution device for many HPC applications.”
“We have been developing a fully-parallel computational tool based on the AMD GPU heterogeneous computing platform and OpenCL,” said Omid Mahahadi, co-founder and director, Geomechanica Inc. “This tool accurately captures the complex physics of massive mines plus oil and gas fields rapidly and reliably. Thanks to the impressive 32GB of memory of the new cards, we expect to run computations on massive data structures containing tens of millions of data elements. The combination of rapid double-precision operations with the large memory capacity enables accurate, detailed, and reliable computations. A similar performance using CPUs would likely require much higher capital and maintenance costs. Moving forward, we plan to take advantage of the recent features of the OpenCL 2.0 open API to further enhance the performance of our software.”
- Vulkan API is more low-level than OpenGL (programmer is responsible for memory and threads management for example), what triggered this decision?
A low level API has simpler drivers. This means reduced driver overhead – which results in higher performance for CPU limited applications – and fewer differences between multiple GPU vendors’ implementations. Also, another fundamental advantage of handing the application more control is that the driver has to do less ‘behind the scenes’ management – resulting in much more reliable and predictable performance which doesn’t hit unexpected road bumps as the driver undertakes complex housekeeping tasks.
- What concrete improvements will gamers see, when Vulkan is used by video game studios? Can they expect better performance and better graphics, or is it just about simplifying studios backend work?
For applications that are CPU limited, which happens on desktop, and even more on mobile, end users should notice better performing applications with less stuttering and halting.
- When will Vulkan first version be released?
Vulkan is still on schedule to have specs and implementations before the end of the year.
Havok®, a leading provider of AAA game development technology, extends congratulations to all of the nominees of Game Critics Awards for “Best of E3 2015,” which includes several of Havok’s developer partners. The nominees pushed the limits of realism to create remarkable AAA game experiences. Some of these great titles range from Bethesda Softworks’ wildly ambitious and gigantic open-world role-playing game, Fallout 4, to the deeply compelling narrative and intense adventure of Sony and Naughty Dog’s Uncharted 4: A Thief’s End, to the visually spectacular and blistering firefights of Star Wars Battlefront. Havok’s cross-platform suite of technology helps create some of the most ambitious AAA games that leverage the new hardware, and this same technology continues to service future projects that will become milestone titles for years to come.
Havok congratulates the following AAA projects powered by Havok technology that are among the titles nominated by the Best of E3 2015 awards:
· Star Wars Battlefront - Electronic Arts
· Dark Souls III – BANDAI NAMCO Entertainment
· Fallout 4 - Bethesda Softworks
· Halo 5: Guardians - Microsoft Studios
· Horizon: Zero Dawn - Sony Computer Entertainment
· Just Cause 3 - Square Enix
· Need for Speed - Electronic Arts
· No Man's Sky - Hello Games
· The Last Guardian - Sony Computer Entertainment
· Tom Clancy's Rainbow Six Siege - Ubisoft
· Tom Clancy's The Division - Ubisoft
· Uncharted 4: A Thief's End - Sony Computer Entertainment
· DOOM – Bethesda Softworks
The Cache is always trying to guess what memory you’ll need to have before you request it, this prediction is called Cache Prefetching. This is why when working on an array it’s best to go through in sequential order instead of randomly jumping through, as the Cache Prefetcher will be able to guess what you’re using and have it ready before you need it. Cache loads things in groups of 64 bytes. The size is CPU-dependant and can be checked under your CPU’s specification under Cache Line size, although it’s typically 64 bytes. This means that if you have an array of integers and you grab 1 of those integers, the cache has also grabbed the Cache Line that it sits on. Grabbing the next integer stored next to it will be a Cache Hit and subsequently extremely fast. The alignment of the Cache Line will always be a multiple of the Cache Line's size, meaning that if you fetch memory at 0x00 (0) then what will be cached is everything between 0x00 (0) and 0x40 (64) and if you fetch something at 0x4F (79) then you’ll get everything between 0x40 (64) and 0x80 (128).
In the horror genre, gore and guts are commonplace. And the folks at Tripwire Interactive are using our technology to take the gore in their new horror survival game to a new level. In Killing Floor 2, you must fight your way through waves of mutated specimens, called Zeds. The longer you fight, the messier things get.
The three foundations of the game’s initial design mantra were “Bullets, Blades and Blood.” And that lead to the creation of the M.E.A.T. (massive evisceration and trauma) system to depict dynamic gore, blood splatter and detailed graphic violence. To get the M.E.A.T. just right, Tripwire made Killing Floor 2 the first game to use our NVIDIA PhysX FleX technology for soft tissue and fluid interaction. That’s geek for guts and blood splatter.
Metal for desktop has instancing, sane constant buffers, texture barrier, occlusion query, and draw-indirect. It looks like it does not have transform feedback, geometry shaders or tessellation. (The docs do mention outputting vertices to a buffer with a nil fragment function, but I don't see a way to specify the output buffer for vertex transform. I also don't see any function attach points for geometry shaders or tessellation shaders.)
We present a technique for synthesizing the effects of skin microstructure deformation by anisotropically convolving a highresolution displacement map to match normal distribution changes in measured skin samples. We use a 10-micron resolution scanning technique to measure several in vivo skin samples as they are stretched and compressed in different directions, quantifying how stretching smooths the skin and compression makes it rougher. We tabulate the resulting surface normal distributions, and show that convolving a neutral skin microstructure displacement map with blurring and sharpening filters can mimic normal distribution changes and microstructure deformations. We implement the spatially-varying displacement map filtering on the GPU to interactively render the effects of dynamic microgeometry on animated faces obtained from high-resolution facial scans.
The largest update to Unreal Engine to date, this release includes 189 great changes that were submitted from our amazing community of developers, plus loads of new upgrades from Epic.