Wildfire 2 MDO Issues

[darcyo]

Hello,
I would like to know if anyone out there is having similar issues to me with regards to slow mechanisms in Wildfire 2.0. More specifically, I am on M030 and am running a mechanized motion using drivers. the driven motion of the assembly is extremely slow and choppy ONLY when i have parts who contain Inheritance Features! when i either remove the parts that contain Inh. feats. OR make a Simplified Rep that puts those parts to geometry rep, will the mechanism become buttery smooth. I do a great deal of MDO work and am wasting a lot of time with this issue. PTC is denying that i have a problem and are suggesting that this problem is due to the fact that they have decertified my DELL workstation/supercomputer. (infact the tech suggested that i try getting a new $10000 certified computer to fix this issue). f that...

if anyone has similar issues i would definately be interested in hearing about them.

I am going to try upgrading to M050 to see if this fixes this problem. i'll post if this fixes the problem.

thanks,
D'Arcy O.

 

[cfee]

This is HUGE ! Keep us posted?

BTW- Which video card are you using?

Also- Why did they "de-certify" a compatible system??
If Pro-E 2000 & 2001 ran successfully on your station, and W/F 2.0 runs successfully, why was the station de-certified for W/F 2.0 running the mechanism driver you use? Do they no longer want to support that particular platform? Their solution is for you to add $10k to the software purchase price? Whew!

Keep us updated ?

Thanks.

 

[darcyo]

hey, yeah, this is kinda huge. sorry to dissapoint, but i found out what the problem is... search_path_file... when i point to search_path locations over the network, my mechanism is slow and choppy, when i change the contents of search_path_file to only point to directories that are local, my mech will move smoothely. and this problem is still related to inheritance features in mechanism parts... i know that this is related to a software change made to 2001 where the software would recognise prt001.prt if it existed in any search_path locations already...