The latest driver (3.4.2) installs a protk.dat that you are to copy into the text directory of your Wildfire installation. There are several problems with the installation:
1. The path listed for the .dll file in the protk.dat is:
$ProgramFiles\3Dconnexion\3DxProENGINEER\x86e_win64\obj\3dxProe.dll
but the file resides at:
C:\Program Files\3Dconnexion\3Dconnexion 3DxSoftware\3DxProENGINEER64\x86e_win64\obj\3dxProe.dll
Once the path is corrected, the driver works fine in Wildfire 3 M070 64-bit
2. Protk.dat does not work in Wildfire 3 M070 32-bit. Can you recompile the toolkit app so it will run in 32-bit mode?
3. protk.dat does not work in Wildfire 2. If you do not load the toolkit app, you can use rotate and pan functionality in Wildfire 2, but once Wildfire 2 is launched, 3DxWare panel will not launch. Also, pushing any of the buttons can cause Wildfire 2 to exit. I know this has been discussed previously. I am just listing it for reference.
HP xw9300
Windows XP 64 bit OS
AMD Opteron 252 2.59 GHz
4 GB RAM
Wildfire 2 M200 32-bit & 64-bit
Wildfire 3 M070 32-bit & 64-bit
Problems with Pro/E Wildfire Driver
Moderator: Moderators
Re: Problems with Pro/E Wildfire Driver
Actually, the installer should either create a protk.dat file in the text directory, or if the installer finds one- this is not necessarily in the text directory - add the startup entries to it.Wayne wrote:The latest driver (3.4.2) installs a protk.dat that you are to copy into the text directory of your Wildfire installation.
The protk.dat file in the 3DxProengineer directory is a last resort and as the readme states "... may need editing", but I agree the installer should be able to put the correct path in it.
The 32bit plug-in can be found under C:\Program Files (x86)\3Dconnexion\...Wayne wrote:2. Protk.dat does not work in Wildfire 3 M070 32-bit. Can you recompile the toolkit app so it will run in 32-bit mode?
Markus
Markus,
I already had a protk.dat and it didn't append it, but I do have several different versions of Wildfire on the machine, so maybe it didn't know where to put it. If it did append it, would it have put in the wrong path anyway?
Thanks for pointing me to the location of the 32-bit plug-in. I will give that a shot. Is this in the documentation?
I already had a protk.dat and it didn't append it, but I do have several different versions of Wildfire on the machine, so maybe it didn't know where to put it. If it did append it, would it have put in the wrong path anyway?
Thanks for pointing me to the location of the 32-bit plug-in. I will give that a shot. Is this in the documentation?
Re: Problems with Pro/E Wildfire Driver
By the way, the 32-bit protk.dat also has the wrong path.mbonk wrote:The 32bit plug-in can be found under C:\Program Files (x86)\3Dconnexion\...
Markus
