Visual C++ runtime error - anyone else? -> How to Fix??
Message 1 of 13
Message 2 of 13
Among the many other is also this occurs on 2012 that i would describe the worst version of any software i have ever had , never had many problems with a software, what they tried in 2 beta?
Message 3 of 13
Hi, I'm not a cam ,use only cad but i didn't have the same problem , i have removed all the template and the bundle of the Ver.2011 that i imported and tilework healthy plan, the problem has not occurred more (babylon traslator)
Message 4 of 13
Message 5 of 13
Message 6 of 13
Was having these same or similar issues on previous config, (started this thread) before 2012SP1. 2011SP2 I don't think did this. However it does now. The only VCredist installed on the system was packaged with ZW3D 2012SP1..
Fresh OS install, storage update. Else is all the same! 2K3r2 SP2.
Stinks man. I'm going to have to go to an older system config..
Message 7 of 13
Simplest fix and least resources, is to use the microsoft native video driver for a given video board. You guys(zwsoft) need to look long and hard at what nVidia is doing with their next gen boards and drivers. These are causing the problems that I've been having. The old driver sets do not cause these same issues, as I can tell, at this point. they also do not perform as well as the latest drivers..
If you run an Quadro FX engineering graphics board, driver 275 is where you really should stop. I'll know more later on the Quadro Fermi Based boards with 295 driver and beyond.
295 driver works well with the FX boards, and for ALL other ENG apps I run. BUT NOT ZW3D. The 295 drivers, on FX is simply clean and free of aliasing and fast fast fast. Tool path verify would go so fast I could not even see the cutter.. But would blowup everytime as memory stacked to 1.8gig, not releasing memory resources... And then crashing C libs..
Well that's it for now.. I expect more from my CAD/CAM software than video issues. Video is what these systems are about!
Message 8 of 13
Please see the Video Best Practices thread. This is not resolved, but I have found that certain drivers for the nVidia boards cause different behaviors. Also, I have found drivers that work and do not cause Z3D to blow-up VS C++ redist., during solid verify based on a clean install of OS and ZW3D 2012SP1, with FX and Fermi boards.
Message 9 of 13
Thanks for the detailed test of the graphic card driver, it is very helpful for our test in the new graphic enhancement project. With more and more efforts on the V17 development, we are getting more and more progress, which will enable us to assure the graphic enhancement and optimization in V17.
I'm also looking to get more feedback your Video Best Practices thread.
Message 10 of 13
As the world moves on to 64 bit ZW is still 32 bit so you have a severe memory cap. There are only two things I know to do.
You have to just reboot sometimes. There is also in CAM under tools two items of note. "clean quickmill cache" and "clean quickmill dir". There can be a ton of stuff pile up in here and it will effect performance with ZW so clean it outwhen you are having problems. An old Mike Lynch tried and true trick, boy do I miss him and Earl Thornton.
I posted a part here recently that never would finish verify due to memory problems. I did finally get it to finish and reboot and cleaning the quickmill stuff is I am guessing what worked. This may be worth a try for your problem to.
Message 11 of 13
I and another operator have been having all sorts of graphics related problems in 2012. Curiously the same files run good on 2011. our conclusion is that there is a difference between the two versions that is a real party stopper. These issues need to be resolved in 2012 SP2.
FT is right when he says ZW needs to really get it sorted with nVidia All levels.
Re 64 bit.
As I understand it, 2012 is V15. That means 2013 will be 32 bit only? If so, then I am thinking this is definitely not good enough as Cutter.
2013 needs to be 32/64bit no question.
Please update on these issues.
Message 12 of 13
Please post what video board and driver versions you are using in the Video Best Practices thread. This is the only way we will get this figured out. Visual Studio Runtime has issues when combined with some code since 2010. I found a couple things that happen when the driver is going to work correctly. Mainly, memory usage is greatly decreased. AND typically when there is a tool change memory is released for the completed path. BUT not always.
My understanding is, 2013 or V17 as it were, will be 64bit. I guess the question is will there be a 32bit and a 64bit version starting 2013. There's really no need for 32bit beyond 2013.
The Visual Studio runtime vCredist.exe(version), works with driver version 275.36 Unified driver, perfectly well. I get ZERO blowups. If I load any of the later drivers tool paths simply will not finish if they have any length and complexity. But that(275.36) driver is not so good from a shader, anti-alias, and OGL for 2012, as compared to the later drivers.
Assembly routines are the best practice for this type of code rather than C++ and can be directly compiled in with the C routines without external calls. These routines execute fastest and are smallest in size but most difficult to write. Out of school I programmed video libraries in C/Assembly for automation along side a buddy who programmed Assembly/PASCAL. You are earning your pay if you are doing it correctly. (well out of the scope of this thread)
These discusions need to move to the Video Board thread.
aka - FT/Factorytuned
Message 13 of 13
The answer I think is not to try to find a specific graphics driver and hope for the best. From the sounds of it there are a number of drivers used here and problems with I am gathering more than one. I still tend to think it is more than just graphics which is why I made the suggestion above. One thing I have observed with every company that went to 64 bit is it is not trouble free and I wonder if some of this graphics stuff is becuase of the intitial moves towards 64 bit. So this brings me back to drivers are not the answer if the underlying code in ZW is screwed up. Considering the weird problems I am having with tool path generation I have to wonder if they are are related to changes in the program. 64 bit is not going to be fun is my thought here as people with far more money and experienced coders have lots of trouble so just what exactly is ZW going to bring to the table I wonder. Personaly I have stayed with 2012 SP0 as it seems to be more stable.
- autocad autosave location
- dgn to dwg
- 2d drawing to 3d model
- autocad area calculation
- how to open dwg on ipad
- autocad 2012 serial number
- Dwg Converter
- catia windows 8
- can i change a raster image to a hatch
- autocad .bak viewer
- cad corner blocks
- zwcad price in india
- what is cam software
- dgn to dwg converter
- how to import autocad file into sketchup 2013