Ruedii

Members
  • Content Count

    1,146
  • Joined

  • Last visited

Community Reputation

167 Excellent

1 Follower

About Ruedii

  • Rank
    Spontanious Unplanned Disassembly Expert

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Yeah, that is what I meant. You need to check their behavior. Make sure it's starting at it's maximum extended state instead of at the middle or top. Also, you might want to make sure your wheel collider isn't creating two colliders for the wheel (one general physics, one wheel) instead of one.
  2. I'll have to test the mods in question. I should see if it's been fixed by this change first.
  3. Should this fix other mods that also have NREs on drag cubes, or just the fairings. Several mods have run into NREs on loading drag cubes for non-fairing parts.
  4. You might want to talk to the developer of Airplane Plus about how he manages wheels. He has a lot of good wheels in his set.
  5. If they could (I know it is added lawyer expense) they should make a specific EULA for each game and service, and give the user the choice of agreeing to the 2K EULA or each individual EULA. Generally most people would rather do the former, for simplicity. The game or service EULA should be based on an option selection of boilerplate clauses based on what types of games or services you are using.
  6. I really think the privacy section of the EULA does need to be updated with details under what they use each type of information for. It also needs to be clarified that it's the EULA for ALL services by 2K. It also needs to be clear that the information given is in a Non-Exclusive Unlimited license to 2K to utilize in purposes relating to the games and services you wish to use. Then add a second section for anonymous analytics with what information is stored there separately.
  7. As a note, any tests for the latest KSP version on this? Some part-only mods ran into trouble.
  8. Several minor changes to part handling *cough*Drag Cubes*cough* broke a bunch of parts. Hopefully they will fix that in 1.10.1
  9. To address your initial problem: That is behaving as intended. Don't do that. As of how to prevent that: Parts clipped together should ALWAYS be treated as a single segment when setting up staging, this means you need to set up a parent mount that ALL the clipped shields link to for this case and decouple the parent mount from the ship. This will give you a clean decouple. Any option to force them to self destruct after a delay will involve mods as far as I know. I'm not sure if the sequencer part from Breaking Ground might be able to be used to create a delayed action, though.
  10. Is that going to be early access release, stable with features still to be added release, or complete release? I know the primary scope change of KSP 2 will be colonization. I presume this takes a lot of balance.
  11. Might I suggest something: A series of visual scanners specifically for mounting on planes and rovers, as well as some missions specifically for them (scan a specific location.) The first one would be an early visual scanner with low resolution black and white visual with anomaly detection. The second would be high resolution color visual with biome, high resolution altimeter and anomaly identification. They would both require being under 12Km to work and would have an ideal altitude of 5Km making them impractical for both full planet scanning, but great for scouting an area or for attaching on a lander so you know what's in the immediate area when you land.
  12. NDA issues with Private Division, If I Recall.
  13. Quick question, do you have mods installed? Many times unsupported mods will soft-fail leading to lag, bugs, and save file breaks.
  14. Not compatible with KSP 1.10. (Linux) I might look into it later. OK, Looked into it. The Drag cube computation is throwing an NRE on initialization of the game database. It probably needs it's drag cube to be specified properly in the part file. Hopefull this same bug won't affect every mod out there with wierd shapend objects missing manual drag cubes. Log:
  15. I don't know who to blame for the whole mess of the transfer. I do not see anything wrong with the change of development company. Star Theory didn't want to continue developing under the terms provided by Private Division, so they decided that a new company would be made. The problem is that the developers weren't consulted in all of this. I don't know who is to blame, but if Star Theory was in these negotiations and they are the formal employer, it is their duty to consult them and bring them in on the discussion. Honestly, Star Theory has had a lot of problems, and 2K's largest ethical problems have been in not mandating that their subsidiaries follow proper ethical behaviour, and then taking the blame so they can be the big corporate bad guy and the middle management gets off with no blemishes on their reputation. So I think logic says that 2K didn't make Star Theory bring in the programmers, and Star Theory didn't think to. Making Star Theory at fault, and 2K Negligent (as usual with anything that happens under their umbrella, which is why I was so glad to see Squad keep it's current management lineage in the merger.) Fortunately nothing here is more than bad corporate practice. Nothing illegal, and everything did get sorted out in the end. Still, it is a good reason to pressure 2K to try to at least give some decent advice to their subsidiaries about when something is a bad idea. They also should probably go and maybe get some people with some real world experience to consult in these sort of things as to know what sort of things can go wrong, and what the fallout might be from it. I think part of the problem is that 2K's business division is too far detached from the real world and doesn't know what kind of mistakes can happen and what the press will think of it. The later one is the bad part. For instance, letting the greedy stand-up guys at RockStar request cease and decist letters against modders was a clear and obvious bad press moment. A more kindly worded letter saying to restrict particular usages of the modkit would have been better. Even better would be to provide guidelines for modding in an EULA ammendum for GTA V and GTA V Online, with separate designations of what is acceptable for regular play and online play. As of what I would like to see now, as of cleaning up this mess on KSP 2 should be done in a fully transparent manner. They also need to make sure this kind of mess doesn't happen again.