Alo

I've tested FMD 0.3 on 0.25 and it works fine (i.e. not broke anything). If you'll have some bugs with it or broken saves, i'll check it.

Lights from LLL - Lack Luster Labs. Craft mostly form LLL too.

Found incompatibility with Infernal Robotics that cause IR breaking. I like Graphotron, but it unacceptable for me. Look for details here and here.

I have no idea. When AGM, Rollcages, Garphotron, Chatterer and RT remained i had no doubt it was RT But Garphotron for 0.23.5 is a branch from original old graphotron, it may contain some bugs i think. I wonder what mods have others with that bug? And... Space dock Mk2 come back online! Thanks Sirkut and Omgnull!

I found out, it was incompatibility bug with graphotron. (lol, it was in last 6 mods in check list) That mods work fine with IR (in that combination): KW LLL ScanSAT B9 Firespitter KJR FAR TreeEdit Editor Extentions Active Texture Managment Clouds and citylights Multiple Saves DA Part Catalog Part Highlighter Persistent Trails Precise Node ResGen Select Root UbioWelding VNG Extraplanetary launchpads Hiperedit Kethane AlarmClock CrewManifest Custom Biomes EnHanced Navball Habitat Pack Procedural wings Procedural farings RCS Build Aid RealChute Lazor TAC fuel balancer Shuttle Parts DR Enginner Redux Hull Cams KAS kOS Differential thrust AGM Rollcages Chatterer RemoteTech

Here https://db.tt/f9FKKyrc I place log file, savegame and some screenshots. Bind 1, 2 for shortcut, 3, 4, 5 for action group, but they don't work. Also found strange bug. Then i place claw on top of piston it doesn't hold joint between piston halfs in place. Some other parts work fine. UPD: remove all mods except IR and toolbar. All works fine, except that i can't hide servo controls. I'll try to find what is causing this problem. UPD2: That's not KJR, it would be too easy. Only 99 options left

I installed new IR 0.14 (uploaded 2014-04-22 06:38:38) and have no toolbar button in VAB and flight. Menu showes in VAB only. If i use action groups or shortcuts to control IR parts, they don't move. I delete previous version. I've tried it with last toolbar and toolbar that comes with IR, existing craft and new game. Is it my mistake and what can help me?

I had same bug back in 0.23. When you dock crafts to each over, game rebuild them in one craft. So piston's top node became connected to root part, making it broken. If it possible to remake joints after docking, that'll be great. Till then don't place pistons between root part of craft and docking port.

Wow! We have a good news! Looking how all that PASSED was showing up was amazing!

No matter, C # or Pascal, the plugin should act differently. While I try to find outcome of docking port bug in save file, plugin should resolve reason of bug. This challenge is much more difficult, i not sure if can i make this. Then i faced docking port bug, i just wanted to have my station working again. Having big save file i tried to make program, that help me to find broken port. And then decided to share it.

technogeeky, thanks for checking grammar. You can open .pas file with notepad. I can try to compile it for Linux. It has no Windows specific functions, but i have no Linux installed to check that. I have no idea how remake it into plugin. It should be bugfix to resolve this problem. Making plugin just to change save files without having some knowledge about docking port problem may cause more errors in saves. The way how next docking port was broken can be a surprise, so i don't want to make any changes in files right now.

Fix my docking is a tool to find and fix problems with docking ports in quicksave. Now added automatic quicksave correction Features Show docking ports on vessel Show docking ports relationships Identify problematic docking ports Support stock and mod docking ports Support multidocking (correcting is not yet implemented) Backup quicksave file Planned Features Full support of multidocking Full support of docking ports with multiple docking modules (partially implemented) Repair docking port problems in quicksave file Changelog Version 0.3 Automatic quicksave correction Fix: ARM compatibility bug Fix: Long strings bug (compatibility with mods which write long strings of data in savefile, like Kethane, SCANsat, ect) More checks added to file analysis Version 0.2 List of critical errors added (errors caused by KSP or mods which usually break docking ports) Docking port UI analysis added Fix: Status "Disabled" now known Version 0.1 initial How to use If you have a problem with docking port: Backup your save files! Make quicksave (F5) Put "Fix my docking.exe" in your save folder near quicksave.sfs. Quicksave shouldn't be open in word processor. Run "Fix my docking.exe" Load quicksave.sfs (F9) Look at "fmd log.txt" for more details Log example ... 39 base comand 1 rootID: 4137735778 Found 6 docking ports 0 part: 15 dockingPort2 ID: 33069350 attached to asasmodule1-2 parent: 3 rootDP: 0 bottom: 3 top: -1 srf: -1 INT: TRUE True > Ready < DockID: 1717145760 == 39 1 0 base comand 1 rootID: 4137735778 Docked (docker) part:27 ID: 1717145760 DockID: 33069350 !I 13 Connected port on same vessel !E 24 Incorrect state of INTERNAL port !I 35 Port has connection !I 39 Port connects to Docked (docker) 1 part: 27 dockingPort2 ID: 1717145760 attached to trussPiece3x parent: 15 rootDP: 15 bottom: 28 top: -1 srf: -1 INT: TRUE True > Docked (docker) < DockID: 33069350 base ing 1 RootID: 3666921736 == 39 0 0 base comand 1 rootID: 4137735778 Ready part:15 ID: 33069350 DockID: 1717145760 !E 4 Docked part connected with non docked part !E 8 Docked vessel name incorrect !E 9 Docked vessel root id incorrect !E 11 Docker not connected with dockee !I 13 Connected port on same vessel !I 35 Port has connection !I 36 Port connects to Ready 2 part: 46 dockingPort2 ID: 603666381 attached to trussPiece3x parent: 45 rootDP: 27 bottom: 45 top: -1 srf: -1 INT: TRUE True > Ready < DockID: 1766022032 == 39 3 0 base comand 1 rootID: 4137735778 Docked (docker) part:67 ID: 1766022032 DockID: 603666381 !I 13 Connected port on same vessel !E 24 Incorrect state of INTERNAL port !I 35 Port has connection !I 39 Port connects to Docked (docker) ... Download links Fix my docking v 0.3https://db.tt/KXAZBtre Source https://db.tt/HfBW2PCd License Fix my docking is published under CC BY-NC-SA 4.0 license

Test on 4.0.2: 1: recycle empty fuel tank 2: recycle full fuel tank

Taniwha, I have vessel explosion few second after production finished, even if if's already released, when production finished at time warp (and it turn back to x1 automatically). When I change time warp manually to x1 it always works well. State of launchpad is prelaunch or landed. And could you look at recycler issue. When it count mass of resourses to produce more metal, then from dry part.

Found bug with resycler. It calculates amount of metal from total mass, not dry mass of part. Thus when i recycle fuel tank, i get back fuel, oxidizer and more metal than from empty tank.