Jump to content

Jetski

Members
  • Posts

    767
  • Joined

  • Last visited

Everything posted by Jetski

  1. This is fantastic! You beat my entry by over 15k I like the creativity showing up here
  2. First stage drops at 6000m Seriously though, for Kerbin takeoffs, I generally use SRBs attached radially to the end of a wing. Slap an LFO tank on top, enable crossfeed, and your first core stage reaches 40km still full of fuel. Also the wings keep the boosters far enough away from the core to avoid the need for Seperatrons. Decouplers can go at either end of the wing, depending if you want to still have fins on the core after decoupling. So first stage drop is just SRB/droptanks, and between 30 and 50 km.
  3. I've been having the same problem since 1.3 dropped - fairly simple vessels with a payload inside a fairing are exploding consistently. I've altered my play to stop using fairings altogether, because every launch they fail. Modded or stock, same behavior. I don't use fuel lines, and I autostrut pretty much every part, but nothing fixes it except removing the fairing. Identical ship without fairing, loads no problem
  4. @Mesklin great job! I liked the extra science mining at Duna, well done. You are added to the board!
  5. Here's a run at the challenge. I did this kind of the hard way, took forever to find an arch as I had not visited any of them yet in this save. I learned a lot about scanning for anomalies though. Did all my launches the hard way, no Hyperedit or cheat menus. Max speed I could screenshot was 325 m/s. Certainly won't be the best speed, but it was a lot of fun. Ignition! TWR > 100 Basically just Mohat Kerman in a command chair with a Mammoth and a fuel tank strapped to his back. Imgur full album Spoiler alert! Warning! 2 of the images in the full album have Kerbnet open, and show the lat/long of one of the Mun arches. I highly recommend finding your own arch. FYI the Mk2 drone core has the highest probability of detecting anomalies, but only a 20 degree field of view. Unless you are suborbital. Scanners and such are useless, probe cores are mediocre (18% or so). Orbital height doesn't seem to matter though, was picking up anomalies at 100k orbit just fine. Lots of warping and refreshing Kerbnet though...
  6. Great job @jonny You get the badge, and top of the board for completing this the (really) hard way!
  7. Great, let me know if you need a Linux test on anything Happy to help any way I can. This is a pack I'm super excited to play through - I only got a teaser few planets visited before 1.3 dropped and I became incompatible. The art is awesome!
  8. One thing I found helpful was to have at least a little fuel in all the debris to keep Bill and Jeb from being stranded
  9. For what it's worth New Horizons loads up and plays fine - this is a different issue than the pathing problem with Linux/Kopernicus. The pathing bug can be worked around by loading up the game from within the KSP_Linux folder. This one is specific to GPO - spamming NullRefs from the StarLightSwitcher function, Main Menu loads up fine but crash happens when KSC tries to load on starting a new game or loading a save.
  10. @Gameslinx hey buddy, still broken for Linux, same bug as before. Freezes on the screen just before KSC appears, stuck on loading screen with spinny planets ksp.log
  11. @nascarlaser1 when you have a good save put together, can you post it? My old 1.0.5 save won't load up, and besides I've already played it
  12. Interestingly, f5 save a few hundred feet up while landing on Tylo with engines running full blast has been Krakened. When I quickload, the engines are off, and the lag of relighting them makes me smash into the planet every time. Dang.
  13. A little more information after messing around a bit. I got the same bug trying New Horizons - which seems to point towards Kopernicus. I got curious though - an unrelated fact is that Linux KSP install by default stores the KSP.log and MiniAVC.log on my Desktop, odd behavior by my reckoning. Perhaps Linux sets a "working directory" based on where you are when you start running a program? Anyway, after some messing around I found I could get New Horizons to work by running the Launcher executable from within the game folder instead of the link on my Desktop. Also log files no longer appear on the desktop. I'll try this with OPM next, but it's late here and I must sleep. TL,DR: possible workaround is to open the Launcher from within KSP folder instead of using a Desktop shortcut to run the game.
  14. Hi there @Sigma88, Linux x64 user here. I'm having a game breaking bug on every planet pack I install, and the error shows up under [Kopernicus] in the KSP.log. Game is hanging on the Loading... screen just before the main menu pops up and after all the parts loading and modulemanager stuff. I reported it already here in OPM, but then I tried New Horizons and got the same thing. Basically it's looking for .dds files on my desktop instead of in the game folder. I know Linux is extra picky about filenames, maybe this is the problem? KSP.log Edit: possible workaround discovered! A later attempt running the Launcher directly from within the game directory (instead of the Desktop link to the executable that I normally use) and New Horizons loaded up. Not sure why - maybe if the KSP runs from the game folder instead of Desktop it picks a different working directory and pathing issues go away?
  15. Hi there, @Galileo or possibly @CaptRobau Linux x64 user here - reporting a game-breaking bug every time running this mod (and nothing else). Fresh install, fresh download of OPM, latest version of Kopernicus, game hangs on the loading screen before the opening menu can even come up. Not the screen with the pictures and talking about module manager and parts etc, but the fraction of a second later where the screen goes black and the Loading... icon appear with the spinny planets just before the main menu appears. [snip] Here's a snippet from KSP.log - a pathing issue maybe? it's trying to find GameData on my desktop, which is definitely not where it lives. Linux is extra finicky about filenames and paths... I'm happy to upload the whole thing if that helps, or any other Linux troubleshooting that may be necessary. Or even better maybe you can just tell me I messed up something while installing? Edit: posted my very first bug report on github (probably completely wrong)
  16. Cool no worries. Let me know if there's anything I can do to help with testing or anything.
  17. Here's a quicky Imgur scrambled the images as usual. Also couldn't bring myself to leave Bill on Duna, so brought him home
  18. @Gameslinx I'm going for another playthrough now that 1.3 seems stable(ish). I've got a game-breaking bug right away though. New KSP install from the Store, fresh install of your mod from the zip file, and no other mods except Engineer Redux. When I start a new game, or even try to open the Settings Menu, the game hangs on the loading screen (black screen, the word Loading in the bottom right and spinny planets icon cheerfully spinning). Here's my KSP.log which looks to be spamming nullRefs from something called Starlight Switcher and below is my Kopernicus.log I'm running this on Linux Ubuntu x64, which is much more persnickity on filenames and case sensitivity than WIndows for what that's worth. I can load up the game if I delete ModularFlightIntegrator, which generates the following Kopernicus.log, but only the stock planets show up, so clearly not a good solution. Edit: looks like Someone is having the same problem with GPP running in Linux
  19. Yikes. forum code for imgur albums is royally borked. I was able to retrieve my first album by wading through the HTML of the forum page and searching for the imgur HTML tag, but it's so time-consuming I can't do it for all those albums. They worked when I posted them, but even now I cant get them to show right. I may go for a run at this on Hard
  20. My Duna mission without patched conics was cost about 1100 dV extra just in futzing around to get an intercept. Bring extra fuel or do maths
  21. Excellent job! Also thanks for showing me a glaring hole in the rules That's a great mission, but I fear that "Recovery in Orbit" is far too common a theme, as contracts spawn routinely for this, and many KSPers are very familiar with this type of mission. I'm altering the rules so future entries must be landed
  22. Ever wonder what happens when you click that lovely green Recover button at the top of the screen? Now you can find out! Jebediah has unfortunately failed to land the good ship Untitled Space Craft in an acceptable manner, and now Bill has to drive the recovery vehicle and collect the remaining pieces. Your mission is to build a realistic recovery truck (or plane or rocket) that can drive over, pick Jeb up, and bring him back to the launchpad or the runway start. Sounds easy right? Here are some rules, because challenges need rules, right? You can recover whatever you like - a plane, a capsule, a spent booster, a crashed part and you can land it however you like. We will call this the Debris. Your Recovery Vehicle can be whatever you like - a plane, a truck, a rocket, a VTOL, whatever. We will call this Bill's Ride. Bill's Ride must start either on the Runway or the Launchpad, and return to the exact same spot intact with the recovered parts. Staging is technically permitted, but crashing either the Debris or Bill's Ride will result in fewer points. No cheats of any kind, although HyperEdit or similar is permitted to place the Debris. Mods are permitted, but will be listed as Modded. Bills Ride and the Debris (which might be a good name for a band) should both be intact at the recovery point to be scored. The Debris must be landed, preferably on Kerbin (but I won't disallow other bodies), ideally in some awkward manner suggesting a crash There are a number of ways to be awesome at this challenge, and the scoreboard will reflect your awesomeness accordingly. Long Drive. Get a screenshot either in Map or Flight mode showing the distance to the Debris. Debris not on Kerbin will be scored separately. Go for distance! Big Debris. Points for the largest item returned intact! Show a screenshot of the Debris in the VAB with the Engineers Report showing tonnage. Bigger is better! Style. Build the coolest Recovery Vehicle you can, either realistic or creative or both! Here's my mission (Imgur Album) Leaderboard: @Cunjo Carl with a badS airplane recovery vehicle, collects 15T from 1000km away across the ocean! @qzgy recovered a 6T shuttle from LKO, helped me refine the rules a bit , and will be our last orbital Debris entry @Jetski Bill drove a tractor 1.7km to recover the capsule of Untitled Space Craft (1.09T)
  23. A followup on the RSS config - initially everything seemed OK, only the right planets showing up in the Tracking Station, etc. I played through a bit of career and unlocked the various telescopes, and some judicious poking around revealed Venus and Mercury, which then showed up in the Tracking station minus their orbits. As I understand this, I should now be able to research stuff either by paying in the Observatory or the pay-for-Contracts, correct? I tried both and no further research is being completed, no matter how much time I spend warping. The contracts either complete or fail (I don't know why) but Mercury and Venus remain stubbornly unknown objects. I took some photos, which gave me a little science but did not reveal any orbits or any info. Am I doing something wrong? Has anyone else gotten this to work with RSS or another planet mod? I'm happy to provide logs if that helps, but as nothing crashed or visibly broke I'm hoping this is pilot error
×
×
  • Create New...