linuxgurugamer

After looking at the code and the release notes, I can state with certainty that the version on Github won't work. However, I did some playing, and have a compiled DLL here if you would like to try it: https://www.dropbox.com/s/bzf7k9zkclp7piu/stageRecoveryDll.zip?dl=0 @magico13 All the changes were in RecoveryItem.cs, I found the following note in the Build 1548 notes and used it to make the fixes: I had a problem getting a clone of the repo, so I don't think I can (yet) create a PR for you. I'll keep working on it, but I can always send you the file. Let me know Going to do a PR for you

Can you post a picture, please?

Ummm, what? See here for a version for 1.2:

That was compiled 3 weeks ago. there have been a number of changes, it's unlikely to work without at least a recompile

Updated for 1576: https://github.com/linuxgurugamer/EditorExtensionsRedux/releases/tag/3.2.19

Try removing all of them, but leave MM. Then add them back one at a time.

Do you have any MM patches? If so, which ones?

One more update: You can now show parts with specific resources. Click the "Resources" button to select which resources parts need in order to show. Both the Categories and the Resources filters work together. Version is now 1.2.6.3 https://www.dropbox.com/s/1d486k4gf8vawzy/PartWizardUnofficial.zip?dl=0

An update to my changes: I've added a way to only display specific class of parts. Click the "Categories" button to select which part categories to show Same file as above, the version in the .version file and in the compiled dll is now 1.2.6.2

I've added some code to PartWizard which will show bad struts & fuel lines. This gives it the functionality of the old StrutFinder mod. @ozraven, Let me know if you would like me to create a PR on github for you Compiled for 1.2: https://www.dropbox.com/s/1d486k4gf8vawzy/PartWizardUnofficial.zip?dl=0

This topic reminds me of an old D&D game. The DM had a monster called an Ohmygod, so named because when you saw it, you would say: OH MY GOD!

What makes you think there aren't more developers?

It's normal for developers to come and go. Kudos to them for stating until 1.2 was mostly finished. They still have a number of developers, in fact, they have more total developers now than at the beginning of the year. Please drop this, since the topic has been beaten to death in other forums and threads

Your welcome. It was an interesting experience, I learned about some of your modlets I wasn't aware of before

This mod needs to be recompiled and adjusted for every build. I haven't had a chance to do it yet for any of the current ones

@ozraven Are you going to update this for 1.2? Do you need any help with it? I took a quick look, and have a working DLL. Not too much testing, but there weren't too many changes needed.

Ummm, it wouldn't make sense for this mod; when a launch fails, things explode. And it's only in atmosphere. Sounds like you would like a modlet to do that; why not ask @Malah or @magico13 to write something?

You probably have two ModuleRCS entries in the cfg. There is one at the beginning of the rcs module parameters, comment it out

Try adding this: MODULE { name = ModuleRCS thrusterTransformName = rcsTransform thrusterPower = 10 fullThrust = false runningEffectName = running flameoutEffectName = flameout engageEffectName = engage PROPELLANT { name = IntakeAir ratio = 15 } atmosphereCurve { key = 0 1000 key = 0.3 1800 key = 1 2000 } } and let me know how it works.

Can you define "not working properly"? I'm pretty sure things won't work, the commented code refers to ModuleRCSFX, which doesn't exist anymore

The patch was updated a while ago to be "NEEDS" rather than "FOR". please download the latest and try again KSP Version, & a log file would be useful. This is NOT updated for 1.2, so if that's your problem, please wait. This mod depends on two other mods, and until they get updated, I won't be doing anything with this

Then you and I will have to agree to disagree on this question.

But it isn't a CKAN problem, so taking it to the CKAN thread is useless. The correct answer is: It's a beta, and it's not on CKAN, and it won't be on CKAN until the full 1.2 release in a week or so

@goldenpsp, if you actually READ the thread, you would know that it isn't in CKAN because of, among other things, a version mismatch. Please keep in mind that this is a BETA. 1.2 IS A BETA CKAN is not for betas.

Well, he DID say that it wouldn't work in 1.1.3