Function Keys Fails to Lauch on SpacePilot Pro

Questions and answers about 3Dconnexion devices on Windows.

Moderator: Moderators

Post Reply
hgagne
Posts: 11
Joined: Sun Jun 10, 2012 8:54 am

Function Keys Fails to Lauch on SpacePilot Pro

Post by hgagne »

Hi Folks,

Posted about this issue a while back with no replies (viewtopic.php?f=25&t=7978).

Approximately 80% of the time, the Function Keys applet will fail to appear on my SpacePilot Pro on all of my workstations (Windows 7 Ultimate 64-bit). If I follow the procedure below, I can get the Function Keys applet to launch:

1. Open the Logitech LCD Manager (3.06.109 08/03/2010).
2. Launch Windows Task Manager (taskmgr.exe).
3. Select the Processes tab and select End Processs on 3DxLCD10SPPRO.EXE.
4. Select the Programs node in the Logitech LCD Manager.
5. Right-click on the Function Keys applet and select Start.

At this point, the Function Keys applet will not appear on the Space PilotPro display, the Function Keys applet will not display the "Running" status, and the Windows Task Manager will show the 3DxLCD10SPPRO.EXE process as running.

6. Select the Processes tab and select End Processs on 3DxLCD10SPPRO.EXE.
7. Select the Programs node in the Logitech LCD Manager.
8. Right-click on the Function Keys applet and select Start.

The Function Keys applet will appear on the Space PilotPro display, the Function Keys applet will display the "Running" status, and the Windows Task Manager will show the 3DxLCD10SPPRO.EXE process as running.

Additionally, I have noticed that changing options in the Logitech LCD Manager will occasionally crash after making option changes before closing the window (see error in code window below).

Obviously, I've gone through that typical workstation purging exercise of removing all Logitech & 3DConnexion related software from the workstation, removing extraneous folders and registry entries. I'm not opposed to trying a newer version of the Logitech LCD Manager software if one is available. Would just like to eliminate the above noted ritual from my daily workstation startup activites.

Regards,

Code: Select all

Version=1
EventType=APPCRASH
EventTime=130505976924749178
ReportType=2
Consent=1
ReportIdentifier=d930b257-1271-11e4-8abd-0010186f5463
IntegratorReportIdentifier=d930b256-1271-11e4-8abd-0010186f5463
Response.type=4
Sig[0].Name=Application Name
Sig[0].Value=LCDMon.exe
Sig[1].Name=Application Version
Sig[1].Value=3.6.109.0
Sig[2].Name=Application Timestamp
Sig[2].Value=4c58421d
Sig[3].Name=Fault Module Name
Sig[3].Value=ntdll.dll
Sig[4].Name=Fault Module Version
Sig[4].Value=6.1.7601.18247
Sig[5].Name=Fault Module Timestamp
Sig[5].Value=521eaf24
Sig[6].Name=Exception Code
Sig[6].Value=c0150010
Sig[7].Name=Exception Offset
Sig[7].Value=000000000006f822
DynamicSig[1].Name=OS Version
DynamicSig[1].Value=6.1.7601.2.1.0.256.1
DynamicSig[2].Name=Locale ID
DynamicSig[2].Value=4105
DynamicSig[22].Name=Additional Information 1
DynamicSig[22].Value=580c
DynamicSig[23].Name=Additional Information 2
DynamicSig[23].Value=580c55310ea55ec208c8f803df1b3c87
DynamicSig[24].Name=Additional Information 3
DynamicSig[24].Value=44c4
DynamicSig[25].Name=Additional Information 4
DynamicSig[25].Value=44c44fece3e2f5fde990de1f498f991a
UI[2]=C:\Program Files\Logitech\GamePanel Software\LCD Manager\LCDMon.exe
UI[3]=Logitech LCD Manager has stopped working
UI[4]=Windows can check online for a solution to the problem.
UI[5]=Check online for a solution and close the program
UI[6]=Check online for a solution later and close the program
UI[7]=Close the program
LoadedModule[0]=C:\Program Files\Logitech\GamePanel Software\LCD Manager\LCDMon.exe
LoadedModule[1]=C:\Windows\SYSTEM32\ntdll.dll
LoadedModule[2]=C:\Windows\system32\kernel32.dll
LoadedModule[3]=C:\Windows\system32\KERNELBASE.dll
LoadedModule[4]=C:\Windows\system32\USER32.dll
LoadedModule[5]=C:\Windows\system32\GDI32.dll
LoadedModule[6]=C:\Windows\system32\LPK.dll
LoadedModule[7]=C:\Windows\system32\USP10.dll
LoadedModule[8]=C:\Windows\system32\msvcrt.dll
LoadedModule[9]=C:\Windows\system32\MSIMG32.dll
LoadedModule[10]=C:\Windows\system32\COMDLG32.dll
LoadedModule[11]=C:\Windows\system32\SHLWAPI.dll
LoadedModule[12]=C:\Windows\WinSxS\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac\COMCTL32.dll
LoadedModule[13]=C:\Windows\system32\SHELL32.dll
LoadedModule[14]=C:\Windows\system32\WINSPOOL.DRV
LoadedModule[15]=C:\Windows\system32\ADVAPI32.dll
LoadedModule[16]=C:\Windows\SYSTEM32\sechost.dll
LoadedModule[17]=C:\Windows\system32\RPCRT4.dll
LoadedModule[18]=C:\Windows\system32\oledlg.dll
LoadedModule[19]=C:\Windows\system32\ole32.dll
LoadedModule[20]=C:\Windows\system32\OLEAUT32.dll
LoadedModule[21]=C:\Windows\WinSxS\amd64_microsoft.windows.gdiplus_6595b64144ccf1df_1.1.7601.18455_none_2b283fd671e9bf4d\gdiplus.dll
LoadedModule[22]=C:\Windows\system32\WINMM.dll
LoadedModule[23]=C:\Windows\system32\SETUPAPI.dll
LoadedModule[24]=C:\Windows\system32\CFGMGR32.dll
LoadedModule[25]=C:\Windows\system32\DEVOBJ.dll
LoadedModule[26]=C:\Windows\system32\HID.DLL
LoadedModule[27]=C:\Windows\system32\apphelp.dll
LoadedModule[28]=C:\Windows\AppPatch\AppPatch64\AcGenral.DLL
LoadedModule[29]=C:\Windows\system32\SspiCli.dll
LoadedModule[30]=C:\Windows\system32\sfc.dll
LoadedModule[31]=C:\Windows\system32\sfc_os.DLL
LoadedModule[32]=C:\Windows\system32\USERENV.dll
LoadedModule[33]=C:\Windows\system32\profapi.dll
LoadedModule[34]=C:\Windows\system32\dwmapi.dll
LoadedModule[35]=C:\Windows\system32\MPR.dll
LoadedModule[36]=C:\Windows\system32\IMM32.DLL
LoadedModule[37]=C:\Windows\system32\MSCTF.dll
LoadedModule[38]=C:\Windows\system32\uxtheme.dll
LoadedModule[39]=C:\Program Files\NVIDIA Corporation\nview\nview64.dll
LoadedModule[40]=C:\Windows\system32\PSAPI.DLL
LoadedModule[41]=C:\Windows\system32\VERSION.dll
LoadedModule[42]=C:\Windows\system32\WTSAPI32.dll
LoadedModule[43]=C:\Windows\system32\POWRPROF.dll
LoadedModule[44]=C:\Windows\system32\ntmarta.dll
LoadedModule[45]=C:\Windows\system32\WLDAP32.dll
LoadedModule[46]=C:\Program Files\NVIDIA Corporation\nview\NVWRSENU.dll
LoadedModule[47]=C:\Windows\system32\WindowsCodecs.dll
LoadedModule[48]=C:\Program Files\Common Files\microsoft shared\ink\tiptsf.dll
LoadedModule[49]=C:\Windows\system32\CRYPTBASE.dll
LoadedModule[50]=C:\Windows\system32\WINTRUST.dll
LoadedModule[51]=C:\Windows\system32\CRYPT32.dll
LoadedModule[52]=C:\Windows\system32\MSASN1.dll
LoadedModule[53]=C:\Program Files\Logitech\GamePanel Software\LCD Manager\LCDDevices\EDMBTDD.dll
LoadedModule[54]=C:\Program Files\Logitech\GamePanel Software\LCD Manager\LCDDevices\LCDExtDevMngrEmulator.dll
LoadedModule[55]=C:\Windows\system32\WINSTA.dll
LoadedModule[56]=C:\Windows\system32\CLBCatQ.DLL
LoadedModule[57]=C:\Windows\system32\oleacc.dll
LoadedModule[58]=C:\Windows\system32\CRYPTSP.dll
LoadedModule[59]=C:\Windows\system32\rsaenh.dll
LoadedModule[60]=C:\Windows\system32\RpcRtRemote.dll
LoadedModule[61]=C:\Windows\system32\SXS.DLL
LoadedModule[62]=C:\Windows\System32\hhctrl.ocx
LoadedModule[63]=C:\Windows\System32\itss.dll
LoadedModule[64]=C:\Windows\system32\urlmon.dll
LoadedModule[65]=C:\Windows\system32\api-ms-win-downlevel-ole32-l1-1-0.dll
LoadedModule[66]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l1-1-0.dll
LoadedModule[67]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l1-1-0.dll
LoadedModule[68]=C:\Windows\system32\api-ms-win-downlevel-user32-l1-1-0.dll
LoadedModule[69]=C:\Windows\system32\api-ms-win-downlevel-version-l1-1-0.dll
LoadedModule[70]=C:\Windows\system32\api-ms-win-downlevel-normaliz-l1-1-0.dll
LoadedModule[71]=C:\Windows\system32\normaliz.DLL
LoadedModule[72]=C:\Windows\system32\iertutil.dll
LoadedModule[73]=C:\Windows\system32\WININET.dll
LoadedModule[74]=C:\Windows\System32\ieframe.dll
LoadedModule[75]=C:\Windows\System32\api-ms-win-downlevel-shell32-l1-1-0.dll
LoadedModule[76]=C:\Windows\system32\api-ms-win-downlevel-shlwapi-l2-1-0.dll
LoadedModule[77]=C:\Windows\system32\Secur32.dll
LoadedModule[78]=C:\Windows\system32\api-ms-win-downlevel-advapi32-l2-1-0.dll
LoadedModule[79]=C:\Windows\System32\mshtml.dll
LoadedModule[80]=C:\Windows\system32\WS2_32.dll
LoadedModule[81]=C:\Windows\system32\NSI.dll
LoadedModule[82]=C:\Windows\system32\IPHLPAPI.DLL
LoadedModule[83]=C:\Windows\system32\WINNSI.DLL
LoadedModule[84]=C:\Windows\system32\mswsock.dll
LoadedModule[85]=C:\Windows\System32\wship6.dll
LoadedModule[86]=C:\Windows\system32\msimtf.dll
LoadedModule[87]=C:\Windows\system32\MLANG.dll
LoadedModule[88]=C:\Windows\system32\PROPSYS.dll
LoadedModule[89]=C:\Windows\System32\jscript9.dll
LoadedModule[90]=C:\Windows\system32\d2d1.dll
LoadedModule[91]=C:\Windows\system32\DWrite.dll
LoadedModule[92]=C:\Windows\system32\dxgi.dll
LoadedModule[93]=C:\Windows\system32\d3d11.dll
LoadedModule[94]=C:\Windows\system32\msls31.dll
FriendlyEventName=Stopped working
ConsentKey=APPCRASH
AppName=Logitech LCD Manager
AppPath=C:\Program Files\Logitech\GamePanel Software\LCD Manager\LCDMon.exe
hgagne
Posts: 11
Joined: Sun Jun 10, 2012 8:54 am

Re: Function Keys Fails to Lauch on SpacePilot Pro

Post by hgagne »

... strange, could have sworn there was an "Edit Post" option on this forum.

Driver details

3DxWare: 10.1.2
3DxWinCore: 17.1.2.10488

Logitech LCD Manager Software: 3.06.109 08/03/2010

Function Keys: 1.3.2.8789
C:\Program Files\Logitech\GamePanel Software\LCD Manager\Applets\3DxLCD10SPPRO.exe
stefanp
Posts: 2
Joined: Fri Oct 12, 2007 2:05 am

Re: Function Keys Fails to Lauch on SpacePilot Pro

Post by stefanp »

This problem is still present with 3DxWare 10.2.6 :cry:

How can this be resolved entirely?
Stefan
dseeni
Posts: 25
Joined: Wed Jul 01, 2015 9:12 am

Re: Function Keys Fails to Lauch on SpacePilot Pro

Post by dseeni »

I have this problem also, I use my SP PRO in Maya.

Anyway, before starting your 3d app, go to your task manager and find your LCD applet in your 3d connexion app c drive. I play around with terminating the process and restarting it from the drive and from the 3d connexion lcd driver pannel as well as task manager. After a few tries it works and I can see my hotkeys on the LCD. IT's super annoying though to do it everytime so I only put in the effort when I can't remember a new function key. Ugh so many bugs with the drivers.....................................................
dseeni
Posts: 25
Joined: Wed Jul 01, 2015 9:12 am

Re: Function Keys Fails to Lauch on SpacePilot Pro

Post by dseeni »

I have this problem also, I use my SP PRO in Maya.

Anyway, before starting your 3d app, go to your task manager and find your LCD applet in your 3d connexion app c drive. I play around with terminating the process and restarting it from the drive and from the 3d connexion lcd driver pannel as well as task manager. After a few tries it works and I can see my hotkeys on the LCD. IT's super annoying though to do it everytime so I only put in the effort when I can't remember a new function key. Ugh so many bugs with the drivers.....................................................
jhourihane
Posts: 1
Joined: Sat Aug 15, 2015 7:05 am

Re: Function Keys Fails to Lauch on SpacePilot Pro

Post by jhourihane »

Same problem here using 10.2.8 (64-bit) on Windows 8.1

The "fix" works but is very tedious and distracting, would be great to see this resolved.

Thanks.
Post Reply