Jump to content


  • Posts

  • Joined

  • Last visited


936 Excellent


Profile Information

  • About me
    Capsule Communicator

Recent Profile Visitors

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

  1. I don;t know why this should be so hard as to make my head want to explode.


    I want to lock steering to up


    wait until reaching 50m/s

    roll 90 degrees so pitching down has my ship going east!!!

    I have googled for hours and read the docs and cannot figure out how to accomplish this SIMPLE task!!!


    Can you, as if describing to a three year old child, explain how I do this in kOS please?

  2. It's wonderful that someone is doing this. As the person maintaining kOS for KSP1, I felt bad that my computer is not up to being able to do KSP2 so I'm not part of the KSP2 hype so kOS for KSP2 isn't really a thing I can be working on. (Also, I am in a job search where until I land a job it would be irresponsible for me to be shelling out the cash and free time it would take to be doing a kOS for KSP2 right now.) There's things I'd want to do differently if I did do a kOS for KSP2 and it looks like some of those things are in the mind of the person doing this. For one thing I didn't start the kerboscript language so when I enhanced it with lots more stuff like scoping, function calls, and delegates, it was always piecemeal one new feature at a time and therefore I sided with "keep it looking similar" rather than "do it like normal languages would do it" a lot of the time. That led to, well, the weirdness that is kerboscript.
  3. It should be okay to remove them. And the newer modulemanager should work fine.
  4. Update: kOS - Catch-up for over a year of little things It's been 2 years since the last kOS release, and a lot of small changes have trickled in. None were big enough on their own for a full release but there's been enough of them and it's been long enough that a release has been needed for a while now. Since KSP 2 is about to start hitting early access, it seemed right to get all these little things out for kOS for KSP 1 just before that happens. This will also make it so people won't have to keep overriding the complaints of CKAN for trying to use kOS on KSP 1.11.x or KSP 1.12.x. (Which it worked for but CKAN didn't know that. Now it should know that.) BREAKING CHANGES The bugfix to prevent a local variable from clobbering a builtin name could make existing scripts have to rename a variable or two. Previously if you tried to create a variable that matches the name of a built-in variable, it would let you but then the built-in variable would be permanently masked and unreachable. Now by default it won't let you. BUT you can get the old behavior back again if you use the @CLOBBERBUILTINS directive, if you really want to let yourself do that. pull request NEW FEATURES kOS parts are now findable by typing "kos" into the VAB's part search bar. pull request kOS parts can be placed inside the KSP cargo inventory system. pull request Comma-separated list of LOCAL or SET declarations can now be parsed. Example: old: local a is 3. local b is 5. local c is 10. can now be: local a is 3, b is 5, c is 10. This is similar to how it works with PARAMETER. pull request Added VESSEL:THRUST, VESSEL:ENGINES, VESSEL:RCS. VESSEL:THRUST is the sum of the engine:THRUST of all the engines. VESSEL:ENGINES is the same list returned by LIST ENGINES, but using a somewhat nicer syntax. VESSEL:RCS is the list of all the RCS parts on the vessel. pull request Added OPCODESLEFT bound variable. This bound variable returns the number of instructions yet to execute (how much of CONFIG:IPU's instructions there are to go in this fixedupdate). Intended to help decide if a WAIT 0. would be prudent before entering a critical section of code. pull request Better integration with RP-1's avionics tech progression. (No longer have to buy into the tech from the R&D building to cause the kOS cores in avionics parts to get the upgrade.) pull request Better integration with RP-1's avionics lockouts when the avionics doesn't support the mass. (Previously kOS couldn't use ANY of the controls when avionics were insufficient, even ones RP-1 meant to still work with insuficient avionics, like RCS fore and aft.) pull request kOS parts are now findable by typing "kos" into the VAB's part search bar. pull request Can now read a binary file as a LIST of numeric values (one per byte). pull request BUG FIXES Documentation: Many small one-line documentation fixes that are too numerous to mention all of them one by one. pull request pull request pull request pull request pull request pull request A change to make it backward compatible with a call kOSPropMonitor was doing. pull request Cause the mod RocketSoundEnhancement to stop muffling kOS's sounds. (By explicitly telling Unity those sounds don't emit from the kOS Part's "location" and instead are ambient.) pull request Make PART:DECOUPLER behave more consistently with what the documentation says about docking ports. pull request Reduce excessive repeats of GUI ONCONFIRM calls being triggered when they werent' supposed to be triggered. pull request Remove legacy old version of kOS's computer from the parts definition file so it can't appear by accident in the parts bin. This is no longer needed for backward compatibility like it was before because this version of kOS cannot run on the very old versions of KSP that part was for anyway. pull request When reporting the terrainheight of a geoposition, it no longer returns false results caused by seeing certain stock parts that put trigger colliders on the "terrain layer". pull request Fix SteeringManager believing RCS blocks were capable of more thrust than they were (causing steering to be tuned wrong when steering via RCS). Problem was caused when stock parts now have multiple alternate RCS nozzle arrangements, and kOS was summing up all the thrust all the nozzle variants can do even though only a subset of those nozzles actually exist in any given variant. pull request pull request When setting the volume name for a disk drive by copying the vessel's name to the volume's name, it now strips out characters that are not allowed in volume names (but are in vessel names, thus the bug). pull request BOUNDS now does a better job of calculating based on part's colliders rather than their visual meshes which don't always agree with the colliders. pull request No longer bogs down as much when someone creates the same LOCK expression repeatedly in a loop. (Still not a good idea, but kOS tolerates it better now.) pull request Performance: No longer pays the cost of tracking a stopwatch when the user doesn't even have profiling turned on so they're not looking at the timings anyway. pull request A VOICE's volume is now persisting properly after playing a NOTE. Previously playing the NOTE caused the VOICE volume setting to get clobbered by the NOTE's volume. pull request Make it so kOS's ModuleCargoPart settings don't break in older KSP 1.10.x (which doesn't have ModuleCargoPart). pull request Fix a bug when a thing that is locked is used as the left side of a suffix when setting the suffix. pull request Prevent a local variable from clobbering a builtin name pull request Allow kOS code to "see" a change to a manuever node's ETA made outside the script, after having obtained the node in a variable. pull request Fix Compiler exceptions not showing the filename correctly. pull request Fix ALT:RADAR sometimes wrong when high above ground. pull request Fix race condition that caused terminal to spam the log on scene changes and sometimes spam the log enough to lag the game for some people. pull request Fix throwing exception when setting SASMODE while the navball is hidden. pull request Made the doc generation scripts work on python 3.x pull request
  5. Why does this always happen? Is the procedural generation limiting the options so only these regions ever show up in contracts? There's lots of Kerbin out there that goes unused because of this. https://imgur.com/YpFGhHd
  6. Does anyone else get the problem (only happens to me in JNSQ thus posting here) that the game thinks their comms are out of range for transmitting science, even though the ability to control the vessel is fine, the signal widget in the upper left shows a perfectly fine strong signal, and they're able to control the craft with it? It's only science transmission that believes there's no comms connection. Everything else agrees that there are comms connections. And yes my DSN mulitplier is set to 4.01 and my antenna range multiplier is set to 1.01 as the instructions say (or as close as possible to what the instructions say - I have it at 1.01 instead of 1.0 because of the slider widget on the difficulty screen not letting me type a number directly and that's the closest it can get. I did also try editing the persistent.sfs file to force it to be exactly 1 just to see if that fixed it and it didn't. For now I'm enabling the "cheat" of turning off comms when I transmit, then turning them back on. But I'd rather not have to do that if anyone knows how I can fix this problem. EDIT: I just discovered that, weirdly enough, even though this probe cannot transmit its OWN science back home, other probes CAN use it as a relay through which they transmit *their* science back home. Weird. (Perhaps it has something to do with the vessel being packed and on rails when the focus is on some other vessel using it as a relay - i.e. the transmission works when this probe is on rails but not when it's fully loaded into focus.)
  7. I did a bit of googling and I believe this is caused by the older version of the Parallax mod that Beyond Home uses. Parallax was doing some kind of tricks with the terrain that confuses parts of KSP's system. If so, then the bug was fixed in a newer version of Parallax itself, but Beyond Home uses the older version that still has the bug. The instructions for installing Beyond Home are *VERY* adamant about installing exactly version 1.0.1 of Parallax and not the latest version, so I don't think there's much I can do to fix this other than to hope a Beyond Home update eventually happens that moves the dependency to a newer Parallax.
  8. Has anyone run into this problem before? The stock KSP API call vessel.heightFromTerrain is giving the wrong answer for me in Beyond Home on planet Verna. (i.e. the AGL is being returned as equal to the ASL). Example: Landed base on Verna, Clicking the sea-level altimeter (blue wavy lines button) shows 1294m, And Clicking the terrain-level altimeter (Green mountain button) shows 2m. In this situation vessel.heightFromTerrain SHOULD be showing the 2m number, but it's returning 1294.93977. Because of that wrong answer, I get the following bug symptoms: - Parachutes on planet Verna refuse to ever full-open. They will partial-open (triggered by atmo pressure) but will never go from partial-open to full-open (triggered by altitude above terrain), resulting in a smashed lander. If I set the chutes' terrain height setting high enough, enough to match the ASL reading instead of the AGL reading, then they will full-open, indicating this is directly caused by the confused API returning the sea-level altitude instead of the ground-level altitude. - Wheels don't work right. I can't tell if this is because of the altitude confusion or not. But they just don't act like they're getting any traction at all, and they spin in place. This could be unrelated, I don't know. But the same design of base station with wheels drives fine on other worlds like Lua and Rhode. - EDIT: Additional effect- EVA kerbals instantly go into "ragdoll" mode when I leave the capsule and try to walk on the surface. My controls are locked out and they refuse to respond, slowly sliding along the ground. - As I was playing using kOS, I decided to have kOS print the ALT:RADAR( which should always match the in-game terrain altitude), and it prints the SEA LEVEL altitude, not the terrain level altitude. Any kOS scripts using this end up doing the "wrong thing". This is where I traced down the problem being that vessel.heightFromTerrain is giving the wrong answer, as that's what ALT:RADAR is reading. Presumably the chutes are reading the same thing which is why they have the same problem. I never encountered this problem before I went out to Verna, which is the first planet of Kerbol I tried landing on. When landing on the closer-in bodies that didn't require heading out to Kerbol, things were still working fine. EDIT: Further testing, where I just keep printing out the diff between alt:radar (AGL altitude) and altitude (ASL alttitude), I found that while *in flight* above the ground, it would sometimes be correct (AGL and ASL differ) and other times be incorrect (AGL and ASL look the same), and it would keep toggling back and forth between being right and being wrong. It would be right for a second, then wrong for several seconds, then right for a second, then wrong for several seconds, then right for several seconds, etc. This feels like race condition behavior. As if something (maybe in Kopernicus) needs to keep over-riding a value again and again, and it comes out wrong only when that step doesn't happen "first" like it needs to relative to other things.) Note, once I landed, then it was consistently wrong all the time. (and wheels don't work right, making it impossible to take off again as they always vibrate and "jam".) When I was flying above the ground in a jet, then it was wrong only *most* but not *all* of the time, exhibiting that race-condition-like behavior. EDIT EDIT: I should point out that the stock GUI altimeter at the top of the screen was always doing things correctly, where ASL and AGL differed all the time. Even when the API call vessel.heightFromTerrain was wrong, the GUI still showed the right answer for some reason.
  9. I don't know. It sounds like a question for the Kopernicus dev. I have no idea when the change was first introduced that started making scatter levitate (Where none of the recent changes after that to fix it really seem to fix it). It would depend on when that change was relative to when Koperinicus was updated to 1.12.2.
  10. The problem with trees and scatter rocks levitating in midair: Recent Kopernicus changes have this bug: @BlackEyedPhantom I got it to work (I think - it's hard to prove it's fixed just because it stopped happening, since the problem was intermittent in the first place.) tl;dr:: Use an older version of Kopernicus. Instead of getting the latest Kopernicus release that CKAN claims works for KSP 1.10.1, get whatever Kopernicus release existed *on the date when Beyond Home happened*. That will be the version as it existed when the author of Beyond Home was testing things and released Beyond Home. Apparently Kopernicus started having this floating scatter problem a while ago, and the most recent changes in the last few months *claim* to have fixed it, but they don't entirely fix it and it's probably dependent on your computer performance whether you still have the problem. I had a brief eyeball scan of Kopernicus's code and it seems to have something to do with the when Kopernicus creates and positions scatter objects versus when KSP populates the final fine-grain terrain polygons. It seems to sometimes be picking where to put the trees based on a low-res approximation of the terrain, before the fully populated terrain is loaded in. At any rate, whether I'm right or I'm wrong about the actual cause, an older Kopernicus seems to fix it for me.
  11. At any rate it can kind of be a problem with using airplanes because the midair trees often get in the way of takeoffs and landings (i.e. a levitating group of trees 50 meters in the air at the end of the runway). Also, when I have this problem it sometimes spawn trees right IN the runway. Even when the trees are on the ground, they're often not avoiding the runway space like they should. It feels like the trees are basing their position on a false notion of where the terrain is. They're either using terrain from the wrong position (i.e. "let's put this tree on the slope of that mountain over there, oh wait we placed it 30 kilometers east of the mountain where the terrain is flat"), or they're maybe using the wrong notion of what the body looks like, like maybe using the stock version of what would be on Kerbin at that lat/lng instead of what would be at Rhode at that lat/lng? I have no idea but it's bizzarre.
  12. I have almost the same problem, but for me it happens right away, at Rhode, near the start of the game. KSP 1.10.1. BeyondHome 1.4.0, installed via CKAN, telling CKAN to only grab KSP 1.10.x compatible versions of things. And yes, I have terrain detail on high. Here's two screenshots: https://imgur.com/a/BWBGO83
  13. "When saving them in drive 0" from kOS or from outside the game in some file manager or text editor? I believe when kOS *reads* the files it can accept them without mentioning the .ks but when *writing* them you need to explicitly include it. When in doubt just state it explicitly. Also, if you are on Windows, be aware of the secret trap where the default settings for its file manager window actively lie to you about the filename by hiding the extension portion of the filename. If you are on Windows, then in Windows Explorer (the file browsing window), open the folder Ships/Script and click folder options in the top of the window and then "view" and there should be a checkbox that hides extensions. It's turned on by default and you need to change that so it will stop hiding the true filenames.
  14. "Why" as in "What is the mechanical difference in how the game implements them?" or "Why" as in "What was the reason for choosing the implementation that has this limitation"? I can answer the first, but the second is harder as that requires dev insider knowledge. The mechanical difference is that Gilly, being a moon, is modeled as a kind of CelestialBody, while asteroids are a type of Vessel, much like flags are a type of Vessel and Kerbals floating in their EVA suits are a type of Vessel. The game does not calculate the effects of a vessel pulling on another vessel due to gravity, since most of the time a vessel's mass is so small that the effect isn't worth the computing time it would take to bother. Also, when you go into time-warp mode, the game doesn't *really* use Newtonian gravity from a celestial body to pull on the ship anymore, it instead just uses Kepler's ellipse formulas to decide where along the orbit path the vessel would be at time=t. To do that in the stock game model requires that the body you are orbiting be your sphere of influence center point. So that answers the first kind of "why". As to the second kind of "why", now I have to speculate about what was in the dev's heads. But I'll do that. I just want to throw the caveat that at this point I'm trying to read their minds and this is not definitive: So here goes: To do gravity with asteroids using the stock system, those asteroids would all have to be modeled as tiny planets with their own little spheres of influence. The sphere of influence model really breaks down at that point, as you have to be SUPER close to the asteroid before it's gravity is strong enough to treat it like its own little pocket reference frame that ignores perturbations from the sun. I suspect they didn't bother because it's an organizational mess to have that many asteroids being modeled as planetary bodies instead of as vessels, especially when for the smaller ones their spheres of influence wouldn't even be above their ground altitude. Imagine if it treated them as planets what the map view would look like with all those little orbit lines. I think before it becomes even possible to do it well, the game would first have to leave behind the sphere of influence model and use an N-body model like Principia mod does. And a change like that is *massive* and breaks some other parts of how the game is meant to be simple for players.
  15. Update: I found a way to identify which of the thrusterTransforms are actually present in the current part variant and which are not, so I made a PR about it.
  • Create New...