John, Phenomenal! Thanks for providing a solution to my problem. May I ask for some additional detail as to why, from SU's viewpoint, the Home scene must have a Home layer as well as a Layer 0 to have all this work properly? Thanks,

Jim

Hi, In continuing to learn SU, I am finally attempting to use Layers and Scenes. My issue is that even though I create a scene in which only one layer is visible and current, when I transition between scene tabs other layers become visible. Strangely, the results vary when I navigate through the scene tabs from Left to Right vs Right to Left.

Before posting here I did several searches to find out if this is a user issue or some bug. Most of the posts alluding to this problem were dismissed by experienced users. So I believe this is my problem. I created a small test model that exhibits the behavior and attached it below in the hope someone can explain what I am doing incorrectly.

Scene Test.skp

Note that the scene, layer, and component are identically named for purposes of documentation. In constructing the model I created a component on Layer 0 that consisted of 3 sub-components. Then I made two of the sub-components unique and re-assigned them to dedicated layers, DTL-2 and DTL-3. Then I created three scenes: Home, DTL-2, and DTL-3. The latter two share a similar style, while Home's style differs. Home contains Layer 0. DTL-2 reflects the DTL-2 Component and DTL-3 reflects the DTL-3 component. The preliminaries end there.

Then I did the following:

1. Went to Scene DTL-3, set DTL-3 as the current layer and visible, and made all other layers invisible, before updating the scene.
2. Went to Scene DTL-2, and noticed that DTL-2 is the current layer and it's the only one visible.
3. Selected the Home scene. Only Layer 0 is current and visible, as expected.
4. Returned to scene DTL-2, only to discover that Layer 0 is current and visible! On the plus side layer DTL-2 is visible. [This was not what I observed and set in step 2, above.]
   Why is Layer 0 current and visible in Scene DTL-2?
   BTW, the behavior in which the layer visible in the previous scene comes through to the next scene usually only occurs when going from left-to-right. When going in the opposite direction, the previous active layer remains invisible.

Also, when going left-to-right, DTL-2 disappears--as it should--when transitioning from DTL-2 to DTL-3. But, Layer 0 is still there.

Any help resolving this will be greatly appreciated.

I have experienced the same issue using 2016 on Windows 10. It's so prevalent I cannot depend on the date/time of last modification to determine if this is the most recent version.

gregw, Sorry for the bother. I just discovered that the Viewer is the avenue to getting the documentation. Unfortunately, it failed to load on my machine even with several attempts to fix the installation. Each time it generates a 1603 Error. I've had an e-mail request for support in to 3dConnexion for over a week now with no response. Calling them now. Regardless, thanks again for answering my question.

Thanks, gregw. Works like a charm. Is there some documentation describing this or other combinations?

Hello, I just recently acquired a 3Dconnexion SpaceMouse specifically for use with SketchUp. So far, the SpaceMouse has fulfilled all of my expectations, with one exception. With my Logitech mouse in SketchUp, I could position (select) a point of interest and when I scrolled the wheel to zoom, the zoom, either in or out, would focus on the selected object or point. With the SpaceMouse, that does not appear to be the case. After clicking on a point with my mouse and using the SpaceMouse to zoom, the zoom seems to have a mind of its own. The focus disappears off of my screen or flys off elsewhere. The results are definitely not the same as those resulting from scrolling the Logitech mouse's wheel. Has anyone else noticed this difference? If so, is this behavior the result of some setting, or combination thereof, in SketchUp, 3DXWare, or the SketchUp driver? BTW, I do not believe my use of the SpaceMouse is causing the zoom to have a rotational component. Thanks.

Dave, Thanks for mentioning about the differences between Scale and Move when working with items in drawing. I learned that lesson the hard way, early on. In this case, since these are metal slides, I was only interested in a pictorial representation that was true to overall size. Issues resulting from scaling like any increase in internal channel size were immaterial.

As for the explanation of my problem, your analysis was right on. In order for the correctly sized component to replace the existing ones, I first had to open an existing component for Edit and, then, apply the Reload. Voila, all instances changed to 22". Something so simple, but ...

Again, thanks for the help and insights.

I am developing a model for an item I want to build in my woodshop. In that effort I have made extensive use of components for basic items, sub-assemblies, and major assemblies. Along the way the designs have developed and changed. So I have "Reload"ed components and, barring the need to reposition, have not experienced what I am now facing. The details follow using woodworking terms.

Originally, I used 24" slides to support some drawers. Since the size of the drawers needed to change, I made a unique copy of the 24" slide component, edited it by scaling it on the red axis to 22", updated the name to eliminate the reference to the 24" slide and also removed the #1, and "Saved As" the newly edited component in my Hardware collection. When I Reloaded the 24" slides on the existing drawers, the size of the slide became 26+", yet the outliner lists the correct source file, the updated name of the 22" slide, and the correct sub-assemblies. What's even more curious, if I then load a separate version of the 22" slide from the component collection, it comes in with the same name and so on, but it's the correct size: 22".

Obviously, I am missing something fundamental. Can someone point me in the right direction, please? By the way, I did a search of the forums (as I have done in the past when I ran into difficulty) but did not discover an answer or a lead. My apologies, if this topic has already been covered.