micha

It "should" still work. Unfortunately my plans for updating this mod have pretty much come to a standstill since moving to Japan. That said, if anybody finds anything broken, I'd still be very much invested in supporting and fixing it.

Thanks to everybody commenting and the final conclusion on this. I wonder if it's possible to create a ModuleManager patch to fix the part and include it in DPAI.. but I suspect it's an issue with the actual part model and the way it's oriented.

G'day Gingt, I'm sorry, it's a bit difficult to understand what you're trying to say without a video, but I think I know what the issue might be. So in "standard" rockets, the docking port is at the front (top), and in the same orientation as the cockpit. In your spaceplane, it seems that the docking port is in the middle, and facing upwards in relation to the cockpit. Even though DPAI will use your docking port as the part it uses to calculate all of the alignment displays, your craft controls will be based on your cockpit. So I think this is why you might be confused between why the various axes aren't lining up the way you expect during your docking maneuvers. To "fix" it, you can right-click on your docking port and select "control from here" during the docking maneuvers. That way when you thrust up/down/forward/back, it is relative to the docking port, and not your cockpit. Remember to change it back to the cockpit after you have undocked as otherwise you will have a very confusing time of flying your spaceplane afterwards! To clarify, the DPAI indicators are: * Orange crosshair - orientation of your craft's docking port (or "control from here" part) to the target docking port * Yellow crosshair - X/Y velocity of your craft in relation to the target docking port (Z direction is indicated by the shape of the yellow crosshair, "open" when approaching the target, and an "x" when flying away) * Green crossbars - alignment of your craft in relation to the target docking port; if they are red, the target docking port is "behind" you. To "move" the green vertical bar to the right, the yellow indicator must be to the left of the centre. To "move" the green horizontal bar up, the yellow velocity indicator must be below the centre. If the green crossbars aren't centered, you want to "move" the yellow crosshair towards the green crossbars; not away from them. The further away from center the yellow crosshair is the faster the velocity. In all of your pictures (except the first), you were always doing the opposite of that, and your craft wasn't even aligned with the target docking port (the orange arrow indicates the direction you should rotate your craft to align it). The closer you get to your target, the more sensitive the display gets; think of it as an approach cone. So even if you were "perfectly" aligned and move directly towards your target, you might see the alignment indicators drift, so you'll need to compensate. It's important to have your RCS well balanced on your craft (there's a mod to help you with that while building).

First of all, I hope you've taken a copy of your save-games and stored them somewhere safe before trying to load them with the new version of KSP. Secondly, could you please post the full logfile (*) from the game somewhere (not here!) and link it? For example, to pastebin? It will help people see what the possible problems could be. Thirdly, if you don't mind sharing it, you could also upload the savefile for people to take a look at. (*) To find the logfile, open your KSP directory. It should be called "KSP.log" If you're playing in a Steam-installed copy of the game, you can right-click on the game, select "Manage" and then select "Browse Local Files" to open the folder.

For @BarnabeLEPD and anybody else who's had issues with surface-attached parts, could you possibly try out this unofficial build : https://github.com/mwerle/ConnectedLivingSpace/commit/844e5ec8d7f1d346642d0e76b3f2c01d3c39fc3e To try, Download the DLL's and replace the ones from your GameData (might be an idea to copy the original ones somewhere safe so you can return to them once you finish testing).

It's been confirmed non-Linux since pretty much forever. The official line is "There is no announcement for these platforms at this time." - https://steamcommunity.com/app/954850/discussions/0/2686880925155743711/ I believe it's also been mentioned (officially) in various other places using different wording - Google is your friend. People are still hopeful that it may eventually be ported to Linux; given it's still based on Unity the actual technical work should be minimal. So it depends on how much it costs them to support another platform vs the projected sales on that platform. (Getting a touch OT for this thread though...)

Agreed. And besides which, unless things have changed which I haven't heard of, KSP2 will be Windows-only (or at least, not Linux). Which will exclude a lot of people who currently play (and mod) KSP. Overall I think this is a really poor decision by the devs. Yes, the Linux playerbase is tiny in comparison, but by developing something on multiple platforms, _especially_ when using a cross-platform engine anyway, you can discover a lot of bugs and poor coding practises during the development stages and mitigate them early on. The long-term cost savings in post-release support is, I think, worth the initial investment of building the game for multiple platforms. As for modding, one of the core architectural changes which I really hope KSP2 brings to the table is dynamic loading of mods. Basically I'd like each save-game to be able to specify which mods (and ideally, which versions of those mods) it uses. Icing on the cake would be a CKAN-like mod-manager built right into the game.

In what world is a DLC a microtransaction? Edit 2022-04-18 : Sorry, that probably sounded a bit facetious. A DLC is a major optional addition to a game, developed and released separately and usually costing a significant fraction of the original game price. Sometimes a DLC modifies the core game experience, but usually the primary focus of a DLC is on expanding the playable area via new maps which sometimes allow for an entirely new style of gameplay compared to the original game. A microtransaction is something built into games, often free-to-play games, which allows people to pay a small amount to immediately unlock something which can usually be unlocked through in-game activities. The in-game activities are often purposefully developed to be "grindy" or to take long real-world timers to complete in order to encourage people to pay for the unlock instead. Unlocks are usually fairly minor such as new characters, weapons, outfits, etc.

Given that star systems are handcrafted, there'll only be a few. With possibly more coming as DLC in the future but unless they add new gameplay options, what's really the point? The alternative would be procedurally generated, but then there's the risk that no matter where you go, it'll all be very similar and thus somewhat pointless as we've seen in other games using this approach.

Can you please try with a copy of the game which ONLY has DPAI and its dependencies installed? I'm not aware of any incompatibilities, but you have quite a large number of mods installed there and there are several (probably unrelated) errors in your logfile..

Please note that @Papa_Joe has resumed development of CLS. And if he reads this, I strongly hope that he will not do so. ClickThroughBlocker pulls in other dependencies and some of those I refuse to install in my game. I've discussed my issues with the author of those mods and we agreed to disagree. That said, implementing similar functionality to avoid click-through is something I do strongly support and have already implemented and/or started work on such for other mods. For CLS I was torn between implemeting it for the current implementation, or by moving all of CLS to the "new" Unity windowing system which would provide this functionality by default as well as other benefits, albeit at a significant amount of initial development effort. ---- @Mods please lock this thread as it is no longer required. Please see the original thread on CLS (linked in the OP).

How did you install it? (CKAN or manually) Does your logfile show any errors? (In fact, if you can upload your logfile somewhere that'd be best) Do you have Blizzy's Toolbar installed (DPAI _should_ default to the stock toolbar, but possibly it's on Blizzy's) ? If you start a brand-new save with no other mods (remember, you can keep multiple copies of the game so there's no need to futz about and potentially break your main game), does it work?

Hi @Papa_Joe, sorry, I didn't realise you didn't have access. I've checked and I was able to give you full control over both SM and CLS on Curse. If you prefer, I can transfer the actual ownership. I've sent you a PM to organise how to transfer ownership.

Doh! I didn't think I included MM anymore.. but I checked one level too high. Thanks for pointing this out.

Sorry for the hugely-long delay. DPAI 6.10.0.0 is up. It's exactly the same, just recompiled using KSP1.12.2 assets. EDIT: Wow; seems it's still quite popular! The last version had over 40k downloads from SpaceDock, nearly 55k downloads from Curseforge, and 900 from GitHub. CKAN is linked to SpaceDock, which makes the Curseforge number very impressive indeed!

Was about to say the same thing!

As @Papa_Joeis resuming support for this fantastic mod, the discussion will move back to the original forum thread here: @MODS: This thread can be locked to further replies. Thank you.

Thanks everybody for chiming in, and argh, what a nightmare! Why the bleep did KSP break something which has worked fine for years and years? Moving forward, IMHO the best approach will be a unified one by all mods which publish APIs or include dependant DLLs from other mods. Will need to collate a list of mods and then have a chat to the authors to see what people think.

Yeah, unfortunately the game is "broken" when you start installing science mods; there's simply no way to balance it. I usually dial science right down to compensate but that can make the early game a bit more difficult.

Hi @Tacombel, not entirely sure what you're asking? CLSInterfaces is just a really tiny wrapper which exposes the CLS functionality to other mods. Only the latest version of CLSInterfaces should load and be active even if multiple mods have it installed. If that's not the case then I'll need to take a look into that. If you're asking about making CLSInterfaces a separate mod in CKAN that's a possibility although won't really remove the issue - for people not using CKAN, it will still be need to be bundled with mods.

W00t! Welcome back :) I'm not exactly "active", unfortunately (RL), but still around. I had lots of plans to work on "my" mods now that we have a "final" version of KSP, but haven't really had/made the time to actually do so. Partially the fact that everything just seemed to continue to work also let me be a bit lazy in that regard. I'm more than happy to pass Ship Manifest back to you - I was only ever caretaker , but I'm also happy to continue to collaborate! As regards the resizing, I had a bit of a look, and while it's not super difficult, it's a lot of work given the amount of windows in SM. So I started looking into converting it into "native" Unity UI although there's pros and cons to that approach with KSP. Pros being less resource usage and able to use a GUI to design the UI, cons being it's a bit of a faff, needing multiple DLLs, and losing the ability to make quick tweaks using just code.

Awesome, thank you. Afraid I'm a tad busy IRL, so this might still take a little while.. I haven't had much time for KSP lately

Hi @Grokit, thank you! I'll add your patch to the next release.

Great update and thanks for the huge list of bug fixes! And quite a bit sooner than expected Still sad to hear that this really is the end for KSP1.x... there's still quite a few things which could do with a tweak or a fix! I know it's a long shot, but I don't suppose there's any chance at all of open-sourcing the game once KSP2 is released??

Thanks for the detailed mini-tutorial, @luna_cat. Just a note along with this is that the mod is trying to encourage multiple visits / resupply missions to a long-term station. So rather than trying to launch all the equipment and experiments in one go, it was really thought of to build a station out slowly, adding items, and running the experiments while doing other stuff, to collect and return the completed experiments on the next resupply mission.