JetEngine and turboFanEngine in Parts folder?

[Deadweasel]

Anybody notice those two engines showing up in the old Parts folder? I wonder why they're exempted from the GameData system like the rest of the default components?

[Tw1]

Hey, same here!

And the game acts as if I have no parts when I try to add more things to that file, which is a little inconvenient.

[astropapi1]

Heh, I noticed that too.

[Aphox]

I'm guessing it has something to do with the reworked assets that Bac9 did for those two engines.

[Tiron]

Last I heard this was a steam thing. If anyone's got this on a squad store version they should probably speak up about it. As for me, my fresh, clean steam install actually ALSO has them in gamedata. So I'm guessing it's just a steam frak up. I'm gonna try deleting the ones in the old parts folder and see if it still works, I'm guessing it will.

Edit: Seems to work fine if you just delete them. Seems like Steam just being dumb again.

Edited July 25, 2013 by Tiron

[Giggleplex777]

It's in my store install.

[Deadweasel]

It's in my store install.

Same here. I didn't buy it from Steam (joined in waaaay before that collaboration took place), and the Parts folder has them. Besides, Steam has nothing to do with individual file placement in a game.

[Big_Ron]

I have the same thing in my parts folder and i'm none steam

[Tw1]

Maybe I'll also delete them, then try adding the other parts that I want there, like the weight pack I uses

[Deadweasel]

Interestingly, the one thing that would determine the requirement of their placement, the config file, is not included with the versions in Parts, but are there in the ones in GameData.

I think this might have just been a simple oversight during the process of updating them.

[Deadweasel]

Maybe I'll also delete them, then try adding the other parts that I want there, like the weight pack I uses

Best thing to do for simplicity's sake is to edit the .cfg files and enclose everything in "Part { }". This will allow you to create a folder in GameData and keep the mod in there instead. That way you won't have to worry about odd interference from something else in the legacy Parts folder.

[Comrade Jenkens]

Mine are in both the old and new parts folders.

[Giggleplex777]

Could this be the cause to SAS problems?

[Tw1]

Best thing to do for simplicity's sake is to edit the .cfg files and enclose everything in "Part { }". This will allow you to create a folder in GameData and keep the mod in there instead. That way you won't have to worry about odd interference from something else in the legacy Parts folder.

I might go do that at some point, it'd help with the mod sorter mod I use as well.

[Deadweasel]

Could this be the cause to SAS problems?

I kind of doubt it, given that the ones in Parts don't have configs at all. They're just the models and textures.

Besides, I'm pretty sure, since SQUAD are already looking into that issue, they'd already have found it and called it out as the fix by now.

I get the feeling that either the release version came from the wrong build, given these odd redundant parts, or that testing was done on an earlier build, and the bugs were missed on the later one actually intended for release.

[C7Studios]

We're removing those, they're just clutter left over from changes to the jet engine parts.

[Tw1]

Which are beautiful, BTW. And congrats to whoever did the new engine glows, really nice reminder we're spitting fire, not just glowy white stuff.

[Deadweasel]

We're removing those, they're just clutter left over from changes to the jet engine parts.

Aha! Thought as much. Thanks for the confirmation C7, and let me echo Tw1's sentiments as well. They're gorgeous indeed!

[Giggleplex777]

I kind of doubt it, given that the ones in Parts don't have configs at all. They're just the models and textures.

Besides, I'm pretty sure, since SQUAD are already looking into that issue, they'd already have found it and called it out as the fix by now.

I get the feeling that either the release version came from the wrong build, given these odd redundant parts, or that testing was done on an earlier build, and the bugs were missed on the later one actually intended for release.

Okay, after some testing, still SAS ,problems.