ProE Config Cycling

[isomorphous]

My Space Pilot doesn't cycle through configs when pressing the config button within ProE. I currently have two different configs and 3DxProE is NOT installed.

After searching, I tried the solutions from the following post like disabling unused configs and changing app_controls_buttons to false, and the recommended BUTTON_28_USER = { UI_CONFIG_KEY, HOLD } but nothing helps:

viewtopic.php?t=1147&view=next&sid=df40 ... 7c88c98137

ProE occasionally would crash when trying to cycle (but still never cycle) but using the methods in the referenced post crashing stopped but cycling still doesn't happen.

When I press the button, the screen on the device flashes "Cycle Button Mapping" but nothing happens. I can still switch the configs manually via the 3DConnexion Control Panel.

Windows XP Pro 32 SP2, Wildfire3, Driver 3.6.7, Firmware 3.12

Thanks for any help!

[isomorphous]

Delving deeper into the problem. It still causes ProE to crash occasionally. Here is a portion of the log file with failure to roll the config file:

Any ideas?


16:53:52.777: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\xxxxx\Application Data\3Dconnexion\3DxWare\profiles\user01.scg
16:53:52.855: UdArbitrate: New Target: hWnd: 0x54048e, Class Name: PGL_STD_WN_CLASS, AppName (SiOpen): Pro/ENGINEER, ExeName: xtop.exe
16:53:52.855: UdCtl: Open accepted on protocol 30 for application: Pro/ENGINEER(xtop.exe)
16:53:52.855: mwmtranslog - App sends us its handle under command event
16:53:52.855: UdCtl: Protocol 10 request to open connection for hwnd 0x54048e.
16:53:52.855: UdCtl: Open denied on protocol 10. Already have connection on protocol 30.
16:53:52.855: mwmtranslog - UdCtlOpen failed
16:54:2.105: mwmtranslog - App sends us its handle under command event
16:54:2.105: UdCtl: Protocol 10 request to open connection for hwnd 0x990422.
16:54:2.105: UdCtl: Open denied on protocol 10. Already have connection on protocol 30.
16:54:2.105: mwmtranslog - UdCtlOpen failed
16:54:2.105: mwmtranslog - App sends us its handle under command event
16:54:2.105: UdCtl: Protocol 10 request to open connection for hwnd 0x4f0494.
16:54:2.105: UdCtl: Open denied on protocol 10. Already have connection on protocol 30.
16:54:2.105: mwmtranslog - UdCtlOpen failed
16:54:2.105: mwmtranslog - App sends us its handle under command event
16:54:2.105: UdCtl: Protocol 10 request to open connection for hwnd 0x990422.
16:54:2.121: UdCtl: Open denied on protocol 10. Already have connection on protocol 30.
16:54:2.121: mwmtranslog - UdCtlOpen failed

[rstadie]

Hi,

Thank you for this information. Currently I am trying to reproduce this issue. Please let me know if you find out something new - I will come back to you as soon as I have news on this.

Could you please send a trail.txt including the crash to me? You will find my Email-address in your inbox.

[isomorphous]

Just adding the solution for future record and to the benefit of those that might run into the same problem I did.

Thanks to rstadie and all his help in resolving this issue! I would have been hopelessly lost without his help. It turns out that once 3DxProEngineer was activated and running within ProE, the crashing stopped and the config profiles would cycle. The 3Dx plugin was never activated in ProE due to a company wide custom installation of ProE. The plugin is registered and started within ProE when written into the protk.dat file but the custom installation of ProE prevented this and would overwrite the protk.dat file every time that the program was started. The solution was two-fold: I created a custon protk.dat file and a config.pro path entry that pointed to the new protk.dat file. The correct paths also had to be entered in the protk.dat file within the 3Dx directory. Once these were in place, everything worked. After 1 week, ProE has yet to crash, the config profiles change on command, and I have full capabilities provided by the ProE plugin.

Thanks again rstadie!

[rstadie]

Hi,

Some buttons cause specific Pro/E versions to crash (only if our PlugIn is not installed - so we can not avoid the crash). This issue seems to have been fixed in WF3 M120 - which version of Pro/E do you use?

[chaseacej]

I am having the same issue as you. If you could tell me what you had to add to the protk.dat file and anything else would be great.

Thanks.

[rstadie]

Hi chaseacej,

Under

Code: Select all

C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxProENGINEER\i486_nt\

you will find an example protk.dat-file. You will need to adjust the paths and copy the file to the "text" subdirectory of Pro/E.

[chaseacej]

Our Pro/E is installed on a network so I do not have access to the Pro/E install directory.

[rstadie]

Please see this article about Pro/E being installed on a server.
You will need to adjust the protk.dat file which is used by your instance of Pro/E in order to load the Plug-In.