aradapilot has quit [Ping timeout: 207 seconds]
Snoozee has quit [Ping timeout: 183 seconds]
Snoozee has joined #RO
Snoozee is now known as Majiir
aradapilot has joined #RO
awang has joined #RO
<awang> \o
egg is now known as egg|z|egg
<lamont> awang: in “settings” “
<lamont> “RO/RSS special handling (WIP)”
<awang> I have that checked
<awang> Is that bad?
<lamont> i don’t think its bad but it might explain the bug
<lamont> hah!
<awang> Wait
<lamont> replicated, yeah, thats it
<awang> wat
<awang> Why does that cause autopilot to not kill engines
<awang> It seems totally unrelated
<lamont> its a very strangely named option, that is what it does
<awang> Strange indeed
<awang> I'll try unchecking it and see what happens
<awang> Why does that option exist?
<lamont> if you want to flip between different mechjeb autopilots in RO you don’t want it killing your engines and using a restart (or not being able to restart at all)
<awang> That makes sense
<awang> Although I guess now that you have the One True Autopilot, seems that option isn't needed
<awang> For me at least
<lamont> i don’t precisely know why people like to do that, i tend to like to use disabling the ascent autopilot to kill my throttle as well, and its how NK flies in his videos as well, but i can see the point behind it because if you really want to do that then having it burn a restart is awful
<lamont> yeah hopefully with better and better PEG it becomes less necessary
<awang> That should be renamed at least
<lamont> yeah
<awang> I thought that it was controlling some other settings that would make MJ more accurate for RO
<lamont> nope, its just about not killing throttle
<awang> Jeez
wb99999999 has joined #RO
<awang> I guess the other question is what is WIP about that setting?
<wb99999999> maybe they have a whipping of an idea
<awang> Whipping in progress?
<awang> WIPing in progress?
<wb99999999> lol
<wb99999999> that was my clumsy attempt at a pun
<wb99999999> now I shall get out
<awang> What does the proc parts useEndDiameter field mean?
<awang> lamont: MJ seems to be killing my upper stage now!
<awang> Thank you for finding the cause!
<lamont> =)
<lamont> i still need to fix it, since its still a bug but at least the major part of the mystery is solved
<awang> What's the bug?
<lamont> PEG still should kill the throttle even if that box is checked
<awang> Ah
<lamont> if you disengage PEG and then stop the ascent guidance before you hit orbit, it should totally not kill the throttle with that checked, but if its engaged and PEG hits its terminal conditions then the throttle should cut either way that box is set
<awang> That sounds a lot more reasonable
<awang> I wish MM had a better way of specifying dependency order besides adding a bunch of Zs to FOR[] :(
egg|z|egg is now known as egg|zz|egg
egg|zz|egg is now known as egg|zzz|egg
<awang> "Thanking Jack D. Ripper"
<awang> Uh
wb99999999 has quit [Ping timeout: 180 seconds]
wb99999999 has joined #RO
<wb99999999> strange
<wb99999999> My 1.3.1 stock install started to have a wired stutter
xxp has joined #RO
<xxp> CALL L0DE RADIO HOUR NOW @ 415-349-5666
<xxp> WATCH L0DE RADIO HOUR @ https://youtu.be/zqPvm4Vk6ik
<xxp> wb99999999 awang aradapilot Majiir ProjectThoth Rokker Shoe17 mkalte Wetmelon stratochief acharles Bornholio egg|zzz|egg Qboid ferram4 Raidernick xShadowx VanDisaster BasharMilesTeg Sarbian Iskierka Daz lamont SirKeplan JPLRepo gazpachian Ezko_ taniwha soundnfury Kraken X Pap petti NCommander A
xxp has left #RO [CALL 415-349-5666]
<Raidernick> oh for fucks sake
<wb99999999> really
<wb99999999> REALLY
<awang> wat
<Raidernick> wb99999999, i like how it put you first
<egg|zzz|egg> I WAS SLEEPING YOU STUPID BOT
<Rokker> egg|zzz|egg: I blame you
<egg|zzz|egg> grrmbphblgmrph
<wb99999999> I think that's because I was the last one to say a damn thing
<wb99999999> and he just kinda traced to the last few people who have said anything and pinged them
<Rokker> wb99999999: I blame you
<wb99999999> well since most people was out
<wb99999999> anybody know why I am having jitter and stutter with 1.3.1 stock?
<awang> wb99999999: Even after a restart?
<awang> And no log spam?
<wb99999999> after tuning down graphics, locking down framerate and a graphics card driver update
<wb99999999> It doesn't seem to be performance-related
<wb99999999> when it jitters the whole game freeze for a brief moment, not only the rendering
<awang> GC, maybe?
<wb99999999> what does that stand for?
<awang> Garbage collection
<wb99999999> hmm...what does that have to do...
<awang> The whole program has to stop while GC is taking place
<awang> Or at least it does in simpler algorithms
<awang> I think
<wb99999999> I confess that I didn't know what you're talking about
<wb99999999> but what should I do then
<awang> It's something that has to do with C# being used
<awang> C# doesn't require that programmers explicitly say that they're done with a particular piece of RAM
<awang> Instead, it stops the program, scans memory to find RAM that is unused, the recycles it
<wb99999999> hmm...I think it might be performance-related...
<wb99999999> or not..I am so confused
<wb99999999> I have never had something like this happen to me in a videogame, not to mention KSP
<wb99999999> it does seems to get worse the closer I am to the ground
<awang> Hmmm
<awang> I wouldn't know, unfortunately
<awang> Can you try rolling back the graphics driver update?
<wb99999999> good thinking
<wb99999999> I'll try that
<wb99999999> I think memleak is the explanation
<wb99999999> or GC or whatever, it's on the game
<awang> If you're familiar with version control, you can try versioning KSP to be absolutely sure that there weren't any advertent changes
<awang> A memory leak could certainly cause jitters
<awang> idk what about the ground would make it worse, though
<awang> Or why changing graphics settings would make it worse
<awang> I don't think graphics should affect garbage collection
<awang> At least for stock
<awang> Unless there's some kind of programming horror behind the scenes I'm not aware of
<wb99999999> I have no idea
<wb99999999> yes, it does have something to do with memory
<wb99999999> oh god...
<awang> ?
<wb99999999> the fact there's not much solution available especially for someone who know nothing about code like me
<awang> Yeah, unfortunately tools for figuring out exactly what's going on memory-wise aren't the easiest to set up or use
<wb99999999> I did get the memgraph mod for info
<wb99999999> well...every once a while the memory usage dip, with a visible stutter
<awang> Yep, that's garbage collection
<wb99999999> yep
<wb99999999> it didn't do this to me until now
<awang> Reinstall KSP?
<wb99999999> doing it
<wb99999999> I mean I was about to do that anyway
<wb99999999> now I am just doing it immediately since you mentioned it
<awang> Rolling back your graphics driver didn't help?
<wb99999999> I didn't actually try it, but I doubt it has anything to help
<awang> I'd agree
<wb99999999> I am familiar with actually slow downs due to high memory use or simply graphic card power when I play RO with a hundred mods
<wb99999999> this is not that
<awang> You don't get jitters with a lot of mods installed?
<wb99999999> no
<wb99999999> I get low frame rate and low simulation speed
<wb99999999> but not jitter
<awang> Hmmm
<awang> Or maybe the jitter is there, but the low frame rate hides it
<awang> I should really install MemGraph
<awang> And figure out what keys to bind it to
<wb99999999> it has a default bind that's pretty good
<wb99999999> mod+numpad / to toggle the display
<awang> Unfortunately, I'm on a laptop
<wb99999999> puff
<wb99999999> I feel sorry
<awang> I travel around way too much for a desktop to be much use
<wb99999999> some laptop gamers keep an external keyboard
<awang> I have one, I just didn't bring it with me
<awang> And it's not that convenient to use when laying in bed
TM1978m has joined #RO
<awang> Hmmm
<awang> Something in my copy of KSP is leaking memory like a sieve
<awang> Up to 28.5 GB of RAM used
<wb99999999> hah
<wb99999999> reinstall the sucker helped
TM1978m has quit [Remote host closed the connection]
<awang> Good news!
<awang> Wonder what changed to cause the stutter...
<awang> I think I managed to break RP-0's tooling
<wb99999999> I am still in the dark about that
<awang> Changed proc decouplers to use the cylinder shape, now RP-0 thinks all proc decouplers have a diameter of 0 meter
<wb99999999> I speculated about some visual mod doing something to the memory
<awang> About what?
<wb99999999> but I did reinstall them, and the effect is far less severe
<wb99999999> the jitter
<awang> Same graphics settings as before?
<awang> lamont: I'm getting a ton of NREs from MJ
<awang> Stack grace MuMech.MechJebCore.OnGUI
<awang> MuMech.MechJebModulePEGController.DrawCSE
<awang> s/grace/trace
<Qboid> awang meant to say: Stack trace MuMech.MechJebCore.OnGUI
<awang> I'm in the VAB when this is happening
<awang> !tell blowfish Is MM supposed to be allocating memory like crazy while applying patches?
<Qboid> awang: I'll redirect this as soon as they are around.
<awang> Seeing some interesting behavior from mono here
<awang> Assuming MemGraph is right
<awang> Mono's basically constantly collecting
<awang> But it's refusing to increase heap size above about 750MB
<awang> And reduces it quite frequently
<lamont> PEG should not be running in the VAB you can’t ascend from there
Wetmelon has quit [Ping timeout: 186 seconds]
<awang> idk, looks like I broke something else?
<awang> No idea why PEG was on
* xShadowx fails at making factorio mods
* xShadowx crawls back to ksp to land on mars
<lamont> i can probably do something about preventing that from ever being enabled there...
ProjectThoth has quit [Quit: +++out of cheese error+++]
TM1978m has joined #RO
Wetmelon has joined #RO
BadRocketsCo has joined #RO
BadRocketsCo has quit [Read error: Connection reset by peer]
ferram4 has quit [Ping timeout: 200 seconds]
<acharles> I’m starting a new save with the latest RP-0 (development) and RO (dev) and I see this weird thing where when I apply an upgrade to the VAB, it doesn’t give me 0.05 BP/s anymore and it doesn’t start at 0.1 either. Though, this only happens after the first contract happens, I think.
<acharles> Anyone else experiencing this?
Rokker has quit [Quit: Connection closed for inactivity]
<acharles> Maybe this is what it’s supposed to be (looking at the formula) but the UI in KCT is buggy and shows +0 instead of something more useful?
ferram4 has joined #RO
<acharles> Apparently the new formula is just very different and the UI is weird.
<acharles> The UI doesn’t like small numbers.
Senshi has joined #RO
Hypergolic_Skunk has joined #RO
BasharMilesTeg_ has joined #RO
BasharMilesTeg has quit [Ping timeout: 200 seconds]
wb99999999 has quit [Ping timeout: 180 seconds]
TM1978m has quit [Remote host closed the connection]
Rokker has joined #RO
schnobs has joined #RO
<awang> lamont: Yeah, I'm seeing the NREs as soon as I load the craft into the VAB
<awang> This is from a fresh start of KSP, so I haven't touched the flight scene
<awang> MM question
<awang> Is @PART[*]:HAS[@MODULE[ModuleDecouple]|@MODULE[ModuleAnchoredDecoupler]] valid?
<awang> Specifically, am I allowed to use | to indicate a part has either of those modules?
<awang> Gah
<awang> Can I get line numbers from KSP exceptions?
<awang> lamont: You're on mac, right?
egg|zzz|egg is now known as egg
aradapilot has quit [Ping timeout: 207 seconds]
aradapilot has joined #RO
aradapilot has quit [Remote host closed the connection]
aradapilot has joined #RO
QuantumSwag has joined #RO
QuantumSwag is now known as QuantumFalcon
QuantumFalcon has quit [Client Quit]
<awang> soundnfury: Back when you asked me to look at the PARTUPGRADE for RCS TL2
<awang> You said that that isn't in the tech that actually unlocks it
<awang> How do I determine which is actually right?
ProjectThoth has joined #RO
schnobs has quit [Ping timeout: 186 seconds]
aradapilot has quit [Ping timeout: 207 seconds]
<ProjectThoth> Got a stock question - is it possible to fly past Duna and return to Kerbin with relatively low delta-v?
<ProjectThoth> That is, do free return opportunities exist with every departure window?
TM1978m has joined #RO
blowfish has joined #RO
Hypergolic_Skunk has quit [Quit: Connection closed for inactivity]