<Raidernick>
SirKeplan, is there any particular reason why realfuels is showing the ASL thrust in the editor now
<Raidernick>
instead of vac
<Raidernick>
it's stupid and confusing
<SirKeplan>
Raidernick: i don't know why, it is really annoying yeah
<Raidernick>
when did that start happening
<SirKeplan>
with 1.2
<Raidernick>
is it a ksp change?
<SirKeplan>
KSP 1.2
<SirKeplan>
i don't know
<Raidernick>
is there no way to fix it?
<Raidernick>
does nathkell know about it?
<SirKeplan>
don't know, i have mentioned it in here before
<Raidernick>
is there anyone else who works on realfuels that can look into it besides nathan
blowfish has quit [Quit: Leaving]
<Raidernick>
if it is a stock behavior we may be able to override it
<SirKeplan>
probably open an issue on the github.
<Starwaster>
KSP 1.2? Not 1.2.2?
<SirKeplan>
probably 1.2.2
<SirKeplan>
yeah
<Starwaster>
even if that can be confirmed, it's not getting fixed. Not unless someone has a KSP 1.2 compatible branch around that they could make changes in
<Starwaster>
meaning I don't think the current branch is compatible
<SirKeplan>
honestly i don't know pecisely when it changed but on KSP 1.1.* it was ok
<SirKeplan>
this sets the EngineThermodynamics to atmo conditions before reading the thrust.
<blowfish>
SirKeplan: yeah, that should probably be vacuum
<SirKeplan>
blowfish: yeah that what it used to be according to github blame :P
<blowfish>
or wait, actually that line should just be removed
<SirKeplan>
what was it trying to fix?
<blowfish>
changes in SolverEngines API
<blowfish>
but clearly I did it wrong
<SirKeplan>
ah
<SirKeplan>
oh i see that gets set to standardconditions earlier too
<SirKeplan>
so simply removing the line fixes it?
<SirKeplan>
can't break anything....
<blowfish>
I'm going to implement a real fix which is creating a method to get vacuum conditions in SolverEngines
<SirKeplan>
Ok, cool
<blowfish>
I think it's about time for a release of both anyway
szyzyg has quit [Quit: Leaving.]
<Starwaster>
blowfish, not quite yet please
<Starwaster>
still trying to iron out some boiloff-analytic bugs
<blowfish>
cool, no worries
Wetmelon has joined #RO
<Starwaster>
blowfish wouldnt mind another set of eyes on that either. It's something stupid-simple but I can't seem to find it. When CalculateTankLossFunction() is called in analytic mode it's not actually resulting in mass or flux being lost
<Starwaster>
changes are already pushed
<Starwaster>
oops crap, might also have some debug spam so definitely dont update with THAT :P
<Starwaster>
btw, white corn popcorn + coconut oil + salt + curry powder = yum
Hohman has quit [Quit: ChatZilla 0.9.93 [Firefox 52.0.2/20170323105023]]
szyzyg has joined #RO
regex has joined #RO
szyzyg has quit [Quit: Leaving.]
szyzyg has joined #RO
szyzyg has quit [Quit: Leaving.]
<xShadowx>
zilti: both OS have ups and downs, in the end though ram is cheap and cpu is what matters at bottleneck time, from testing i usually get roughluy 20% higher part count on windows
<xShadowx>
granted not a huge indepth test though
BadRocketsCo has quit [Ping timeout: 200 seconds]
<waerloga>
originally I did ksp on linux because 1: it's my primary os anyway, 2: when I started, win was 32bit only and ram was hard limited to not quite 4GB for the game :P
<xShadowx>
i used win32 for my entire play until 1.1 brought 64 :D all that manually pruning files to fi stuff, but then i cheated, 2 installs, 1) all the parts for VAB only play > save craft > put caft file into 2nd install 2) RSS and all the goodies, only tjhe parts used in currently active craft
<waerloga>
heh
* xShadowx
is happy those days are over
Aepelzen has joined #RO
<Aepelzen>
hey guys
<Aepelzen>
my orbit lines in map views are flickering weirdly, is there a way to fix that?
<Aepelzen>
ksp 1.2.2 on linux btw
<regex>
Can RO 1.2.2 work without Test Flight?
<zilti>
Aepelzen: Only the orbit lines?
<Aepelzen>
yes
<Aepelzen>
they are jumping around, like sometimes when ksp can't decide between 2 predictions for orbits (on encounters for example)
<zilti>
Ah, like that. Hmm, I never had that...
<Aepelzen>
i am also getting spam of nullReferenceExceptions, not sure if that is related
<xShadowx>
engines will be fakey and never fail without TF
<xShadowx>
to me that isnt RO
<Agathorn>
which is why it is listed as a requirement but you can physically run without, it won't cause errors to do so
<xShadowx>
i think any mod in RO can be taken out, and still works? i mean sure RSS needs kopernicus, some mods need mods, without em the concept of RO wouldnt be ther, but almost everything is fairly standalone as far as being able to run ksp without errors
<regex>
Can you guys fuck off and answer the question seriously?
<xShadowx>
he did
<regex>
or just shut the fuck up?
<regex>
so it's a requirement, thank you.
<xShadowx>
[10:47:55] <@Agathorn> but seriously , yes it can
<regex>
okay, great, thanks.
<Agathorn>
regex it is marked as required for gameplay reasons but on a technical level you CAN run without it
<regex>
thank you
<Agathorn>
it won't cause errors to do so
<Agathorn>
well nothing breaking anyway, maybe some benign config errors
<regex>
is there any way in-game, in sandbox, to tweak engine running times?
<Agathorn>
not really because it is controlled by configs. You can, in the TF options set everything to be max reliability if you want but the run times would still be the same
<xShadowx>
tweaking fuel load / how fast it uses fuel, else no
<Agathorn>
now you could probably with a simple patch make the runtimes longer, or even enable some of the more advanced features RO doesn't use such as engine cool downs, or burntime based on throttle
BadRocketsCo has quit [Ping timeout: 383 seconds]
<Agathorn>
apparently it isn't realistic, but TF has the ability for example to reduce the burn time used when an engine is shut down, EG between coasts. RO just doesn't use that feature
<Agathorn>
you can also make it so that an engine at say 50% throttle only accrues burntime at 50% of the normal
<Agathorn>
or go completely unrealstic and make it so that at 100% throttle it only accrues at .1% of normal :p
<Agathorn>
but the actual rated burn times are config so don't change..just how that time is accrued or decayed is - not sure if that makes sense
<regex>
Just wondering, that's not really how my headcanon workls when I play. None of Test Flight really bothers me, I found it pretty intriguing, but I'm building fantasy rockets.
<regex>
Also not playing progression anymore.
<Agathorn>
we tried to mak the burn times be a bit longer than real life to not force replicas, but yeah I can see it being a restriction
<Agathorn>
I haven't really looked at my code in ages, but it might be easy to add an option to igniore burn times
<regex>
I could say something like "I'll take a look at it during my project time and add the feature I want" but I know that's 99% not likely to happen.
<Agathorn>
Just like I could say the same :D
<Agathorn>
I'd like to be accomdating but i'm really stuck in a maintenence mode at the moment..almost forced into it by just not having touched the code in so long I'm afraid to break it
<regex>
Oh dude, I'm in your corner. Burn out is a real thing.
<Agathorn>
I couldn't even get RSSTimeFormatter recompiled this weekend without Xamarin thwing weird errors at me
<Agathorn>
Everytime I try to get back into KSP something makes me mad and I jst don't bother heh. So I try not to abondon you guys completely but adding new features is just not high on my list right now sorry
<Agathorn>
too busy working on my own game, and my novel at the same time
Wetmelon has quit [Ping timeout: 180 seconds]
<zilti>
Huh, what does xamarin have to do with KSP?
Senshi has quit [Quit: Leaving.]
Thomas is now known as Thomas|AWAY
<regex>
zilti: Xamarin is an IDE for C#, I used it when I modded too.
<zilti>
regex: ah, I see. I'm more of a JVM guy, so I assumed xamarin was just that mobile stuff
diomedea has quit [Quit: Bye!]
<Agathorn>
MonoDevelop that comes with Unity is just a dumbed down Xamarin actually
<Agathorn>
On Mac I prefer using Xamarin straight up - though it was a lot better before MS got their hooks into it
Hohman has joined #RO
<zilti>
Agathorn: stuff like this is why I try to stay away as far as possible from MS stuff. They try to "improve" stuff, they try to control everything you do.