3DxProENGINEER problem with Wildfire 3 x64

[mbonk]

The good news is: The beta version does not make it worse

True: The fixes for Pro/E x64 didn't make 3.1.1. They will be in 3.1.2, so no need to worry quite yet.

[alfredix]

The good news is: The beta version does not make it worse

True: The fixes for Pro/E x64 didn't make 3.1.1. They will be in 3.1.2, so no need to worry quite yet.

I hope you are not angry about my sarcastic post.
This was after more than an hour of trying the new version, sorry.

Is there a schedule for the 3.1.2?

Alfred

[mbonk]

Hi Alfred,

Absolutely no offense taken: we are new to posting betas publicly and if it were production code it wouldn't be beta.

Momentarily, there are no immediate plans to release 3.1.2 (which we are currently testing) as a beta.

Markus

[Brieldo]

an update on my situation. The only message I'm getting now is:
"Startup of application '3DxProENGINEER' failed"

In the lower message/info area, the message reads:

"Pro/TOOLKIT application '3DxProEngineer' was built to run with a newer version of Pro/Engineer."
"Pro/TOOLKIT version 0.0, Pro/ENGINEER version 27.0"


So, would this be the issue that will be resolved in the newer release?

[mbonk]

an update on my situation. The only message I'm getting now is:
"Startup of application '3DxProENGINEER' failed"

In the lower message/info area, the message reads:

"Pro/TOOLKIT application '3DxProEngineer' was built to run with a newer version of Pro/Engineer."
"Pro/TOOLKIT version 0.0, Pro/ENGINEER version 27.0"


So, would this be the issue that will be resolved in the newer release?

The short and sweet answer: Yes.

[Brieldo]

Where we at on the fixes for this issue? Us in industry work at a pretty rapid pace and would love to get a fix implemented. I know I'm not alone in this.

[ngomes]

Hi Brieldo,

Where we at on the fixes for this issue?

We have completed the qualification of our product for Pro/ENGINEER. The fix for Wildfire 3 x64 (add-in not loading) has been verified.
Unfortunately, the second beta of release 3.1 is delayed. We expect to have it available next week (tentatively set as version 3.1.3). We are sorry for frustrating your expectation but we cannot release code that does not meet our specs.

[DaveF]

Hi-

I am having the same problems as everyone else with the x64 version of WF2. Looking forward to the fix.

Is there an update planned for the other functionality of the SpaceBall within Windows x64? Mine still has zero functionality outside of ProE. I have heard that this is because the 3DxOffice plug-in has not been updated. Is there a timeline for that?

Thanks much!
-Dave

[Brieldo]

Still waiting to hear on this. I've been patient all week. I'm ready to throw this 400 dollar coaster at the wall.. ...

[ngomes]

Hi Brieldo,
The second beta of release 3.1, version 3.1.3, can be downloaded from the software page. Please make sure you uinstall version 3.1.1 first before updating.
We appreciate if you could post here your test results.

[alfredix]

Hello everybody,

I downloaded 3.1.3 beta.
Works fine.
No more senseless errormessages from Pro/E , Button mapping is working.
Only one "small" thing.
There are only pre configured mappings for Assemblies, which you can use as they are or create new ones.

but there is no mapping for Parts. If you open / create part, the mapping for Assembly is still active.
In configuration window, there is no option to Create a mapping for Parts.

If anybody has the same experience, let me know. Otherwise, I will blame, like usual, my machine

Good job guys from 3DConnexion, one down; still a few to go

Alfredix

[Brieldo]

Hi Brieldo,
The second beta of release 3.1, version 3.1.3, can be downloaded from the software page. Please make sure you uinstall version 3.1.1 first before updating.
We appreciate if you could post here your test results.

I'm in the midst of trying out 3.1.3. I'll say that even with 4GB RAM, the use of the SpacePilot induces a lot of lag following lots of movement of the part or assembly. Also, the 3dConnexion menu freezes probably 50% of the time when accessing it from within Pro/E. Finally, when using the SpacePilot and then reverting back to the mouse to do a movement, there is considerable lag, sometimes to the point of requiring a Cntl-Alt-Del and closing the xtop.exe process, and restarting pro/E. I will post more as I try various features out.

I should add that I'm using the following system and Pro/E version:

Dell Precision 690
Graphics Card: Quadro FX4500
Ram: 4GB

Pro/E:
Wildfire 3.0 x64
Datecode: M050

[JockeR]

- sorry, post was under wrong topic -

I'm removing it to

"Change window in Pro/E Wildfire - slower than before"