Kobymaru

You might want to look at my Post edit

Hey guys, does anybody happen to know how to access the new epic highlighting stuff? The Part.setHighlight() method only gives the plain old boring highlighter. Edit: I figured it out: Part p = ...; // old highlighter. Not necessary, but looks nice in combination p.SetHighlightDefault(); p.SetHighlightType(Part.HighlightType.AlwaysOn); p.SetHighlight(true, false); p.SetHighlightColor(Color.red); // New highlighter HighlightingSystem.Highlighter hl; // From Assembly-CSharp-firstpass.dll hl = p.FindModelTransform("model").gameObject.AddComponent<HighlightingSystem.Highlighter>(); hl.ConstantOn(XKCDColors.Rust); hl.SeeThroughOn();

Hey guys, is there a procedure to include Mods with MIA maintainers into CKAN? There's a nice little Mod called ActionGroupManager which allows you to update Action Groups during flight. The Mod author hasn't been heard from since February 2014, but with a trivial patch and a recompile, the mod is fully 0.90-Compatible. Would be a shame if people would miss it from the CKAN repo.

Nah, red is nice, I think. Although, is there a way to use the new highlighting mode (as used for stages since .90)? Also, I think the Community rules state that you have to link to or include a license and source code in any post with a Mod download link. At least I got reprimanded by a Mod for not doing that.

I'll look into it. This bug came along with FAR 0.14.5 and it completely broke Trajectories with FAR installed. Just wait for the next FAR release and I will upload a Trajectories version with FAR enabled. Also, ÃÂ (spelled rho) is the atmosphere density and very relevant to drag calculations. But this kind of math is best left to Ferram4

Ok, thanks. Too bad I dont have them researched.

Highlighting a part should not work, because the KSP API changed. Can anyone confirm? Should I bother to post a recompile or can you guys live without it?

Well actually, this time it's really FAR atomicfury found out that the Rho value passed to FARBasicDragModel.RunDragCalculation() does not get passed around internally. Ferram said he'd fix that in the next release. I reenabled FAR support in the master branch and if people need it really badly and can't wait, I could make some builds of FAR and Trajectories with the hotfixes.

When you say "fix", do you mean that it doesn't lock up anymore, or that the prediction accurately works? Because I am having an issue that with FAR, the impact marker constantly drifts to the West as soon as the craft enters the atmosphere. Edit: Ok, at least that's not a new bug. Tested with KSP 0.25, Ferram 0.14.4 and Trajectories 1.0.0.0 and the behaviour is the same. Still kind of unpleasent if the marker keeps drifting. Edit 2: "Fixed" if you set the AoA in the descent profile to -180°. On one hand that's logical because if you point your nose retro, then the air is coming from behind you. On the other hand, then 0° should not be default. And +180° should give the same result as -180° (but it doesn't). Note to self: some thinking about reference frames is in order.

Hi, is there a way to temporarily disable an antenna that is used for the command connection? It's for earobraking. The basic Idea is: - Command Antenna to disable 30 seconds after command arrives - Command Antenna to enable 5 minutes after command arrives I tried to do that, but after I disable the antenna on the craft, the "deactivate" button does not turn into an "activate" button until the command arrives and the antenna is actually already down.

Wow, thanks for your work. I will release a new version with FAR enabled when ferram releases a new FAR version to the public.

Looks awesome. What about the guys Mod? Does it exist already?

Rumor has it that it does NOT work with RSS. You are very welcome to try and report your findings, though!

Okay, new threads are opened. Release thread: http://forum.kerbalspaceprogram.com/threads/104694 Development thread: http://forum.kerbalspaceprogram.com/threads/104696 (please continue the debugging discussion there)

This is the development thread for the Trajectories Mod, which predicts atmospheric trajectories. This thread is mainly for Bug reports and discussions about the development (with icky code and stuff ) For the download of the latest release and information on the usage, please see this thread:

No FAR/NEAR at the moment. Work is underway, but no ETA. Sorry.

C# is a good language, most of it should be clear when looking at it. Your detangling knowledge could be very useful! Wow, that's amazing work! That helps a lot (I think). There is one call to FARBasicDragModel.RunDragCalculation() at VesselAerodynamicModel.cs, Line 349 that causes FAR errors. Is it possible that under some conditions, one of the parameters (maybe machNumber?) is not properly initalized and the calculation produces nonsense (but didn't with FAR .14.4 because it was not important)? p.s.: While it's pretty awesome if we could pin the bug on this one, I think there still needs to be some refactoring done, because the code (and the code paths) look kinda weird and there is an awful lot of zero-vectors passed around and "isFARInitialized() == false" happening.

Sorry guys, but I give up for the moment: I can't fix the FAR issue soon. I decided to release the Mod with FAR/NEAR support disabled. That's sort of good news for Stock users, I guess! Stay tuned for FAR support! Download here: https://github.com/fat-lobyte/KSPTrajectories/releases/download/v1.1.0.0/Trajectories-1.1.0.0.zip Source code here:https://github.com/fat-lobyte/KSPTrajectories License here: https://raw.githubusercontent.com/fat-lobyte/KSPTrajectories/master/License.txt A new release thread and development thread will follow Soonâ„¢. @hakan: Please things and stuff

I haven't tried but I suspect not. You are welcome to try.

If CKAN doesn't like pre-releases, what's its stance on broken code? Well, OK then. The git tag is v1.1.0.0-pre3 . Go ahead. From reading this thread, I hope you understand that it can cause Game Lock-ups with far? Do I have to write some sort of config file for CKAN?

Thanks. It's not just creating on the launchpad. The first time you fire it up in Debug mode (bypassing the main menu and going directly to the craft with the DebugFastStart plugin), everything is fine. If you go to KSC then back to the vessel via tracking station, then the bug happens. Maybe this helps: http://i.imgur.com/VmYOVdI.png

Thanks for the encouragement guys But first the debugging, then the politics. Thanks for that! That's not really necessary. I have forked your repo and it can stay that way, no problem at all. I will let you (and everyone else) know!

There is a .90 version. It's not in the OP first post post because - The original author is not interested in maintaining it anymore. I "took over", but I can't modify the first post - It works with stock, but there are problems with FAR. I want to fix that before releasing the new version See this post for a download link to the prerelease: http://forum.kerbalspaceprogram.com/threads/93685-0-24-0-25-Trajectories-v1-0-0-%282014-11-17%29-atmospheric-predictions-FAR-NEAR?p=1620366&viewfull=1#post1620366

Thanks for the testing guys! I prefer not to do that, because OP already wrote a nice abort/timeout logic - it just doesn't work for some reason. Better to fix what's already there. Strangely enough, yes. I saw missing FAR modules on the craft, and also I'm consistently seeing the behaviour that after loading the save it works the first time, and reloading the vessel so my guess is that there is something wrong with initialization. I don't know, and I'm not to keen on testing it because that would require taking out the .90 specific code again. There's also the new version of FAR.

Thanks. Looking ahead for 1.6 (?) then.