This is a serious issue with the sort of work I do, and I really need a resolution. I'm in my final 7 days of trial with progeCAD 2010 professional and if I can get it resolved, I'm definitely buying the software, but if I can't, then I'm definitely not.
I'm running the trial version of 10.0.6.23 progeCAD pro, Windows XP, Adobe Standard 8, don't know what else might be relevant. Here's a comprehensive list of my symptoms:
I have 8.5x11 layouts, in which I've drafted a border, and have a single viewport. In model space, I have .tif images inserted and scaled up, and I have drawing entities drawn on top of these .tif images. The .tif images aren't particularly large - 639kb black/white, for instance.
When I go to plot preview and select Adobe PDF as my printer, the viewport doesn't show up at all, neither the image, nor the model space drawing entities, but the paper space drawing entities do preview properly. If I then print, however, the result is a completely blank page.
When I go to plot preview and select a "real" printer (HP Laserjet P1006 for instance) then the paper space entities show up, and after a short wait the viewport entities show up as well, including the image. However, if I print, the result again is a completely blank page.
If I freeze the layer with the image in it, everything works as it should.
If I transfer the image to paper space entirely, delete the viewport, and then draft on top of the image in paper space, then it works. But that sucks because I need the ability to draft like a regular human being without having to scale everything.
I tried using the "ProgeSoft PDF Printer 2010" option, and I get an error message: "Printer not activated, error code -20," then says "could not start print job."
This has happened to me on two completely different drawing files with different images referenced in them, and it's driving me nuts. I'd really rather not buy AutoCAD because they're a bunch of nazis (or worse - expensive nazis) but if I can't get this bug figured out I probably won't have a choice.
I can't imagine that this sort of problem would go unnoticed, but I can't find reference to it using the search function in these forums. Someone please tell me there's a .dll or widget or workaround that fixes this problem.
Thanks in advance.
I'm running the trial version of 10.0.6.23 progeCAD pro, Windows XP, Adobe Standard 8, don't know what else might be relevant. Here's a comprehensive list of my symptoms:
I have 8.5x11 layouts, in which I've drafted a border, and have a single viewport. In model space, I have .tif images inserted and scaled up, and I have drawing entities drawn on top of these .tif images. The .tif images aren't particularly large - 639kb black/white, for instance.
When I go to plot preview and select Adobe PDF as my printer, the viewport doesn't show up at all, neither the image, nor the model space drawing entities, but the paper space drawing entities do preview properly. If I then print, however, the result is a completely blank page.
When I go to plot preview and select a "real" printer (HP Laserjet P1006 for instance) then the paper space entities show up, and after a short wait the viewport entities show up as well, including the image. However, if I print, the result again is a completely blank page.
If I freeze the layer with the image in it, everything works as it should.
If I transfer the image to paper space entirely, delete the viewport, and then draft on top of the image in paper space, then it works. But that sucks because I need the ability to draft like a regular human being without having to scale everything.
I tried using the "ProgeSoft PDF Printer 2010" option, and I get an error message: "Printer not activated, error code -20," then says "could not start print job."
This has happened to me on two completely different drawing files with different images referenced in them, and it's driving me nuts. I'd really rather not buy AutoCAD because they're a bunch of nazis (or worse - expensive nazis) but if I can't get this bug figured out I probably won't have a choice.
I can't imagine that this sort of problem would go unnoticed, but I can't find reference to it using the search function in these forums. Someone please tell me there's a .dll or widget or workaround that fixes this problem.
Thanks in advance.