ferram4 changed the topic of #RO to: Welcome to the discussion channel for the Realism Overhaul (meta)mod for KSP! Realism Overhaul Main Thread https://goo.gl/wH7Dzb ! RO Spreadsheet http://goo.gl/Oem3g0 ! Code of Conduct http://goo.gl/wOSv2M ! | Maximal & soundnfury's RP-1 Race Into Space Signup: http://bit.ly/2DEVm2i [15:01] <soundnfury> Straight Eight Stronk (and) RP-0/1 is basically "Space Agency Spreadsheet Simulator"
_whitelogger has joined #RO
<soundnfury>
Bornholio: worcestershire
<Bornholio>
its no good if you don't misspell it
<Bornholio>
like benedonk cumberbranch
<Starwaster>
isn't it weird that no matter how someone mispells Bindersnatch Crinklypants that you always know who is actually being talked about?
<soundnfury>
you mean cumberdick bendypatch
<soundnfury>
cumberland bandersnatch
<soundnfury>
benzedrine cabbagepatch
<soundnfury>
bundeswehr kesselslatch
<soundnfury>
basilect campervan
<Bornholio>
yes, yes, maybe, yes
<github>
[RealismOverhaul] lpgagnon opened pull request #1947: Fix gimbal on BDB LR79 (master...patch-1) https://git.io/fpwPH
<Bornholio>
raider nick intends on skipping, as soon as RF has a release i believe
Senshi has joined #RO
egg|zz|egg has joined #RO
<Starwaster>
some things in RF could use some love... minor code fixes and tweaks
<Starwaster>
although NOT directly touching part.mass when you're setting mass deltas is probably not so minor
<Starwaster>
can't believe that's still there, thought I had done something about it but apparently not
oeuf has joined #RO
egg has quit [Ping timeout: 202 seconds]
awang has quit [Ping timeout: 202 seconds]
awang has joined #RO
awang_ has joined #RO
awang has quit [Ping timeout: 200 seconds]
egg|zz|egg has quit [Ping timeout: 183 seconds]
egg|zz|egg has joined #RO
<Starwaster>
This shit drives me crazy...
<Starwaster>
"With respect to units, the LGC was eclectic. Inside the computer we used metric units, at least in the case of powered-flight navigation and guidance. At the operational level NASA, and especially the astronauts, preferred English units. This meant that before being displayed, altitude and altitude-rate (for example) were calculated from the metric state vector maintained by navigation, and then were converted to feet and ft/sec. It would have felt
<Starwaster>
weird to speak of spacecraft altitude in meters, and both thrust and mass were commonly expressed in pounds. Because part of the point of this paper is to show how things were called in this era of spaceflight, I shall usually express quantities in the units that it would have felt natural to use at the time."
<hoglahoo>
tl;dr
_whitelogger has joined #RO
<Starwaster>
hoglahoo tldr: STOP MIXING METRIC AND IMPERIAL
<Starwaster>
better yet let's switch. It'll be easier not having to keep track of two systems in my head
<soundnfury>
well whether you prefer metric or imperial, surely we can at least all agree on one thing
<soundnfury>
a billion is 10¹², long scale rules O.K.
<Pap>
Absolutely should switch to metric
<Pap>
Also, all scientists use metric, we couldn't expect the astronauts to learn metric?
<Pap>
Is there any reason not to shoot for a 1.5 release for RP-1? Is releasing on 1.3.1 still worthwhile?
<soundnfury>
Pap: if we can make a fully-fledged CKANnable RP-1 release on 1.3.1 I think we should just for the sake of having a release out
<soundnfury>
then we can target 1.5 after that
<Pap>
Are we allowed to distribute the .DLL's that we currently have to download manually?
<Pap>
Next question, what if we moved away from CKAN for RP-1 and built a custom installer?
<soundnfury>
dunno. I'm not even sure which ones we need to.
<Pap>
Is it against TOS?
<soundnfury>
well, CKAN's totally unofficial so we should be able to do anything it can
<Pap>
Would it be better to do that to be able to control all of the proper downloads, as well as the proper order of installation?
<soundnfury>
v0v
<Mike`>
no idea if it would be good to create another ckan? doesn't ckan support proper versioned dependencies, and if not, shouldn't that be integrated there?
<Mike`>
never used ckan though
<soundnfury>
ckan is a shitty implementation but does do all the stuff a package manager should (versioned deps etc). Except that it sucks at conflict resolution.
<Pap>
You also cannot specify which exact things to download like you can with a singular installer
<Pap>
Or the order to install
<Pap>
For example, if we distribute the KRASH dll that can turn off Testflight and then distribute through CKAN...
<Pap>
It will not overwrite the file properly
egg|zz|egg has quit [Ping timeout: 180 seconds]
<lamont>
Pap: i think you should just release RP-1 as it is right now on 1.3 and then focus on 1.5
<Pap>
How should we Lamont, through CKAN?
<lamont>
yes
<lamont>
just fucking ship it
<Pap>
All the dependencies are not there
<Pap>
It won't function
<lamont>
ergh
<Pap>
Always the problem with it
<lamont>
wait 1.3 or 1.5?
<Pap>
1.3
<lamont>
still?
<lamont>
i thought everything was in CKAN for 1.3?
<Pap>
We still have to download external .DLL files to make everything work