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 2 [3] 4 5 ... 100
The only end-user benchmark I have for Linux is GpuTest. But GpuTest has no option to select the GPU. It's an OpenGL benchmark. You can perhaps force GpuTest to use a particular GPU by launching it on the right monitor (assuming you have a monitor connected to each GPU). But I'm not sure if this works. The successor of GpuTest will have Vulkan support which will make easier the selection of a particular GPU.

Looks like the same issue I had with my MSI GTX 970. You probably have to update the GTX 970 vbios. Before the bios update, the score of the GTX 970 was 3335 points with FurMark P1080. After the bios update, the score jumped to nearly 4000 points which is the correct score for a GTX 970. Try to update your MSI card with MSI Live Update tool. Let us know.

New features and changes:
Support For
- Total War: Three Kingdoms

Fixed Issues
- AMD Radeon VII may experience screen flicker when multiple displays are connected on desktop or while applications are running.
- Radeon WattMan may list the incorrect max temperature for some graphics products.
- GPU Utilization in Radeon Performance Metrics Overlay may sometimes show on unsupported products.
- HDR Video may freeze or have corruption during playback when using Movies and TV Application with some Ryzen APUs.

- Latest Adrenalin driver win10 64-bit @ Geeks3D
- Latest Adrenalin driver win7/win8 64-bit @ Geeks3D

- Adrenalin 19.5.2 @ AMD

Adrenalin 19.5.2 exposes  OpenGL 4.6 (324 extensions - GL=300 and WGL=24) and Vulkan 1.1.106 for a Radeon RX Vega 56, like previous 19.5.1.

AMD Adrenalin software information panel + Radeon RX Vega 56

GPU Caps Viewer + Radeon RX Vega 56

3D-Tech News Around The Web / Irfanview 4.53 released
« on: May 17, 2019, 04:43:07 PM »
Irfanview, one of the best image viewers on Windows has been updated:

- New effect in Image->Effects menu: Insert Speech Bubbles
  Examples/Screenshot: speech_bubbles.jpg
- New effect in Image menu: Add Shadow, Shape, Rounded corners, Snowflake etc.
- New effect in Image menu: Add Hexagon (or tiles), Star, Spikes, Heart etc.
- Show mouse zoom magnifier: CTRL+SHIFT + Mouse-move in the image
  (mouse wheel zooms within magnifier area, click inside closes it)
- New border effect in "Add Frame" dialog: Broken Edge
- New effect added: Radial Brighten (Effects browser dialog)
- New option in Capture dialog: Draw red circle around cursor
- New option in Advanced batch dialog: Set maximal dimensions for resize
- Profiles option added to Contact Sheet dialog
- Option to read 1 BPP images in RAW dialog
- Command line: /filepattern can be combined with /slideshow
- TIF/PCX/PSD loading bugs fixed (thanks to Apriorit)
-  Some PlugIns are changed/updated, please install the newest versions:


- Downloads @ Author site

- Irfanview (64-bit) @ Geeks3D
- Irfanview plugins (64-bit)  @ Geeks3D
- Irfanview (32-bit) @ Geeks3D
- Irfanview plugins (32-bit) @ Geeks3D

3D-Tech News Around The Web / Re: Download Zone - Latest Updates
« on: May 17, 2019, 04:36:49 PM »
Thanks, Irfanview + HWinFO updated.
ResetWU added!

VSCode and its tracker-free version VSCodium have been released in version 1.34.

Welcome to the April 2019 release of Visual Studio Code. During April, we were busy with the Preview release of the Remote Development extensions. These extensions let you work with VS Code over SSH on a remote machine or VM, in Windows Subsystem for Linux (WSL), or inside a Docker container. You can read the Remote Development with Visual Studio Code blog post to learn more.

Complete release notes about version 1.34 are available HERE.

You can download VSCode / VSCodium for Windows 64-bit from these links:

- VSCodium 1.34 win64 direct download
- VSCode 1.34 win64 direct download

or from the following pages:

- VSCodium 1.34 downloads
- VSCode downloads

VSCode / VSCodium

I updated the HTTP request sample of the Python 3 demopack to make it compliant with latest GeeXLab. I also added a secondary field for the script (/index.php for example):

- Python 3 Demopack Download

The demo is available in the py3-03-socket-http-request/ folder.

GeeXLab - Python 3 - HTTP request

A new GeeXLab is available for for Windows 64-bit, Linux 64-bit, macOS, Raspbian (Raspberry Pi) and TinkerOS (Tinker Board).

Release notes


Full changelog:

Version - 2019.05.14
. (2019.05.14) recompilation for all platforms, minor bugs fixed.
! (2019.05.14) updated Bullet3 plugin with latest version 2.88
  on macOS, Raspberry Pi and Tinker Board.
+ (2019.05.14) added Python 3 support on Raspberry Pi and Tinker Board.
+ (2019.05.13) added create_box_8v() to gh_mesh.
+ (2019.05.12) added create_from_file_loader_gltf() to gh_model.
! (2019.05.09) added automatic call to ImGui terminate function
  at the end of a demo. Useful if you forget to explicitly call it
  in the TERMINATE script...
+ (2019.05.08) added set_next_item_width() to gh_imgui lib.
! (2019.05.08) updated ImGui with latest version 1.70.
! (2019.05.08) updated SQLite3 with latest version 3.28.0.

GeeXLab for Tinker Board

Like Meltdown and Spectre, the new MDS attack takes advantage of security flaws in how Intel's chips perform speculative execution, a feature in which a processor guesses at what operations and data it will be asked to execute or access ahead of time to speed up the chip's performance.

In these new cases, researchers found that they could use speculative execution to trick Intel's processors into grabbing sensitive data that's moving from one component of a chip to another. Unlike Meltdown, which used speculative execution to grab sensitive data sitting in memory, MDS attacks focus on the buffers that sit between a chip's components, such as between a processor and its cache, the small portion of memory allotted to the processor to keep frequently accessed data close at hand.


RIDL and Fallout: MDS attacks
The RIDL and Fallout speculative execution attacks allow attackers to leak confidential data across arbitrary security boundaries on a victim system, for instance compromising data held in the cloud or leaking your information to malicious websites. Our attacks leak data by exploiting the newly disclosed Microarchitectural Data Sampling (or MDS) side-channel vulnerabilities in Intel CPUs. Unlike existing attacks, our attacks can leak arbitrary in-flight data from CPU-internal buffers (Line Fill Buffers, Load Ports, Store Buffers), including data never stored in CPU caches. We show that existing defenses against speculative execution attacks are inadequate, and in some cases actually make things worse. Attackers can use our attacks to obtain sensitive data despite mitigations, due to vulnerabilities deep inside Intel CPUs.


RIDL whitepaper:

Fallout whitepaper:

Disabling Hyper-Threading below 8th, 9th Gen CPUs can protect:
Intel in its white paper detailing the vulnerability admitted that disbaling HT might be warranted as a protection against MDS attacks - and you can imagine how much the company must have loathed to publish such a thing.


A new class of side channel vulnerabilities impacting all modern Intel chips have been disclosed, which can use speculative execution to potentially leak sensitive data from a system’s CPU.

Intel said that the newest class of vulnerabilities, dubbed Microarchitectural Data Sampling (MDS), consist of four different attacks, which all ultimately depend on different ways of executing side channel attacks to siphon data from impacted systems.


The  four different attack vectors are dubbed ZombieLoad, Fallout, RIDL (Rogue In-Flight Data Load) and Store-to-Leak Forwarding.


Intel said that the new MDS class of flaws is addressed in hardware starting with select 8th and 9th Generation Intel Core processors, as well as the 2nd Generation Intel Xeon Scalable processor family. Future chips will also have integrated fixes.

Source: Intel CPUs Impacted By New Class of Spectre-Like Attacks

CVEs assigned for MSD vulnerabilities
- CVE-2018-12126: Microarchitectural Store Buffer Data Sampling (MSBDS) - CVSS score 6.5: Medium, exploited by Fallout attack
- CVE-2018-12127: Microarchitectural Load Port Data Sampling (MLPDS) - CVSS score 6.5: Medium, exploited by RIDL attack
- CVE-2018-12130: Microarchitectural Fill Buffer Data Sampling (MFBDS) - CVSS score 6.5: Medium, exploited by RIDL attack
- CVE-2019-11091: Microarchitectural Data Sampling Uncacheable Memory (MDSUM) - CVSS score 3.8: Low, exploited by RIDL attack

Source: New RIDL and Fallout Attacks Impact All Modern Intel CPUs

Radeon GPU Profiler (RGP) is a tool from AMD that allows for deep inspection of GPU workloads.

The Radeon GPU Profiler (RGP) is a ground-breaking low-level optimization tool from AMD. It provides detailed timing information on Radeon Graphics using custom, built-in, hardware thread-tracing, allowing the developer deep inspection of GPU workloads.

This unique tool generates easy to understand visualizations of how your DirectX 12 and Vulkan games interact with the GPU at the hardware level. Profiling a game is both a quick, and simple process using the Radeon Developer Panel and the public display driver.

The new version 1.5.1 brings the following changes:

This release has support for detailed instruction tracing. This feature is currently available in the 19.10 driver for Ubuntu and the Adrenalin 2019 Edition 19.5.1 for Windows. Newer drivers will continue to support this feature.

Radeon GPU Profiler

-  Support for displaying profiles taken with instruction tracing data
-  Support for displaying user events in the Wavefront Occupancy timeline view
-  Support to display GCN ISA disassembly in the Pipeline state view
-  Support for showing and colorizing API PSO hash for each event
-  New grouping modes based on API PSO hash
-  Improved grouping of events and waves
-  Additional state bucket to support API PSO hashes
-  Barriers pane now has sortable columns in the table
-  Version number added to title bar
-  A Check For Updates feature has been added to alert users when a new version of the tool is available.

Radeon Developer Panel

- Support to capture detailed instruction tracing data based on API PSO hash
- Connection pane redesign with basic and advanced modes, allowing for a simpler workflow.
- Bug/stability fixes


Radeon GPU profiler

Change log for May 13, 2019 Vulkan 1.1.108 spec update:

  * Update release number to 108.

Internal Issues:

  * Clarify that only external resources can be bound to external memory in
    valid usage statements for flink:vkBindBufferMemory,
    flink:vkBindImageMemory, slink:VkSparseMemoryBind, and
    slink:VkSparseImageMemoryBind (internal issue 1496).
  * Move all `vk.xml`requirements for
    flink:vkGetDeviceGroupSurfacePresentModes2EXT into
    `<<VK_EXT_full_screen_exclusive>>` (internal issue 1622).
  * Add some missing valid usage statements for
    flink:vkCmdEndQueryIndexedEXT (internal issue 1638).
  * Specify rules for defining "`New Flags and Bitmask Types`" in that
    section of the style guide (internal issue 1649).
  * Add a comment to the `vk.xml` extension block for
    `VK_ANDROID_native_buffer` explaining why the extension is tagged
    `"disabled"` (internal issue 1657).
  * Fix typos in the description of slink:VkImageViewCreateInfo (internal
    issue 1661).
  * Modify valid usage statements for slink:VkImageViewCreateInfo to fix the
    description about the restriction for pname:baseArrayLayer and
    pname:layerCount from pname:extent.depth to the depth of mipmap level
    while creating a 2D array image view on a 3D image.
  * Forbid structures that contain opaque types (images or samplers) in the
    SPIR-V <<spirvenv-module-validation, Validation Rules within a Module>>
  * Minor editorial changes for the `VK_EXT_swapchain_colorspace` extension
    in the description of slink:VkColorSpace KHR and `vk.xml`, including:
  ** Consistently specify which function (OETF or Inverse-EOTF) is being
  ** Remove the Display P3 EOTF, since no other EOTFs are defined;
  ** Include luminance range for the HLG OETF;
  ** Remove a duplicated paragraph; and,
  ** Rename ename:VK_COLOR_SPACE_DISPLAY_P3_LINEAR_EXT, leaving the old
     ename:VK_COLOR_SPACE_DCI_P3_LINEAR_EXT token as an alias.

New Extensions:

  * `<<VK_NV_framebuffer_mixed_samples_coverage_reduction_mode>>`
  * `<<VK_KHR_uniform_buffer_standard_layout>>`


New extensions:
- VK_KHR_uniform_buffer_standard_layout
- VK_NV_framebuffer_mixed_samples_coverage_reduction_mode: not yet documented.

Toon rendering.

GeeXLab - Toon / cel-shading

Testing some outline techniques.

GeeXLab - Outline rendering

GeeXLab - Outline rendering

Geeks3D's GPU Tools / Glitches in Seascape demo, the return!
« on: May 12, 2019, 09:46:40 AM »
I received this screenshot:

GPU Caps Viewer - Seascape demo, visual glitches

Hardware: GeForce GTX 960M with latest 430.64 driver.

The artifacts are also visible on my RTX 2070. In Vulkan and OpenGL.
It's weird, because I never saw these artifacts nor received feedbacks before. Looks like something has changed in NV drivers recently...

I'm working on the demo...

NVIDIA has fixed several security flaws in recent graphics drivers and, for GeForce users / gamers, it's recommended to install the latest 430.64 that includes all security patches.

NVIDIA has released a software security update for the NVIDIA GPU Display Driver. This update addresses issues that may lead to denial of service, escalation of privileges, code execution, or information disclosure.

NVIDIA Windows GPU Display Driver contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DxgkDdiEscape where the product does not properly synchronize shared data, such as static variables across threads, which can lead to undefined behavior and unpredictable data changes, which may lead to denial of service, escalation of privileges, or information disclosure.

NVIDIA Windows GPU Display Driver installer software contains a vulnerability in which it incorrectly loads Windows system DLLs without validating the path or signature (also known as a binary planting or DLL preloading attack), leading to escalation of privileges through code execution.

NVIDIA Windows GPU Display Driver contains a vulnerability in the kernel mode layer (nvlddmkm.sys) handler for DeviceIoControl where the software reads from a buffer using buffer access mechanisms such as indexes or pointers that reference memory locations after the targeted buffer, which may lead to denial of service.


NVIDIA security patches in graphics driver - May 2019

We're continuing to expand the impact of Vulkan on Android, our implementation of the low-overhead, cross-platform API for high-performance 3D graphics. We’re working together with our device manufacturer partners to make Vulkan 1.1 a requirement on all 64-bit devices running Android Q and higher, and a recommendation for all 32-bit devices. For game and graphics developers using OpenGL, we’re also working towards a standard, updateable OpenGL driver for all devices built on Vulkan. In Android Q we're adding experimental support for ANGLE on top of Vulkan on Android devices. 

Android Q is the 10th version of Android.


Android Q

New features and changes:
Game Ready
- Provides the optimal gaming experience for RAGE 2, Total War: Three Kingdoms, and World War Z

Fixed Issues
- Fixes higher CPU usage by NVDisplay.Container.exe introduced in 430.39 driver. [2577118]
- [3DMark Time Spy]: Flickering observed when benchmark is launched. [200511272]
- [BeamNG]: The application crashes when the game is launched. [2575392]
- [Shadow of the Tomb Raider]: The game freezes when launched in SLI mode. [2575536]
- [Hitman 2 DirectX 12]: The game crashes. [2584342]
- The desktop flickers when videos are played on the secondary monitor. [2552316 2565509]

- Latest GeForce driver @ Geeks3D
- 430.64 win10 64-bit (desktop + notebook) @ NVIDIA
- 425.31 win7 64-bit (desktop) @ NVIDIA

GRD 430.64 exposes  OpenGL 4.6 (419 extensions) and Vulkan 1.1.99 for a GeForce RTX 2070, like previous GeForce 430.39

GPU Caps Viewer + RTX 2080

Do you happen to know, how to select the GPU in Linux?

I believe you can force the GPU by launching the app on the monitor connected to the GPU you want to test (assuming you have a monitor connector to each GPU). But I'm not sure. Maybe there is a way to force a particular display in command line using args like "localhost:0.1"...  Let me know if you find something interesting.

Beginning with Windows Insiders builds this Summer, we will include an in-house custom-built Linux kernel to underpin the newest version of the Windows Subsystem for Linux (WSL). This marks the first time that the Linux kernel will be included as a component in Windows. This is an exciting day for all of us on the Linux team at Microsoft and we are thrilled to be able to tell you a little bit about it.


The kernel itself will initially be based on version 4.19, the latest long-term stable release of Linux. The kernel will be rebased at the designation of new long-term stable releases to ensure that the WSL kernel always has the latest Linux goodness.


Pages: 1 2 [3] 4 5 ... 100