[18:30:18] NASSP Logging has been started by thymo [18:30:20] indy91: PR merged [18:31:02] ah thanks! [18:31:10] I looked at drawPad and have decided that I don't care enough to be assed to fix it. [18:31:13] do you still plan to have a general look at draw... [18:31:16] hahaha [18:31:29] well, if you want to you could look at one specific PAD [18:31:44] and I copy that style for the other PADs [18:31:58] Yeah, maybe when I get into a refactoring mood I'll take a look [18:32:11] but in general, let's talk about sprintf etc. [18:32:17] snprintf is the best choice? [18:32:39] As long as it's supported both on Windows and Linux. As snprintf is [18:33:00] right [18:33:31] I did have some CTDs a few years ago that I couldn't figure out and I blamed unsafe code using sprintf for it [18:33:59] so I wanted to use sprintf_s then to at least get a hard CTD and not a random one when there was a problem [18:35:01] I guess snprintf is both portable and doesn't do unsafe things, right? [18:35:25] it's a fairly relevant question because I am using these functions 1000s of times between the MCC and RTCC MFD [18:46:48] And you still had some issues with the variable naming that I didn't understand. "It tells me what it is, not what it is for." [18:47:45] I think a general chat about this topic here is fine, we can always improve. I was probably a bit rude on Github, I was just annoyed that we are now combing through every small PR for stuff like that. That would make development really really slow. [19:14:41] I stepped away to eat dinner for a little bit. snprintf is save, provided the size that you give it fits inside the buffer you write to. [19:15:16] It will never copy more than n bytes to the destination even if the source is bigger [19:16:24] With "it tells me what it is, not what it is for" I mean that tempString tells me that it is a variable that is a string (I already know that) and that it is temporary, so it tells me what it is (which I already know). I want to know what the purpose of the variable is (e.g. a line in a PAD). [20:13:18] yeah I will use snprintf from now one, let's see how it goes. Eventually I might then convert everything to snprintf. And I think I understand now what you mean with the variable name. [20:39:14] Doing Docked DPS this evening [20:39:56] This is going to be my first burn on a scenario other than the PDI for 11 lol [20:49:27] definitely picked a rather unusual burn then haha [20:49:47] It's the first one on 9 [20:51:37] first LM burn yeah [20:52:09] get your manual throttling cue card ready :D [20:52:19] Yeah. About that... [20:52:22] It's broken [20:52:27] Not sure if VESIM or something else [20:52:40] hmm ok [20:52:44] what's your setup? [20:52:45] I configured it as Axis Z [20:52:49] Saitek X52 [20:53:07] so one joystick only? [20:53:13] Yeah [20:54:19] normally (and without VESIM) I am using the joystick as the ACA in that case. translation commands with keyboard. And the throttle lever on the joystick as the cheaty TTCA throttle [20:55:59] but I guess you would be able to set up one axis for throttle with VESIM [20:56:10] Manual throttle should work using numpad 0 and period right? [20:57:29] yeah, unless it's set up differently [20:57:45] I disabled the joystick, it doesn't work still. [20:57:46] that's really the no-joystick variant [20:57:59] What else could mess it up? System wise [20:58:12] how do you know? Are you already trying to fire the engine? [20:58:42] if the DPS engine is off you still needs engine arm to DPS so that throttling shows up on the meter [20:59:34] Oh [20:59:38] I knew that [20:59:44] flips Eng Arm to DES [21:00:05] Totally not because I don't know what I'm doing [21:00:34] haha well there is a throttling test during activating the LM is there not? [21:00:48] That's what I was trying to do [21:00:51] aaah [21:02:54] I'm also like half an hour behind in the checklist, not really helping [21:06:32] Nice. The soft stop in the X52 matches the 50% stop in the LM [21:07:15] ah that's fun [21:11:11] RCS TCA and red quad talkbacks is probably a fuck up by me? [21:11:47] I expected thrust during the RCS Hot fire test. lol [21:12:01] I want my CSM back.. :p [21:14:21] haha [21:14:26] during that test you are pushing in the 8 TCA circuit breakers [21:14:29] did you already do that? [21:14:49] No [21:15:14] I'm stepping back to cold fire so I don't have to rush so much [21:15:42] seems like you are only pushing in those breaker partway through the procedure [21:16:11] breakers* [21:16:30] before you do the checklist always says "Possible QUAD Flags & RCS TCA Warn Lts - On" [21:17:13] without those breakers the RCS can't fire. Only in hardover mode [21:17:46] hardover mode is equivalent to direct RCS in the CSM [21:17:58] hardover needs ATT DIR CONT and full deflection [21:18:04] ATT DIR CONT breaker* [21:18:20] normal RCS operation needs the 8 TCA breakers [21:18:44] so yeah the very first test in the hot fire procedure is not yet firing hot it seems [21:26:45] I'm looking at the AOH and the checklist MFD and the MFD doesn't mention the Att dir cont breaker at all [21:27:07] It's used during cold fire but the MFD never called to close it [21:29:47] I'm seeing it in the checklist file for Apollo 9 LM [21:29:52] in the hot fire procedure [22:21:16] good night! [00:07:56] thewonderidiot, your website appears to be down [00:17:51] not completely down.... although its letsencrypt/ssl stuff is completely broken [00:18:11] and I haven't really felt like dealing with it :/ [00:22:17] it still works if you force http://www.... [00:22:19] http://www.apolloguidance.computer/2003993_061/pins