I have just created a Layout file in LO 2018 that has a problem. I cannot upload it as it is just over the size limit. Whilst SU crashes reasonably often for me, LO has always been very stable. However, if I try to turn the embedded files to Hybrid rendering, LO crashes out. I have tried saving and reloading but it happens reliably every time. I have not had it happen before. The SU file has PDFs embedded in it and I cannot lock them or the layer they are on. I don’t know if that is normal or if there is something about the PDFs that SU doesn’t like and is somehow causing the crashes in LO. Any ideas anyone? That includes any suggestions about how to share a file that is too big to upload (Trimble Connect? Haven’t used it before).

I am not sure your issue is quite the same. I don’t get bugsplats or not responding. What I get is immediate crashes which bypass the whole bugsplat reporting procedure. Sometimes it is just LO that crashes but sometimes it crashes the whole computer. It seems to be random (some files affected but not others) but the source of the crash is always the same - changing rendering from the default raster to hybrid or vector. I did try what you suggested about saving in 2017 format and opening in LO 2017 but the same thing happened. So it must be something about the way LO handles files leaving an inbuilt problem. My only totally failsafe option is to revert to SU and LO 2017 altogether. I really hope I don’t have to do that! I am surprised that I am (so far) the only one with this very specific issue as there must be a lot of people out there running 2018 on a Mac just like mine.

Over the holidays, I have been testing various things to try to find out what is causing the LO crashes. I have found that if I delete Warehouse components and use Cleanup, it seems to fix the issue. So, maybe there are certain components I am using that cause the crash even thought they don’t in earlier versions. But there might be other things that Cleanup is doing that solves it. I would probably have to do a series of step by step tests to be sure of identifying the cause. That would probably take too long and if I now have a workaround, that will probably do. There was a suggestion earlier in this thread that it could be to do with OpenGL settings or my graphics card. That now seems unlikely.

A friend of mine who also uses Mac had problems with LO crashing when his models contained certain components from the 3D Warehouse. This goes back a few years and versions. Maybe SU2015? In any case, we found that cleaning up and simplifying the components before inserting them into his models eliminated the crashing. Maybe you can do the same if you really want to use those components.

Yes, like many people (I suspect), I tend to assume Warehouse drawings are safe to use and tend to import them as they are. I guess I should get into the habit of editing them first as you suggest. I think I have read before that you tend to avoid downloading models and prefer to make them yourself. I guess you know they’re kosher that way. Happy New Year to you Dave! Long may you continue to dispense your wisdom in these parts.

I think if you are going to use components from the Warehouse, best practice would be to open them in a separate file and inspect them to make sure they are suitable for addition to your model. Be prepared to edit them to make them usable if they have issues. The friend I was referring to does beautiful kitchens and other interiors. The components creating problems for him were kitchen appliances from a manufacturer. The appliances were heavily over-modeled including internal elements that no one needs for kitchen designs. I’m talking about the compressor and motor in a refrigerator and the regulator and gas valves in a range. Lots of the geometry was of the tiny variety that causes validity errors in SU. After he started gutting them and keeping only the shells, the crashing problems were exacerbated. I tend to not bother with components from the Warehouse because I can generally draw them myself so they are suitable for my needs with less effort than I would have to spend repairing someone else’s work. That’s just me, though.

As examples of extreme detail I found in the 3D Warehouse, that are fine if the one object is all that is in your model, but will kill you if you use them as “entourage”: A grand piano that had over 56000 faces, including models for all the inner workings. A sink that had over 30000 edges in the drain basket and strainer alone! An automobile that had 15000 edges in the license plate.

I can see why large amounts of data would slow things down. Does it also lead to crashes (maybe by virtue of overload)? The puzzle here is that it did not affect LO 2017 so there must be changes in LO 2018 that contribute to the problem. It would be great if some clever chap could produce an extension that checks over imported components and produces a report followed by options for dealing with any issues encountered. Maybe the Cleanup plugin I use does that job satisfactorily?

[image] simoncbevans: The puzzle here is that it did not affect LO 2017 so there must be changes in LO 2018 that contribute to the problem. As I said, this isn’t new to LO2018. You might not have run into it but I’ve seen it going back several versions. [image] simoncbevans: It would be great if some clever chap could produce an extension that checks over imported components and produces a report followed by options for dealing with any issues encountered. That would be nice but it would require some user input to determine what needs to be kept and what can go. I doubt a plugin could make those sorts of decisions autonomously. CleanUp might help to some extent.

[image] DaveR: That would be nice but it would require some user input to determine what needs to be kept and what can go. I doubt a plugin could make those sorts of decisions autonomously. CleanUp might help to some extent. I agree, it would require some user input. That’s what I meant by "“followed by options”. Cleanup offers some limited options, though you have to choose them in advance, not after an analysis. It would be interesting to know what steps you take Dave to pare down imported components.

[image] simoncbevans: It would be interesting to know what steps you take Dave to pare down imported components. I did fixed a couple of the kitchen appliance components for my friend when he was having the problem. It was a PIA and made me think bad thoughts about the author but it helped make them usable. Delete unneeded geometry including all of the internal stuff as well as things like branding badges and other small details that won’t be visible or at least readable in the overall views. Only leave what will be visible. A refrigerator component doesn’t need a back or bottom or even feet. At most, front sides and top will be enough. Simplify remaining details to reduced entity counts. Use components as appropriate. Example: the grates on a gas hob are likely identical left and right. Make one a component and copy it for the other. The same with knobs which will most likely be loose geometry or groups. Eliminate unneeded textures/materials. If an image is used for a digital clock display on the back of the range, get rid of it. It’s not needed in an overall kitchen model. Also look at those texture images you do want to keep. Perhaps they can be reduced in size. Basically you need to be kind of ruthless in your cleaning of components before adding them to your model. If you add five or six appliance or fixture components that each contain tens of thousands of entities are each several Mb, you can quickly bloat the file size and make your model unmanageable and problematic. I’ve had people tell me it takes too much time to do these fixes so they prefer to use the components as they come. My thinking is, if you’re using components from the Warehouse, spend a little time on the front end making sure they are good enough for your model or spend more time fixing it later after you’ve lost control of your model. This applies to making your own components, too. Don’t get sloppy thinking it’s saving you time. More often than not, the seconds you save up front will cost you minutes later.

Layout 2018 crashing

LayOut

MikeWayzovski January 4, 2018, 6:14am 51

When it crashes, do you send the bugsplat?
I know that ‘being busy’ often priorities other things, but by sending them, and provided that it is a known issue, you will get a report back with a suggestion for the problem you’re dealing with. Lately, many High Sierra issues can be resolved by typing a command in the terminal.

Topic		Replies	Views
Layout Constantly Crashing LayOut layout	50	7526	February 10, 2022
Layout crashing today LayOut mac	19	2090	March 9, 2018
LO file keeps crashing and won't open anymore LayOut	19	909	July 22, 2021
LayOut 2020.1 's bugs LayOut	50	5386	April 26, 2021
SU-Layout is on strike -how to get it back to work! LayOut	18	502	June 10, 2025

Layout 2018 crashing

Related topics