Im coming back to using Sketchup after a couple of years away from it. I used to use the Pro version of this plugin all the time. I've looked on the Smustard site and it looks like its closed shop. Is this plugin still available anywhere or is there anything that does the same job. I've tried SimJoubert's component to scene but I want to be able to make scenes from groups and / or components. Any help or pointers much appreciated...

@tig said:

The newer Ruby version is unsympathetic to coding errors !
Using a plain-text editor, like Notepad++, edit the file:
C:/Users/Architekt/AppData/Roaming/SketchUp/SketchUp 2019/SketchUp/Plugins/Matt_Toggle_Units/Toggle_Units.rb
Find line #205
return if not settings.include?("true")
Add an initial #
#return if not settings.include?("true")
Save the file and restart SketchUp, to test it...

Other 'returns' in the code seem OK...

Amazing - thanks TIG!!! (and Matt666 for the original). Was really panicking as I couldn't find an alternative to this, really great to get it working on 2019!

Thanks

Thanks Baz,
As far as Sketchup are concerned it is a known bug - I just got this email from Yogesh in the Sketchup team:

*Hi Sam,

Thanks for your note.

We have two other post with the same issue
https://forums.sketchup.com/t/layout-scenes-and-scale-nightmare/34813
https://forums.sketchup.com/t/sketchup-2017-scenes-not-working-as-expected-in-layout/34210

And as mentioned by Marc in https://forums.sketchup.com/t/sketchup-2017-scenes-not-working-as-expected-in-layout/34210/11 we are working on a fix. Please check the release notes for the future maintenance releases of 2017 for official word that it's been fixed and also subscribe to the about forum posts for any further updates .

Please reply to this email if you need further assistance with this specific issue.

Regards,
Yogesh
The SketchUp Team at Trimble Inc.*

Marc's (from Sketchup) post said the following:

This is a bug related to the graphics refactor. It will affect scenes that don't save one or more of these settings: camera, shadow, axes. We've got a fix in progress!

I've been advised by DaveR and Sonder that scenes should be used for every viewport which I'm looking into and testing on some current projects - thanks again for your advice on the other thread DaveR and Sonder. Sonder - I bought your book too. Some great templates, resources and tips in there and some new working methods for me to test out - thank you.

Thanks Play404,
Been looking at the SU forum site too and it sounds like its a bug so, like you Im hoping for a solution soon.
Cheers

Link to the same topic on Sketchup Forum in case anything useful comes up on there.

https://forums.sketchup.com/t/layout-updating-su-model-to-2017-throws-out-views-in-layout/37567

Ive done some further testing and when the file has been updated (from a modified view) it throws out the scale, changes it to perspective, moves it to a different location within the view window and consequently throws all the dims off into strange positions. If I select the viewport, change it to what I want (ortho, scale 1:10, right hand view) and then go to update the view (in scene pallet drop down) it throws everything out again despite the original view in SU having no camera associated with it.

I've tried adding my file to a new document and playing around with it and am having the same problems. I've uploaded a sequence of images to show what I mean. My SU window is shown on the left in the yellow box and the LO window on the right.

Image 01
Original setup of SU with one scene called Scene 1 that has no camera associated with it. LO files with SU model set out in LO and views manually changed to show plan, front and right.

Image 02
Small change to SU file, elevation styles changed in LO and then context menu view update in LO to show red top.

Image 03
In SU yellow disc is added and shadows altered. In LO context menu update shows that shadows are not the same as SU because view is (modified) Scene 1 in scene pallet.

Image 04
All views selected and changed to Scene 1 (in Scenes pallet dropdown) and now they are all perspective, all looking at the origin and all at a random super zoomed scale - this never happened before.

I draw lots of production details and generally set one view to use for my front, plan and side views that doesn't have a camera associated with it in SU - I find this is a lot quicker and less confusing than having to set views for all the elevations in SU and allows for much quicker updates but this doesn't appear to work in LO 2017!

Can anyone shed any light on why this is happening now as its a major upheaval in the way I'll have to draw things up. Having to have a scene in SU for every view and elevation is a nightmare and makes organising a file really difficult. If I update a associate a camera with each elevation and then update a scene on a different PC where the screen is a different aspect ratio or the pallets are laid out differently (even if the pallet block is set wider or narrower) then the views all get thrown out if the view is updated from (modified) Scene X to just Scene X!

Any help very much appreciated....

Hi,

I've just installed 2017 Pro. I have opened a layout file to test it and have found that when I save the SU file and update it in LO most of my modified views change. Any view that's been modified (where it says '(modified)' before the name in the scene dialogue) and just seems to shift to a new position throwing all my dims and annotations out. I've tried updated to an oversaved copy of the original file and have also tried re-linking to a copy of the original file saved as SU 2017 but get the same result with both.

I've attached some views to show what I mean. The one called 'On Open' shows the layout file (created in 2016) opened in LO 2017; all the dims are ok and the views are correct. The file called 'After Save and Update' shows how most of the views have changed and all the dims have been thrown off.

Having to rework my drawings to account for this view shift will be a serious pain - I often have to go back and revisit and amend old drawings from a couple of years ago.

Is this a bug or is there any way around it?

Thanks

Sam

Hi Stuart Fuel - only just seen this, thanks for the heads up. I'll give this a try and see what happens. More components to make / amend next week so this info is timely!
Cheers

Anyone know if there is likely to be any movement / development on this. Being able to export more than one page of a PDF and being able to do this for individual pages in a sequence (1,5,15) rather than as a run of pages in a sequence (1-15) would be great. Also being able to export by file and page name would be incredibly useful - would save a lot of error prone file renaming (post export) and its a feature that lots of other drafting packages have. Id love to be able to name a file, label the pages and choose what pages to export and whether to export them as individual PDFs that have the file name as a prefix and the page name as a suffix eg,
File name = 123-ABCD-4567
Page name = 01_A_General Arrangement
could export as = 123-ABCD-4567 - 01_A_General Arrangement

At the moment I have to break up my PDFs in Acrobat and manually rename them. On projects that have documents with lots of pages and clients that are forever changing their mind, renaiming all the files is very time consuming and its very easy to make mistakes.

Hi Stuart Fuel,
No, Im afraid not. The new workflow is much more time consuming and its MUCH easier to make an error or overlook an incorrect name or worse still oversave an existing name. I wish it still worked in the old way!
sdmitch's plugin / workaround is excellent but when you are working with more than 5 files its repetitive and time consuming. This is NOT not a criticism of your plugin sdmitgh (its great), - just that the way that you currently rename / save existing components that have been made unique is much less user friendly than it used to be - SU team is there anything that can be done to make this easier or are any developers able to write a plugin that can 'resave as renamed' unique components.
Thanks