Realistic View will not Print!

[tampac66]

Every sheet that has a realistic view shown on it, does not print. It hangs up and does nothing. Does anyone else have this issue? Or am i doing something wrong?

[cliff collins]

Try setting print settings to Raster, not Vector.

Does that help?

cheers

[tampac66]

Try setting print settings to Raster, not Vector.

Does that help?

cheers

That is what i did it on. I haven't tried it on Vector though, ill give that a shot.

Edit: Nope.. no dice

[rkitect]

Just out of curiosity, could you try this with TaskManager open and see what happens to your Revit memory usage after you hit print? This sounds vaguely familiar with the good ol' print too large issue that we often have when printing some sheets. These sheets cause Revit's memory usage to skyrocket and Revit just sits there until the print command is canceled.

[tampac66]

Just out of curiosity, could you try this with TaskManager open and see what happens to your Revit memory usage after you hit print? This sounds vaguely familiar with the good ol' print too large issue that we often have when printing some sheets. These sheets cause Revit's memory usage to skyrocket and Revit just sits there until the print command is canceled.


It definitely just sits there says "100%" until i cancel the print from the printer, then i hit escape and cancel it in Revit. However, the CPU usage isn't going as crazy as i expected. It jumps between 10-90% sitting mostly around 60%. System memory is fine.

Still, no print though.

[cliff collins]

Will the realistic views themselves print? i.e. not being on a sheet?

Try this:

Duplicate one of the realistic views, then change it to smaller viewport size,
and see if it prints.

Also, try turning off AO if it's on.

Just some troubleshooting ideas.......

cheers

[rkitect]

...System memory is fine.

Still, no print though.

Interesting indeed. Is this just to the one printer or can you try printing to a PDF and then sending it to a printer? Export the sheet to DWF then try printing? A whole assortment of debugging SOP run through my mind.

[josh.made4worship]

I just printed a project I have to PDF (see attached)...not printing Ambient Occlusion is a known issue...(see attached Screen shot of Revit in same view with ambient occlusion turned on).

So, anyway, seems to be printing ok for me (besides the ambient occlusion).

[tampac66]

Hey guys. I got it to work. It turns out that it was just taking so long to load/print those pages that i thought i was hung up. Ended up taking about 10 min to print 1 page with a realistic view.

However, Ambient Occlusion was on so i may turn it off and try.

[josh.made4worship]

Can you post an image of what you were trying to print? Mine only took about 30 secs to print...but your model is probably a lot bigger than mine??? What's the speed of your machine? Were you printing to PDF or a local printer or a network printer?

[narlee]

So far as I can tell, Ambient Occlusion does not print. When making either an image export, or printing, raster or vector, it does not take...

[narlee]

However, you can do the following: Hit the Print Screen Button, Paste into a Paint program, Crop to the view. Hopefully, Revit will fix this bug.

[josh.made4worship]

However, you can do the following: Hit the Print Screen Button, Paste into a Paint program, Crop to the view. Hopefully, Revit will fix this bug.

Correct, that's how I was able to get the jpeg image with it showing, but my PDF "printed" from Revit doesn't show it.

[narlee]

So far as I can tell, Ambient Occlusion does not print. When making either an image export, or printing, raster or vector, it does not take...

I'm wrong. If you export to a jpeg, AO prints.

[tropitech]

if it took 10 minutes to print a single sheet i'd be looking at the speed of your hardware

[narlee]

So, I guess a current workaround would be to:

1) Export as an image(s), with Ambient Occlusion turned on.
2) Import that (those) image(s) onto a sheet.
3) Adjust the image size to match the original view crop size (if you wanted to keep the same scale.

I tested a simple one, and the quality seemed ok.

[Alex Page]

So, I guess a current workaround would be to:

1) Export as an image(s), with Ambient Occlusion turned on.
2) Import that (those) image(s) onto a sheet.
3) Adjust the image size to match the original view crop size (if you wanted to keep the same scale.

I tested a simple one, and the quality seemed ok.

Even easier (I think its a new feature in 2011) - when in the view - right click on the name (within the project browser) and "Save ro project as Image"
A nice little time saver

[martijnderiet]

Even easier (I think its a new feature in 2011) - when in the view - right click on the name (within the project browser) and "Save ro project as Image"
A nice little time saver

This is indeed a new feature in 2011... Very handy one too!
Too bad you have to use this in order to get AO to work! Don't see the benefits off a graphics style that you can't print.

But, back on topic: 10 minutes is a very long time for a print! What dpi-settings are you on?

[narlee]

Even easier (I think its a new feature in 2011) - when in the view - right click on the name (within the project browser) and "Save ro project as Image"
A nice little time saver

Ah! Thanks, Alex. Every little time-saver helps!

[ron.sanpedro]

Even easier (I think its a new feature in 2011) - when in the view - right click on the name (within the project browser) and "Save ro project as Image"
A nice little time saver

Just be aware that Revit will report a bogus scale. If you make an image from a scaled view, it will indeed be a scaled image, and dropping it on a sheet next to the original view it is almost indistinguishable. BUT it will only claim a scale of 1"=1', or maybe 12"=1', I don't remember now. It is to a scale, but it reports a scale that is totally wrong (the majority of the time, as the reported scale is rarely used, and so will rarely be the scale of the original view). Once again Audesk manages to get something so close to right, and yet manages to drop the ball in the end, know about before the product ships, and choose to ship it broken rather than get it right. It seems a trivial fix, so I hope for a resolution in sp1, but then I had also hoped for a fix by ship date, to no avail.

Gordon

[narlee]

Just be aware that Revit will report a bogus scale. If you make an image from a scaled view, it will indeed be a scaled image, and dropping it on a sheet next to the original view it is almost indistinguishable. BUT it will only claim a scale of 1"=1', or maybe 12"=1', I don't remember now. It is to a scale, but it reports a scale that is totally wrong (the majority of the time, as the reported scale is rarely used, and so will rarely be the scale of the original view). Once again Audesk manages to get something so close to right, and yet manages to drop the ball in the end, know about before the product ships, and choose to ship it broken rather than get it right. It seems a trivial fix, so I hope for a resolution in sp1, but then I had also hoped for a fix by ship date, to no avail.

Gordon

That's a great point. You'd have to overwrite the scale indication.

[dfriesen]

That's a great point. You'd have to overwrite the scale indication.
I just tried it, making an image from a plan. The plan is at 1/8"=1'-0", and the image it created came out as 12"=1'-0". I changed the image scale to 1/8"=1'-0", and then scaled the image by 96, and it came out perfect. Just a couple of extra steps to get it to the scale of the source view, but seems to work! (someone want to write an API module for that?)

Thanks for the tip, Alex! I didn't know about that feature.

[ron.sanpedro]

I just tried it, making an image from a plan. The plan is at 1/8"=1'-0", and the image it created came out as 12"=1'-0". I changed the image scale to 1/8"=1'-0", and then scaled the image by 96, and it came out perfect. Just a couple of extra steps to get it to the scale of the source view, but seems to work! (someone want to write an API module for that?)

Thanks for the tip, Alex! I didn't know about that feature.

Yep, it works, but do that 10 or 12 times per project, and it becomes work. Work the idiot savant computer is SUPPOSED to do. Now do it a few hundred times in CA (a potentially VERY cool use of the new Save as Image tool) and you have a lot of work, and a lot of potential for error as well. Not to mention that spasm of pain some will go thru when they see a table of scaling factors again. And how many people will try to type 1/96XP at some point? Oh, the humanity! ;)
No, it seems to me that Autodesk should just suck it up and fix it, rather than us finding extra work kludges to make up for the tool not being done.

That said, I continue to hold out hope that this is a simple fix that can be addressed in SP1. The tool has some real potential, and I really hope to see that realized rather than wasted.

Gordon

[dfriesen]

Yep, it works, but do that 10 or 12 times per project, and it becomes work. Work the idiot savant computer is SUPPOSED to do. Now do it a few hundred times in CA (a potentially VERY cool use of the new Save as Image tool) and you have a lot of work [...]
That said, I continue to hold out hope that this is a simple fix that can be addressed in SP1. The tool has some real potential, and I really hope to see that realized rather than wasted.
Ah yes, that's very true - one small demo is not the same as real-world use. Have you submitted a support/feature request/bug report?

[narlee]

Yep, it works, but do that 10 or 12 times per project, and it becomes work. Work the idiot savant computer is SUPPOSED to do. Now do it a few hundred times in CA (a potentially VERY cool use of the new Save as Image tool) and you have a lot of work, and a lot of potential for error as well. Not to mention that spasm of pain some will go thru when they see a table of scaling factors again. And how many people will try to type 1/96XP at some point? Oh, the humanity! ;)
No, it seems to me that Autodesk should just suck it up and fix it, rather than us finding extra work kludges to make up for the tool not being done.

That said, I continue to hold out hope that this is a simple fix that can be addressed in SP1. The tool has some real potential, and I really hope to see that realized rather than wasted.

Gordon

Ok. I'm starting the pool, by betting 100 AUGI-Bucks, that they fix it in SP1...