Rob2222

After leaving a Hullcam or also a "Camera Tools" cam the focus is on the root part, not on the center of mass. When one right clicks the root part it officially says "Reset Camera", which is an indicator, that it's focused on the root part. It would be nice, if leaving a hull cam gets back to the normal, unfocussed center of mass view. "Camera Focus Changer" goes back to the normal center of mass view when unfocussing. So maybe a point for a comparison.

Nice Mod! Anyone tested it in 1.2 prerelease, yet?

Is there a compiled prerelease version for 1.2-pre aviable anywhere, yet? Maybe? :-)

@TriggerAu Could we maybe change the colors of USI-Mulch (orange) and USI-Fertilizer (blue) to the inverse? Cause on the USI-Containers Fertilizer has a orange drawing, so that would be more intuitive. BR Rob

TWP-Ejection-Inclination is not the Precise-Node-Ejection-Angle... It's the inlination of the resulting orbit _after leaving the SOI_. Afaik precise node doesn't show that. But precise maneuver shows it. See here at "Incl." (not ej. inclination or ej. angle).

OK, just found out... I think... the "ejection inclination" is is inclination of the resulting solar orbit after leaving the SOI of kerbin. The mod "precise maneuver" (not precide node) can show this value when setting up a maneuver node. And regarding my question before that, the 4d offset is the 24h alarm margin that TWP is using when setting up a KAC alarm. One can change/disable this marging in the TWP setting. BR Rob

I just wanted to ask EXACTLY the same... :-)

@NathanKell Hello, I've a question regarding the utility.cfg file... @PART[SurveyScanner] { !mesh = DELETE !MODEL {} %MODEL { %model = VenStockRevamp/Squad/Parts/ScienceParts/surveyScanner } @MODULE[ModuleAnimationGroup] { @deployAnimationName = SurveyScanner } %rescaleFactor = 1 } Can it be that the two % before MODEL and model are wrong? It deletes the model but doesn't define a new one? This is no problem, until you install Indicator Lights mod, which wants to add a light to the antenna but instead it shrinks the antenna. When I remove the two % all is fine. The antenna has the correct form factor and the light is on the antenna. BR Rob

@Snark Hello, I've reported that indicator lights breaks VENs docking ports... I now have some more information. It only breaks vens docking ports, if you have VENS + Indicator Lights + KOAS installed. (Note: KOAS is only listed 1.1.2 compatible, but works in 1.1.3). In the MM CFG your comment "We have to re-specify the model for the stock part, because this is/ an older part that uses the mesh...." got me on the right track. KOAS reloads the model, like IL does.... then afterwards VENS seems to dumps the model and replaces it by its own model. However, when you have KOAS and IL installed, you get the ven-dp-model double spawned... which glitches the mechanics of vens docking ports. Removing 4 lines "MODEL { model = Squad/Parts/Utility/dockingPort/model }" from your CFG and the problem is solved. The stange thing is, KOAS has the same line (with a addition line "!mesh=DELETE"), and does not cause issues (KOAS+VEN). However IL+VEN has also no issues. Only KOAS+IL+VEN has problems. Is this maybe cause MM can create duplicate entries? ( " foo = <value> creates a new variable called 'foo'; if there was already a variable called 'foo', now there's two of them. ") So I dont really know 100%, why we get 2 docking ports spawned in each other with IL+KOAS+VEN. But I know that it works when VEN=Installed then "don't apply the model line in IL-MM-CFG". So I've duplicated your MM-CFG for the docking ports and added a :NEEDS[VenStockRevamp] and a :NEEDS[!VenStockRevamp]... In the version for VENS I have removed the model part and adjusted the mesh positions for VENS docking ports. If you wanna use/improve it, feel free. BR Rob

@TriggerAu When I plot a depature for the _current_ day and time, and then set a KAC alarm, the KAC alarm is 4 days in the past. Is there maybe a bug?

Hello @JPLRepo Thx for your mods. With the ScanSat mod (I think) the (stock) M700 Survey Scanner (0.5EC/s) and the (stock) M4435 Narrow-Band Scanner (0.4EC/s) are getting a "Start Resouce Scan" option. Could AMPYear maybe detect and implement this? BR Rob

In general docking issues with vens revamp for me occured by using one of 2 other mods. KOAS docking camera, which fixed the incompatiibility already. And indicator lights. Both mods make a ghost bumper appear, which prevented docking. Do if you wanna use vens revamp and having issues with docking, you also can try to update / remove these 2 mods, if you are using them.

Just scroll and read 2 posts back...

I just would like to know, why is a fix made toggleable? Has it a downside?

Thx for the update. Is there an option to switch from blizzy's toolbar back to the stock toolbar?

Hello. Just wanted to report, that TimeControl offsets the KOAS (mod) docking port cam badly to a unusable state. When setting camfix to false in config.txt, the KOAS docking port cam is where it should be again. For what camfix is needed? BR Rob

Hello. Just wanted to report, that the mod TimeControl offsets the KOAS cam badly to a unusable state. I don't know why. Timecontrol has a config.txt, which includes a "camfix = true". When setting this to false, the KOAS cam is where it should be again. BR Rob

Yes, drill cooling is now working. Thank you very much.

I had problems in the campaign, but all testing I've made in sandbox. I just wonder when I switch the radiators on and off on the launchpad, the drill core temperature does not sink even a single kelvin. Without interstellar... with enabled heat control systems ... the drill sets at 100% thermal efficiency and 500K. With interstellar it is going to 740K, 12% and I have no idea how to cool it. Maybe I am doing something wrong, I don't know.

It is working without interstellar. With Interstellar it was only working, when removing the "@PART[foldingRadMed]:FOR[WarpPlugin]" section from the kspstockthermal.cfg file, making it basically a stock radiator. I was using the stock medium folding heat control system. However it seems to be normal that it works, when removing the interstallar changes from the part making the part stock again. Can you reproduce the problem or does it cool the drills for you?

Unfortunately, there seems still no way to cool the stock drills to 500K. They still max out at 740K an 12% efficiency. Tried with the stock thermal control system medium on the launchpad. Some days ago I removed the modulemanager cfg part/changes of Interstellar to the thermal control system.Then it does cool to 500K.

Unfortunately, that doesn't help. No matter what combination of "core cooling" and "global cooling" I set up in the VAB, the stock standard size drills will not getting cooled. They max out around 740K. For this test I only use stock 1.1.2 and Interstellar+dependencies. Just used a big Kerbodyne 14400 tank, 4 standard size stock drills, a stack of huge batteries, ore tank and probe core. Plus different radiators. Then drilling at the launch pad. No luck with cooling.

When installing KSP Interstellar Extended the stock folding radiators are not able to cool down the stock drills to 500K anymore. EDIT: To be more precise, no radiator at all is able to cool the drills at least a little bit... Is this a bug or wanted behaviour?

Does anybody know here, if these (fixed) radial attachment VAB crashes equal the VAB crashes on deleting things? For me and at least 2 other people the VAB crashes when removing a attached part and deleting it (crash on put it left / hit DEL) are far more common. However, modded installs.

Hmm, for me are "pushing a new version out for that fix only" and "offer it as self download after QA test of the fix for those who have problems" two different things... However, I hope for the steam dev version then. BR Rob