Show Posts

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.


Messages - JeGX

Pages: 1 ... 17 18 [19] 20 21 ... 74
361
Quote
* Bump API patch number and header version number to 46 for this update.

Github Issues:

  * Add language to the <<fundamentals-validusage-enums, Valid Usage for
    Enumerated Types>> section allowing values to be returned from Vulkan
    that are not present in extensions explicitly enabled by the
    application, similar to existing language for bit flags in the
    <<fundamentals-validusage-flags, Valid Usage for Flags>> section (public
    issue 442).
  * *Important*: run `gem update --pre asciidoctor-pdf` before trying to
    build this version of the spec - 1.5.0.alpha15 is required for this
    change. Removes the monkey patch currently used to draw valid usage
    blocks across multiple pages which had numerous issues. A fixed version
    was incorporated into Asciidoctor-PDF for the latest release, so the
    monkey patch or any variant thereof is no longer required (public issue
    465).

Internal Issues:

  * Add ename:VK_DEBUG_REPORT_OBJECT_TYPE_DESCRIPTOR_UPDATE_TEMPLATE_KHR_EXT
    to `VK_EXT_debug_report` extension
  * Fix ptext:pNext member of
    slink:VkPhysicalDeviceDiscardRectanglePropertiesEXT to be a non-const
    pointer. Properties structures return values, so the chain should be
    non-const.
  * Explicitly remove gl_NumSamples from the `GL_KHR_vulkan_glsl` extension,
    against 1.0 (internal issue 612).
  * Add Valid Usage statements requiring that each structure type valid in a
    ptext:pNext chain must: not appear more than once in a chain (internal
    issue 752).
  * Use ename:VK_USE_PLATFORM_WIN32_KHX in the
    `VK_KHX_external_memory_win32` extension, rather than etext:_KHR
    (internal issue 754).

New Extensions:

  * `VK_KHR_incremental_present`

source: https://github.com/KhronosGroup/Vulkan-Docs/commit/f985a50c1f0b6f37c706db32d70da85bc1e2d78f

362
Geeks3D's GPU Tools / GPU Caps Viewer 1.34.1.x released
« on: April 01, 2017, 04:33:33 PM »
I think I fixed the bug with Radeon GPUs. Try the new version 1.34.1.0:

http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/#20170401

On my notebook (a Lenovo ThinkPad E460 with an Intel HD 520 + Radeom R7 M360), the R7 M360 is now properly detected by GPU Caps.

363
Geeks3D's GPU Tools / Re: GPU Caps Viewer 1.34.x.x released
« on: April 01, 2017, 10:48:46 AM »
Update log file of AMD WX 7100
=================================================================================================
01:16:54 | 26 >> - DEV 0 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 27 >> - DEV 0 - DeviceName: \\.\DISPLAY1
01:16:54 | 28 >> - DEV 0 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 29 >> - DEV 0 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0000
01:16:54 | 30 >> - DEV 1 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 31 >> - DEV 1 - DeviceName: \\.\DISPLAY2
01:16:54 | 32 >> - DEV 1 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 33 >> - DEV 1 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0001
01:16:54 | 34 >> - DEV 2 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 35 >> - DEV 2 - DeviceName: \\.\DISPLAY3
01:16:54 | 36 >> - DEV 2 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 37 >> - DEV 2 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0002
01:16:54 | 38 >> - DEV 3 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 39 >> - DEV 3 - DeviceName: \\.\DISPLAY4
01:16:54 | 40 >> - DEV 3 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 41 >> - DEV 3 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0003
01:16:54 | 42 >> - DEV 4 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 43 >> - DEV 4 - DeviceName: \\.\DISPLAY5
01:16:54 | 44 >> - DEV 4 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 45 >> - DEV 4 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0004
01:16:54 | 46 >> - DEV 5 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 47 >> - DEV 5 - DeviceName: \\.\DISPLAY6
01:16:54 | 48 >> - DEV 5 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 49 >> - DEV 5 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0005
01:16:54 | 50 >> - DEV 6 - DeviceID: PCI\VEN_8086&DEV_193D&SUBSYS_07B11028&REV_09
01:16:54 | 51 >> - DEV 6 - DeviceName: \\.\DISPLAY7
01:16:54 | 52 >> - DEV 6 - DeviceString: Intel(R) Iris(TM) Pro Graphics P580
01:16:54 | 53 >> - DEV 6 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{674CA461-FAB1-44C5-BB14-5ED2DFBA2C37}\0006
01:16:54 | 54 >> - DEV 7 - DeviceID:
01:16:54 | 55 >> - DEV 7 - DeviceName: \\.\DISPLAYV1
01:16:54 | 56 >> - DEV 7 - DeviceString: RDPDD Chained DD
01:16:54 | 57 >> - DEV 7 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{DEB039CC-B704-4F53-B43E-9DD4432FA2E9}\0000
01:16:54 | 58 >> - DEV 8 - DeviceID:
01:16:54 | 59 >> - DEV 8 - DeviceName: \\.\DISPLAYV2
01:16:54 | 60 >> - DEV 8 - DeviceString: RDP Encoder Mirror Driver
01:16:54 | 61 >> - DEV 8 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{42cf9257-1d96-4c9d-87f3-0d8e74595f78}\0000
01:16:54 | 62 >> - DEV 9 - DeviceID:
01:16:54 | 63 >> - DEV 9 - DeviceName: \\.\DISPLAYV3
01:16:54 | 64 >> - DEV 9 - DeviceString: RDP Reflector Display Driver
01:16:54 | 65 >> - DEV 9 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{b043b95c-5670-4f10-b934-8ed0c8eb59a8}\0000

Thanks for the log. That's what I thought, the AMD GPU is not listed in the active Windows adapters. Actually I have the same problem with a notebook that has an Intel GPU + AMD GPU: GPU Caps Viewer shows the Intel GPU only. I'm investigating about this issue... I let you know asap.

364
Geeks3D's GPU Tools / Re: GPU Caps Viewer 1.34.x.x released
« on: March 30, 2017, 03:59:00 PM »
Actually what I need is the log file of GPU Caps Viewer (_log.txt in GPU Caps folder). I need to know if the  WX 7100 is listed or not in Windows devices. On my system for example, the GTX 1060 is listed like that:
Quote
15:52:49 | 28 >> - DEV 0 - DeviceID: PCI\VEN_10DE&DEV_1C03&SUBSYS_61633842&REV_A1
15:52:49 | 29 >> - DEV 0 - DeviceName: \\.\DISPLAY1
15:52:49 | 30 >> - DEV 0 - DeviceString: NVIDIA GeForce GTX 1060 6GB
15:52:49 | 31 >> - DEV 0 - DeviceKey: \Registry\Machine\System\CurrentControlSet\Control\Video\{3FDB2FF5-A64B-4CA6-9A2B-0D133FF04B78}\0000

365
Just added to the code sample pack this cool multipass demo. I will try to upload the new code sample pack today. The demo can be found in the gl-21/shadertoy-multipass/gl21-alien-corridor/ folder.




366
DepthOfFieldFX is a DirectX 11 library that provides a GCN-optimized Compute Shader implementation of Depth of Field.

Quote
The DepthOfFieldFX library provides a GCN-optimized Compute Shader implementation of Depth of Field using the Fast Filter Spreading approach put forth by Todd Jerome Kosloff, Justin Hensley, and Brian A. Barsky in their 2009 paper – Fast Filter Spreading and its Applications.

The library implements depth of field using a Bartlett and Box filter. There is an option to run the Bartlett at quarter resolution for improved performance in some cases. The advantage of this approach is a fixed performance cost that is not dependent on kernel size. The library takes the scene Color Buffer and Circle of Confusion buffer as input and an Unordered Access View for the final results.

Links:
- https://github.com/GPUOpen-Effects/DepthOfFieldFX



367
You might have read that Microsoft will stop supporting Windows Vista on April 11. Futuremark will stop supporting two Windows Vista benchmarks, 3DMark Vantage and PCMark Vantage, on the same day.

Quote

3DMark Vantage and PCMark Vantage support ends April 11
Our Vantage benchmarks were designed for Windows Vista, an operating system that is over 10 years old and which is now used by only 1.12% of Windows users according to StatCounter.
 
From April 11, 3DMark Vantage and PCMark Vantage will:
- No longer be sold on our website.
- No longer receive updates, (other than SystemInfo).
- No longer be guaranteed to work with our online services.
- No longer be eligible for customer support.

Alternatives to 3DMark Vantage
3DMark Vantage is a benchmark for DirectX 10, an API which is now two generations old. For benchmarking modern gaming systems, we recommend using the latest 3DMark benchmarks:
- 3DMark Time Spy for DirectX 12 systems.
- 3DMark Fire Strike for high performance DirectX 11 PCs.
- 3DMark Sky Diver for DirectX 11 laptops and mid-range PCs.

Alternatives to PCMark Vantage
PCMark Vantage is a system benchmark for Windows Vista. If your PC is less than seven years old, you will get more relevant results by using a more recent version of PCMark. We recommend:
- PCMark 7 for Windows 7
- PCMark 8 for Windows 8
- PCMark 10, coming soon, for Windows 10.

Legacy benchmarks are free to download
All of our legacy benchmarks going back to 3DMark99 are available to download for free from our website. Each benchmark comes with a key to unlock the Advanced Edition features. 3DMark Vantage and PCMark Vantage will be available for free from April 11.

https://www.futuremark.com/benchmarks/legacy


369
Geeks3D's GPU Tools / GPU Shark 0.9.11.1 released
« on: March 27, 2017, 01:41:52 PM »

370
Geeks3D's GPU Tools / GPU Caps Viewer 1.34.x.x released
« on: March 27, 2017, 01:40:55 PM »
The new version of GPU Caps Viewer is available.

More information and dowmload links:
http://www.geeks3d.com/20170327/gpu-caps-viewer-1-34-0-released/

371
Download zone updated: HWMonitor 1.31

372
3D-Tech News Around The Web / AMD Compressonator v2.5 released
« on: March 24, 2017, 06:14:29 PM »
Compressonator is a set of tools to allow artists and developers to more easily create compressed texture image assets and easily visualize the quality impact of various compression technologies. It consists of a GUI application, a command line application and an SDK for easy integration into a developer tool chain.

The v2.5.3297 beta version has been released few days ago.

- Compressonator @ github
- changelog

373
3D-Tech News Around The Web / Anvil Vulkan framework released
« on: March 24, 2017, 05:53:21 PM »
Quote
Anvil is a cross-platform, open-source, MIT-licensed wrapper library for Vulkan™, developed by AMD engineers. It has been designed with the goal of reducing the amount of time that developers need to spend in order to write a working Vulkan application from scratch. As such, not only does the library provide the usual C++ wrappers one would expect, but also includes extra features, as described below:

-  A memory allocator which allocates as little memory as necessary for the specified list of memory regions, miptails, objects or subresources from one or more memory heaps, depending on platform’s capabilities.
- Automatic object lifetime management, thanks to auto pointers being used across the library.
- Descriptor sets and descriptor set layouts are automatically generated from user-created descriptor set groups.
- Helper routines for FP16<->FP32 conversion.
- Integrated validation support. Validation can be enabled by changing a single argument value at Vulkan instance creation time.
- Integration with glslang for run-time GLSL -> SPIR-V conversion. Assembly of the result blob can also be retrieved for further analysis.
- Object tracker which can be used to detect wrapper object leaks.
- Page tracker, useful for the purpose of tracking memory bindings, if sparse residency is used for buffers or images.
- Windowing system integration – current support includes XCB and Windows platforms.

Links:
- http://gpuopen.com/gaming-product/anvil-vulkan-framework/
- https://github.com/GPUOpen-LibrariesAndSDKs/Anvil/




374
3D-Tech News Around The Web / Vulkan API Overhead Test Added in 3DMark
« on: March 23, 2017, 03:18:39 PM »
Futuremark has released a new version of 3DMark that adds the Vulkan support to the API Overhead test. We can now compare the API performance of Direct3D 11, Direct3D 12 and Vulkan.

http://www.geeks3d.com/20170323/vulkan-api-overhead-test-added-in-3dmark/

375
Geeks3D's GPU Tools / GPU Shark 0.9.11.x released
« on: March 23, 2017, 02:51:14 PM »
GPU Shark 0.9.11.0 has been released. Complete story and download:

http://www.geeks3d.com/20170323/gpu-shark-0-9-11-released/

376
Quote
At GDC 2017, in San Francisco during February, Khronos™ released several new Vulkan® extensions for cross-platform Virtual Reality rendering and multiple GPU access. This functionality has been initially released as KHX extensions to enable feedback from the developer community before being incorporated into final specifications.

One key question that we have been asked since GDC is whether the Vulkan multi-GPU functionality is specifically tied to ship only on Windows 10.

The good news is that the Vulkan multi-GPU specification is very definitely NOT tied to Windows 10. It is possible to implement the Vulkan multi-GPU extension on any desktop OS including Windows 7, 8.X and 10 and Linux.

Some of the Khronos GDC presentations mentioned that for Vulkan multi-GPU functionality, Windows Display Driver Model (WDDM) must be in Linked Display Adapter (LDA) mode. That was not a very clear statement that has caused some confusion. And so it is worth clarifying that:

1/ The use of WDDM is referring to the use of Vulkan multi-GPU functionality on Windows. On other OS, WDDM is not necessary to implement the Vulkan multi-GPU extension.

2/ On Windows, the use of LDA mode can make implementing Vulkan multi-GPU functionality easier, and will probably be used by most implementations, but it is not strictly necessary.

3/ If an implementation on Windows does decide to use LDA mode, it is NOT tied to Windows 10. LDA mode has been available on many versions of Windows, including Windows 7 and 8.X.

Khronos always strives to make its specifications as cross platform as possible. Of course, what products ship on which OS is up to the implementers of each specification, but Khronos is already aware of vendor plans to ship multi-GPU functionality on platforms other than Windows 10, including Linux.

Source: https://www.khronos.org/blog/vulkan-multi-gpu-support-not-just-for-windows-10



377
GeeXLab - english forum / Shadertoy demos in Vulkan (Geomechanical)
« on: March 22, 2017, 11:35:42 AM »
Another shadertoy demo ported to Vulkan:



Will be available in the next update of the code sample pack.

378
3D-Tech News Around The Web / WebGLNext: Obsidian API Proposal
« on: March 22, 2017, 09:36:05 AM »
Quote
This is Mozilla's draft proposal for the GPU API for the Web, called Obsidian. It is a low-level API that provides maximum feature set of the GPU to the web applications. The API is designed for WebAssembly, modern GPUs, and multi-threaded environment in mind.

Obsidian is a temporary code name, signifying the Vulkan roots of the API:

Obsidian is a naturally occurring volcanic glass formed as an extrusive igneous rock.
This proposal is not a specification. It includes reasoning for the design decisions, draft WebIDL and a bit of example code. We don't aim to provide a complete specification, instead we want this proposal to represent our vision of the future API in the working group discussions, a vision of rich graphics on the Web powered by a low-level explicit API.

The contents are split into the following sections:

1/ introduction and philosophy
2/ design details, differences from Vulkan/D3D12
3/ synchronization and memory model
4/ API and examples

Link to the complete proposal:
https://github.com/KhronosGroup/WebGLNext-Proposals/tree/master/Obsidian-Mozilla

379
Quote
This patch set adds support for vega10.  Major changes and supported
features:
- new vbios interface
- Lots of new hw IPs
- Support for video decode using UVD
- Support for video encode using VCE
- Support for 3D via radeonsi
- Power management
- Full display support via DC
- Support for SR-IOV

Source: https://lists.freedesktop.org/archives/amd-gfx/2017-March/006525.html

Quote
Vega 10 device support:

    {0x1002, 0x6860, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
    {0x1002, 0x6861, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
    {0x1002, 0x6862, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
    {0x1002, 0x6863, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
    {0x1002, 0x6867, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
    {0x1002, 0x686c, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},
    {0x1002, 0x687f, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_VEGA10},

Polaris 12 device support:

    {0x1002, 0x6980, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},
    {0x1002, 0x6981, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},
    {0x1002, 0x6985, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},
    {0x1002, 0x6986, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},
    {0x1002, 0x6987, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},
    {0x1002, 0x6995, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},
    {0x1002, 0x699F, PCI_ANY_ID, PCI_ANY_ID, 0, 0, CHIP_POLARIS12},

Other related links:
- AMD Sends Out 100 Patches, Enabling Vega Support In AMDGPU DRM
- AMD GPU Linux driver patches lists seven Vega 10 IDs
- AMD's Vega 10 GPU has appeared in Linux drivers


380
Falcor is a Direct3D 12 real-time rendering framework. It aims to improve productivity of research and prototype projects. Its features include:

- Abstract many common graphics operations, such as shader compilation, model loading and scene rendering.
- VR support using OpenVR.
- Common rendering effects such as shadows and post-processing effects.

This is an alpha version. The interfaces are not final yet and there might be some performance/stability issues.
If you'd like OpenGL support, please consider using Falcor 1.0 ('rel-1.0' branch). Note that though Falcor 1.0 is not supported anymore, it is stable and optimized.

More information and source code: https://github.com/NVIDIA/Falcor

Pages: 1 ... 17 18 [19] 20 21 ... 74