• Content Count

  • Joined

  • Last visited

Community Reputation

16 Good

1 Follower

About StarStryder

  • Rank
    Rocketry Enthusiast

Recent Profile Visitors

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

  1. v1.2.2 has Set Orbit build in on the cheat menu (RightAlt+F12 or RightShift+F12 on Linux). No mods needed.
  2. It didn't, but I have solved the problem. I'd completely forgotten my Windows training and had not turned it off and on again! That solved the problem although it still breaks if launched from CKAN. Not sure what's going on there. Launching from cli is fine.
  3. The game window appears for a fraction of a second and then disappears again. The window manager doesn't crash though. No libraries are listed as missing by ldd I'm using Linux Mint 18.0 I have an Nvidia Geforce 1060 using driver 375.39 Yes, it's installed in my home folder. All of the files are owned by me and my personal user group. They are a mixture or rw+u and rw+ug permissions.
  4. Yes, that is the entire log before the program exits to the terminal. Same issue with both KSP.x86 and KSP.x86_64. oh, and no KSP.log file is generated.
  5. I have this problem and deleting settings.cfg and ~/.config/Unity3D did nothing to fix it. Running Kerbal Space Program Set current directory to {home}/bin/kerbal/v1.2.2/game Found path: {home}/bin/kerbal/v1.2.2/game/KSP.x86_64 Mono path[0] = '{home}/bin/kerbal/v1.2.2/game/KSP_Data/Managed' Mono path[1] = '{home}/bin/kerbal/v1.2.2/game/KSP_Data/Mono' Mono config path = '{home}/bin/kerbal/v1.2.2/game/KSP_Data/Mono/etc' displaymanager : xrandr version warning. 1.5 client has 4 screens displaymanager screen (0)(DP-4): 1920 x 1200 displaymanager screen (1)(DP-2): 1920 x 1200 Using libudev for joystick management Importing game controller configs I have had v1.2.2 running on this system. I don't know what's changed between then and now other than the usual system updates.
  6. I wasn't talking about beta (<1.0.0) vs. released (>1.0.0) but about the release cycle for 1.2. They're nearing the end of the "experimental" phase for the 1.2 release and they're still adding new features. This is a fundamentally bad idea as it massively increases the risk of new bugs making it through to the public release. New features really should be held until release 1.3 now.
  7. So your ore carrier is full at the time of contract acceptance. You empty the tanks, head to the contracted ore source, fill up from the miner and head to the contract destination. Does the contract complete? It's not as simple as you're making out.
  8. Am I the only one concerned that there is still new feature development being done at this late stage in the release process. It really should be bug fixes only at this point.
  9. No, they were discussing the "rumour" that Porkjet may no longer be working for Squad.
  10. They weren't talking to you. Different thread of conversation entirely.
  11. Welcome to software project planning. It is notoriously difficult to estimate development times. Tasks that should be simple unmask some horrible technical complication that triples the estimate. Or you encounter a bug in a third party library that takes weeks or months to get fixed (*cough* Unity *cough*). Big companies smooth out these blips by virtue of running bigger teams and bigger projects so the delays are easier to absorb. Even then, it doesn't always result in deadlines not being missed or QC targets being missed. However, for small companies, these issues really hit hard. Now Squad have a history of releasing anyway rather than delaying to fix issues. This has generally worked out because the PC based players are much more used to small software developers. Console gamers, due, I suspect, to the more complex release cycle imposed on them by the platform vendors, are more used to dealing with larger companies and so are a lot less forgiving. They're simply not used to the hobbyist aspect of gaming.
  12. Also, not technically a Dyson sphere if it's encapsulating a planet. The whole point of a Dyson sphere is to capture the entire energy output of a star. Putting one round a planet would both cut the population off from the star's energy while also presenting a sub-optimal surface on the outside for solar energy capture. Still, a planet circling ring station would be rather cool.
  13. What I do is launch into the same orbit as the target. Then put a maneuver node at Pe and add prograde until the intercept marker gives a close pass. Remember that you need to make sure your relative inclination is low. Burn at An or Dn to adjust it. This method will give you an encounter in a single orbit, although it uses more dV than a multi-orbit solution.