Lisias

It's easy, but somewhat worksome without Unity. Using Blender, you need to setup a vertex for each Kerbal seat (this is the vertex that will be used by the InternalSeat module in the internal cfg - do not misunderstand it with with the Seat_Passenger prop!). It's easier to do that using an already known Part as basis. Check what I'm doing here: https://github.com/net-lisias-ksp/mkext/tree/dev/Mk1/Spaces/mk1CabinInternal (in special, the blend and the cfg file for the mk1CabinEconomicInternal). It's not that hard, besides I'm currently having my cheeks being mercilessly bashed by the internal cameras (that are also set on vertices in the mu model, but by some reason they are screwed in my model besides I'm trying to mimicking the original).

Worst, they do it blatantly ignoring evidences, real life evidences (almost proves) that they are wrong.

For sure. But he have the will? This dude is not stupid - he have a plan, a long term plan, on everything he does. How footing the money for KSP2 development would fit on it? Elon is not only a dreamer, he's a maker (an incredibly rare combination). He makes things happen (at least, some of them - and it's incredibly entertaining while he fails his way into success!! most of the time, at least). But he does that with a purpose. I suggest a thought experiment: let's pretend we are like traveling salesman, and we just knocked Elon's door trying to selling him encyclopaedias KSP2. Incredibly surprising, he attended the door and is listening. How we should try to sell him this thing?

There're alternatives, field proven and demonstrably effective. And, perhaps, their best shot at this point. Disclaimer: I'm not implying it will be easy, neither that it doesn't have it's share of risks - Open Source is a development model, not a panacea that will fix all the illness in the World.

Speaking frankly... None of the alleged problems was a deal breaker for me, no matter how bad they looked. I'm a seasoned software developer, and more than once I did things similar - delivered alpha versions of the software absolutely terribly looking, but with things done right under the bonnet (at that time, I was still believing they are coding everything from scratch), and then adding the bells and whistles at the last moment on the last beta, when only small visual glitches would be needed to be fixed because the internal mechanics were ironed out already. The only real red alert was the pricing: this is not how you do Early Access, this is not how you reward your user base for doing free work for you (beta testing and development feedback). This was the deal breaker for me: if it looks as a scam, smells like a scam and behaves like a scam, it should be a scam - or at least, something pretty near one. Things slowly and gradually starting to fall in their place as the patches were applied only reassured me I was initially right: the thing was rushed into the wild by a management decision - what hinted the project was risking getting doomed (or already being) by mismanagement. The game being dumbed down was a show stopper for me for sure, but it didn't meant that the game would be a failure - it only meant I would not buy it. There're good things on KSP2, there're real improvements over the sequel - they could had succeed under a saner environment (even if by delivering a game I would not like - I would not be their only customer, after all).

No. They are "torts" (civil wrongs). They are the things you are accused when you crash your car into another, for example. If you prove that you wasn't negligent, incompetent or imprudent on the crash (for example, someone else hit you, made you lose the control, and then you crashed into another car), you will walk. Except that it's not a product, it's a service. Check the EULA. You can't have it both ways. They advertised a Service, not a Product (again, check the EULA). In a way or another, I explicitly mentioned FTC for the Customers as I already had stated that the share holders would be the ones with a (somewhat) solid case in a lawsuit, not the customers. FTC is the way to go by the customers. The FTC's mission is to protect "the public from deceptive or unfair business practices and from unfair methods of competition through law enforcement, advocacy, research, and education." . Launching a terrible, unfinished service (remember the EULA) to earn some extra bucks besides knowing the service is unfit to use may be a good cause for a lawsuit by the FTC. Again, winning it it's another history.

The best thing I can say from KSP2 is also the worst. The launch. Boy, they got a huge amount of interest, the Steam Charts skyrocketed. Had the launch be successful, they would had eclipsed the prequel easily. They proved there was a demand for the game.

Not necessarily. There're three Civil Responsibilities you can get sued on a Court of Law for failing them: Imprudence Negligence Inexperience Incompetence And we have evidences that TT2 was responsible for Negligence by failing look out PD, and PD was responsible for Inexperience Incompetence or Imprudence while carrying on their duties. But these faults are towards the share holders, not the customers. From the Customer's point of view, they may be liable by the FTC if they fails to deliver something until the end of the month that could reasonably fulfill the promises they openly made about the product. On Europe, they surely are liable for failing to deliver a reasonably working product that would match the expectations generated by the Marketing- it's the reason Steam is granting refunds to the Europeans, they think it's cheaper to refund than risking a class suit in Europe. There're grounds for trying a lawsuit for sure. Winning it, on USA are least, it's a completely different problem.

Boeing 767X . They literally took a 747, inverted the X axis and replaced the wings and engines. Mostly Kerbal.

[snip] There're are years of fixes and workarounds made by 3rd parties, most of the fixes due absolutely silly mistakes that were made on code that, frankly, only survived for so many years because there was absolutely no due process to properly handle regressions, with the people responsible dismissing them alegging exactly what you are alleging. There's no point to hunt bugs if they are not fixed because the idiot that called the shots just dismisses the bug reports as "there's no fixing KSP". And once the bugs pile up, things start to get hairy because you build new code over bad code, and fixing the bad code will break the new code. And then, finally, you get near the point in which fixing things became expensive. I'm following (and even working around) these pesky silly mistakes that played havoc on the game for years already, and I had tracked them down to the KSP release they were introduced in all cases. And I affirm without the slightest doubt that the bugs that rendered KSP "unfixable" (please note the quotes) were introduced by the very people that claimed KSP were unfixable. This is a fact. That are being double checked as people decide to play older versions of KSP and suddenly realises they have less bugs than the newer. [snip]

Oh, now I see. Unfortunately, both sections are part of the same Forum - they stop moderating the KSP2 subforum, whatever happens will affect the KSP¹ subforum the same. Think on an airplane where by some reason beyound imagination the crew decide to stop serving the the last rows of passengers - the uproar will be felt in the whole airplane, not only on the affected section. We have only one Forum. For the best and for the worst. But... I would like to have the KSP¹ section restored to its former glory. Posts on the KSP2 one will be essentially rants, interrelated by one or two support requests that will not be answered - all the action is happening on KSP¹ nowadays, and I really think this is not going to change soon. Wondering if I should go back to mod Orbiter, as I was doing before knowing KSP.

What's not happening. People are ditching KSP2, not KSP¹. Steam's concurrent players are rising, the online users on this Forum are stable at worst (long time user, we have way less people around in the past and yet we are still here). Whatever is happening (and it's happening), it's affecting only KSP2. Destroying what's still working is not a constructive way to protest about what's not. TL;DR: Scorched Earth tactics negate food and resources for everybody, and not only to the enemy - it's only used on the motherland by an army as a last and desperate measure. We are not fighting an enemy (if we had one, he already fled). We are fighting for survival.

They do something remotely similar to what you are suggesting, they get their arses sued by damaging the Property (Forum) they were granted permission to care (not to mention a nasty NDA). Being not enough, they are also kicked from the job, leaving the Forum unmoderated - bringing to the owner serious liabilities that will prompt them to turn the whole site read only (at best) or just nuke the whole thing (at worst). If any of this is not enough to change your mind, I'm afraid people that minds the Forum may be tempted to consider you as someone less than supportive for the welfare of this Forum. An uncomfortable position IMHO - as you would be hurting KSP¹ users too. Your only mistake, IMHO, is to use the Evil-Corp as a composition as there would be possible to exist a Corp that it's not evil. Every Corporation is evil, and it's the reason they have to pay high salaries and grant a lot of perks to lure someone to lead them - no to mention to merely work for them. Evil-Corp is a pleonasm we should avoid as useless redundancy. On reddit I talked to someone alleging being a former Moderator from this site. He said to me that they had to sign NDAs. Well, if this is true, you have your answer about.

I remember someone saying that it was a modded KSP¹ with MultiPlayer.

2mb was (approximately) the capacity of the specially formatted disks Microsoft used to distribute Window 95 by the first time. 13 disks "only". After OSR2.1, this number jumped to 26 disks. It was absolutely wundebar when the install failed on the last disk due on an I/O error...

They are the Microsoft, "they know better". It's some time Windows are applying some updates without even notifying you. (There're cases from Windows 10 too)

This Forum have the very solution for this problem: don't allow easy, cheaply created accounts to post anything. Mass harassment happens because it's dirty cheap to create another account that will have all the privileges for free. The problem with this approach is that most social media are evaluated by the numbers of active accounts they have, and so they have an incentive to keep the problem alive. Nope. No one wants double crossers, back stabbing <insert your favorite non Forum compliant expletive here> in their timeline. Keep your friends close, and your enemies closer - but know exactly how to tell one from another. Ask Cesar about. ("Et tu, Brute?"). I don't want to be used as a vector to monitor my friends. Well, I am. Or was. Even on my LinkedIn. I will refrain from further commenting the subject. Here.

You copied some files on the wrong place. I suggest to delete the faulty one. There's a trick on Windows that works fine: Select the KSP directory you want to duplicate. Hit CTRL-C (Copy into the Clipboard) Hit CTRL-V (Paste from Clipboard) This will create a new directory called <original name> copy with a copy of every file/directory from the original Rename the "copy" one to whatever you want. This will garantedly duplicate the original directory ipsi literis, without mistakes! Cheers!

I won!!! lisias@macmini62 ~/Workspaces/KSP/runtime > ls -l total 0 drwxr-xr-x 21 lisias staff 672 Jan 26 2022 1.1.3 drwxr-xr-x 23 lisias staff 736 May 16 12:37 1.10.1 drwxr-xr-x 23 lisias staff 736 Apr 22 2022 1.10.1.DDS drwxr-xr-x 4 lisias staff 128 Apr 4 2022 1.10.1.bkp drwxr-xr-x 24 lisias staff 768 May 16 01:36 1.11.2 drwxr-xr-x 24 lisias staff 768 Jan 27 2023 1.11.2.DDS drwxr-xr-x 18 lisias staff 576 Jul 15 2023 1.11.2.bkp drwxr-xr-x 25 lisias staff 800 May 6 00:05 1.12.2 drwxr-xr-x 41 lisias staff 1312 Oct 24 2021 1.12.2.bkp drwxr-xr-x 28 lisias staff 896 Feb 13 12:41 1.12.3 drwxr-xr-x 29 lisias staff 928 Sep 16 2022 1.12.3.<snip>.ptbr drwxr-xr-x 22 lisias staff 704 Jun 23 2022 1.12.3.<snip> drwxr-xr-x 12 lisias staff 384 Jun 23 2022 1.12.3.<snip>.blp drwxr-xr-x 26 lisias staff 832 Jul 24 2022 1.12.3.<snip> drwxr-xr-x 27 lisias staff 864 Jul 17 2022 1.12.3.bkp drwxr-xr-x 21 lisias staff 672 Jun 29 2022 1.12.3.saves drwxr-xr-x 25 lisias staff 800 May 5 23:58 1.12.4 drwxr-xr-x 26 lisias staff 832 Jan 14 2023 1.12.4.<snip> drwxr-xr-x 5 lisias staff 160 Jan 13 2023 1.12.4.pt-br drwxr-xr-x 25 lisias staff 800 Jun 1 12:43 1.12.5 drwxr-xr-x 23 lisias staff 736 May 23 17:22 1.12.5.KSPCF drwxr-xr-x 25 lisias staff 800 May 26 15:48 1.12.5.acp drwxr-xr-x 13 lisias staff 416 Sep 8 2023 1.12.5.bkp drwxr-xr-x 22 lisias staff 704 Mar 19 07:39 1.12.5.dbg drwxr-xr-x 5 lisias staff 160 Jan 13 2023 1.12.5.pt-br drwxr-xr-x 25 lisias staff 800 Jan 18 2023 1.12.5.<snip> drwxr-xr-x 20 lisias staff 640 Aug 11 2022 1.2.2 drwxr-xr-x 7 lisias staff 224 Jan 26 2022 1.2.2.bkp drwxr-xr-x 23 lisias staff 736 Mar 31 21:07 1.3.1 drwxr-xr-x 21 lisias staff 672 Apr 28 2022 1.3.1.DDS drwxr-xr-x 40 lisias staff 1280 Jan 28 2023 1.3.1.bkp drwxr-xr-x 2 lisias staff 64 Oct 30 2022 1.3.1_bkp drwxr-xr-x 24 lisias staff 768 Apr 30 03:17 1.4.1 drwxr-xr-x 16 lisias staff 512 Mar 16 00:49 1.4.1.bkp drwxr-xr-x 21 lisias staff 672 Mar 19 06:54 1.4.1.dbg drwxr-xr-x 26 lisias staff 832 Jun 5 13:32 1.4.3 drwxr-xr-x 24 lisias staff 768 Nov 14 2021 1.4.3-35 drwxr-xr-x 24 lisias staff 768 Apr 28 2022 1.4.3.DDS drwxr-xr-x 22 lisias staff 704 Jul 19 2022 1.4.3.bkp drwxr-xr-x 27 lisias staff 864 Apr 22 2023 1.4.5 drwxr-xr-x 28 lisias staff 896 Nov 28 2021 1.4.5.DDS drwxr-xr-x 12 lisias staff 384 Jan 27 2023 1.4.5.bkp drwxr-xr-x 22 lisias staff 704 Apr 22 2023 1.5.1 drwxr-xr-x 23 lisias staff 736 Dec 16 2021 1.5.1.DDS drwxr-xr-x 24 lisias staff 768 Jan 27 2023 1.6.1 drwxr-xr-x 24 lisias staff 768 Jan 16 2022 1.6.1.DDS drwxr-xr-x 13 lisias staff 416 Jul 17 2022 1.6.1.bkp drwxr-xr-x 25 lisias staff 800 May 16 00:51 1.7.3 drwxr-xr-x 24 lisias staff 768 Apr 28 2022 1.7.3.DDS drwxr-xr-x 9 lisias staff 288 Jul 17 2022 1.7.3.bkp drwxr-xr-x 23 lisias staff 736 May 18 22:57 1.8.1 drwxr-xr-x 24 lisias staff 768 Apr 28 2022 1.8.1.DDS drwxr-xr-x 21 lisias staff 672 Sep 28 2021 1.8.1.bkp drwxr-xr-x 23 lisias staff 736 May 19 05:27 1.9.1 drwxr-xr-x 22 lisias staff 704 May 16 17:10 1.9.1.DDS drwxr-xr-x 3 lisias staff 96 Apr 4 2022 1.9.1.bkp drwxr-xr-x 27 lisias staff 864 Jul 12 2023 Company.173 drwxr-xr-x 13 lisias staff 416 Apr 19 2019 Demo drwxr-xr-x 5 lisias staff 160 Dec 17 2019 __update drwxr-xr-x 126 lisias staff 4032 May 6 17:38 _pool drwxr-xr-x 27 lisias staff 864 Nov 5 2022 pdlauncher and lisias@macmini62 ~/Applications/Games/KSP > ls -l total 0 drwxr-xr-x 3 lisias staff 96 Jul 21 2023 CKAN.app drwxr-xr-x 30 lisias staff 960 Jul 23 2019 Career drwxr-xr-x 29 lisias staff 928 Nov 22 2019 Challenge.KAX drwxr-xr-x 25 lisias staff 800 Feb 23 2019 Challenge.KAX.1.4.1 drwxr-xr-x 24 lisias staff 768 Nov 7 2019 Challenge.RACE drwxr-xr-x 2 lisias staff 64 Oct 31 2019 Challenge.RACE.1.8.1 drwxr-xr-x 23 lisias staff 736 Jun 2 2019 Challenge.Walker dr-xr-xr-x 26 lisias staff 832 Aug 10 2021 Company drwxr-xr-x 29 lisias staff 928 Nov 7 2019 Company.170 drwxr-xr-x 26 lisias staff 832 Aug 8 2021 Company.BKP dr-x---r-x 29 lisias staff 928 Jun 6 2018 Company_old drwxr-xr-x 24 lisias staff 768 Jul 23 2019 Company_previous drwxr-xr-x 30 lisias staff 960 Sep 1 2019 Exodus drwxr-xr-x 31 lisias staff 992 Sep 23 2023 'Exodus backup' drwxr-xr-x 33 lisias staff 1056 Feb 14 2019 Exodus_previous drwxr-xr-x 33 lisias staff 1056 Feb 14 2019 'Exodus_previous copy' drwxr-xr-x 31 lisias staff 992 Jul 23 2019 'Kerbal Space Program 1.4.1' drwxr-xr-x 33 lisias staff 1056 Jul 23 2019 'Kerbal Space Program.1.4.5' drwxr-xr-x 24 lisias staff 768 Sep 1 2019 SpaceAge drwxr-xr-x 26 lisias staff 832 Oct 11 2023 "Wernher's-Dream" drwxr-xr-x 6 lisias staff 192 Dec 11 2019 __BACKUPS -rwxr-xr-x 1 lisias staff 307 Nov 24 2018 t.sh The top listing is my development installments. The bottom one, my "production" installs. ----- @stupid dumb idiot, as said by @Poppa Wheelie, you don't need to rename things all the time. In my case, I just open the directory I wanna run using Finder (I'm on MacOS) and double click the KSP icon.

A heads up to people with .blend files from the 2.79 era (as I have - many!)! By some reason, opening a 2.79 .blend file on Blender > 2.8 will make the lights 10 times stronger than they should - everything will be washed out on IVAs. By importing the mu files again on Blender > 2.8, things will be fine - the problem only manifests itself by opening .blend files that had imported a mu file on the 2.79 era. It's probably some stupid configuration I need to do somewhere on 2.8 after loading the older blend file, but I'm still struggling to find it. My work around is to just set the light intensity to 10% of the original - i.e., if the light had a 250W intensity, I set it to 25W. P.S.: Remember to set the Scene Property's Units to Metric too! This will allow you to use Watts on light's intensity.

If you are clipping parts on a craft, be sure you are not setting the Same Vessel Interactions on the clipped parts. Check this before hunting for a falty mod.

Yes. And it's allowed by the license, so you won't need to be "cautious" about. The license says you can't run more than one at once, but there's no technical measure preventing it. Just be cautious not to run or delete the wrong KSP installment by accident. Believe me, it's frustrating... === == = POST EDIT = == === If you are on MacOS, read about CoW and Compression. If you are on Linux, I suggest using BTFS and using CoW and Compression. If you are on Windows, you can tell NTFS to automatically (and transparently) Compression everything inside a directory. I suggest activating it on GamaData.

Hey, case closed! In theory, it's how things should be. Security matter. Well... KSP, in an ideal world, should be doing that. But the modding scene decided to write things on GameData, and so the best practices were thrown troughs the Windows. (pun really intended). Originally, on the Windows 3.11 and 9x times, programs used to mix program code, program data and user data on the same subdirectory - some games are still this way even nowadays, and KSP is, well, more than 10 years old at this time. So, nope. In order to run KSP, the while directory and subdirectories must be owner by your user, with Read/Write rights. You will probably need to remove KSP from your C:\Program Files into somewhere into your $HOME. It's a wise decision, and I also enforce it on an add'on of mine (a library I'm building). You should never run anything you downloaded from the Internet as Administrator no matter how much you think you trust the developer. It's more than possible (in fact, it's how most malware infections happens) that someone could forge the package injecting some nasty stuff that, once is kicked in using an Administrator account will literally do whatever they want - from installing Bitcoin miners to include your computer into a botnet (not to mention stealing bank data, you name it!). And this include games. If you run KSP as Admin, every single add'on you install will run as Admin too. Good to know you don't do it. ---- Well, back to the problem - probably some Windows update decided to "fix" your KSP's access rights. There's no other option than move KSP to somewhere in your home directory and run KSP from there - it's what I do anyway, even on MacOS and Linux. Cheers!

Last time I got problems on College, I had to drive half the campus to talk to different coordinators - each one on a different building, each building about 5 to 6 KM from the other. Send the emails and stop complaining - trust me on this one, you are good!

CKAN is alright, the problem I though it could be happening happens only when launching from Steam with a unfortunate hack that induces KSP to write and read some files on the wrong place - a mess. Since you are launching from CKAN, this is not the problem. So my next best guess is that somehow the directory where KSP is installed is set to read/only. It's a possible explanation for some Assemblies not being able to read some files - not to mentino the KSP.log not being created (but I think this would create an entry on the Player.log...). Do you now how to check and maybe set a directory's owner and file permissions? Until the moment, it's the only hypothesis left - your CPU is an Intel with 8 cores and 16 threads, symmetrical (i.e., all cores with the same speed), and so a known situation that happens on assymetrycal CPUs (the e-core, p-core thingies) is not the cause for your problems. You need to be sure that the directory where KSP is installed is set to your user as owner, and that you can read and write to all files on it. If you have Steam, I would also verify the installed files.