Efour

Am I posted that .... some sort of..... a 'crude' stock skylon before? I welcome you selected my skylon to compare your mod and stock skylon. But although it is very similar with my kerbalx-posted stock skylon, the stock skylon in your screenshot is not my own made skylon. To tag my name at stock skylon in your screenshot, please use "my" skylon. Anyway, your mod is good and I gladly downloaded it. thank you.

I think I found a bug related with canard. Left : 1.7.3, powerful canard, 118 m/s. Right : 1.8.1, weak canard, 165 m/s this two planes are almost same plane. raw picture and .crafts are here. 1.8.1 picture, ..craft file, stock video(youtube), FAR video (youtube) 1.7.3 picture, .craft file, stock video (youtube) The problem is this : canard is nerfed too hard. is it intended? or bug/mishap?

Link to youtube video regarding this behavior is it a bug? or intended behavior? I had no problem like this until 1.7.3. just after takeoff, v-tail makes abnormal lifts so I can't control my plane's pitch midair. .craft file is here

Kerbalnauts makes a craft as only vehicle. Not a main actor, but disposable vehicle. Other simulation games handle craft as a main actor or player. But kerbals make a kerbal as main actor and crafts are just tools. This is important and really making missions living. If there is no kerbal, expedition missions for KSS are just docking and reentry missions. But there is a kerbal and kerbal makes expedition missions meaningful like changing kerbals.

As you know, kerbalistic crafts are elastic and fantastic. Yes. It is the one of identities of kerbals. But, is it more important than making massive things without physical lag? Without allowing elasticity, the craft will not need to be a "tree". It makes everything improving. Multiple linkage can be allowed. Torques and linear forces are able to be calculated simpler. I cannot judge it is wrong or not. But at least in my opinion, elasticity needs massive cost. How about your opinion? Elasticity or Massive?

I considered it before releasing this mod, but I decided not including that feature. Because it is too complicated and similar feature is exist in other mod :

I'm sorry to say this, I missed 1.4.x version. I didn't test so I'm not sure, but maybe 1.0.3.1 will work. Not overriding, but both of them should be same. because TL uses that factor to calculate sci reduces for promotion. I saw there are an API to get current star of kerbal, in APIdoc. So my plan is reading current star and providing next-level-training. But as I said, I'm very busy now and I don't have time to do this until my real-life plan is very busy. updating my mod in CKAN and providing AVC support is delayed by same reason. I think it is considerable merging these two mods, like this : Training regarding stupidity consuming time and resources, graduating using sci point in one mod. But it is interesting to me too, I will add a pole when I make an major update of these mods.

Actually, It is not same kerbal stars with level of this mod. This mod displays only 'Training Level'. If it is 5, that kerbal is 5-star. but it doesn't guarantee 'Training Level' and stars. If a kerbal have many experiences to reach 3 star and Training Level is 1, that kerbal will be 3-star, not 4-star. because training is treated another experience in game. I have a plan to make Training level matches stars, modifying Training level calculation. But I'm not sure when I can do that. Yes, these mod intend using like "school".

1. That is.... hmmm... good question. In game system, It only adds training stuffs for kerbals to crewed module. I thought MPL can be training ground. That is a reason I named my first mod as "Training laboratory". honestly, FTF is named not seriously. If you ask me that 'Is it worthy to facility?', I can say 'I dunno.'. If your question is 'Adding MPL is enough to use TLFTF?', It's correct. 2. no. this mod not touches any option.

I use necromancy sometime, so I can say it will not be disappeared. but I don't have any plan about CKAN now.

Thank you for suggestion @Gordon Dry, but.. honestly, I couldn't fully understand what that codes are doing. Because I'm not good at modulemanager coding, I need some more information or description(especially, Where they will place). Thank you for report. If I was not busy now, I could debug or at least test with them now. I will do something including remake and merge someday, but I can't promise before ksp 1.5.2. I think that problem is from kerbal experiences block in save file, and it is the reason I'm planning remake. I will appreciate someone or some group adopt and improve it. the core idea is it : 1. kerbal training system, 2. using sci point to train.

Sorry for very late update. I'm busy awhile, so I almost forgot these mods. I can maintain this mod with recompile, but I don't have enough time to improve this. This mod uses MIT license. If you want, you can fix/update/modify/improve these mod. Sources are included in .zip file.

I totally agree your mention about black ribbon problem and I think it is from KSP 1.4, Unity 2017, or Catalyst's own bug. I'm not saying this problem should be fixed by you. But, shiny effect with this and SVE is at least reported once more by windmt that nVidia Geforce GTX 560 user. I also think shiny glitch is not this mod's problem and fix is needed from T2, but I just wanted to notice it to you.

I have same glitch like windmt, and I found that Flight Indicator mod causes same problem. I think it regards about lighting. I don't have log now but I can create and serve it if you want. Win 10 64bit, KSP 1.4.2, Radeon HD 6370M(shown as 6600M series). P.S. KSP 1.4.2 doesn't fixed that black ring glitch.

I tested previous version(1.3.4, for ksp 1.3.1) too, but same black ring appears. almost 20km black ring starts appearing, and until 55km ribbon becomes thicker, and at 55km ribbon suddenly disappears. While reentry, thick ribbon appears suddenly at 55km and becomes thinner and disappears 20km, mirroring takeoff sequence. I also think this is Unity 2017 or KSP 1.4.1 bug with radeon, but in my case this bug disappears without navhud.

In my case, that black ring starts almost single pixel line and inflates to black ribbon. but disappears suddenly. I've tested stock ksp too, but I can't see that black ring in stock. and It disappears when I turn off NavHUD with shortcut key or interface and appears when I turn on NavHUD. I will test that with previous version of NavHud and report here as soon as possible.

I cleaned my KSP and only installed NavHUD, and I can see that black ring too. (picture below) and, I attatched my output_log.txt from %USER_FOLDER%/AppData/LocalLow/Squad/Kerbal Space Program, deleted just before starting KSP and recreated after doing below picture. output_log.txt I'm using HP Pavilion dv6-6122tx Laptop. It contains i7-2630QM and Radeon HD 6370M(if my memory correct) and windows 10 64bit.

I found a bug. This black ring occurs only I'm using NavHUD. When I turn off NavHUD with shortcut Y, that black ring disappears too and turning on NavHUD that black ring occurs too. Not every situation, but only specific height. (about 20km ~ about 70km. not precise but steadily seen).

I found it. that's from NavHUD and I will go and report that bug right now. hmm.

This black ring occurs everytime when I launch rocket or plane. That black ring conseals everything including esc menu and It disappears when my spacecraft overs about 70km. I use ModuleManager, MechJeb, NavHud and dependencies, AtmoshphereAutopilot. I'm using laptop that contains Radeon HD 6370M and i7-2630QM. Is it occurs only me? or someone of you can see this bug? I can't find what is reason of this problem. I hope you can help me.

As you can see, Mk3 to 2.5m adaptor is colored as grey. slanted adaptor is remain white. (1.3.1, win64, steam) Does this problem occures my KSP only? Is it intended? Or is it just bug?

Ferram made things fly again

We believe Ferram will make thing Fly.

At first, I'm using AVC and I can see compress(rotate). I'm sure that I'm using latest version. KJR was out of my GameData when testing 120 degree rotation. The bug I reported is this: When using compress(rotate), my space station module welded 0 degree(what I wanted) just 1 frame. After 1 frame, it rotated once more to unwanted angle(previous, the angle I docked manually). It happened regardless KJR(I tested both of situation repeatly) If I can record that situation, I will upload here. But my laptop has slightly old graphic driver(Evil God loves HP), so I can't say I can do zhat.

I think I found a bug. when compress(rotate), A space station I made doesn't weld correct angle. It welded correct angle just 1 frame, but after first frame It rotated to previous angle. and I tested almost 120 degree rotate, but it destroyed after 1 frame. I attached save file : https://drive.google.com/open?id=0B-HJUJ6farqxSUN2dV9CWjNxalk I used Kerbal Planetary Base Systems mod. I think you know, this. : http://forum.kerbalspaceprogram.com/index.php?/topic/133606-12-kerbal-planetary-base-systems-v132-24th-october-16/ and others are not adding parts at all. My suggestion to fix this bug is this : make problem simpler and make usage simpler too. 1. remove angle snap and roll/torque param from constroport. 2. Add adjust absolute/relative angle without compress. 3. then remove compress(rotate) If you accept my suggestion, users can dock any angle and fix angle after docking. then users will not annoy from snap rotates modules violently, and users will not have to concern angle of docking port. I hope you accept my opinion.