Lisias

Multiplayer é complicado porque as pessoas precisam jogar todas ao mesmo tempo, e pelo menos eu sou um que nunca tenho mais de 30 minutos de uma vez pra brincar. O KSP às vezes fica ligado o dia inteiro em pausa, e eu volto lá umas duas ou três vezes pra uns 15 ou 20 minutos de missão. Já sobre jogos mutliplayer… Não tem jeito. Pessoas diferentes se divertem de forma diferente. Eu sou zoeiro, me divertia mais dado razante em vôo invertido num 747 nas pistas de pouso nos meus tempos de Flight Simulator que voando de cidade em cidade. Uma vez pousei o 747 num porta-aviões - só não consigo lembrar qual foi o simulador (crashei, óbvio, as asas bateram na torre). Já meus amigos eram "sérios", um fazia as vezes de ATC e ficava no chat do jogo ordenando os poucos e decolagens. Adivinha quem não se continha e dava "Mayday, Mayday, Mayday" no pior momento possível?? Então as regras precisam ser definidas de antemão - e o código do jogo precisa "enforce-them" à ferro é fogo. O que é um dos trampos mais chatos de fazer num jogo, então quase ninguém faz. Se o Luna não fizer algo assim, vai se estrepar igual ao Dark.

Isso me deu algumas idéias… Que bom que hoje é sexta, hoje de noite (se o TwekScale deixar… hehehe) vou testar umas maluquices aqui do meu lado do cable modem.

And now for something slightly newer.

Been there, done that. But I got "lucky", and solved it the only way it works. I quit. She (as me at the time) got into a terribly nasty situation: responsibility without authority. Having some training on PMBOK, I quickly recognized what your wife needed to learnt the hard way and knowing the aftermath in advance, I turned the table and did it at my least inconvenience, not their best convenience. This is a loose-loose situation, there's nothing your wife could had done that would had prevented this outcome. On the bright side, your wife did the second best thing about the issue: she stood her ground and got fired by trying to do the right thing. As the word spreads, this eventually will caught the attention of someone that knows the trade. Once your current job is going down, you need to work thinking on your next one. Good managers pave the way for their led ones. Bad managers pave the way for themselves. These guys are social climbers, they need to manage every little aspect of the work so they can claim the merit for themselves. She was framed. Bad management uses the feedback process to pinpoint dissidents and punish them. This company is over, you get what you promote - no one will ever try to ask for help about anything on that sheet perforation again. The message was crystal clear. On the bad side, once that nice piece of used paper starts to hit the turbofan, she will be blamed for it for some time. There's not much anyone can do about, as trying to fight this, in my experience, usually lead to worst results. It's better to let them badmouth you on something that you did right (as it eventually will be realized), instead of defending yourself and taking the risk of the offenders looking for something that you may had be done wrongly on the past, and using it instead. And since everybody make mistakes, they will find something. It's the reason the best line of action when you detect this loose-loose situation is to just leave, the fastest you can. It's the only way they manage to "outperform" the "competition" - by getting rid of them until no one better stands. I will refrain on further commenting on this matter, as Forum rules forbids political discussions here. In a way or another, the Company will face some really harsh problems in the near future. Boeing style. if by some reason this company works on something that involves Public Safety (transport, mining, construction, etc), find a lawyer and take some precautions on the matter as soon you can. I'm serious - better safe than sorry. These situations usually leave a foul taste on the mouth. I got a serious burn-out, took me almost an year to be fully recovered. Of course, money talks and from the professional point of view, it's better to be hired for some time when the bullets start to fly on the previous job on a Witch Hunt. This will shield her, as the current coworkers, by knowing her for some time by then, will be able to detect the badmouthing and the reasons behind it. If they are smart enough (and wants to), they can use it to steal some clients from her former employers by diligently (but discretely) informing the clients that some of the people that were there when things worked fine now work for them. It works. I see this happening all the time. And this explains why the youngsters on management needed to get rid of her. She was the one risking getting into higher management as time passes, not them. It's, really, an impression. The problem is a bit worse. Somehow, we, as a Society, are allowing a cast of people to weaponize social behaviour against other people as a way to get what they want. It's, effectively, a new cast - as only them are allowed to use such weapons.

These ones are warnings. There're some parts that doesn't have TweakScale installed (to tell you the true, TweakScale uninstall itself from the part) for lack of proper support, so these parts are not scalable yet. The Engine Plates and Tubes have a thing called ModuleVariantPart with mass, and TweakScale chokes with the mass, so TweakScale removes itself from the part to prevent problems. There are a few other parts from other Add'Ons with similar problems - all of them safe to be used, however without TweakScale support. Yet. These parts will be supported on the 2.4.4.x series. These small annoyances are useful because as people get here with logs like yours, I can look and then priorize the parts that need to be worked first. These 9 ones are from Making History (if memory serves me well), and yeah, will be the first ones to be tacked down.

Now I understand! The transparency is done using the same technique used by the Interior Overlay!

The Barn! That would be something I would throw some money into! Specifically on a career mode starting from the very first rocketing experiments!

I would throw some money on The Barn. Hell of an idea, I would like to start an Career that way

"My SeQueL... It's full of bug-reports!"

Thanks for the heads up! I just fixed it. But this time, I'm innocent! Bitbucket had problems last night with GIT LFS, that is something not too unrelated to github's way of storing attachments. I wonder if something similar happened to github? I clearly remember **NOT CLOSING** the page while uploading (yeah, learnt it the hard way). Interestingly, imgur had just failed on me too. The damned thing unlogged me after posting this image and it's refusing my logins. [edit: And then I asked for a new password, got the email, clicked on the link and imgur page's appaers WITH ME LOOGED. Whatahell???] Well… one more step on the check list - be sure the github download is okey. https://imgur.com/a/Px4d19o

Announce. Minor Release 2.4.3.3 is on the wild. Just some typos fixed and added support for the new Cryo Engines from Nertea's. 2019-0814: 2.4.3.3 (Lisias) for KSP >= 1.4.1 Added support for hot-fixes - handcrafted patches to brute force a correct path when the normal way is not possible - as when an unmaintained ARR Add'On is involved on the mess. New hot fix for CxAerospace:Station Parts breaking Bluedog_DB. Links on the OP. CurseForce and Spacedock will be updated on the Weekend. — — News — — TweakScale 2.4.3.3 know recognizes and keep track of HOT FIXES. A Hot Fix is a hand crafted patch that fixes by brute force patching problems, forcing the original intended result for a given KSP installment. The difference from an overrule is that Hot Fixes don't break compatibility with sane installments, so you can start new savegames and share your crafts without worries. However, a Hot Fix is highly specialized to a given situation, and there're no guarantees that it will behave correctly as the affected Add'Ons are updated by the maintainers. So, a pesky Advise will popup when Hot Fixes are detected to prevent you from forgetting a old Hot Fix on your installments. In an ideal World, Overrules and HotFixes would not be necessary. These are temporary workarounds to keep KSP installments sane enough to keep going. Apply Hot-Fixes or Overrules only when recommended by me, LisiasT. It's ok to reach me asking about if you think it will help you, but please confirm with me first. These things can cause as much damage as they can fix them. Each Hot Fix will have an URL associated pinpointing to the Post where the problem were detected and fixed for traceability.

Hi, @cxg2827. Some people are still using your Add'On (and it's pretty easy to see why - if we manage to reach an agreement about what follows, I'll be another one! Excellent work!), but we are now facing some issues and I will need your help on it. Your patches were made for an environment where only you would be using parts you authored. With your decision of allowing some hand picked Authors to use them, your TweakScale patches (I'm the current maintainer of TweakScale, by the way) are being applied on some other Add'Ons by accident, as you can see on this post on TweakScale's thread. Would you consider a new maintenance release of your Add'On with the MM patches fixed? The best solution for the problem is, indeed, a new release of CxAerospace with the patches fixed, and may I suggest using also :FOR[CxAerospace] (and :NEEDS[<dependency>] where applicable)? We could check for any problems with the others Add'Ons and fix them too - so people that are still running savegames with your Add'On could keep going on. I'll gladly help on anything you need. No strings attached. Cheers!

Neither do I. I know perfectly how is to lose months of game play. I know people that runs the same one for years. It's the reason I try hard to prevent the breakage, and once I fail on that (being my fault or not), I try harder to make patches to keep things going. That said, I'm sorry for not being able to respond faster - to you or anyone else, including on GitHub. Old Farts like me have old fart's problems, and sometimes all of them decide to gather up and pay a visit at the same time! oh well. Don't be shy to kick me here or in PVT if you think I forgot you. It will eventually be true! . Need to go now. Still at work! — — back from the dungeons — — @Starman17 - I did a second analysis on your KSP.log and realized I missed some details. I found the problem. [LOG 2019-08-07 18:35:01.895] Applying update CxAerospace/Station Parts/MM_configs/CXA_TweakScale/@PART[*]:HAS[#author[cxg2827]:HAS[!MODULE[ModuleCommand]]]:AFTER[CxAerospace] to Bluedog_DB/Parts/APAS/CXA_APAS_A_L04F.cfg/PART It's CxAerospace. The double patching is happening for sure: @PART[*]:HAS[#author[cxg2827]:HAS[!MODULE[ModuleCommand]]]:AFTER[CxAerospace] { %MODULE[TweakScale] { type = free } } Do you see the "type = free" thingy? There's no "%" in it. So the "type" is being added (instead of edited) to any part that has "cxg2827" as the author and does not have ModuleComand. Guess what? The parts in Bluedog that where double patched has "cxg2827" on the author and does not have ModuleCommand. This patch is somewhat insecure as it appears. It doesn't even check for the TweakScale being available (:NEEDS[TweakScale]) before applying the patch. It probably had worked at that time, but nowadays things changed - there are more than one Add'On using "cxg2827" in the author, this should not be used anymore as criteria. From the Add'On's thread, I learnt that CxAerospace was discontinued, is unmaintained and the license is ARR. Well, there's nothing I can do fix the problem directly, as one could call me in copyright infringement by distributing a derivative - I checked the package, and the config files were not exempted from the copyright claim or double licensed. It was mentioned that the Author decided to give the assets to some other Add'On authors to be used at their discretion, so perhaps this is the reason Bluedog was caught in the crossfire. So, I advise to you: Check if your flying crafts are using CxAerospace . If not, delete this Add'On. I say this with a broken heart, this is a very nice looking Add'On, sir - perhaps the Author would accept fixes for a new release? No strings attached. Reach Bluedog's Author and ask him to help on the matter. He's using cx2827 parts, so perhaps he is one of the guys mentioned above, and so authorized to act on it. In the mean time, I'm cooking a OVERRULE HOTFIX patch that will fix your installment by brute force. Keep in mind that this patch is good only for your current installment. I don't foresee problems if you install or delete some Add'Ons from your installment (except Bluedog_DB, of course), but yet… Don't thrust it too much, use S.A.V.E.. . — — Hot Fix — — @Starman17, I have a (hopefully) temporary workaround for you. Analysing the patches, I'm sufficiently sure that I know how the intended ending results. So I cooked a brute force patch that will shove the correct results on the offended parts. This will keep your KSP installment sane while a proper fix is not applied on the right place. Download and install TweakScale 2.4.3.3 (see OP), and then copy the following file(s) from the distribution package: Extras/TweakScale/HotFixes/CxAerospace--Bluedog_DB.cfg into your GameData. I strongly advise to use the following directory (create it if needed): So the patches will survive updates and will be easily found when the time to delete them come. I tried to make the patch the more safe I could, but as always, I recommend to use S.A.V.E.

Excellent point. I didn't verified the facts by myself and commented based on what was told to me.

I say keep walking. And let's see how it works. Historically, Add'Os developed by Squad's staff are more polished, and better copes to the KSP API (for obvious reasons). However, on the long run, some of the Add'Ons can be leaved behind due day-work pressures (see Firespitter). My advise is to do not try to be better than the other guy. Just be yourself, do what you think is right and see what happens. You will bork eventually (more frequently while you are getting your feet wet on the thing), so use Beta releases and call for feedback before releasing the thing as stable on CKAN or something.

Today I have to write a Spacecraft Accident Report. Tough times for L Aerospace/KSP Division! Do you remember the Maiden Flight for the Kermas/Sub-Orbital Space Tourism Vehicle? Well, the tourism business are tough. The craft need to be fully recoverable, including the boosters, in order to keep the business profitable and securing the revenue for the development of the Kermas family of Spacecrafts. So recoverable boosters were developed. But things didn't worked out very well with the new boosters! Kermas Sub-Orbital Space Tourism Vehicle :: Fully Recoverable Boosters Spacecraft Accident Report Synopsys A Kermas Sub-Orbital Space Tourism Vehicle, currently in development by L Aerospace, also the only operator and identified by Karmas/SOSTV-01, suffered a major incident at KSC, Year 1, Day 7, 00:10:35 UGT (Universal Game Time). The purpose of the flight was to transport tourists above Kerbin's Karman Line, into the verge of the Sideral Space, for a few minutes of amusement and joy. Departure from KSC was at 00:09 UTG. When the spacecraft took off and tried to keep level flight in preparation for the main boosters ignition, the spacecraft dived violently into the sea, severing large parts of the vessel. Full report can be found here, or clicking on the screenshots.

Unfortunately, and by reasons he choose to share to no one known by me (including me), SpannerMonkey choose to retire from the scene, as well to take down all of this SM series of Add'Ons. I believe that initially this was not his intention, but events beyond his control forced his hand leading him to withdrawn all the (known) downloads of the mentioned Add'Ons some time after the retirement. There're no way, at the moment, to legally redistribute any package from the SM Industries that are not yet available on Github or Spacedock. I ask you to exercise your discretion on the matter. I suggest you to carefully backup any copies you have, and to remember that SpannerMonkey are the only legal source of the packages (salvo some exceptional rights current users have, all of them out of the scope of this forum). Believe me, I'm so sad as you about this - perhaps more. They had some great parts to play with. But still, I'm glad I had the chance to play with them. Thanks, @SpannerMonkey(smce). You gave us some great time.

Obligatory mention. Who would say it's the Schrodinger's cat music?

Because we limited the possible outcomes to two: or the cat is alive, or the cat is dead. Both are the predestined outcomes of the cat inside the box. Since the box is closed and its inside is unobservable, at a given instant, the can be alive or can be dead - and by practical meanings, they can be both. The cat is inside the box, out of our reach. But this doesn't means that the cat is, effectively, dead and alive at the same time. It's just means that for us, outside of the box, it doesn't really matter - as long we don't open the box.

Son is cooking today. Caught him listening to this. Damn, I was a kid last time I heard this!

That's the point. It's impossible to know. So if you ask about it, the only logical answer is "no".

This is the first of the Kermas family of small space vehicles. As L Aerospace needs money to fund the development, the first model available to the public is the Sub-Orbital, aimed to space tourism. Full (short) history by clicking on the pictures.

Yep. However, TweakScale is not doing the :FOR yet, and I can't shove it now due the breakage it did with a lot of Add'Ons. Since my guess that that Author choose to use :FINAL on their patches.

To tell you the true, I think that the guy did that due TweakScale patches being outdated. TweakScale should be using :FOR, so the guy could use :AFTER. (But by adding :FOR now on TweakScale, a huge amount of Add'Ons on the wild bork relentlessly (yes, I tried that on test bed) - so I'm paving the way before putting that on mainstream.) So I'm wondering he did that to be sure his patches prevails over the TweakScale's ones. I never tried using :AFTER on something that doesn't have the :FOR - so I can't tell if what he did was, indeed, the best way out of the mess. But at least, it's working for now.

It's a wild guess, but something that happened to me is that KSP on 1.7 series are more VRAM hungry. My MacPotato has about 384Mb of VRAM, and it was enough for 1.4. I was using texture quality at 1x. By installing Add'Ons, demanding more VRAM, I ended up settling with 2x. With 1.7, I'm using 4x and almost considering going to 8x. What happens is that when you exhaust your VRAM, the GPU starts to fetch textures from the CPU's RAM through the PCIe bus, and this is way slower than fetching them from the GPU's VRAM. It's like loading files from the USB's pendrive and not from your hard disk - you end up loading the file, but gosh.. It's slower.