I keep having the experience that when I run PowerTRACE it says the bitmap is too large and must be reduced to trace. If I click cancel, X5 crashes immediately. If I click reduce it works sometimes and crashes sometimes. I tried tracing some of the same bitmaps in X3 and they worked fine. Is there something I need to change to allow PowerTRACE in X5 to run more smoothly? Is there a way to up the memory allotted to the program?
I'm running XP SP3 with an Intel Core 2 E8400 processor and 4gb of ram (3 of which XP actually knows how to use.) Not the most spectacular setup but it worked fine with X3. I tried adjusting the quality vs. performance option in the PowerTRACE settings but I can tell any difference. If anyone has run into this and/or has any suggestions I would appreciate your help. Thanks!
This is probably no help to you, Kevin, but I'm running X5 SP3 on XP SP3 and I don't think I've ever managed to crash PowerTrace. If I did, it was so seldom I've forgotten. I do occasionally get the message a bitmap is too big, but I click resize and it hums along.
So since we're running pretty much the same setup, maybe the difference lies elsewhere. Are the files you're tracing especially large or complicated?
Ok, we just switched from X3 to X5 not long ago so I've only run PowerTRACE a handful of times but it's crashed more times than it hasn't. Last time I was trying to use it was with a scanned file that was 600 dpi so that one was pretty high resolution. Other than that I don't think I've been trying to trace unusually large files. I do have a program called Vector Magic that is similar but gives you more options to customize the way it traces so I'll probably just have to use that for larger files. By the way, Vector Magic is worth checking out for anyone who's not familiar.
Thanks for your reply!
Hi Keven,
We have the same problem on 3 computers running Windows 7 and Coreldraw X5 sp3.
I assume that you haven't get an answer yet, but if you did: please let me know.
Thanks!
I hate to say it but my solution was to go back to using X3. There were a couple other things about X5 that I didn't really like so we're just going to return it for a refund. I hear X6 is supposed to be out early next year anyway so we're going to wait until then and hope they change the things we don't like about X5.
Assuming this is not an option for you I would suggest downsizing graphics before you attempt to trace them. When I was using X5 if I clicked trace and it gave the "bitmap is too large" warning it would always crash if I hit cancel. It would only crash some of the time if I chose to reduce bitmap. Most importantly, always save your work before you attempt to trace. I learned that one the hard way!
Well here it is in March of 2012 and I'm still looking to an answer for this same issue - W7 and X5 - Trace crashing Corel:(