Sovetskysoyuz

I don’t think this is a hard-and-fast rule that non-UWP apps must use the registry, though? Off the top of my head, the Total War games save their preference data into AppData (with other data still kept in the registry) and they’re definitely not UWP apps.

No messing around with fairings was necessary; KSP had a specific part for these tanks.

For me, it’ll be more about the extent to which Science improves upon or diverges from how it worked in the first game. Because the closer it is to the previous system, the harder it becomes to understand why it wasn’t in at release.

Hard disagree on this; blackrack’s clouds look a lot better on my PC than the KSP2 ones do, and the mod’s other features (rain and lightning/thunder) aren’t even present in KSP2.

It turns out the flickering was caused by having Temporal Anti-Aliasing turned on in Scatterer; switching to SMAA has fixed the flickering text. I can't imagine what's causing that interaction for TEXT_LABELs and nothing else.

Alright, I have a pull request created now. I had to cut out the AtmosphereAutopilot work because it would have created a hard dependency on that mod.

I have RPM installed but I disabled PropBatching.cfg because it was causing some other errors with MAS props. That said, it was a few specific props that were giving me errors (mostly using the switchRotary model) so I may try editing PropBatching.cfg to skip those ones and see if it works better. On another note, is anyone still accepting pull requests into the MAS GitHub in MOARdV's absence? I have a few things that I've been working on that I could put into pull requests: a list of fixes to MAS_ASET props, including implementing the audio warnings and altitude callouts for the MAS_Tablo_Alarm parts; new props, including sets to allow editing maneuver nodes and creating KAC alarms from the IVA; a new module to enable controlling AtmosphereAutopilot with IVA props (not fully implemented, but it works for the cruise mode), based on @Flibble's module that provides AA support in kOS; and compatibility with ProbeControlRoom by resolving issues with uncrewed vessels.

Thanks, that resolved the issue.

Is there any sort of known issue with this mod where having a large number of props onscreen in an IVA may cause text on a TEXT_LABEL to flicker? I have an IVA that's up to almost 400 props and noticed that the text renders fine on my few-mods test installation but flickers heavily on my 100+ mods career installation. If I zoom in really far so that only a few props with text are on the screen, then they stop flickering. Nothing else flickers either, it's purely TEXT_LABEL things. Just wondering if it's as simple as me adding too many props on an installation that's already loaded down with mods or if I should bother with trying to triage a possible mod conflict.

I'm getting INITIALIZATION ERROR when trying to switch to MAS IVAs using this mod. This is on 1.12.5 on a test installation of KSP that only has RPM, MAS, Reviva, DE_IVAExtension, the three ASET MAS IVAs for stock pods, and dependencies for those mods. MAS works correctly on its own, and RPM IVAs work correctly with Reviva. Looking at the logs, there are a bunch of errors configuring various props, mostly related to not being able to find certain transforms. Link to zipped log file.

Aircraft have already flown on Mars (the Ingenuity helicopter) and NASA has proposed fixed-wing designs too (Mini-Sniffer, ARES). The thinner atmosphere is a significant constraint but not a showstopper for Martian aviation.

It was Ghostii, on the Discord in late April. yes it does! Nate is actually a huge fan of HOTAS, so it is something we talk about occasionally. I think it be after 1.0 though so that the majority of the issues are ironed out

I found the quote that @Turbo Ben was referencing on the Discord, from 24 April in the ksp2_general channel: yes it does! Nate is actually a huge fan of HOTAS, so it is something we talk about occasionally. I think it be after 1.0 though so that the majority of the issues are ironed out AFAIK while there have been other statements that full controller support is on the roadmap, this is the only one that has tied it to a specific point.

What happened to the joystick control? It was already pretty barebones to begin with.

Yeah, concurrent player numbers are not a good proxy for the number of copies purchased. Dwarf Fortress sold 160,000 copies on its first day (confirmed by the publisher) but has never broken 30,000 concurrent players.