Hi, This might be (I'm hoping it is) a bug in Vectrosity 4.2 and Unity 5.2.0... KSP's map view draws orbit lines using Vectrosity, and because of the scale of the thing (literally astronomical), we need to switch the lines from 3D drawing (so they're culled by objects like planets and such) to 2D drawing, to avoid floating-point inaccuracy issues. This happens when the camera zooms out past a certain distance. This has always worked fine, and worked fine in V4.2-U5.1.3. After moving to U5.2.0 however, zooming out like this makes the game go into a semi-crashed state where it maxes out all CPU cores and starts leaking memory like mad. I would have updated to V5 already, but it's not up in the asset store just yet. I'm sending you a PM with a question about that. But anyhow, is this something that sounds likely to happen with running V4.x (and doing the 3D/2D shifts like this) in unity 5.2.0? Thanks in advance! Cheers .