Prepare 1.5.5.0 Release

[jwvanderbeck]

TestFlight Release 1.5.5.0

• [x] Determine proper version number
• [x] Verify good Travis build
• [x] Change log in Markdown
• [ ] Change log in BBCode
• [ ] Github Release Tag
• [ ] Forum OP Change Log updated
• [ ] Forum OP Title updated
• [ ] New reply in Forum thread with Change Log and any important notes

[jwvanderbeck]

1.5.5.0

KSP Version

KSP 1.0.5

Highlights

• New optional module for working with RealFuels. This module will only load if RealFuels is present, and if found will allow TestFlight to inject burn times into the RF EngineConfig GUI in the editor. This means you will be able to mouse over engine configs, even unlocked ones, and see the rated burn time for that config.
• Multiple failures! TestFlight now allows multiple failures to stack up on a single part. No more hoping for a "safe" failure that will block more dangerous ones. The only limitation is a part can't have the same failure happen more than once.
• Multiple core. Configs can now place multiple TestFlightCore modules on a single part. Additional TestFlight modules can also be added that work with particular cores. Each will bind to the core with the same alias. In short this allows for essentially virtual sub-parts on a given part. So that if you have composite parts, like say a probe core that has modules for the probe, a built in antenna, and a science experiment, you can now have those show up as actual distinct parts in TestFlight.
• TestFlight no longer handles repair functionality. Parts can fail, and the TestFlight API has a call to instantly repair them, but does not itself provide any interface to the player for doing so. The repair functionality in TestFlight was always rather bare bones, and did not really do the topic service. Repair functionality is really a whole mode in itself and now it can be! I may write a bare bones repair system to work with TestFlight in the future but it is my hope that someone will jump on this to make a really nice in depth repair system.

Changes

• NEW: For parts with stack icons, TestFlight will now change the background of those icons when failures occur. Orange = Minor failure, Red = Major failure. More options for failure identification will be coming in the future
• CHANGE-API: TestFlightUtil.GetFullPartName has been removed and is no longer available. Every module should know its part name anyway
• NEW: Tweakable menu will now display a R&D button for each activecore, distinguished by the Alias, and allow opening the R&D menu forthat sub part directly.Updated all modules to use new method for getting the core that usesthe Alias.Fixed calls to GetFullPartName() to simply use the Alias instead.Updated method of modules determining enabled status by simplyretrieving their bound core and return that status.Removed old method of determining part for editor windowUpdated R&D Scenario to work with new multi cores
• NEW: Major refactor to allow for multiples cores on a single part, creating essentially virtual sub parts within one part. This involves major API changes which need to be documented.
• NEW-API: ITestFlightCore.Alias property returns the alias of the core configuration
• NEW-API: Added overloaded TestFlightUtil.GetCost() method toretrieve an active core based on alias.
• CHANGE: Engines now properly start their cycle at ignition rather than after clearing the tower. NOTE: You will still not start accumulating data until the craft actually launches.
• FIX: Don't allow multiple instances of the same failure.
• NEW: Parts can now have multiple failures. This means that after the initial failure on a part, the part can continue to receive other failures. There is no hard limit on the number of failures that can accumulate on a part.
• CHANGE: TestFlight no longer handles repairs, and all repairfunctionality has been removed.Major rework/refactor to handle multiple part failures and removerepair system project updates, build test
• NEW: Report rated burn time in pretty format, not just seconds.
• NEW: For EngineCycle modules, add rated burn time to the RealFuels config descriptions, if RealFuels is installed
• NEW-CONFIG: Added new property engineConfig to the ITestFlightReliability_EngineCycle module for use in RealFuels injection
• NEW-API: TestFlight main assembly now identifies as KSPAssembly TestFlight
• FIX: Fixed bug causing Editor Info window to display wrong amount of flight data units.

[jwvanderbeck]

Beta 1 out

[stratochief66]

Since this is open, I figured I'd record it here.

I'm not seeing the RealFuels report anywhere of the burn time. For example, I would expect to see it when I bring up the RealFuels dialog in the VAB that lets me switch to & unlock other variants of an existing engine.

[rsparkyc]

Also, the times seem to me malformed on the flight results page (F3)

[jwvanderbeck]

Well that is odd. I'm not doing any formatting at all, I just pass the MET straight through.

[jwvanderbeck]

Times in flight log should be fixed in beta 2 but I haven't been able to run it to very yet, as I made the changes while at work. If someone could verify that'd be great

Still not sure what the heck is going on with the RF info. Works for me, doesn't work @stratochief66 . Can anyone else chime in on either works or not works side?

[rsparkyc]

Here's a screenshot of it not working for me (at least this is where I'm thinking it would be)

[jwvanderbeck]

Yep that is where it should be :(

So why the heck is it working for me!

[rsparkyc]

Sound's like you're between steps 2 and 3: http://plasmasturm.org/log/6debug/

[jwvanderbeck]

Haha that is so true sometimes.

[rsparkyc]

FYI, flight log looks good now.

[jwvanderbeck]

FYI, flight log looks good now.

Excellent.

[jwvanderbeck]

If someone can get me a player log from a run where the RF integration didn't work, that would be great.

[rsparkyc]

Why can I not find the player log file? I'm on a mac.

[rsparkyc]

Found it! Player.log.zip