Next stage from finished .blend model

[Fengist]

Fengist, that small utility was based on procedures mbartelsm and I discovered back in July 2014. I've gotten said procedure to work myself for 4.3, but that and Xypho's utility no longer works reliably for 4.6+. I'm not sure exactly how much has changed between 4.6+ and 5.x for emissives, but at this is stage in KSP's development cycle, it's a bad idea to jump the gun and use Unity 5.1 just because it's the latest and coolest.

Until SQUAD releases a new set of PartTools that specifically gear towards Unity 5.x and coincide with the engine update for KSP 1.1, please refrain from using Unity Editor 5.x, and more importantly, please don't perpetuate incorrect information.

I'm using 5.1 because I let Unity upgrade itself not knowing about the emissive changes, not because I wanna be some uber cool modder and play with the latest toys. When I discovered the issue, rather than go through the pain of uninstalling, reinstalling 4.2 and then reloading all of my work, I simply edited the .anim. Regardless of why I'm using it, the method does work.

Nextly. Since I'm already using 5.1 and that's what I'm becoming familiar with, and since everything I've tried so far does work, I see no reason to un-fix what isn't un-broken.

Nextly, since Xypho's post references my post then I assume it's been at least upgraded to fix the .anim files in accordance with how I fixed them.

If Unity Editor 5.1 works and KSP is moving toward at least Unity 5.0, then I consider it beneficial, at least for me, to start using Unity Editor 5.1 so that when KSP 1.1 does come out, I'm not totally lost as to how it works and I'm not fumbling around trying to figure out how to upgrade my emissives from 4.2 to 5.1, I already know how.

Finally, I'm not perpetuating anything other than solutions to existing problems. Telling people 5.1 doesn't work seems to be incorrect information when you yourself obviously found a way for it to work and admit you have no idea if it works past 4.6 (it does). Nowhere did I perpetuate any incorrect information so please refrain from trying to make me look like some liar or fool.

[sumghai]

you yourself obviously found a way for it to work and admit you have no idea if it works past 4.6 (it does).

I've stated clearly that the technique does not work for 4.6.

[Fengist]

I've stated clearly that the technique does not work for 4.6.

And I've stated clearly it DOES work in 5.1.

[sumghai]

And I've stated clearly it DOES work in 5.1.

Perhaps it does.

However, I should probably point out that, given KSP 1.1 is supposedly porting over to Unity 5.x, it is entirely possible that SQUAD will completely switch over to using mecanim for emissives, rendering every emissive made under the legacy animation system non-functional, regardless of whether add-on authors are using 4.2, 4.3, 4.6 or 5.x with the various community hacks.

Other than the emissive animation issue, Unity 4.2.2 isn't any inferior to 5.x, at least for the parts that matter to KSP. On the other hand, when you get to more complex parts, Unity 5.x may introduce things that KSP 1.0.x can't handle yet, and it's a bit premature to be preemptively preparing for that when we're not sure whether KSP 1.1 will adopt all or some of 5.x's features.

In short - avoid workarounds whenever possible, especially if there's the risk of introducing unknown issues one is not necessarily aware of.

[Fengist]

Perhaps it does.

However, I should probably point out that, given KSP 1.1 is supposedly porting over to Unity 5.x, it is entirely possible that SQUAD will completely switch over to using mecanim for emissives, rendering every emissive made under the legacy animation system non-functional, regardless of whether add-on authors are using 4.2, 4.3, 4.6 or 5.x with the various community hacks.

Other than the emissive animation issue, Unity 4.2.2 isn't any inferior to 5.x, at least for the parts that matter to KSP. On the other hand, when you get to more complex parts, Unity 5.x may introduce things that KSP 1.0.x can't handle yet, and it's a bit premature to be preemptively preparing for that when we're not sure whether KSP 1.1 will adopt all or some of 5.x's features.

In short - avoid workarounds whenever possible, especially if there's the risk of introducing unknown issues one is not necessarily aware of.

Now that, I will agree with. If you have 4.2.2 already installed, I see no compelling reason to switch. If, however, you're like me and find you have 5.1 installed, I see no compelling reason, yet, to downgrade.

[Dispatcher]

I like to remain up to date with Unity. That said, my sig line has a link to a photo of some fuel tanks I had made quite some time ago (pre-Curse; they're not available anymore as I don't seem to have the time it takes to do things right in terms of updates and expansions). Good luck!