I have an issue with capture 17.2 base release and current ISR 031 running on windows 10 pro. What is going on is the screen refresh is slow whencapture is running. When capture loads it seems like you can see the tool bar icons getting drawn on the window, then they refresh and appear.
Moving Capture tool bar Icons across the screen has the effect of huge mouse trails on the canvas. The PCB editor works fine, Display is very fast. I tested capture v17.2 on windows server 2008 R2 and it works well.
Things I tried.
Re-InstallChecked Licensing - No issues foundVerified graphics card drivers were fine - Checked ok PCB editor is really fast.Checked windows logging etc - Nothing found.Ran capture as an admin - Made no difference.Disabled Firewall and anti virus software - Made no difference.
The issue seems to be related to win 10 Pro as things work fine on winserver 2008. I will do some more checking but in the mean timeif anyone has any pointers, that would be a big help.
Just a follow up on this issue with capture. I have isolated the problem to be related to Windows 10 release V1709 Build 16299.125 (Believe it is called fall creators edition)Running capture V17.2 with update 031 on windows 10 V1703 Build 15063.786 seems to work OK. Upgrading to the current version of windows 10 (MS Forced release) causes a big hit to capture on my system. I believe the issue relates to my Radeon video drivers even though the driver is valid on win 10. "Something changed with V1709 on win 10"On this newer release of win 10 the GUI in capture is very slow. When you move tool bars around inside capture you get rectangle ghosts on the screen, You can basicallyfill the screen completely with little rectangles :) , when you let the mouse button go the display refreshes and looks ok. The physical canvas where symbols are placeddoes not look to have this issue. Issue is only with the actual IDE in capture.
Over on the Orcad/Allegro PCB editor things look great even on the current ver of win 10. The open GL display is seriously fast, it is very impressive and a pleasure to use.Would be really nice if capture was OpenGL enabled too.
To run capture effectively on win 10 I may just go ahead and update my graphics card. Does anyone have a recommendation for use on win 10 that you found to work well ?I was looking at the AMD FirePro workstation cards. I am a bit on the fence with updating the video card as everything other than capture performs very well in the 2d rendering space. Older schematic capture programsalso work fine, Fast just like orcad pcb editor.
I have not updated my version of 10 pro, but will be cautious when I have to. Does any of the apps compatibility modes help with this problem? Does it generate any errors/warning in the windows logs?
In the windows logging I checked that and found noting. I tried invoking capture running as an administrator. The results above are still the same.Looking around the internet, I found a bunch of hits with respect to the current ver of win 10 causing issues in particular to games. I went ahead and ordered a new video card. It is way better than what I have now. It will be interesting to see if indeed a new video card is the fix, if it is not wellhey I have a new vid card
It would be great to hear if anyone else had updated their win 10 system to the latest and is experiencing the same issues. Win 10 is nice, I don't necessarily have to use it as a cad OS, but the apps - On day one all of them got uninstalled. I'm kind of the frame of mind that I don't want a cell phone as my desktop OS.
If I find anything else, I will update. FYI if you decide to bite the bullet and are on win 10 V release V1709 Build 16299.125 you can go back to the prior installed version.I went back to V1703 without any issues. Thanks Paul.
I'm having this issue as well. But, I'm having it with an nvidia 1050 graphics card and the latest drivers. And this is with a new kickass MOBO and i7 CPU. It's particularly bad when I'm trying to draw a new symbol and all the little icons on the tool bars update after every action. It's almost like ORCAD isn't taking advantage of 2D acceleration.
I've been seeing this too. I thought it was just my computer until I saw the same thing happing on a co-workers computer. CM in allegro has bouts of this also, just not as slow as Orcad.