Jump to content

Redchrome

Members
  • Posts

    97
  • Joined

  • Last visited

Reputation

5 Neutral

Profile Information

  • About me
    Rocketry Enthusiast

Recent Profile Visitors

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

  1. Thank you for the hint on watching the wheel information windows! I had considered adding some trailing small wheels for steering.
  2. Thanks for the feedback. Thing is, I never saw any indication that either side was speeding up, even on my short-wheelbase test vehicle.
  3. I can't seem to get rovers based on the XL3 wheel to steer. They just go straight down the runway. I'm working on a giant rover, but when I found this problem I built a tiny rover (just two Mk2 cans back to back, with 4 XL3 wheels on a very short wheelbase) and even that doesn't steer. I checked the wheel settings, and even tried reversing the direction of steering, but to no avail. It seems I'm not the only one with this problem I have not yet found a resolution tho. I believe in the past I've used these wheels successfully, but it's been a while. Does anyone have any experience to shed light on this? I do realize based on my reading of the forum here that these wheels are supposed to use differential steering. However, even that doesn't seem to work for me.
  4. @linuxgurugamerThank you for keeping these old mods alive. the Taurus capsule from RS Capsuledyne is an amazing piece of work. I signed up on your Patreon to give you a little support. It would be nice to have the RSCapsuledyne mod at least updated so that it reports as being compatible with the latest KSP.
  5. Solved it! TL,DR: I needed to upgrade my graphics drivers. Thanks to the *other* troubleshooting guide in this forum, I found the Player.log file. cat ~/.config/unity3d/Squad/Kerbal\ Space\ Program/Player.log Mono path[0] = '/home/chrome/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/Managed' Mono config path = '/home/chrome/.local/share/Steam/steamapps/common/Kerbal Space Program/KSP_Data/MonoBleedingEdge/etc' Preloaded 'libkeyboard.so' Preloaded 'liblingoona.grammar.kerbal.so' Preloaded 'libsteam_api.so' Preloaded 'ScreenSelector.so' Display 0 'KJTHDMI2.0 32"': 3840x2160 (primary device). Desktop is 3840 x 2160 @ 60 Hz Unable to find a supported OpenGL core profile Failed to create valid graphics context: please ensure you meet the minimum requirements E.g. OpenGL core profile 3.2 or later for OpenGL Core renderer No supported renderers found, exiting (Filename: ./PlatformDependent/LinuxStandalone/main.cpp Line: 611) However, it looked like my 'OpenGL core profile version' should be sufficient. $ glxinfo |grep -i version server glx version string: 1.4 client glx version string: 1.4 GLX version: 1.4 Version: 19.2.8 Max core profile version: 3.3 Max compat profile version: 3.1 Max GLES1 profile version: 1.1 Max GLES[23] profile version: 3.0 OpenGL core profile version string: 3.3 (Core Profile) Mesa 19.2.8 OpenGL core profile shading language version string: 3.30 OpenGL version string: 3.1 Mesa 19.2.8 OpenGL shading language version string: 1.40 OpenGL ES profile version string: OpenGL ES 3.0 Mesa 19.2.8 OpenGL ES profile shading language version string: OpenGL ES GLSL ES 3.00 Obviously it wasn't tho. So I spent several hours wrestling with getting my nVidia driver updated, kernel updated (turns out upgrading from 4.15 to 5.4 is not quite trivial), and getting all the driver versions to match. I haven't updated my kernel and drivers for some time because my last attempt resulted in crashes once a day. In retrospect, I should have just made sure I had this Ubuntu PPA installed: https://launchpad.net/~graphics-drivers/+archive/ubuntu/ppa remove the nVidia .run package I had installed, then run: apt-get install nvidia-driver-455 but it took me a while to catch on to exactly what I needed to do. If I'd just been a user who installs the system and never does anything funky other than the occasional 'do-release-upgrade' I probably would have been fine.
  6. Hi there, After several months hiatus while working hard at a new job, I'm trying to launch KSP again. Unfortunately, when I try to launch it (from Steam, CKAN, or the Linux command line) I see a bare wallpaper image ever so briefly (as if the game is trying to set the graphics mode) and then I'm back to my usual desktop and the game isn't running. I'm on Ubuntu 18.04, a GTX750 Strix video card, and 20GB RAM. Direct rendering is working. $ glxinfo |grep 'direct rendering' direct rendering: Yes I tried completely removing my KSP instance by renaming ~/.local/share/Steam/steamapps/common/Kerbal Space Program and letting Steam re-install it. So I believe I have a completely stock instance now, and it still crashes. I don't see any logs generated, and I tried looking (unsuccessfully) for .dmp files. I tried looking at the troubleshooting hints pinned in this subsection of the forum and didn't have any luck adding options to the launcher (hopefully I'm correctly guessing at what to do here). This is the most debugging output I've been able to get. Please tell me if there are any additional debugging steps I can do: [email protected]:~/.local/share/Steam/steamapps/common/Kerbal Space Program$ ./KSPLauncher.x86_64 -disable-gpu-skinning -force-gfx-direct Set current directory to /home/chrome/.local/share/Steam/steamapps/common/Kerbal Space Program Found path: /home/chrome/.local/share/Steam/steamapps/common/Kerbal Space Program/KSPLauncher.x86_64 INTEL-MESA: warning: Ivy Bridge Vulkan support is incomplete INTEL-MESA: warning: Ivy Bridge Vulkan support is incomplete XIO: fatal IO error 0 (Success) on X server ":0" after 288 requests (286 known processed) with 26 events remaining. What's the next thing I should try to debug this?
  7. Yeah, I recognized this after I solved the problem. The number of files Steam 'repairs' seemed to have no correlation with the problem or its solution.
  8. After some experimentation with a no-mods install (thanks to whomever built the "Manage KSP Instances" feature into CKAN) and slowly adding mods to it, it *seems* that uninstalling and reinstalling the Fuel Tanks Plus and Toolbar mods in my stock KSP instance, has fixed the problem. I'm not sure that those were actually the things at fault, but so far the problem has stayed fixed. I also noted that the 'Suborbital' training mission was much easier to accomplish now. I suspect there was some dark matter which must have been inadvertently attached to the capsule model, making it weigh more than was obvious by the figures.
  9. It seems that just loading the game corrupts one (1) file. I will play with trying to build a completely vanilla game and see if that makes a difference.
  10. It seems I spoke too soon. The problem is back. Repeated trials have shown that the game seems to corrupt itself somehow. I can 1. Launch Steam 2. Verify the file integrity 3. Repair the corrupted files (usually 22 or 23 now) 4. Re-launch Steam 5. Verify that there are no corrupt files 6. Play the game 7. Find that the bug is back (I don't know why it worked that first time after repairing 54 files) 8. Go back to Steam 9. Verify the files and find that there are about 22 corrupt files to be re-downloaded. Need to experiment with this some more.
  11. I had done that once already, but I tried it again, and that seems to have fixed the problem. Thanks!
  12. This was a short hop with a 'Flea' SRB. Never got above a few km. It's an even lighter version of the 'Hopping Flea' stock ship, with less mass to land because it drops the SRB. The pod was hanging from the parachutes for quite some time. Didn't time warp it either. I used both a drogue chute as well as regular chutes. I kept getting this same result when in the training scenarios as well. The Mk1 pod always exploded on landing. Could this be an artifact somehow resulting from my upgrade from an earlier version? Notably, the Mk1 spaceplane cockpit lands just as gently as can be under 2 parachutes. See screenshot below of it coming down at a gentle 3.6 m/s, even though it has about the same weight (~1.2t).
  13. I've been away from KSP for about 4 years, but picked it up again recently. So I know I need to get up the learning curve for heat shields, radios, fairings, and a few other things. The unexpected problem is that my Mk1 command pod always explodes on splashdown. I see that it has a 14m/s maximum impact speed (which seems awfully low), but I'm finding it impossible to slow it down enough to land. Even with 4 parachutes on it, it's still coming down at 19m/s. Is there a mod making this thing too heavy? Too fragile? See screenshot for mass & speed numbers.
  14. I note that if you make a craft, push the button to 'Weld It!' and then click 'cancel' when you're at the dialog where you fill in the parameters of the weldment, the welding dialog goes away, but so does the part assembly you were working on! I'm running KSP 0.90 on Linux.
×
×
  • Create New...