Jump to content

steve_v

Members
 View Profile  See their activity

  • Posts

    3,438

  • Joined

  • Last visited

 Content Type 

Everything posted by steve_v

  1. steve_v
    Every time? Intermittent flooding of the KSC is an old scatterer bug, AFAIK nobody is sure exactly what triggers it, but it's purely cosmetic... and reported to be fixed a while back (v0.0324?). Modlist?
  2. steve_v
    Is there any way to permanently disable the "parachute is in fairings" limitation? I'm running FAR so the stock aero shielding is somewhat irrelevant, but I keep getting this if I place radial chutes too close to engine shrouds or cargo bays. I can remove the shielded state from the save file with sed, but it's a bit bothersome when I'm in the middle of landing a spaceplane and my drag chutes refuse to deploy... I don't see a shieldedCanActivate or shieldedCanDeploy line in the part configs as I do with engines & landing gear, is there something similar for RealChuteModule that I can get at with modulemanager? KSP 1.3.1 & RealChute 1.4.5, FWIW.
  3. steve_v
    Probably better to ask in here: Is 143MB... TL;DR.
  4. steve_v
    Eh? speak for yourself, I really don't care if kerbals are male, female, or androgynous. I don't care what they eat, where they crap, or why their planet is so inexplicably small either. They're Kerbals. Like Tribbles, but more green. None of this mattered in alpha, why does it matter now? There are far more important things to work on than arguing over the supposed gender equality of fictional and largely unexplained green toons. I guess it's a nice bit of variety that there are now two kinds of kerbal, but they're functionally identical. This is not an RPG and there's no reason to identify with the cannon rocket-fodder, so why do we care? Perhaps we should just introduce a third type and give them some less human names, then this irrelevant distraction can go away and we can focus on things that matter... like bugs and half-finished game modes. I'd neither noticed nor cared, TBH. They're just random animations to make it look less bare, I don't think I've ever looked at them closely. It'd be nice if the creature in mission control would quit with the annoying noises though.
  5. steve_v
    No. I'm not any kind of "'ist", and I don't much care what year it is. We have enough starting kerbals as it is (one too many of which are named after real astronauts), any more will disrupt gameplay progression. Any further kerbals generated for hire are of randomised gender. The original 3 are artefacts of early game development, when there was exactly one kind of kerbal. Nobody needs to "equalise" them to appease some real-world issue, it's a game and these are fictional little green aliens. If you really want to give your aliens specific human names, there are ways to do that. As kerbals-for-hire, perhaps. As starting crew, you loose an element of gameplay progression - available crew being limited by available funds. With 6 for free, I'd not need to hire any at all until late in the game, when the cost doesn't matter. Meaningful decision lost. 4 is too many already.
  6. steve_v
    Yes, and no, not if it's what I think it is. Install Memgraph and see if it's the well known garbage collection problem. Indeed, this is what kills my career games. Fixing it is in the "too hard" basket though, as it's a game engine problem.
  7. steve_v
    Amen to that.
  8. steve_v
    Further down: From the bug report: TL;DR: No, the workaround listed on the Unity forum doesn't work. Not for Badsector, and not for me.
  9. steve_v
    I am quite calm. The bug is set "investigating" not "need more info", and no comment WRT to reproduction or affected systems has been made there, from which I read they're not looking for more info. If they were, I'd gladly provide it. The Arch wiki is not particularly relevant for Gentoo or Debian, the two systems that I have reproduced this on. However, sdl2-jstest works perfectly with my device on both, and I fixed permissions on the input device long ago. ed. I can now add Artix to that list as well. I began as accepting and patient. Patches came and went, no mention was made. My patience has expired. A little bit of (or any) communication would have gone a long way. My complaint is not that this is not fixed yet, it's that there's been no communication and no apparent progress. If I see "We hope to have it sorted for 1.4.4", I'll be happy. Ask me "Can you test [X] and report back" and I'll hop to it. Give me deafening silence, and I'll be annoyed.
  10. steve_v
    That does not prevent SQUAD from adding it, does it? And I'll be happy to help them with that by buying the DLC, after this blindingly obvious bug is addressed. No, but Those ratbuggerers too often are. I'm far more interested in fixing that which should be fixed than appeasing managers, beancounters or marketing departments. Too late, this ridiculous forum software has already attached it Observe the previous iteration of this bug: Set to "confirmed" by SQUAD staff, no updates at all until a user reports that it is fixed, then no further updates for nearly a year, after which it is simply closed. Nobody assigned, no target version set, no indication of when a fix is ready to test... This is not how you bugtracker.
  11. steve_v
    Whoop-de-do, I can filter on target version... What does this have to do with anything? Expectation: Regressions this obvious are dealt with swiftly, or ideally, caught long before release. Expectation: Two patches (one of which made other problems worse) do not go by without any kind of update on basic functionality being restored on one of the supported platforms. Expectation: Restoring said basic functionality takes higher priority for a patch than introducing additional content. Sorted, defined and managed. Not to your liking perhaps, but that's not my problem.
  12. steve_v
    Not really, though it's better than not closing them. Again, for clarity: My point is that no indication is given as to the progress on a bug or in which version it is likely to be resolved. Which results in me being annoyed that there is another patch announcement with serious bugs going unmentioned. In this particular case*, after "investigating" for a month I would expect that someone has an inkling as to when it might be fixed. *Indeed. Note the lack of a target version, any comment from the devs, any official updates at all in the last 30 days, and the arbitrary "20%" set when the status was set to "investigating". Not exactly informative WRT when the game is likely work properly again on GNU/Linux.
  13. steve_v
    Sure, but that's not the same as not providing any status updates on reported bugs. How about a quick "We're working on it" message and setting "target version" to "1.4.4", rather than just setting the status to "investigating" an leaving it at that for eternity? Besides, in other (though generally open-source) projects I have been involved with, direct dev interaction on bugtrackers is not at all uncommon. Seems to work just fine.
  14. steve_v
    It just gets unusably messy, then gets a "cleanup" later on, at least that's what happened last time. I suspect there's another bugtracker that we don't get to see, and select reports are pulled from the public one. It seems like dev attention to the public bugtracker isn't much greater than dev attention to forum bug posts... That'd be cool if it meant they were busy fixing bugs, but ya know, joysticks on Linux. It'd sure be nice if the bugtracker was updated properly, preferably with other useful stuff like target releases and meaningful progress percentages, then I could stop complaining about the "total silence" treatment for certain bugs...
  15. steve_v
    I don't like stock aero, I don't want stock aero, and as much as I like this thread, it's not enough to motivate me to relearn all the unrealistic design habits stock aero encourages.
  16. steve_v
    So long as the engine isn't rotating when the fish strikes, no big deal. Fish are slow. Seaplanes that take off with the engine partially submerged are silly though. IRL you'd never be able start an engine that is full of water, and if somehow you did, that dense and incompressible water would do horrible things to the compressor. Also, awesome thread. I'd enter something, but I've been running with FAR too long to go back to stock aero.
  17. steve_v
    Ahh, so you have those too. While I do care about the environment, I tend to start rolling my eyes when someone self-describes as an "environmentalist". Too many are pushing a thinly veiled alternate agenda or simply woefully uninformed. 80% of those I hear protesting <insert controversial technology> have little concept of how it works or what its environmental impact really is. 80% of those are simply NIMBYs with no useful input at all, beyond "I don't like it" or "I don't trust them". The thing about low quality Chinese made goods is that they are intentionally low quality. The factories that make those budget office chairs will make office chairs to any quality standard you like, and as the (bulk) customer you get to specify how much they are to cost per-unit. If you select the cheap option, you get cheap rubbish. Personally, I've seen both ends of the spectrum with industrial equipment (not reactors, but related technologies). There's cheap Chinese gear, and then there's not-cheap Chinese gear. The quality varies proportional to the price, and the good stuff is actually rather good.
  18. steve_v
    None of which are fixing joystick support on GNU/Linux, unless I am missing some white-on-white text there. What about joysticks on Linux? Are you actually going to fix this? Why the total silence, despite 2 (and soon 3) patches? The relevant bug report has been sitting at "investigating" for a month now with no updates at all, do you need more info or what?
  19. steve_v
    It's totally reasonable to blame the people who selected this Unity release for 1.4.x. Delay the release until the problem is fixed, obviously. If that means waiting for an update from Unity or rolling back to a previous version, so be it. Right now it's looking like we'll be getting an entire release cycle to flush down the toilet, due to engine bugs that should have been caught before anyone committed to basing 1.4 on this unity version. Just like we had with 1.1.x and the "double free or corruption" crashes. Who wants to bet that joysticks being non-functional on GNU/Linux gets blamed on Unity and left unfixed too? Failing to do proper testing and releasing with "unfixable" game engine bugs to meet a marketing agenda appears to be the SQUAD way. So does blaming such things on Unity. Did anyone hold guns to the dev's heads and force them to work with this particular Unity release? No? Then it's not a Unity problem, and the blame rests squarely with whomever decided to roll with a broken engine and release the game regardless. Likewise. Got any clues? SQUAD doesn't appear to have one... I'm also hoping to see some polished releases in the future, but if nobody complains then what we're getting must be okay.
  20. steve_v
    Unless you are running the GNU/Linux build, as usual.
  21. steve_v
    Unlikely to cut it. Install more RAM. You can try running it with 2GB at minimum texture detail, but it will be paging like crazy and that means horribly slow. That bay trail atom CPU is going to be on the slow side too. You have 250GB of Read Only Memory?
  22. steve_v
    Indeed, but one can't see the mess until after buying it... I'll buy the DLC when the regressions in the base game are fixed, not before. Why get hung up on wanting the parts? Mods already provide equivalents, and if you really want the buggy SQUAD rendition, $15 is peanuts.
  23. steve_v
    True. There's that new Telepathy thing, if one can get it to work... I just use Pidgin. Clementine, or Cantata. Agreed, though it's getting usable again in KF5 (if you can tolerate the sematic desktop) now that akonadi doesn't crash every 5 minutes. Dolphin has grown on me, it took a while. I never much liked the idea of the web browser also being the file-manager either TBH. It's the web-browser bit that killed it, just not enough manpower to keep KHTML up to scratch. Meh. I don't see the login screen often enough to care. SDDM works fine. Gwenview. There's still a note app. Lacks those nifty features I didn't know about though.
  24. steve_v
    How so? KDE5 / Plasma is pretty nice (now, early releases were typically buggy), and I don't find It lacking in customisability. Not a big fan of the "sematic desktop" bit, but a recompile fixes that. Gentoo is the king of customisability. It's also one of the few remaining "old guard" distros that still do things the way I like - i.e. no dependency bloat, no "unified experience, fat-fingers noob friendliness over functionality, copy the M$ UI, tablets are the future" new-age shenanigans, no forced systemd / pulseaudio / <insert other software I don't want>, and user-readable text-file configuration. Flexibility and end-user hackability FTW. The devs even get into arguments on the forums. It seems odd to think of Gentoo as "old", but that's what people are calling it. It was the latest shiniest whiz-bang meta-distro when I first tried it. Came back 10 years later, after Debian annoyed me, and it's the same as it ever was.
  25. steve_v
    I don't use Ubuntu, but I've been running Debian (a different variety of apple, but an apple nonetheless) for years without a dist-upgrade going pear shaped. This machine went through 6 releases without a reinstall before I switched to Gentoo (for unrelated reasons). Unless somebody really made a hash of the excellent package manager they swiped from Debian, upgrading shouldn't cause any trouble at all. Just read the release notes and do a system backup first. If you're compiling stuff yourself, put it in /usr/local/ and distro packages will never touch it. Worst case you will need a recompile against new system library versions. Install KDE. Problem solved. Editing the desktop and menu launchers is easy and obvious, as it should be. And it's a "classic" logical menu to boot... None of this touchscreen nonsense unless you want it, it's configurable. There is a big drive for minimalism and hiding all the controls in GNOME, menu bars and window controls are vanishing, hamburger menus and tiles are turning up where nobody wants them. It's horrible and it's getting worse. I tried using a some not-KDE desktops recently (Mate, Cinnamon, GNOME3), and all of them lasted less than an hour due to missing knobs. One can't even modify toolbar entries in any of the filemanagers without digging about in undocumented config files.
×
×
  • Create New...