Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
3D-Tech News Around The Web / (Demoscene) Experiments in Motion Graphics 1968
« Last post by Stefan on May 02, 2016, 08:40:12 PM »
Demo video by John Whitney @ IBM, 1968 (!)


Rendered on IBM 2250

IBM still offers the programming manual






62
3D-Tech News Around The Web / Intel HD Graphics Driver 20.19.15.4444
« Last post by Stefan on May 02, 2016, 05:12:28 PM »
DriverVer=04/22/2016,20.19.15.4444

64bit

32bit

No Vulkan support

No obvious changes to OpenGL
63
3D-Tech News Around The Web / NVIDIA GeForce Game Ready driver 365.10
« Last post by Stefan on May 02, 2016, 04:32:19 PM »
Quote
Our new GeForce Game Ready 365.10 WHQL drivers are optimized for Battleborn, Forza Motorsport 6: Apex Beta, the Overwatch Open Beta, and the ongoing Paragon Beta. To download and install, simply fire up GeForce Experience and click on the "Drivers" tab.
 

Gearbox Software's "hero shooter", Battleborn, launches May 3rd. Mixing first-person shooting with MOBA-style gameplay, Battleborn pits teams of players against one another online, or co-operatively in the game's story mode.
64
3D-Tech News Around The Web / Re: (Vulkan) Stardust demo/benchmark
« Last post by Stefan on April 26, 2016, 10:28:55 PM »
Sascha Willems forked a version fixed for AMD GCN 1.0 and NVIDIA

Demo runs 10 fps slower on NVIDIA 840M than on Intel HD 5500
Looks like there is room for optimisations...

65
3D-Tech News Around The Web / Re: (Vulkan) Stardust demo/benchmark
« Last post by Stefan on April 25, 2016, 06:33:17 PM »
I edited that in "normal" notepad (Windows), ok?

Windows' notepad dislikes big text files, also make sure the file is not saved as IGDLH64.INF.TXT

Maybe device name is wrong.

It's hard coded "GPU" for any GPU. I informed the developer, maybe he handles it in future correctly like with the Linux driver.
However patching it is only for your convenience, but not mandatory.
 
Run cmd (admin) and run "bcdedit..." but I got:...
I booted to choose "Disable Signed Driver Enforcement".
I tried to patch and to update driver with success... but VK-Z doesn't detect HD 4600 yet because look "bad" 2nd and 3rd steps.

I had noticed a BCDEDIT issue last autumn, and used an older version from WINDOWS.OLD folder at the time.


67
3D-Tech News Around The Web / Re: (Vulkan) Stardust demo/benchmark
« Last post by nuninho1980 on April 23, 2016, 07:42:22 PM »
1) patch igdlh64.inf with Notepad++

[iHSWM_w10]
FeatureScore=D1
CopyFiles=igfx.Miniport,

[iHSWM_w10]
FeatureScore=D1
CopyFiles=Vulkan.Copy , Vulkan.Copy32, igfx.Miniport,
I edited that in "normal" notepad (Windows), ok?

Quote
2) there is an issue in the runtimes giving all iGPUs the same device name: "GPU"
patch igvk64.dll and igvk32.dll with a hex editor

VK_KHR_win32_surface....
GPU.....
18:42:19........20.19.15

VK_KHR_win32_surface....
HD 4600.
18:42:19........20.19.15
Maybe device name is wrong. My i7-4790K has iGPU as "Intel(R) HD Graphics 4600".
I edited that in Hex Editor Neo 6.20.

Quote
3a)
disable driver signature - secure boot off

 bcdedit -set load options DISABLE_INTEGRITY_CHECKS
 bcdedit -set test signing ON

3b)
 disable driver signature - secure boot on

 bcdedit -set load options DISABLE_INTEGRITY_CHECKS
enable test signing via enhanced start options
Run cmd (admin) and run "bcdedit..." but I got:
Code: [Select]
The element data type specified is not recognized, or does not apply to the
specified entry.
Run "bcdedit /?" for command line assistance.
Element not found...

I booted to choose "Disable Signed Driver Enforcement".


I tried to patch and to update driver with success... but VK-Z doesn't detect HD 4600 yet because look "bad" 2nd and 3rd steps.
68
3D-Tech News Around The Web / Re: (Vulkan) Stardust demo/benchmark
« Last post by Stefan on April 22, 2016, 07:22:01 PM »
I tried to install Intel driver same version without "patched" for HD 4600 and I run VK-Z 0.2.0 but it detects 1 device as GTX 780 Ti and doesn't support HD 4600.

How do I patch Vulkan for HD4600?

1) patch igdlh64.inf with Notepad++

[iHSWM_w10]
FeatureScore=D1
CopyFiles=igfx.Miniport,

[iHSWM_w10]
FeatureScore=D1
CopyFiles=Vulkan.Copy , Vulkan.Copy32, igfx.Miniport,

2) there is an issue in the runtimes giving all iGPUs the same device name: "GPU"
patch igvk64.dll and igvk32.dll with a hex editor

VK_KHR_win32_surface....
GPU.....
18:42:19........20.19.15

VK_KHR_win32_surface....
HD 4600.
18:42:19........20.19.15



3a)
disable driver signature - secure boot off

 bcdedit -set load options DISABLE_INTEGRITY_CHECKS
 bcdedit -set test signing ON

3b)
 disable driver signature - secure boot on

 bcdedit -set load options DISABLE_INTEGRITY_CHECKS
enable test signing via enhanced start options

4)
Follow this fool-proof "havedisk" installation tutorial


5) check with VK-Z or Vulkan Hardware Capability Viewer
69
3D-Tech News Around The Web / NVIDIA R364.19 for Linux
« Last post by JeGX on April 22, 2016, 05:27:33 PM »
Quote
Release highlights since 364.15:
Added support for the following GPU:
Tesla M40 24GB

Fixed some locking issues in libnvidia-egl-wayland.so.
Fixed several libnvidia-egl-wayland.so interaction problems with buffer management Wayland protocols.

Downloads:
- Linux 64-bit
- Linux 32-bit
- Linux ARM
- Solaris
- FreeBSD 32-bit
- FreeBSD 64-bit

70
3D-Tech News Around The Web / Re: (Vulkan) Stardust demo/benchmark
« Last post by nuninho1980 on April 22, 2016, 04:57:00 PM »
I tried to install Intel driver same version without "patched" for HD 4600 and I run VK-Z 0.2.0 but it detects 1 device as GTX 780 Ti and doesn't support HD 4600.

How do I patch Vulkan for HD4600?
Pages: 1 ... 5 6 [7] 8 9 10