HebaruSan

You're really close! Maneuver or prograde will be lined up by the time you reach the burn, since it's a prograde maneuver, so either would work. And if you point the ship towards the maneuver yourself, you could also choose stability assist.

Imgur has multiple URL formats. You want to post the one that ends in "png". Doesn't work: https://imgur.com/gallery/POehF Doesn't work: https://imgur.com/4AI41Fc Works: https://i.imgur.com/4AI41Fc.png

Taking a look at the files, there doesn't seem to be any such thing. The vanilla assets are all in asset bundles, and the "first parts mod for KSP2" seems to have done everything in C# code; maybe @LuxStice can confirm? https://github.com/LuxStice/SORRY

There is indeed: Hover a user's name to get a member info pop-up. Click "Ignore", then check the "Posts" checkbox in the next screen and click "Update Preferences".

Discussion about games in the KSP franchise and related topics. That's just the moderators keeping things tidy and well-organized. It's one of the nicer things about this place that you don't have to scroll through fifty duplicate threads posted to the wrong sub-forum to find the content that you're looking for, outside of the Science & Spaceflight subforum. The moderators seem to agree, as the stated reason for locking those threads was the ceaseless pointless bickering between forum users, not the fact that player numbers were pointed out.

Thanks for sharing that screenshot. I finally had some time to look into it, and I think I've identified why the error wasn't shown. It should be fixed in the next release: https://github.com/KSP-CKAN/CKAN/pull/3840

The log is shown in the text box under the progress bar:

Probably not, but if you have actual helpful information to contribute, please feel free to do so.

Right, that's not what ctrl-D is for. Press Esc, then +, then F9.

Well if it worked for me and not for you, then the cause must be something that about your situation that isn't true of mine, which rules out both CKAN and SpaceDock. Maybe your PC has a misconfigured firewall or antivirus?

Seems to be working fine now. Probably a temporary glitch with SpaceDock that resolved itself already.

Try the threads for those mods: CKAN can help if there's some indication that they were installed wrong, but we're not experts in problems with TweakScale.

This is a perfect example of how and why saying "see title" fails.

Hi, there's a manual review step to make sure the generated metadata is correct. They're in the queue.

FYI, taniwha's broken server is going to cause problems for people trying to install this (but it already would have been for the old module):

Try the threads for those mods: CKAN can help if there's some indication that they were installed wrong.

For the record, my opinion on KSP2 qua KSP2 is: It has far too many severe bugs for me to enjoy or purchase. (I also don't buy pre-orders, and for me this would constitute a pre-order for the features that were announced but aren't included yet.) I only have it in my Steam library because a generous soul donated it so I could look at the files to add CKAN support; but I have not yet been able to launch it for uninteresting reasons related to OS versioning. So that's not why I was objecting to your complaints about the bug reporting process.

No, nothing was bolded. I think you may be referring to the foreground/background coloring that the forum auto-applied when I pasted the copied text. I did not notice this because it matched my theme. I have gone back and cleared this formatting.

Sorry, what? Between the two of us, only one has used all-caps words in this thread, and it's not me. Intercept's process for receiving external bug reports is at most 69 days old and was created by the same people who are changing it now. Your notions of "newbs to a company" and "established processes" are quite peculiar indeed. (But also just as irrelevant as the initial attempted tangent about your own bug tracker template.)

OK, that's fine. Now imagine you're working on some other project, and when bug reports start rolling in according to the first requested bug report format, you look at them and find that many of them are impossible to investigate or otherwise just not actionable. Do you stubbornly stick to the original format out of fear that someone on the forum will be upset that you changed something, or do you look for ways to improve it so future bug reports will be better?

Maybe there's a reason for that. Imagine being on the other side of the development veil, and when bug reports start rolling in according to the first requested bug report format, you look at them and find that many of them are impossible to investigate or otherwise just not actionable. Do you stubbornly stick to the original format out of fear that someone on the forum will be upset that you changed something, or do you look for ways to improve it so future bug reports will be better?

Maybe it's not a coincidence that multiple games do this. An intentionally unspecified unit with unknown conversions to other more familiar units could serve as a way to hide discrepancies for purposes of game balance. Either way, this is less of a bug report than a disagreement about design.

Wow, that was fast! Confirmed that it's fixed and is now in CKAN.

Hi, unlike the previous release, this ZIP file uses backslash ("\") in file paths. The ZIP spec requires forward slash ("/"): https://pkware.cachefly.net/webdocs/casestudies/APPNOTE.TXT FYI, this has prevented this release from being added to CKAN.

You can't; it's not a mod, so there's nothing to install. You already have; since it's just mock-ups, your browser already downloaded them to display them to you.