On another note, I'm liking the new autoplane measurement strategies. Seems like they still need some work, or I just have to get more used to them. It's definitely an improvement over the old autoplane, which would sometimes just generate a random nonsensical hit pattern that you would have to go in and adjust manually.
Does anyone use the text box mode to find invidual scan hits? i was having trouble getting this to work in 2017R1. Edit window with SHOW HITS on, Text box mode, and I cannot get the prgogram to select any hits. i do have the setting editor value for show scans as hits turned on as well. Happy Weekend All!!
2017 R1 still seems to have problems with Unigraphics DCI I keep altering the NX version In settings editor and this seems to work ok in some cases but not always I currently have two versions of NX installed 7.5 and 9.0, sometimes pcdmis crashes before program loads sometimes it does not load cad at all or I just get a visualization any ideas ? I created a brand new program in 2017.1 and imported an NX model so far so good saved and closed program then tried to re-open it and program crashed if I go back to pcdmis 2016 non of these issues arise and Unigraphics DCI works fine, I did report this in the tech review part of the forum but still have the same problem
CAD and graphic setup>Transparency>Probe>Enable transparency does nothing. Instead, ticking "Enable transparency" on part model and adjusting the slider will affect both the part model and probe model simultaneously. This does me no good when I'm trying to make the probe disappear because it's obstructing my view.
Now this may seem a little bit "out there", but wouldn't a known bug be fixed PRIOR to release of an official release. Or does that seem a bit far fetched?
Sweet! Looking forward to giving it a go. Using the latest version of 2016, I haven't encountered any problems yet other than a few minor issues. But those are easy to get around.
@bfire85: Just because it's a known bug now doesn't mean the fix was known enough in advance to make it into the release. As it doesn't really stop PC-DMIS from working, I can understand them leaving the fix for a Service Pack.
Will update with more information as I go along in 2017 R1
- 2017 R1 messes with my multimonitor setup. I can't get the PC-DMIS window to fill the entire screen. It saves the last window state, but not all the way to the screen edge, despite me moving it, extending it so it fills the screen... If I minimize PC-DMIS and maximize it again, the window layout is messed up, forcing me to reload my saved window layout.
- The icons for graphic objects (labels, GD&T, etc) are all activated when creating new programs. I am sure that 2016 "saved" a default state for me, where I only had the labels active. Is this not possible in 2017?
- I am not seeing the nn% speed increase either which the "Whats new"-screen promised. XactMeasure is slow in (2016) programs, despite saving them in 2017 and opening them again. AFAIC 2016 is much faster in this area. The redraw of the report is also faster in 2016.
-
I noticed that when doing a TP in XactMeasure the "Group" coordinates are always enabled (again!) when printing. This was corrected in an earlier version of PC-DMIS which enhanced the "quality of life" meaning it was NOT checked for printing. Now I have to uncheck this in each and every TP I create and as the XactMeasure is slooower in 2017 it worsens the user experience further... Update: When creating an FCF, the group coordinates are NOT checked. If I F9 the FCF then the group coordinates will automagically get checked.
- Surefire way to crash PC-DMIS: Create a program, save and close. Move the program (or delete it). Open the program from the most recently used list, click away any dialogs and PC-DMIS will crash. It will leave a 12kb "corpse" with the program name in the folder where your program used to be.
