Jump to content

KrakenBait

Members
  • Posts

    19
  • Joined

  • Last visited

Reputation

6 Neutral

Profile Information

  • About me
    Software developer (business)
  • Interests
    Unintentionally tempting the kraken
    Orbital / planetary construction
    3D programming / modeling hobbyist
  1. A lot of them have already been posted in this thread:
  2. I prefer my lunch around noon, but whatever works for you! Your ship looks suitably impressive. I haven't tried to go that big yet in KSP 2. I'll probably wait until things stabilize a bit more before I do that. I do like the lighting they have added in KSP 2 for night launches. It reminds me of a large photo I used to have of a night time space shuttle launch.
  3. I've encountered plenty of bugs and the occasional crash. That being said I wouldn't call the game broken beyond the point where it can't be any worse. Despite all the issues I've managed to do several missions already, and it seems plenty of others have as well. Although I'd like all the bugs to be fixed as soon as possible as well, we've waited several years already so waiting a week or two for the fixes to be tested shouldn't be a big deal. There always KSP 1 to go back to in the mean time.
  4. Maybe try a rocket with multiple stages instead? In this case there is not much information to be shown.
  5. The green button is for triggering the next stage, the first one being the actual launch. The arrow button shows either more or less information on your staging stack. Although I did not notice that immediately either.
  6. I think it would be nice if the large logo on the side of the VAB could be set to your agency's flag. Maybe have multiple flags when multiplayer gets added.
  7. An update on this. It is caused by PROTON_USE_WINED3D=1 I initially set this flag to get it to launch, but it seems this is only required for the annoying pdlauncher. When I skip the launcher and leave it out, it is showing as expected.
  8. After following the instructions above for skipping the launcher, I no longer need the PROTON_USE_WINED3D environment variable. It seems that this actually caused most of my graphical issues.
  9. An update on this. It is caused by PROTON_USE_WINED3D=1 I initially set this flag to get it to launch, but it seems this is only required for the annoying pdlauncher. When I skip the launcher and leave it out, it is showing as expected.
  10. Looking around KSC there seems to be a building that looks like the astronaut complex from KSP 1 next to the tracking station. So far it does not seem to be selectable, maybe it will become functional in one of the later stages of EA?
  11. When right clicking on a part, the menu shows the wrong state initially. Clicking on the part in the menu does work as expected. AMD Ryzen 9 3950X 64 GB DDR4-3600 AMD RX 5700 openSUSE Tumbleweed, KDE Plasma (Xorg) Proton Experimental Launch Options: PROTON_USE_WINED3D=1 %command% Version 0.1.0.0.20892
  12. So far I've not seen any clouds, but there is a layer of grass hanging low above the runway. AMD Ryzen 9 3950X 64 GB DDR4-3600 AMD RX 5700 openSUSE Tumbleweed, KDE Plasma (Xorg) Proton Experimental Launch Options: PROTON_USE_WINED3D=1 %command% Version 0.1.0.0.20892
  13. There are large gaps in the terrain on kerbal. This is visible in KSC view, but also when flying a craft. It seems that the missing parts are always the same though. Although it is not visible, collisions do work. AMD Ryzen 9 3950X 64 GB DDR4-3600 AMD RX 5700 openSUSE Tumbleweed, KDE Plasma (Xorg) Proton Experimental Launch Options: PROTON_USE_WINED3D=1 %command% Version 0.1.0.0.20892
  14. Thanks for the reply Dman979! I had not checked that as I was expecting an account to be required. This works indeed.
×
×
  • Create New...