<stratochief>
a little more 'Buffalo Bill' NSFW than Hugh Hefner. Who tore the skin off?
<acc>
uh, some naked big guns :>
<Rokker>
acc: one of the few guns I haven't shot that I want to
<Rokker>
tho I've shot a 1919, so not that far off
<acc>
could be hard to handle that as hand gun :D
<Rokker>
probably shoot that next time I get the chance
HypergolicSkunk has quit [Quit: Connection closed for inactivity]
rsparkyc has joined #RO
blowfish has joined #RO
<rsparkyc>
stratochief, this got me closer with the interstage nodes: @PART[*]:HAS[@MODULE[KzNodeNumberTweaker]]:AFTER[RealismOverhaul]
<rsparkyc>
{
<rsparkyc>
{
<rsparkyc>
%MODULE[KzNodeNumberTweaker]
<rsparkyc>
%showInterstageNodes = false
<rsparkyc>
}
<rsparkyc>
}
<rsparkyc>
they show up when you first drop the part, but after that they're off
<github>
[RealismOverhaul] rsparkyc opened pull request #1571: Fixed IVA model for landerCabinSmall (master...master) https://git.io/vysDo
<stratochief>
rsparkyc: I got the same result without the :AFTER part, I linked the pastebin while you were offline :)
<stratochief>
rsparkyc: have you had a chance to test that IVA fix yet, to see if I was right?
<rsparkyc>
yep, that fixed it
<rsparkyc>
the interior is a little weird, because it's outside the bounds of the exterior model
<rsparkyc>
but nothing complains
<rsparkyc>
so until we can build a proper model (more likely, modify the old one), this is probably good enough for now
<stratochief>
woo, I guessed right :)
<stratochief>
rsparkyc: I think IVA's have a 'scale' option/factor now. so, if you adjust that, you could potentially bring it within the bounds of the part?
<TheKosmonaut>
Hi stratochief
<rsparkyc>
the real fix is probably duplicating the landerCabinSmallInternal, and adding another InternalSeat MODEL in there
<TheKosmonaut>
(I think you pinged me earlier)
<rsparkyc>
it may have a scale option, i can try messing with that for now
<rsparkyc>
maybe 0.8?
<stratochief>
TheKosmonaut: indeed I did, accidentally. none-the-less, hello :)
<rsparkyc>
or if everything is already blown up by 1.6, maybe i need to set 1.2 or something?
<stratochief>
rsparkyc: whatever you think might make it better :)
<stratochief>
I don't mess with IVA's at all, same as with audio. I just remember the odd thing from time to time
<stratochief>
I've got my LEO station beginnings planned, and my plans for a heavier Gemini-Direct and later Lunar Shelter designed and tested. Also, a ScanSat to map the Moon, Mars, and Venus
<rsparkyc>
someone tagged me on the RO reddit, i should probably reply...
<stratochief>
but most of that is waiting on new tech to unlock, since I rushed techs for Gemini Direct. now, to work out my future Mars lander to capture and liquify CO2 to start the road for ISRU
<rsparkyc>
we pretty much said the exact same thing
<stratochief>
I'd kind of like to have a carbon monoxide powered hopper on Mars, but that would further slow my progress towards Mars colonization :P
<stratochief>
I wonder if you could hop around Mars, just by trapping CO2 in a reservoir, heating it with nuclear heat, then passing it back out through a nozzle
<rsparkyc>
technically, i would think the answer would be yes
<stratochief>
I... I think that someone downvoted your comment. I had upvoted it, and now it is at 1 point.
<rsparkyc>
haha
<rsparkyc>
i have enemies i guess
<rsparkyc>
btw, I took your suggestion about scatter, so I have that running (and have updated the spreadsheet)
<rsparkyc>
put a note in there about some settings i had to change to get rid of the halo around planets, I'm assuming it's because I'm on a mac
<stratochief>
do you have any pic of the halo?
<stratochief>
that sounds right, I don't think I had a halo
<stratochief>
rsparkyc: and I'm glad you were able to get it working :) I might go with clouds again, once I've got things nice enough to start recording in 1.2.2
DormantDex is now known as DuoDex
<rsparkyc>
not ATM, but i may be able to find a similar one online
<rsparkyc>
do we have an official tabs vs spaces policy?
<github>
[RealismOverhaul] rsparkyc pushed 13 new commits to master: https://git.io/vys7K
<github>
RealismOverhaul/master c6d6d6e gavinIRL: Small fixes to Merlin config, fin radiator, etc....
<github>
RealismOverhaul/master 719ff8c gavinIRL: Merge pull request #1 from gavinIRL/several-small-fixes...
<github>
RealismOverhaul/master c690076 gavinIRL: Updated radiator mass
<acc>
rsparkyc: as far as I'm concerend: people who use spaces instead of tabs should burn in hell forever :)
<rsparkyc>
acc: well, i wouldn't take it that far…but point taken
<stratosleep>
rsparkyc: I personally don't care; we takes what improvements we get. PhineasFreak's style is as close to a standard as we get to a standard :P
<rsparkyc>
i told him to join the IRC, maybe i'll tell him i wont approve spaces until he comes in here to defend himself
<rsparkyc>
either that or i'll issue PRs against all his branches swapping spaces for tabs
<rsparkyc>
glad we got that newline issue worked out in that other PR
<stratosleep>
did that get straightened out? good, good.
<rsparkyc>
yeah, i had him fix the massMult issue elsewhere as well, and I merged it in
* acc
gets some gas and a lighter, just in case
<acc>
:D
Wetmelon has joined #RO
Rokker has quit [Quit: Connection closed for inactivity]
Wetmelon has quit [Ping timeout: 206 seconds]
Wetmelon has joined #RO
Addle_ has quit [Ping timeout: 206 seconds]
Addle has joined #RO
Rokker has joined #RO
* xShadowx
agrees with acc
<xShadowx>
to me, tabs should always be used, as any decent text editor can configure how many spaces a tab is, so people who like 2 can go with 2, people who like 4 go 4, etc, spaces is fixed amount like 'no fuck you use it my way'
<acc>
exactly
<xShadowx>
the only valid argument i ever seen for spaces, is for matching alignment with a line above, such as mymethod(arg1, <next line> arg2, both arg allign
<acc>
yeah, that's valid
<xShadowx>
my prefs dont care for that, and i'd still use tab=4, but still valid point
<acc>
and it saves sapce
<xShadowx>
be nice if there were established case rules for editors, tab unless lala
<acc>
space
<xShadowx>
so even if i tab, a rule would cause allignment
<acc>
(space in terms of HDD space)
<xShadowx>
its text, i have 16tb of hdd space, how to put this .......i dont give a flying fuck at saving 2-3 bytes :P
<acc>
but the interpreter/compiler maybe cares
<xShadowx>
to me its 100% about readability heh
<acc>
or takes longer to process
<acc>
the more code, the more it's adding up
<xShadowx>
most languages dont care for whitespace at start/end of lines, and just trim
<acc>
but that trimming takes time
<xShadowx>
and once compiled, no effect
<acc>
after compiling yeah
<xShadowx>
shite code is far more f a drain on a compiler :P
<acc>
yes, and lots of other cases. my point was: it matters
<acc>
even if you have tons of resources to store and process, it's a bad habit to waste anything of it
* Rokker
hides a titan 3m in stratosleep's bed
Senshi has joined #RO
Senshi has quit [Client Quit]
ferram4 has quit [Ping timeout: 194 seconds]
Hohman has quit [Quit: ChatZilla 0.9.93 [Firefox 51.0.1/20170125094131]]
<blowfish>
I suspect that parsing the syntax tree is a small portion of overall compile time
<rsparkyc>
I had an idea about shutting down avionics on parts that had no crew (for instance, escape pods on a space station, or the lunar decent module on an apollo like mission)