Lisias

You are ignoring the numbers that you don't like. NO, I CROSSED WIRES!! I ANSWERED THE WRONG GUY! Really sorry, @YNM. I'll pay more attention in the future, my apologies. ------------- The mass you have to kick into space to do the job is meaningless. What's matter is payload and cost. And that's all what matters. As Elon Musk says, "Fuel is cheap. Hardware is expensive". If it's cheaper to kick 120 tons of hardware to get a useful payload of 20, so everybody will kick 120 tons of hardware into space. It's all about money. It's always about money. Its better to spend 450M to put 27tons of hardware and a crew to assemble the damn thing over there, than to do two launches at 322M each to accomplish the same result - no matter how "efficient" is that second solution.

I'm not saying necessarily that government funding is a bad thing. Like everything else, can be a blessing - or a curse! You are getting it completely wrong. There will be never a new B-52 being kicked out of the production line. Every single B-52 that could be possibly be built it's already built. You can refurbish the ones that are salvable, but that's all. The way you say technology is developed is not the only way. I'm describing how technology is developed by the Military, that happened to be also the way NASA used to develop he Space Shuttle Program. The comparison stops there, with me trying to somehow use the known budget from both projects to compare costs - what appears not to be too distant from the other (something that I can't effectively demonstrate because the B-52 budget is not publicly available). The Space Shuttle would be higher if it would be reinvented each 30 years too. But… We choose to ditch the whole concept before having something able to replace it. Space Shuttle was a bad step, as it appears. But shutting it down without a working replacement was another one - and now we have two bad steps to live with. I think you will need to ask them. But I can guess. The payload of the Saturn B is about 21t., more or less the Space Shuttle. But the Space Shuttle could piggyback 27tons of cargo, and also a full crew for working into space - what would need two launches of the Saturn B to accomplish. With a cost of (nowadays USD) 322M per launch, you would spend 644M USD to the a job Space Shuttle does by 450.

In the original arguing, the guy was comparing the Militar Ways, citing the B-52, with the NASA ways (and I cited the Space Shuttle). It was not meant to be a full, definitive history of expenses. What I did is to take the whole program history of the B-52, and did a half baked comparison with the Space Shuttle program - where I could not do properly due lack of public data about the break-down costs from NASA, and the lack of the effective operating costs from Pentagon about the B-52 (ok, we know how much a hour of flying costed, but how many hours the B-52 flew until the moment?). There're a HUGE difference, however, on both projects. NASA built six Space Shuttles (including the prototype). The Military built 745 B-52, and that's the only reason the B-52 is still operational nowadays - they built it in so large numbers that they could store some of them to replace the ones that would reach End Of Life by material fatigue. Every single plane was born with a pre-determined number of flyable hours in his history, and once these hours if used, the plane is ditched and that's it. The amount of stress a spacecraft has to endure both on begin kicked out of the planet and coming back limits a lot the flyable hours of the craft. But yet, some of us are still building it as the Military does: they draw specifications; invite a lot of people to present proposals; pay for the development of some of them; choose the one that is better, given some criteria this guy builds a finite quantity of such crafts then shutdown everything, archive the plans and dismantle the shop you will never be able to built another one This work fine to the Military, because once a project reach its end of life, they need something new from scratch or they will be behind the hypothetical enemies tomorrow. But for a business sustainable space program, we need something more cost effective - as SpaceX, Virgin Galactic and others appears to be doing. For me, it's just natural. They are funded more or less as the Military are. So they have the same bottlenecks (but also same of the benefits - that model works, otherwise it would not being used anymore). By studying the airplanes that the Military created in the past, you will find that sometimes a good idea reveals itself impracticable on the real life. The Valkyrie was one of these projects, they built the best supersonic bomber in history. But then ICBMs came, and nobody needed such a bomber anymore. B1 Lancer "survived" because they found it specially useful on a niche that it was not designed for, but by "luck" succeed there. So it's still used. Things like that also happens on NASA and Space Programs of every nation and private company. But on state funded enterprises, the huge amount of "beneficial side effects" created by such a program could be considered more important that the direct results of the program itself, and then a "bad idea" is kept in use, besides being a bad idea. With the last Space Shuttle disaster, they could not "hide" anymore that it was a bad idea, then it was shutdown. But… By had been shutdown by political decisions instead of technicals ones, they were shutdown prematurely, rendering NASA without a proper replacement. And now the ISS is at risk, because they depends heavily of a single service provider that, well, sometimes fails as anybody else. And eventually will have to shutdown that service, because the competition is mining their incoming. My personal opinion? A bad idea that works is better than a good idea that will work God knows when. The Shuttle Program should had been kept for a few more years, even if by a slower pace. The Space Shuttle was dangerous and inefficient, but it fulfilled a role that are still needed, and currently nobody is able to fulfill. People that needs Hubble wold be happier too. Yes. Because nobody needs a 140t payload nowadays. A Launch is more than the cost of the launching. You need to account the cost of keeping the facilities (fabrics, storage, transportation - the launch pad is just the tip of the iceberg). So, yes. The Space Shuttle can be better than Saturn V due that. If all I need is to kick 20tons to space, it's better to pay 1500USD for kilo for that launch, that paying 1000USD for each kilogram but have to pay 140-20 = 120tons more because I have to pay for the whole thing, not only the tonnage I need.

Without a lot of further studying, we can't tell. Space business are hard, we don't use the term "Rocket Science" for things extremely hard just because. But "pork barrel" is a real issue on state funding companies and foundations, there're not too much arguing about anymore now that we have some decades of history from NASA and AirBus, to stick with entities still alive (the long dead British/Canadian aero and aerospace companies are also full of examples of direct and indirect government interference, see Avro and Arrow).

Do you your own home work. There're plenty of citations on the Google, this is a already vastly known and debated subject. :-) As was said by an eminent SciFy philosopher: "Dave, this conversation can serve no purpose anymore. Goodbye."

https://www.google.com.br/search?safe=off&q=space+shuttle+pork+barrel Never said it was exclusive. :-)

Problem with NASA funding is that, by being funded by politicians, such funding came with a lot of strings attached. To each Congressman vote, there's at least one demand. "I need to bring the pork home" - or something like that, I'm on mobile, hard to search for the right term - but I found a link about. See below. A lot of the Shuttle expenses, for example, are due the pork barrel. In exchanges for the funding, they had to produce things on some sub optimal places, rising costs. But once the alternative is loosing tbe votes, so loosing the funds... https://en.m.wikipedia.org/wiki/Pork_barrel

Not cost effective. The first prototype had a cost of about 1 Billion USD (in nowadays currency). And they made another 2. The first 50 production planes came at a cost of 260M each. As time goes by, the production cost dropped to about 85M each for the last delivered planes in 1963. But it took about 10 years 742 airplanes manufactured to get to his value. So, the total cost of the B-52 program is about: 55.9 BILLION USD in modern currency, what gave us a mean cost of 75M USD for 742 aircrafts manufactured (plus 3 prototypes). But I can't think there're a market for 740 space planes today. (and, by the way, I can't say how much was spent on maintenance and flights because I don't have such numbers). One can argue that the Space Shuttle Program had cost 196 Billion USD (nowadays money) for 30 years service, and here we have the opposite way: we don't have the breakdown of the plane's cost. But we know that each flight had a cost of about 450M. Since we know that there were 135 missions, we have a 135 * 450M = 60750M = 60.7Billion. So we can assume we had a total cost in hardware of 196 - ~60, 136B USD, or about 136/6 = 22B per shuttle - but this includes the Enterprise and support hardware as launch pad. My guessed costs on the B52 doesn't include the pricing of the specialized support equipment neither facilities (as the Shuttle numbers have them embedded), so a direct comparison is difficult. But with the numbers we have, we can infer that the Military would not ha done too much cheaper. Sources: https://en.wikipedia.org/wiki/Boeing_B-52_Stratofortress https://en.wikipedia.org/wiki/Space_Shuttle_program#Program_history https://en.wikipedia.org/wiki/Space_Shuttle#Fleet_history

The sole purpose of this delay on the release is to be sure that you will not be unwilling to tinker after installing it. And with some important mods being updated to 1.5.1 about these days, I intent to test them with the pre-releases before throwing it into the wild. Better safe than sorry.

Heróis com Pé de Barro Parte 1 Prólogo Essa história se passa imediatamente após os eventos ocorridos em O Ouro de KSC Tomo 2. Após tensa rodada de negociações com um personagem obscuro mas de importância estratégica no Salvamento, Tatiana sente que precisa se informar com Eugene sobre o passado deste controverso personagem - o considera um risco para a missão, para si e até para o Kentágono. Kubrak Tatiane: __ Eugene, essa história toda é muito tocante (e estou sendo sincera), mas não explica como alguém do Kentágono ou Kremnlin não derrubou esse cara ainda. Você deixou bem claro que esse maluco é capaz de passar a mão em partes altamente classificadas das Forças Armadas de Kerbin, e também de outros Reinos! E eu lhe garanto que nenhuma destas Forças é estúpida, negligente nem está preocupada com a vida amorosa de ninguém! Eugene: __ Essa informação pode nos custar a vida, e eu não falo dele - esse Kerbal tem orgulho de sua participação nisso, e adoraria poder falar abertamente sobre o assunto. Ele é tudo, menos modesto. Dando um longo suspiro (Estúpido e teimoso), Tatiana vai até o bar, pega uma garrafa de Kourkon já bem além da metade (Krakens, estou transformando todos ao meu redor em ébrios.) e serve dois copos - um para si e silenciosamente oferece outro para Eugene, que silenciosamente aceita. Apreciam o Kourkon por alguns minutos, e então: Tatiana: __ Ok, sem registros e totalmente pessoal. A Comandante acaba de pular a janela e foi Brincar nos Campos do Senhor, sou apenas Tatiana pelos próximos 60 minutos - ou enquanto durar essa garrafa, o que terminar primeiro. Eugene: __ Me conte o que você sabe sobre a Krise de Krubak… Tatiana, entre desconfiada e perplexa, decide jogar com Eugene. Dá um pequeno gole em seu copo, insinua que espera que Eugene faça o mesmo, e quando é obedecida, começa: __ Quase entramos em uma Nova Guerra. Ainda medíamos forças bélicas com Krússia e Kásia nessa época. A Krússia estava bem à frente de todo o resto na Korrida Espacial, e sabemos que quem é capaz de colocar um satélite em órbita, é capaz de deorbitar bombas onde bem entender. Após mais um gole: __ Krússia e Kásia disputavam Krubak para uma plataforma de lançamento de foguetes, mas a posição de Kubrak a fazia estrategicamente perfeita para uso militar - contra nós. De alguma forma, alguém conseguiu montar uma base de lançamento muito bem escondida por lá e, de alguma outra forma, outro alguém descobriu e entregou para todo mundo. Os Reinos Unidos de Kerbin responderam à ameaça, julgávamos que vinha da Krússia. Parou para pensar, deu mais um gole, olhou para o copo de Eugene e em seguida para o próprio Eugene, que entendeu o recado de também bebericou seu copo, e continuou: __ Bom, vinha e não vinha. Kásia conseguiu convencer o então Regente de Krubak à ceder o local para ela - Kásia estava muito atrás de todos nós na Korrida Espacial e queria a posse da base para forçar negociações. Funcionou, pois convenceu Krússia à equipar a base em troca de Snacks, muitos Snacks - algo que sempre fez falta à Krússia, a geografia deles é péssima para a agropecuária. Mas não sabíamos desse arranjo, e fomos pra cima da Krússia com sangue nos olhos quando identificamos a origem de todo aquele equipamento espacial. __ A coisa escalou, porque a Krússia se sentiu agredida injustamente (e com alguma razão - mas eu não disse isso). Kásia ficou calada (como sempre), aquele linha dura do Kladimir já estava no poder e esse Kerbal nunca entrega um aliado. Vivo, ao menos. __ Fizemos um bloqueio naval à Kubrak, que era uma importante fonte alimentar da Krússia. Kladimir interveio, porque o bloqueio estava colocando a segurança alimentar da Krússia em cheque. Após uma pausa, que usou para servir novamente Eugene pois percebera que seu copo já estava vazio: __ Um erro terrível, um erro que havíamos prometido à nós mesmos nunca cometer. Foi a Fome que levou à Grande Guerra, e foram os Snacks que a terminaram. Aquele bloqueio custou muito caro ao Kentágono, estivemos perto de deixar de exi… - calou-se subitamente, essa informação era classificada. Aproveitou a gafe para servir-se também. __ De um jeito ou de outro, enquanto Krússia e nós mostrávamos nossos dentes uns aos outros, um satélite (e nunca soube se nosso ou krusso) detectou radiação de plutonium em Kubrak, e isso deixou todo mundo absolutamente apavorado. Sabemos do tremendo poder potencialmente destrutivo da fissão nuclear - e achar indícios deste poder na mesma área onde fomos informados que haviam construído uma base lançadora de foguetes? Inadmissível! Fez uma pausa para bebericar, e concluiu: __ Krússia aparentemente concordou conosco (e foi aí que descobrimos o envolvimento de Kásia), mas os detalhes disso tudo estão além do meu Nível de Acesso, e o pouco mais que sei está além do seu. Percebeu que Eugene já tinha terminado seu segundo copo, obviamente estava buscando no Kourkon a coragem para falar sobre o assunto. Bom, eu também precisarei de um bocado dessa coragem pensou consigo mesma, terminou seu copo e serviu à ambos mais uma dose. Dupla. Eugene: __ O plutonium foi descoberto por um civil, que prestava serviços para a Kásia. Ele… instrumentou um dos satélites meteorológicos de um cliente e o usou cautelosamente para confirmar a hipótese que ele intuiu ao analisar as possíveis finalidades do equipamento e matéria prima que estava contraban… digo… fornecendo à Krubak. Isso lhe custou um bocado de Fundos. O Kremnlin recebeu, sigilosamente, acesso à este satélite exatamente no auge da Krise, e sob a confirmação desse grave fato confrontou a Kásia por ter colocado em risco a sua segurança alimentar. Duas vezes, porque plutonium e agropecuária não se misturam. Parou para bebericar também, no que Tatiana - já se sentindo mais corajosa, e já sabendo que não precisava se preocupar muito com Níveis de Acessos, Eugene demonstrou conhecer mais do que ela sobre o que estavam falando - emenda: __ Então foi por isso que a Armada do Kremnlin ofereceu trégua poucos minutos depois de se posicionar para começar o que seria a Batalha Naval de uma Era? Eugene confirma silenciosamente com um aceno grave, então beberica ainda uma outra vez. Tatiana se adianta, e lhe completa o copo antes mesmo que Eugene consiga devolvê-lo à mesa. Eugene: __ Alguém de Kásia entrou em pânico, e o que você deve saber mas não pode me dizer é que… MÍSSEIS FORAM LANÇADOS. Fez uma pausa dramática, mas no fundo queria era disfarçar um pouco os efeitos que o Kourkon já estava fazendo. Essa kerballete é de ferro? Ela faria frente à Jeb e Bill, pelo Amor do Kosmos… Eugene: __ Só que, misteriosamente, o combustível sólido usado nos foguetes tinha ISP demais, os equipamentos de processamento e operação não detectaram o problema e esses mísseis acabaram numa órbita de fuga de Kerbin! Calculamos que mergulharam todos em Kerbol, mas só teremos certeza absoluta em alguns anos quando os que eventualmente não o fizeram estiverem próximos o suficiente para serem detectados (ou não!) pelos nossos radares quando nossas órbitas sincronizarem de novo. __ Não explodiu nenhum, pois isso nós do KSC teríamos detectado. E sim, estamos monitorando. Também. Tatiana: __ E como você sabe disso tudo? - perguntou, mas já intuindo que sabia a resposta… Eugene: __ Eu tenho o privilégio de ter sido amigo do mercador negro que forneceu à Kubrak a matéria prima deste combustível sólido, bem como o equipamento que foi usado no processamento do plutonium. E que também chuta um satélite ou outro para a órbita de Kerbin quando está entediado… - disse Eugene, sorrindo com orgulho genuíno. Tatiana: __ Esse cara, definitivamente, tem uma boa chance comigo! - exclamou Tatiana, desfazendo parte do sorriso de Eugene. Após uma ainda outra pausa, onde apreciam o Kourkon e refletem no que os aguardam nos dias seguintes… __ Gene, você têm um foguete de mil e quinhentas toneladas para chutaraté Mün e não tem partes para a tarefa, e eu tenho que controlar um mercador negro que mete o bedelho em crises nucleares internacionais e é o único capaz de fornecer tais partes, possivelmente roubadas do meu chefe - e de outros chefes por Kerbin inteira. E nenhum deles recebem muito bem a notícia de que foram roubados… Vai até o bar, pega uma garrafa ainda lacrada de Kourkon, e completa enquanto volta: __ Ambos precisamos de uma boa companhia para uma boa bebida - e nenhum de nós pode correr o risco de abrir o bico com mais ninguém. Que os Krakens carreguem a Hierarquia e os Níveis de Acesso, eu sugiro que fique. O que me diz? Eugene nem cogita em questionar o que considerou um magnífico silogismo. Ela tem seus momentos. [prev]—[top]—[next]

Bom, parece que a culpa do meu lançador ter ruído sob seu próprio peso não foi (apenas) minha. Eu brinquei com RealFuels, me arrependi, e troquei pelo ModularFuelSwitch. Neste meio tempo, percebi o TweakScale lançar um bocado de exceções sobre o B9, o que não estava acontecendo antes (bem como duas sobre as "Partes" que Squad usa para os Kerbals fazerem EVA). Bom… Acabou que 'herdei' o TweakScale nessa história, e então minha carga de trabalho para o curto prazo aumentou sensivelmente Isso vai adiar um pouco a construção dessa nave (aliás, o seu conserto porque ela funcionou um dia), mas por outro lado, seja lá o que for que precise ser consertado, será para todo mundo. Para não deixar essa thread muito tempo sem novidade, eu reorganizei a Prequel da Kavalgada para que um dos capítulos virasse um ShortHistory próprio, daqueles que complementam a história à que pertencem mas são legíveis por si só. Bem Asimov, por sinal. Em breve, num browser perto de você.

ANNOUNCE Pre Release 2.4.0.3 available for testing, see OP for links. I think I nailed the last mishap on the packaging - the code appears to be working fine on my KSP installments. I plan to spend the Saturday retesting on a clean KSP (just in case) and to properly publish the thing Saturday Night.

You should be making comparisons with unmodded KSPs first. Using modded installs, you are comparing mods, not just KSP. and since such mods are unlikely to be all "certified" for 1.5, the performance hit can be due exceptions being thrown regularly. It essentially what happens when I mess up on mods I change.

Às vezes, eu tenho dias bons. Outras vezes, dias ruins. Algumas outras, dias como este: Rapaz, tá na hora de reavaliar minhas opções...

Sometimes, I have good days. Sometimes, I have bad days. Sometimes, I have THESE DAYS: I think I need to rethink some things...

From my point of view, it's the other way around: It's TweakScale that didn't caused trouble for CKAN users. CKAN is a Mailer. It deliver packages, it's not up to them to guarantee anything but the package integrity. The package is a bomb? Well, CKAN will deliver a bomb. Unless they take for themselves the burden of curating every mod to guarantee it's not a bomb, the responsibility for the bomb is over the sender's shoulders, not the mailer's.

Meddling with Module Manager and Hide Empty Tech Nodes, I understand how they handle customized Tech Trees. On the fly, in the case of HETN. The same technique appears to be applicable on parts list - obviously, this info is to be confirmed. However... There're risks on such endeavor. I found that it's currently common practice to "hijack" the TechTree unconditionally, what ends up in a race condition where the TechTree currently in use is determined by the not necessarily deterministic order in which such "hijacks" happen. I'm foreseeing the same happening here. I think we will need an Arbitrator for customs Parts List. I think we already need one for TechTrees...

Not to mention the impact on fauna and flora.

I'm not an enthusiastic user of CKAN, mainly because the Mono defaults are a mess on Linux and Mac, and I'm a heavy user of these OS'es. I was also bitten heavily when a bunch of mods were automatically updated, but one of them caused undesired behaviour and it took me an awful amount of time to figure out what happened. Doing things by hand revealed to be a better solution for me, with me relying on KSP-AVC to keep me informed about updates. That said, I will not drop CKAN support on Releases, but pre-releases (the present state) and experimental will not be CKAN'd (neither published on SpaceDock and Curseforge) for obvious reasons.

Curiously, I thought on something like that recently. But I consider this to be "tricky" to implement as it would break an (programming) interface that are in use for years. OK, there're techniques to make things coexist, but we need to balance cost and benefits of such a feature. The "easier" changes on the programming interface would render the user interface less intuitive, and vice versa.

TL;DR : Yes, you can. At least until someone else says you don't. Technically, to the strictest letter or law, by using "KSP" and "Kerbal Space Program" - registered trademarks and copyrights from Squad/TTI , you would doing so under "fair use" (in USA - you need to check if your country has something like that). Fair Use, however, is a claim - you claim you are using it under fair use, and pay to see if anyone disagrees. It's usually said that Fair Use it's something you only is sure you have after a judge says so on a trial. That said, as long you don't claim any representation or association with TTI neither Squad, and make very clear that your Discord server is a Fan Work without any authorization or association with them, I don't think you will have a problem - as long your Work don't cause demeaning on their trademark or copyright - for example. you start to publish Kerbal p0rn on the channel. Keep in mind, however, that you are on "private land" and can be ordered to rename the channel (and/or stop using any copyrighted and trademarked material of them) at any time. It's a right they have, and if they choose not to exercise such right, it's not meaning they waved that right in any way.

Just to clarify some things: There're TWO development branches on the repository: the orthodox and the heterodox. All bug fixes and "safe" development are done on the orthodox, and this branch is the only one that can be promoted to master now and then. The heterodox branch is where we can play with nitroglycerine without killing the neighbours. We can discuss and even implement some ideas on there just to see what happens - the worst it can happens is to ditch the code. This branch will be never merged back to the orthodox one. If the event an idea proves valid and worths the potential migraine of becoming mainstream, the changes will be cherry-picked and eyeballed prior being committed into the production safe branch. On the other hand, every change on the orthodox is merged to heterodox, so it keeps synchronized with the status quo. This broke something on heterodox? Too bad: fix it or ditch it. I didn't mentioned Dante's Inferno just because. So… Yeah.We can go wild on new ideas and even try an implementation on the heterodox branch without opening the gates of hell into us. Note to myself: Implement a very scary warning to be issued every time you enter Space Center on the heterodox branch.

"What could possible go wrong?"

Ouch, man… Let me tell you, I'm staying with Sierra until this machine dies. I found High Sierra unusable and I don't have the slimmest will to try Mojave. =/ Open GL is deprecated on Mojave.

There're new attributes on KSP 1.5 (on the gears, for example) that will need to be handled or stuff will be blown into orbit against your will. I think (but I still need to correctly study the problem) that some issues on 1.4 are due the same. The first step, probably, is to read cautiously every KSP's Change Log from 1.3.1 to 1.5.