Spacepilot ProE WF2 64bit trying to workaround but crashes

Clausen · Post by **Clausen** » Sun Jun 17, 2007 3:47 pm

Hi,

I've just been through the process of working out how I can use my spacepilot with WF2 64bit. I have the latest drivers for my spacepilot, but dont have the 3dxProE software installed. So my device happily moves my model around, but buttons dont work properly. So I have been creating mapkeys in pro, and making keystroke macros in the 3dxware control panel. This is a good enough arrangement to get some use out of my buttons.

The problem is that I want more than 6 buttons mapped, so I want to be able to use the config button to scroll through different sets of keys for parts, assy, sketching, etc. As far as i can see the way to do this is to save some different configurations in the 3dxware control panel, and use the config button to scroll through them.

That would be great except that my proE crashes every time I press the config button. It just disappears.

Any ideas how I could stop this from happening?

Regards

Paul

Post by **jwick** » Tue Jun 19, 2007 7:25 am

Hello Clausen,

Well, that should never happen!
Please turn on the driver log file and post the first few lines that show the version number and the last few lines before it crashes.

Thanks.
Jim
3Dx Software Development

Clausen · Post by **Clausen** » Tue Jun 19, 2007 4:04 pm

Hi, thanks for your reply,

Here's the whole thing

8:56:33.984: mwmtranslog - App sends us its handle under command event
8:56:33.984: UdCtl: Protocol 10 request to open connection for hwnd 0x4053c.
8:56:33.984: UdCtl: App transport list: 8:56:33.984: 50 8:56:33.984: 10 8:56:33.984:
8:56:33.984: UdCtl: Open accepted on protocol 10 for application: Unknown(xtop.exe)
8:56:33.984: UdArbitrate: New Target: hWnd: 0x4053c, Class Name: PGL_MOGL_WN_CLASS, AppName (SiOpen): Unknown, ExeName: xtop.exe
8:56:52.281: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
8:56:52.296: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
8:56:52.750: UdCtl: Closed application Unknown on protocol 0.
8:56:52.750: kbdtrans: UdTransClose request made
8:56:52.750: UdCtl: Closed application Unknown on protocol 50.
8:56:52.750: UdCtl: Closed application Unknown on protocol 10.
8:56:52.750: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\zpxc\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
8:56:52.765: UdUi:TlReadConfigFile: Reading file: C:\Documents and Settings\zpxc\Application Data\3Dconnexion\3DxWare\profiles\user03.scg
8:56:52.781: UdCtlTransSendSync: AppName=Unknown, sync->opCode=3, sync->itemCode=12
8:56:52.781: mwmtrans:UdTransSendSync: sending SI_SYNC_OP_SET.SI_SYNC_ITEM_AXES_STATE: item=12, hashCode=0x25b, state=0x3f
8:56:53.156: udui.cpp:QueryAppForGuiSync: Calling UdCtlSendSync
8:56:53.156: UdCtlTransSendSync: AppName=Unknown, sync->opCode=1, sync->itemCode=2
8:56:53.156: mwmtrans:UdTransSendSync: sending SI_SYNC_OP_COMMAND: item=2, hashCode=0x25b
8:56:53.187: UdArbitrate: New Target: hWnd: 0x103d2, Class Name: PGL_STD_WN_CLASS, AppName (SiOpen): Unknown, ExeName: xtop.exe
8:56:53.328: mwmtranslog - App sends us its handle under command event
8:56:53.328: UdCtl: Protocol 10 request to open connection for hwnd 0x103d6.
8:56:53.328: UdCtl: App transport list: 8:56:53.328: 50 8:56:53.328: 10 8:56:53.328:
8:56:53.343: UdArbitrate: New Target: hWnd: 0x103d6, Class Name: PGL_MOGL_WN_CLASS, AppName (SiOpen): Unknown, ExeName: xtop.exe
8:57:14.875: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
8:57:14.890: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
8:57:15.015: UdCtl: Closed application Unknown on protocol 0.
8:57:15.015: kbdtrans: UdTransClose request made
8:57:15.015: UdCtl: Closed application Unknown on protocol 50.
8:57:15.015: UdCtl: Closed application Unknown on protocol 10.
8:57:15.015: UdCtl: Closed application Unknown on protocol 0.
8:57:15.015: kbdtrans: UdTransClose request made
8:57:15.031: UdCtl: Closed application Unknown on protocol 50.
8:57:15.031: UdCtl: Closed application Unknown on protocol 10.
8:57:22.468: UdCtl: GUI State Change message received. Switching GUI On
8:57:22.468: UdUi->UdUiSetMode: SI_UI_ALL_CONTROLS
8:58:43.453: UdUi->Help: UI Help Called
8:59:20.424: UdCtl: GUI State Change message received. Switching GUI On
8:59:20.424: UdUi->UdUiSetMode: SI_UI_ALL_CONTROLS

Clausen · Post by **Clausen** » Tue Jun 19, 2007 4:09 pm

Here's the first bit and last bit of another one.

I wasnt sure if I did it right the first time.

8:56:33.984: mwmtranslog - App sends us its handle under command event
8:56:33.984: UdCtl: Protocol 10 request to open connection for hwnd 0x4053c.
8:56:33.984: UdCtl: App transport list: 8:56:33.984: 50 8:56:33.984: 10 8:56:33.984:
8:56:33.984: UdCtl: Open accepted on protocol 10 for application: Unknown(xtop.exe)
8:56:33.984: UdArbitrate: New Target: hWnd: 0x4053c, Class Name: PGL_MOGL_WN_CLASS, AppName (SiOpen): Unknown, ExeName: xtop.exe
8:56:52.281: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
8:56:52.296: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
8:56:52.750: UdCtl: Closed application Unknown on protocol 0.
8:56:52.750: kbdtrans: UdTransClose request made
8:56:52.750: UdCtl: Closed application Unknown on protocol 50.
8:56:52.750: UdCtl: Closed application Unknown on protocol 10.

9:6:1.145: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:6:2.301: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:6:3.114: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:6:7.005: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:6:12.537: kbtrans:UdTransSendEvent: Using macroMechanism = 0
9:6:32.179: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
9:6:32.179: UdUi:TlReadConfigFile: Reading file: C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxWare64\en_us\profiles\default\any.scg
9:6:32.288: UdCtl: Closed application Unknown on protocol 0.
9:6:32.288: kbdtrans: UdTransClose request made
9:6:32.288: UdCtl: Closed application Unknown on protocol 50.
9:6:32.288: UdCtl: Closed application Unknown on protocol 10.
9:6:32.288: UdCtl: Closed application Unknown on protocol 0.
9:6:32.288: kbdtrans: UdTransClose request made
9:6:32.288: UdCtl: Closed application Unknown on protocol 50.
9:6:32.288: UdCtl: Closed application Unknown on protocol 10.
9:6:39.898: UdCtl: GUI State Change message received. Switching GUI On
9:6:39.898: UdUi->UdUiSetMode: SI_UI_ALL_CONTROLS

Hope this can help

Paul

Post by **jwick** » Thu Jun 28, 2007 4:44 am

Hi Paul,

Try opening (with wordpad)

%APPDATA%\3dconnexion\3dxware\profiles\user03.scg
(or whatever your current proe config file is)

and change

APP_CONTROLS_BUTTONS = TRUE

to

APP_CONTROLS_BUTTONS = FALSE

Jim

Clausen · Post by **Clausen** » Thu Jun 28, 2007 3:57 pm

Hi Jim,

Thanks for getting back to me,

I tried that, and it still behaves the same. I restarted the computer to make sure it picked up the changes, but still the same,

I also tried the same alteration to all three of my .sgc files, then restarted the computer, and it's still the same.

Sometimes I can press the config button on the spacepilot a couple of times before it crashes, and sometimes it crashes on the first press. When i do press it, it says "cycle button mapping" on the spacepilot screen for a second then goes back to the same screen.

Also if i open the 3dxware control panel, have the button config tab open, and use the drop down to change from one config to another, it works properly, and i can see the changes come up on the spacepilot lcd. The config button is supposed to cycle through those different configs isnt it?

Regards,

Paul

Post by **jwick** » Thu Jun 28, 2007 5:54 pm

And just to be clear here, ProE is crashing, right? Not the 3DxWare driver.

Clausen · Post by **Clausen** » Thu Jun 28, 2007 7:53 pm

That's right, the pro-e windows just disappear instantly,

it seems to be that its cycling though the config files when i press the config button, and i think its when it gets to the "any application" one, proe crashes

ive tried some experiements, like deleting all of my config files and starting again with a couple of new ones (with your aforementioned modification in them). i found a command in the drop down list under each button called "config", so i mapped it to a normal number key and that seemed to work better than the normal config button.

i got it to the stage where it wouldnt crashThe problem is that i cant get rid of what seems to be the default config for proe, and when i try and set it's button 1 to "config" it wont stay there.

should i be trying to cycle through different configs to get different maps of keys on the buttons 1-6, or am i supposed to be able to map more buttons in the one config file? I'm hope that makes sense.

Paul
.

Post by **jwick** » Fri Jun 29, 2007 6:49 am

Hi Paul,

I regret that you are having all these problems. I think it might be rooted in the fact that early versions of 64-bit ProE didn't support the 3Dx devices correctly. As I recall that was fixed quite a while ago (WF3 spring 2006). You aren't by chance running a fairly early 64-bit version? It seems like it from the log file lines you sent and the symptoms you report. I see that mentioned WF2. I realise that you might not be able to upgrade ProE very easily.

There is a conflict with these early versions that causes 3DxProENGINEER to not work correctly. Please uninstall 3DxProE if you have it installed.

Jim
3Dx

Post by **ngomes** » Fri Jun 29, 2007 7:54 am

jwick wrote:Please uninstall 3DxProE if you have it installed.

Hi Paul,

To uninstall 3DxProENGINEER, go to the Add or Remove Programs panel, select "3Dconnexion 3DxSoftware" and click on the "Change" button. The modify wizard will come and, on the "Select Features" panel, deselect the "3Dconnexion Plug-In for Pro/ENGINEER" feature.

Clausen · Post by **Clausen** » Fri Jun 29, 2007 5:06 pm

Hi,

Yes as i mentioned in my initial post, I am using WF2 and dont have 3dxproE installed. That is why I am trying to work around by manually using the config button to change from assy to part to drawing button mappings because i dotn have 3dxproe automatitically switching mappigs when i open a different type of proE file.

I would have htought that withough 3dxproE installed, proe shoudlnt even know that the spacepilot is there? I guess it must because the controller still does move the model on the screen around

Paul

Post by **jwick** » Fri Jun 29, 2007 7:00 pm

Hi Paul,

ProE doesn't know exactly which device is out there. It is just getting axis and button events. It doesn't know about devices that have so many buttons though. Our theory is that it crashes because it gets a button number that is way out of its expected range. It is probably only expecting 8 or so buttons. But, mapping the config button to be used internally by the config function should prevent it from being sent to ProE. That is what is puzzling my puzzler.

Jim

Clausen · Post by **Clausen** » Wed Jul 04, 2007 3:45 pm

So how do I map the config button to make sure it is only used internally? Is that the default (non modifyable) setting for the config button on the spacepilot.

I think the clue might be in the fact that it seems to crash proE when the config button cycles through the different config files and reaches the "any application" config file. I dont seem to be able to remove that config file either.

Otherwise can you think of any work arounds for my work around?

Post by **jwick** » Thu Jul 05, 2007 6:18 am

Ah ha. Maybe you've hit on the key (so to speak) there. If you cycle to a config that does not consume the config button, but tries to send it on to ProE, that will probably kill proe. In fact, if you cycle to the default 3dxproe config file, that will do it.

You can disable any config file from being cycled through by:
1) start proe
2) select each configuration in the 3DxWare GUI
3) right click on the name in the 3DxWare GUI and choose Disable for this config. It will now be greyed out in the list and will be excluded from config cycling.

You could also delete the offending config file from disk, but that seems like a big hammer.

Finally you could change the setting inside the offending config file from:
BUTTON_28_USER = { UI_SB21, HOLD }
to
BUTTON_28_USER = { UI_CONFIG_KEY, HOLD }
to consume it internaly.

Jim

Clausen · Post by **Clausen** » Thu Jul 05, 2007 3:53 pm

Hi there,

I've tried disabling all of the configs except two that i created, but it still crashes.

How do you delete the "any application" config file? it doesnt appear in my user configs dir.

I'll try your last suggestion now

Thanks again