Skip to main content
L
lukaskrasa
Participating Frequently
July 16, 2017
Question

Adobe Bridge CC2017 (7.0.0.93) + Windows 10 (1703) - software rendering only

  • July 16, 2017
  • 4 replies
  • 649 views

Hello,

I recently did clean install Windows 10 (1703) and Bridge CC2017 (7.0.0.93)only have software rendering option ticked and greyed out no matter what I did to solve this issue.

Wierd thing is that my dedicated GPU is normally detected by Photoshop or Camera Raw, only Bridge does seem to have problem to with hardware acceleration.

My system configuration :

Core I7 3610QM, 16GB RAM, Nvidia Geforce 650M, SSD 840pro, Windows 10 (1703) fully updated.

I tried:

- set dedicated GPU in nvidia panel + set compatibility view

- reinstalled nvidia drivers from newest 382 to 378.

- reinstalled both Photoshop and Bridge several times

- reset preferences

- turn off all bridge scripts

Everything worked fine on Win 8.1....

Please help!

sniffer log :

Tester="Photoshop"

snifferStart="2017-07-16_13:38:54"

AIFCoreInitialized=1

AIFOGLInitialized=1

OGLContextCreated=1

NumGLGPUs=1

glgpu[0].GLVersion="4.1"

glgpu[0].IsIntegratedGLGPU=0

glgpu[0].GLMemoryMB=2048

glgpu[0].GLName="NVIDIA GeForce GT 650M"

glgpu[0].GLVendor="NVIDIA Corporation"

glgpu[0].GLVendorID=4318

glgpu[0].GLDriverVersion="21.21.13.7892"

glgpu[0].GLRectTextureSize=16384

glgpu[0].GLRenderer="GeForce GT 650M/PCIe/SSE2"

glgpu[0].GLRendererID=4049

glgpu[0].HasGLNPOTSupport=1

glgpu[0].GLDriver="C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvd3dumx,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvwgf2umx,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvwgf2umx,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvwgf2umx,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvd3dum,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvwgf2um,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvwgf2um,C:\Windows\System32\DriverStore\FileRepository\nvdmi.inf_amd64_ea62e0c945f71b38\nvwgf2um"

glgpu[0].GLDriverDate="20170316000000.000000-000"

glgpu[0].CanCompileProgramGLSL=1

glgpu[0].GLFrameBufferOK=1

gputag.GL_SHADING_LANGUAGE_VERSION=35724

glgpu[0].glGetString[GL_SHADING_LANGUAGE_VERSION]="4.50 NVIDIA"

gputag.GL_FRAGMENT_PROGRAM_ARB=34820

gputag.GL_MAX_PROGRAM_INSTRUCTIONS_ARB=34977

glgpu[0].glGetProgramivARB[GL_FRAGMENT_PROGRAM_ARB][GL_MAX_PROGRAM_INSTRUCTIONS_ARB]=[65536]

gputag.GL_MAX_TEXTURE_UNITS=34018

glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_UNITS]=[4]

gputag.GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS=35661

glgpu[0].glGetIntegerv[GL_MAX_COMBINED_TEXTURE_IMAGE_UNITS]=[192]

gputag.GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS=35660

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_TEXTURE_IMAGE_UNITS]=[32]

gputag.GL_MAX_TEXTURE_IMAGE_UNITS=34930

glgpu[0].glGetIntegerv[GL_MAX_TEXTURE_IMAGE_UNITS]=[32]

gputag.GL_MAX_DRAW_BUFFERS=34852

glgpu[0].glGetIntegerv[GL_MAX_DRAW_BUFFERS]=[8]

gputag.GL_MAX_VERTEX_UNIFORM_COMPONENTS=35658

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_UNIFORM_COMPONENTS]=[4096]

gputag.GL_MAX_FRAGMENT_UNIFORM_COMPONENTS=35657

glgpu[0].glGetIntegerv[GL_MAX_FRAGMENT_UNIFORM_COMPONENTS]=[4096]

gputag.GL_MAX_VARYING_FLOATS=35659

glgpu[0].glGetIntegerv[GL_MAX_VARYING_FLOATS]=[124]

gputag.GL_MAX_VERTEX_ATTRIBS=34921

glgpu[0].glGetIntegerv[GL_MAX_VERTEX_ATTRIBS]=[16]

gputag.AIF::OGL::GL_ARB_VERTEX_PROGRAM=69

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_PROGRAM]=1

gputag.AIF::OGL::GL_ARB_FRAGMENT_PROGRAM=27

glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_PROGRAM]=1

gputag.AIF::OGL::GL_ARB_VERTEX_SHADER=70

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_SHADER]=1

gputag.AIF::OGL::GL_ARB_FRAGMENT_SHADER=28

glgpu[0].extension[AIF::OGL::GL_ARB_FRAGMENT_SHADER]=1

gputag.AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT=81

glgpu[0].extension[AIF::OGL::GL_EXT_FRAMEBUFFER_OBJECT]=1

gputag.AIF::OGL::GL_ARB_TEXTURE_RECTANGLE=58

glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_RECTANGLE]=1

gputag.AIF::OGL::GL_ARB_TEXTURE_FLOAT=53

glgpu[0].extension[AIF::OGL::GL_ARB_TEXTURE_FLOAT]=1

gputag.AIF::OGL::GL_ARB_OCCLUSION_QUERY=37

glgpu[0].extension[AIF::OGL::GL_ARB_OCCLUSION_QUERY]=1

gputag.AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT=68

glgpu[0].extension[AIF::OGL::GL_ARB_VERTEX_BUFFER_OBJECT]=1

gputag.AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD=47

glgpu[0].extension[AIF::OGL::GL_ARB_SHADER_TEXTURE_LOD]=1

NumCLGPUs=2

clgpu[0].CLPlatformVersion="1.2 "

clgpu[1].CLPlatformVersion="1.2"

clgpu[0].CLDeviceVersion="1.2 "

clgpu[1].CLDeviceVersion="1.2 CUDA"

clgpu[0].IsIntegratedCLGPU=1

clgpu[1].IsIntegratedCLGPU=0

clgpu[0].CLMemoryMB=1400

clgpu[1].CLMemoryMB=2048

clgpu[0].CLName="Intel(R) HD Graphics 4000"

clgpu[1].CLName="GeForce GT 650M"

clgpu[0].CLVendor="Intel(R) Corporation"

clgpu[1].CLVendor="NVIDIA Corporation"

clgpu[0].CLVendorID=32902

clgpu[1].CLVendorID=4318

clgpu[0].CLDriverVersion="10.18.10.4653"

clgpu[1].CLDriverVersion="378.92"

clgpu[0].CUDASupported=0

clgpu[1].CUDASupported=1

clgpu[1].CUDAVersion="8.0.0"

clgpu[0].CLBandwidth=2.35244e+10

clgpu[1].CLBandwidth=4.45613e+10

clgpu[0].CLCompute=121.325

clgpu[1].CLCompute=154.917

NumNativeGPUs=0

snifferEnd="2017-07-16_13:38:56"

-

This topic has been closed for replies.

4 replies

Deepak_Gupta1
Deepak_Gupta1
Participating Frequently
October 18, 2017

Hi All,

We have released a new version of Adobe Bridge (CC 2018) on 18 Oct 2017. The new version build number is 8.0.0.262. This version is available to install via Adobe Creative Cloud application.

Please check for GPU issue with the new update.

You may need to update the Creative Cloud application and restart your computer to see the updated installer.

Thanks,

Deepak Gupta

L
lukaskrasaAuthor
Participating Frequently
July 27, 2017

I switched back to Windows 8.1 and Adobe Bridge works as usual with GPU accelaration on.

Sorry guys, nothing helped.

L
lukaskrasaAuthor
Participating Frequently
July 18, 2017

I tried several nvidia drivers from different branches and it didn`t work. Why Bridge is seeing Integrated GPU and other Adobe products not? Bridge is set in Nvidia drivers to dedicated GPU as others.

Mohit Goyal
Community Manager
Mohit GoyalCommunity Manager
Community Manager
July 19, 2017

The switching to the NVIDIA graphics depends on application profiles. If an application has no such profile, you can assign the graphics card manually. Please refer the document: Assigning a graphics card to an application with NVIDIA Optimus

Regards,

Mohit

L
lukaskrasaAuthor
Participating Frequently
July 20, 2017

Please stop with this copy&paste crappy responses, it´s not helpful and really annoying, because it´s listed as something I already tried in original post!!!

Sahil.Chawla
Adobe Employee
Sahil.Chawla
Adobe Employee
July 18, 2017

Hi Lukaskrasa,

Could you please refer to this thread and let us know if it helps:

Hardware acceleration disabled in BridgeCC2015 suddenly

Regards,
Sahil

L
lukaskrasaAuthor
Participating Frequently
July 18, 2017

Yes, i did read that post and tried everything, unfortunately the thread ends with "Connecting with you over email." .... not very helpful for others.

I´am getting very frustated honestly... my deskop PC with GTX980ti and Windows s8.1 works normally.

What to do? Is there any chance how to force Bridge to use hardware acceleration?

Thanks again

Sahil.Chawla
Adobe Employee
Sahil.Chawla
Adobe Employee
July 18, 2017

It should work for Bridge as well. Bridge would only reject the GPU if it was blacklisted (known defective), the driver failed, or the driver said that the GPU didn't have the needed capabilities. That still suggests to me that Bridge is seeing the integrated GPU and not the dedicated GPU (which is a function of the OS/driver).

Terms & ConditionsAccessibility statement
Using the community Terms of use Privacy Cookie preferences Do not sell or share my personal information ad choicesAdChoices