WazWaz

Ported to KSP 1.2.

I reviewed the Shadow code but didn't see anything problematic except the DestroyImmediately with no immediate return, but that wouldn't have caused the crash.

I have seen this happen if you have configs for planets that do not exist (eg. I got it when I accidentally has PoodsOPVO installed but not OPM itself).

Users would need to be able to trust that the donation links are for the person(s) who made the mod, not just someone packaging it up. How can this be...

I guess I just can't think of any other reason mod authors wouldn't like CKAN - it seems like the only way to force people to install prerequisites and to...

There is a related problem that is perhaps also part of the solution: as said here, many people do not even realize that some mods available through CKAN are not...

@ferram4 - I guess I'm still trying to understand why mod authors wouldn't _want_ to maintain the metadata themselves - it only changes when they do something in their release...

@plague006 - that reason would equally apply to releasing the mod at all. FOSS people release stuff to get feedback. CKAN = more feedback just as a forum post does.

@ferram4 - it's sad, but I can see how this is the case (it is with just about every other thing that becomes popularized). I guess then CKAN is to...

Weirdly, it works fine if I comment out the fragment shader. Pass { Name "Transparent" HLSLPROGRAM #pragma multi_compile_instancing #pragma vertex Vert //#pragma fragment FragmentAlphaTest ENDHLSL } No idea why.