Is anybody had this problem?
No. Share the LO file so we can see what you’ve set up.
Test Ground.layout (195.3 KB)
Test Ground.skp (117.7 KB)
Test Ground.pdf (241.1 KB)
OMG! Is this a new feature I missed!! Thank you so much Dave.
No. It’s not a new feature but there’s been a change. In previous versions of LayOut if the style had Sky or Ground enabled that Background checkbox didn’t do anything. It only worked for removing the Background color.
Haaa! That explains it. Thanks again Dude!
Now I have a very strange bug with that new feature. When I switch the background ON, the ground appears higher in LO than in SU. It cuts the bottom of the model, and hide the shadow on the ground!
Share the LO file.
I see what’s going on but can’t identify why the ground appears higher in LayOut. Maybe @adam can comment. He may be at 3DBC right now so might not get to it immediately, though.
In the meantime do the easier thing. Turn off Ground in the style and update it. Draw a large rectangle on the ground plane and, if desired, hide its edges and then make it a group and give it a tag so you can choose to show it or not in any given scene or viewport. It’ll look like this in the viewport, then.
BTW, make sure you are keeping your model clean.
Reduced bloat by almost 48%.
Thanks Dave, but can you please remove the link of the file as soon as possible. I cannot share this model. I did a mistake of thinking by sharing only the LO file with the embedded SU model in it would protect the file to be share, but I was wrong. It’s VERY important that no one have access to this file. Thank you for your comprehension.
Done.
That’s what I usually do. I call it GroundZero. It just takes an additional tag for a feature that is supposed to work natively.
I always keep my model clean but you’re looking at a workfile in progress. I don’t purge my model while I’m working in it. This could creates a lot trouble because the lack of control SketchUp has with the Purge tool. Purging is a quick process, but fixing a LO or SU file that has been purged by mistake can eat up my profit marge very quickly!
Thank you. I appreciate.
I found the problem. Not the cause but just the problem. I skimed down every single element in the model until the problem doesn’t occur anymore. I went down to one component on it’s own tag. While the problem was still happening, I deleted the component, and the problem was gone. Even if I undo the delete command, the problem didn’t come back like it was with all previous deletes. I presume this particularly component was corrupted in some kind of way. Weeeeird!
Thanks for you help.
I too have no idea, but I would check if the component is geolocated, or if the component’s origin is somewhere far away, or if it contains hidden geometry that is somewhere far away. The size of the component’s bounding box might give an idea.