DOF........seems a bit off?............Green screen maybe?

C

@unknownuser said:

That should avoid the diamond icon to appear. Fredo

Ha! and all this time I thought it was a Ruby

Best,
Charlie

Perhaps a shared benchmark file is in order?
(For .pdf export time/file size...I know...I know...but perhaps it is simply not hardware related).

& fwiw, the 2 projects I mention are ~ .25 acre and probably ~6+ acre respectively.
Unfortunately I cannot share the actual project files...maybe a vanilla/pseudo variant?

Thoughts?

Charlie

@unknownuser said:

What's your output quality set to under file/document setup - rendering quality?

I am certain I have tried every combination possible.
Currently I have my edit quality & output set to Medium.

I then typically export to low quality for intial Email/Drop Box correspondence.

Once the design is near complete I up the export .pdf to medium and then export to high for the final.
I typically have to break apart the final to smaller chunks if anyone hopes to open them on their mobile devices.
Otherwise the final HQ .pdf file in DB remains intact for the print shop.

My last two files:
15 sheets @ 11"x17" ~ 47MB
40 sheets @ 11"x17" ~ 69MB

These last 2 projects are exterior elevations/aerials with site.(for ARC Review)
Yes, they have trees and some other goodies that crank things up some....but the buildings are essentially shells for now.(I suspect similar to what TT is doing).

Charlie

TT, Well I figured you did not have any bloat in your models.

I too am not pleased...at least often enough...to wish it were faster and better at .pdf export.

One other thing occured to me is to make sure print paper color is "off".

Charlie

Sorry TT....I have but only one suggestion.
If you have any non visible geometry you can do without, get rid of it.
I do not mean hidden geometry, just any that can't be seen in any given viewport.

OK, maybe two....and I am not 100% certain about this one.
As I recall, any images used in SU can blow up the file size of LO .pdf export, and I think they also contribute to the slowness of .pdf export.
Also, Also, I know you cannot really get any significant .pdf file reduction in Adobe Acrobat...I get a message about masks that could not be reduced (or somesuch).

Charlie

John,
Are you using a style in SU that supports transparency(X-ray)?
Have you updated all of your scenes in SU....and updated all references in LO?

EDIT: Hybrid will likely be your only option to display transparency, seeing how you dislike the raster mode.

Perhaps a bit more information if the above has already been checked.

Charlie

All,
FYI:
Seems Trimble issued a repair for this today (I assume this was all that was fixed).
I had an automatic notification on opening LO.....if you did not maybe try checking for update(About LO...check for updates)
EDIT: Thank you Trimblers for the quick fix.
Charlie

micione,
Same here.......oddly the 1"=400'type seem to work.
However none of the fractional scales work.......total whiteout of the viewport.

Charlie

@unknownuser said:

Ok, I know it must exist, however, I can not find the solution. Is there away, or plugin that will export scenes created by me, to image files. I have a model with 12 scenes showing how to install the equipment, and I wanted to do an export of all the scenes to images files so I could place the images into a PPP.

I did it by going to each scene and exporting to a png, but surely there is away or plugin to do this automatically.

Thanks in advance

Ken

Ken,
Your profile shows you are a SU Pro user.

SU Pro has Layout for just such a scenario.

Open SU model in LO.....generate a page for each scene(add text etc if/as).....export to .jpg or .png.

Best,
Charlie

@pbacot said:

That statement might better be placed there just as a new post and thread, so the simple statement isn't lost. This thread discusses some other things as well.

Done...thanks

Charlie

To simply state the bug:
Editing any "on every page" layer item can/will trigger a SU re-render/model update of all viewports/on all pages.(if status of SU model has been updated)

This can effectively present as a freeze/crash to the unsuspecting user while all the viewports render on all pages in the LO doc.

Charlie

After further thought.......I would now classify/report this as a bug.

To simply state the bug:
Editing any "on every page" layer item can/will trigger a SU re-render/model update of all viewports/on all pages.(if status of SU model has been updated)

This can effectively present as a freeze/crash to the unsuspecting user while all the viewports render on all pages in the LO doc.

Perhaps a moderator could move this thread to the Bug section of the forum.

Best,
Charlie

@pbacot said:

So this is what OP is asking for! .

Not Me (OP).....I just "stepped in it"

@pbacot said:

But done this way is not nice because it isn't what a user would expect, It's not a direct command but an odd by-product. If you set render not to be "auto" then it won't happen. BTW clicking (Or reclicking) auto-on does the same thing, and seems a slightly more logical result. So OP should be (slightly) pleased.

Not pleased.......but half warning.....half happy.......so now you see how it easily could be classified as a BUG..........mmmmm.........but also "used" as a feature.

Cuts 2x I suppose.

Best,
Charlie

@pbacot said:

Doesn't do that, fortunately.

I have at least one file where it does....and a heavy one at that....which is actuallyhowI discovered it does.

In a lighter file,the viewports update quick enough where you may not notice.

Anyway, thought I would share for the good/bad of it.

Edit:
@DaveR
Thanks for the detailed LO/SU good practice/modeling reminders.

I (constantly)remind myself of earlier SU users emphasizing the need to determine the level of detail.........per "scene" (think it was "page" back then).
IOW......a keyhole in a door knob from 20yds.....probably not necessary.
& speaks to your good practice advise.

Also & FWIW...I am still on GSUV8/LOV3...did not "update" to Trimble SUV8/LOV3...as I understood this to be mainly a badge change......that said...perhaps this post was in vain?

Charlie

@pbacot said:

I'll add here, because my earlier post was removed: Just because we can imagine a different way, doesn't mean it's a bug. They just made it that way.

It may be considered a bug if editing text(or other) on the "same on every page" Layer triggers an update.re-render of all viewports on all pages.

I could actually use this as a "feature" as I am sure many of us could.....so maybe leave it as is...........pity the poor guy who simply changes the date and has to wait 30 minutes though........or worse.........thinks LO has frozen and forces shut down.

Charlie

@dave r said:

So you still have to wait for the next page to get rendered when switching pages in LO.

Unless.......you edit a "same on every page" layer element(text in my example).

This appears to trigger update/rendering on all pages.....without having to switch pages.

I suppose you could actually call this a bug.......as it seems native LO controls the re-rendering to user page selection.

Charlie

bMike,
Same settings I have......though my SU models only Re-Render on page selection.
Or even context click update reference only Re-Renders active/current page viewports.

IOW in a 12 page LO doc. ONLY the curent page will auto update.
So if I am on page 1 when I update reference (doesn' matter the method)It will only update (Re-Render) that page and all the viewports asscociated with the updated model.

If I then select say page 3 it will update page 3 viewports automatically (but only when I select that page)

And so on...and so on.

Or.......what?.......some gremlins have a party in my machine?

EDIT:
I should add that the LO normal update behavior I experience is fine, as I could easily see the time to wait for all pages & all viewports to update would get bothersome. (Actually I think it used to "try" to do this in earlier versions)

My point in posting was to share what appears to be a way to trick LO into updating all pages/viewports........while you go get a cup of Joe.........or a tasty beverage.

Best & Thanks,
Charlie

Gai,
Yes......File....Document setup..........references......update.

Typically this is how I update the reference....however it will ONLY update the page that is visible....subsequent pages must be manually selected to auto update the viewports.

(Unless I am doing something wrong....a possibility)

Charlie

When updating a model reference LO only updates viewports on a page by page basis.
(requires selecting each page to initialize the update)

So, today I noticed when I updated the model reference (I only have one in this file)and allowed the first page to complete updating the viewports.
Then edited the date (same on every page layer)this triggered all the pages to update ALL VIEWPORTS (SU Model scenes).......cool.

I have on occasion wished for this type of update function....perhaps you have too.
While not a "feature", it seems to be a way to update all pages.

Warning:Will require patience wile all updates complete.

Best,
Charlie