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 ... 3 4 [5] 6 7 ... 104
Geeks3D's GPU Tools / Re: OpenCL stress test? [Kombuster]
« on: June 14, 2019, 03:27:59 PM »
The OpenCL test has not been removed... it has not been added (yet).
Kombustor v4 is new (even if it's a one-year old product) and I didn't have the time to put all tests of Kombustor v3 in the v4. The Plasma test (particles) is planned in a future update and I will do my best to add the OpenCL test too.

3D-Tech News Around The Web / NVIDIA GeForce RTX 20 SUPER Series
« on: June 13, 2019, 03:11:11 PM »
NVIDIA plans to release shortly (July?) a new set of graphics cards, all more or less derived from the current RTX 20 series.

The following new graphics cards are planned:
- RTX 2080 Ti SUPER (based on a new GPU )
- RTX 2080 SUPER based on a TU104-450 with 3072 shader cores (+128 shader cores or one extra SM compared to current RTX 2080)
- RTX 2070 Ti SUPER (based on a new GPU )
- RTX 2070 SUPER based on a TU104-410 with 2560 shader cores (+256 shader cores or two extra SMs compared to current RTX 2070)
- RTX 2060 SUPER based on a TU106-410 with 2176 shader cores (+256 shader cores or two extra SMs compared to current RTX 2060)



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

Adrenalin 19.6.1 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 / Vulkan Dos and Don’ts
« on: June 06, 2019, 08:38:29 PM »
After its popular DX12 Do's And Don'ts, NVIDIA publishes a new Dos/Donts, this time, for Vulkan:

The increased performance potential of modern graphics APIs is coupled with a dramatically increased level of developer responsibility. Optimal use of Vulkan is not a trivial concept, especially in the context of a large engine, and information about how to maximize performance is still somewhat sparse. The following document is a compilation of wisdom from some of the Vulkan experts at NVIDIA. It is not exhaustive, and is expected to be augmented over time, but should be a useful stepping stone for developers looking to utilize Vulkan to its full potential.


3D-Tech News Around The Web / Google speed test
« on: June 06, 2019, 07:41:43 PM »
Google has published a speed test to check the quality of your internet connection with Stadia.

This speed test provides a general indication of the quality of your connection, but does not guarantee playability on Stadia. Your gaming experience is dependent on a variety of factors, such as your device, internet service provider, and other bandwidth-consuming activities like downloads, file shares, and streaming.

Speed test:

I did a test:
- direct connection: I got 370Mbps
Your connection is great.
Based on your current download speed of 370.426 Mbps, we expect you’ll have a high-performance gaming experience on Stadia.

- connection via Opera's VPN: I got 17Mpbs
Your connection is good.
Based on your current download speed of 17.029 Mbps, we expect you’ll be able to play in high definition on Stadia, but you might not get 4K resolution.

Geeks3D's GPU Tools / FurMark 1.20.6 released
« on: June 06, 2019, 03:21:59 PM »
A new maintenance version of FurMark has been released:

Version - 2019-06-06
* fixed GPU-Z sensors reading.
! updated: GPU Shark and GPU-Z 2.21.0
! updated: ZoomGPU 1.23.1 (GPU monitoring library).

I did a quick test and set the temperature target to 66°C. I let the power target linked and it has been automatically set to 73 % TDP. I ran FurMark for 5min:

FurMark + MSI Afterburner + GeForce RTX 2070

Looks like NVIDIA driver properly limits the GPU temp.

FurMark does not set nor tweak nor play with driver settings. Never.  The only interaction with the driver is the reading of some sensors like GPU temp or usage. FurMark never updates drivers settings.  I currently have no explanation about your issue. FurMark is a 32-bit app. Did you notice this issue with another 32-bit app? Did you test on a non-LTSC Win10? Did you set the temperature target only or was-it also linked with the power target? I did a test with temp target=66°C and power target=100%TDP and in that case, the GPU temp during FurMark stress test has widely exceeded 66°C. FurMark does not care about temperature target or power target, it's the job of the driver to throttle back the GPU to respect user's settings.

Hope that helps  ;) 

We show how to compute global illumination efficiently in scenes with dynamic objects and lighting. We extend classic irradiance probes to a compact encoding of the full irradiance field in a scene. First, we compute the dynamic irradiance field using an efficient GPU memory layout, geometric ray tracing, and appropriate sampling rates without down-sampling or filtering prohibitively-large spherical textures. Second, we devise a robust filtered irradiance query, using a novel visibility-aware moment-based interpolant. We experimentally validate performance and accuracy tradeoffs and show that our method of dynamic diffuse global illumination (DDGI) robustly lights scenes of varying geometric and radiometric complexity. For completeness, we demonstrate results with a state of the art glossy ray tracing term for sampling the full dynamic light field and include reference GLSL code.


Dynamic Diffuse Global Illumination with Ray-Traced Irradiance Fields

3D-Tech News Around The Web / AMD gamedev / Vulkan presentations
« on: June 06, 2019, 11:11:34 AM »
The job of our worldwide developer technology engineers team is to directly help game developers to optimize their games, but also to educate developers by giving talks at various conferences and other events throughout the year. Recently I presented at Digital Dragons in Kraków (Poland), my colleague Lou Kramer visited Vulkanised in Cambridge (UK) to give a talk there, and Dominik Baumeister presented at Nordic Game.

- Optimising a AAA Vulkan Title on Desktop
- Triangles Are Precious – Let’s Treat Them with Care
- Make Your Game Friendly for Graphics Debugging and Optimization


3D-Tech News Around The Web / Python 3.8.0b1 available
« on: June 06, 2019, 11:04:17 AM »
Python 3.8 is still in development. This release, 3.8.0b1 is the first of four planned beta release previews. Beta release previews are intended to give the wider community the opportunity to test new features and bug fixes and to prepare their projects to support the new feature release.

Major new features of the 3.8 series, compared to 3.7
ome of the new major new features and changes in Python 3.8 are:
- PEP 572, Assignment expressions
- PEP 570, Positional-only arguments
- PEP 587, Python Initialization Configuration (improved embedding)
- PEP 590, Vectorcall: a fast calling protocol for CPython
- PEP 578, Runtime audit hooks
- PEP 574, Pickle protocol 5 with out-of-band data
- Typing-related: PEP 591 (Final qualifier), PEP 586 (Literal types), and PEP 589 (TypedDict)
- Parallel filesystem cache for compiled bytecode
- Debug builds share ABI as release builds
- f-strings support a handy = specifier for debugging
- continue is now legal in finally: blocks
- on Windows, the default asyncio event loop is now ProactorEventLoop
- on macOS, the spawn start method is now used by default in multiprocessing
- multiprocessing can now use shared memory segments to avoid pickling costs between processes
- typed_ast is merged back to CPython
- LOAD_GLOBAL is now 40% faster
- pickle now uses Protocol 4 by default, improving performance


For devs who embed Python in their apps (like in GeeXLab or in Blender), this PEP (Python Enhancement Proposals) is interesting:
Add a new C API to configure the Python Initialization providing finer control on the whole configuration and better error reporting.
- PEP 587 -- Python Initialization Configuration

python programming language

Geeks3D's GPU Tools / Re: GeForce GTX Zotac 1080 ti issue
« on: June 06, 2019, 10:54:27 AM »
yes, the only way to get the score box is to press on one of the benchmark buttons.

Geeks3D's GPU Tools / MSI Kombustor 4 v0.8.0.0 released
« on: June 05, 2019, 09:20:22 AM »
After nearly one year without update, MSI Kombustor is back with a new version. This version adds support of recent NVIDIA and AMD GPUs, fixes bugs in the Vulkan renderer and brings two new stress tests / benchmarks. The first benchmark (MSI-01) is a pure graphics stress test (tessellation + DoF + PBR) while the second benchmark is based on PhysX 4 and allows to test either the CPU (multi-threaded simulation) or the GPU. Benchmark scores can now be submitted online.



the FurMark stress test (OpenGL or Vulkan)
MSI Kombustor - FurMark stress test

the PhysX 4 stress test (CPU or GPU)
MSI Kombustor - PhysX 4 stress test

the tessellation / DoF / PBR stress test
MSI Kombustor - PhysX 4 stress test

This post is a walkthrough of the vulnerability that we discovered that allows execution of arbitrary commands on a system with the NVIDIA GeForce Experience (GFE) prior to version 3.19 installed – CVE-2019-5678. The exploit can be achieved by convincing a victim to visit a crafted web site and make a few key presses. This is possible due to command injection which was discovered in a local “Web Helper” server which GFE launches on startup.


MWR Labs stated in this blog post that GFE starts a local API server which allows control over different aspects of GFE. When you change a setting in the GFE GUI interface, it is likely just making a call to this local API. Knowing this, I thought it may be worthwhile to look into the API to see if there was any interesting functionality. The server that is started by GFE is NodeJS Express and many of the JavaScript source files can be found in “C:\Program Files (x86)\NVIDIA Corporation\NvNode”.



Installed on a i8-8700K with an UHD 630:
- OpenGL 4.6 with 250 extensions (GL=230 and WGL=20)
- Vulkan 1.1.103

Same GL/VK extensions than v6861.

Intel HD graphics driver v6890

With Windows Version 1903, we have added a new toggle in Graphics Settings for variable refresh rate. Variable refresh rate (VRR) is similar to NVIDIA’s G-SYNC and VESA DisplayPort Adaptive-Sync.

This new OS support is only to augment these experiences and does not replace them. You should continue to use G-SYNC / Adaptive-Sync normally. This toggle doesn’t override any of the settings you’ve already configured in the G-SYNC or Adaptive-Sync control panels.

This new toggle enables VRR support for DX11 full-screen games that did not support VRR natively, so these games can now benefit from your VRR hardware.


Windows 10 VRR setting

Change log for June 2, 2019 Vulkan 1.1.110 spec update:

  * Update release number to 110.

Github Issues:

  * Fix typo (public pull request 972).
  * Rename Pastel driver ID to SwiftShader (public pull request 974).

New Extensions:

  * `<<VK_EXT_fragment_shader_interlock>>`
  * `<<VK_NV_shader_sm_builtins>>`


New extensions
- VK_EXT_fragment_shader_interlock
- VK_NV_shader_sm_builtins

Geeks3D's GPU Tools / Re: FurMark 1.20.0 released
« on: June 03, 2019, 10:02:20 AM »
Maybe it's related to the fact that I removed the support of Windows XP in FurMark 1.20.3, looks like XP and Vista are the same for Microsoft's compiler...

Geeks3D's GPU Tools / Re: Glitches in Seascape demo, the return!
« on: June 03, 2019, 09:58:59 AM »
Yes the black rope. I found the issue, the new version will be available in the next GPU Caps Viewer.

Pages: 1 ... 3 4 [5] 6 7 ... 104