-
Posts
3,438 -
Joined
-
Last visited
Everything posted by steve_v
-
Personally, I'd do it the other way around: Copy your mods into a fresh, updated stock install, i.e a copy of stock that steam has updated.
-
On the topic of the fallout series, I found Wasteland 2 to be pretty good. Doesn't tick all your requirements though, as you will probably die fairly quickly without a party...
-
Nukes, boss, Nukes. Doable in FAR, used to work in stock and probably still do. Tricky to design around the low rocket TWR though.
-
While the last round of updates did indeed beat the aero model into shape (and I'm fairly happy with it, but will continue to use FAR), the new thermal system introduced with 1.03 still appears to have a few bugs. I'll be happy with it when random things stop exploding and cargo bays work as expected. Bring on 1.0.5, but no more mucking with aero please. - - - Updated - - - And VirtualGL streaming on GNU/Linux has worked since day one, no steam required
-
Ahh, I thought something like this was going on. I take it this is related to (or the the root cause of) the mystery malloc failures on OSX, even when KSP itself is well within the address space limit?
-
While that is generally true, pouncing on anyone with a complaint or telling people not to call attention to bugs or disruptive emergency updates does nothing constructive whatsoever.
-
Oh, that FHS. Thought it applied more to filesystem layout than filesystem selection and partitioning, but I guess it applies there too. I'd recommend Debian also, If you stick with the stable release and Don't Break Debian (this applies to most Debian derivatives too), even a total noob should be fine. The forums can be a little scathing if you aren't willing to read the documentation first... but that is what it's for after all, and it's pretty complete.
-
This I too have noticed. Anything pointing the finger even vaguely in Squads direction is pretty quickly pounced on and there's no way to tell whether it's "Squad can do no wrong" personal opinion or something more official... Very proactive with the glowing praise and sidelining of bugs, not so much with the divulging of actual information as to what went wrong or why certain decisions were made. If that's a personal stance, cool. If not... I'm discussing forbidden topics. From a players perspective, modders are indeed a "special breed" worthy of more consideration, simply because they provide what the community wants and Squad has not (yet) provided. I would have stopped playing some time ago were it not for people like Ferram filling the gaps in the stock game.
-
I'm guessing the issue is the lack of ackermann steering, in that the multiple pairs of wheels all go to full lock, rather than following the curve of the turn. There's no real solution at this point except: Use less wheels, or put up with the skidding and poor steering. Locking steering on the middle sets of wheels helps. Ackermann steering is coming with U5, apparently. For towing (and mods), KAS/KIS has winches and tow cables... You'll have to experiment as to see whether they're a help or a hindrance in this case though.
-
Unless something has changed (I have no windows to worry about these days ) "Install Windows before Linux if on same disk" was standard procedure. Pretty well all modern GNU/Linux installers will offer to resize Windows partitions to make space for install' date=' and will detect most other OSs, setting up chainloading of the existing bootloader from GRUB for you. Windows, by contrast, makes so attempt whatsoever to co-exist with other operating systems. It will simply overwrite the boot sector with it's own code (which cannot boot Linux) [i']without prompting. This will render an existing GRUB/Linux (or any other non-MS OS) setup unbootable until you use a live disk to fix the bootloader. My advise is: If you have any non-MS OS installed, unplug every drive you don't want trashed before running the Windows installer. It won't ask to preserve an existing OS, won't allow you (without some hackery) to install on a secondary drive or non-primary partition, and simply bulldozes anything already on the disk. But yeah, a dedicated disk for GNU/Linux is the better plan, assuming you have one available. On a laptop this is obviously not an option. Also, what on earth is "format partition to FHS"? Multiple partitions for GNU/Linux is a good idea: It allows you to put the swap (pagefile in MS land) on it's own partition so it won't get fragmented and can be positioned on the fastest part of the platter. Splitting out /home to it's own partition allows you to wipe and re-install or upgrade the OS part without touching your personal files and settings. A partition for /boot is for the same reason MS does it - so that you can still get to the bootloader if your OS partition gets trashed somehow. None of these reasons are all that critical anymore, swap won't get much use if you have 8 or more GB of RAM, and you can use a file like MS does if you want to. Likewise /boot and /home can be part of / if that's more convenient for you. FOSS is, in part, about freedom of choice after all. As for "make proper partition of HDD for Linux" all of the above rambling about partitions is largely irrelevant unless you have special needs - the installer will usually handle it all for you. Yeah, that. Hardware vendors must always provide support for Windows, as it comes pre-installed on the majority of PCs. 90% of the hardware support in the Linux kernel is, by contrast, developed by the Linux kernel devs with no help at all from the hardware vendor. Arch is awesome, but it's also more work to set up and maintain than a Debian or RH based distro due to it's inherent 'rolling release' bleeding-edgeness. I'm surprised no-one suggested Gentoo
-
Overheating RTG's and batteries
steve_v replied to xtoro's topic in KSP1 Gameplay Questions and Tutorials
Yeah, and not just RTGs either. The issue is due to another shortcut in the heating system: Parts can't radiate any heat at all when in a cargo bay. Why one would do this I don't know, physics fail. Parts in a cargo bay should radiate, heat be absorbed by the bay walls and re-radiated out into space, possibly via external radiators. Disabling radiant heat in a closed cargo bay is just stupid. Considering the number of "illogical heating / exploding" reports coming in, I guess we'll have to wait for yet another emergency patch for a poorly tested system. This is getting ridiculous. -
1.04 Patch if you unluckily decided to buy at GOG (or even 1.03 ?)
steve_v replied to Sirad's topic in KSP1 Discussion
According to this, the patcher is borked and has been for some time. Also from the same "official" post: But I can't verify the GOG bit. -
I wasn't totally serious on that one TBH. But I have been known to do it to hardware I didn't care much about... or was actively trying to kill. Without success I might add. The layer of metallic grinding dust and drill swarf on my "carpet" (or what was once carpet) probably contributed to the survival rate too.
-
Good to know that is. I patch MechJeb into the command module, so I haven't seen that one. 'tis pretty easy to test though.
-
Nvidia forced AA & AF (via the driver control panel) works fine for me, always has.
-
Yeah, having developed the habit of regularly grounding myself - one hand on the backplane/chassis I've never zapped anything. Your work environment also makes a big contribution to the ESD risk, nylon carpet, relative humidity etc. Handling cards by the edges / brackets is a good idea too. And don't put your new mobo down on the carpet without at least some conductive plastic under it
-
Chrome blocks KSP 1.0.4 download.
steve_v replied to Bioman222's topic in KSP1 Technical Support (PC, unmodded installs)
Google is evil, didn't you know? They're probably just doing it to annoy you. Either that or it's another idiotic "users are stupid" feature... -
The last few updates are exactly what I'm referring to. Prior to the 1.0 release/price hike/bug injection cycle I was patiently waiting for bugfixes and a performance/optimisation pass before leaving the beta phase. I would have been fine with waiting another year or more if that's what it takes to fix all the bugs. It didn't happen, in fact quite the opposite. If Squad had released one stable, mostly bug free "1.0" release for those who expect to be able to play through it like a complete game, that would be fine. Make the "testing" version an option for those who like to live on the bleeding edge, but don't break everyones game within weeks of release. Repeatedly. It's really not cool, and it doesn't bode well for future development. - - - Updated - - - Not all the issues, after all no plan survives contact with reality intact. Just ask the really bleedingly obvious questions early, like: "We are making a sandbox physics sim, with a huge gameworld, can we do this in a reasonable fashion with a game engine that has an already outdated, single threaded physics implementation?" Or: "We envisage our universe to be <this> big, can we do the math and fit the textures into ram on a 32bit platform? maybe we could load textures on demand, does the engine support that?" Squad has been fighting the limitations of Unity since day dot. The time to switch has been and gone, but it's certainly not an unforeseeable situation we're in now.
-
You phrase this as a good thing, but a need then arises to either have both hands on the KB, or grow quicker fingers. Tapping space is a wee bit easier than shifting to the other side of the keyboard after all. It also prevents the use of RCS thrust for stabilisation... as IKJL are the RCS translation keys, and putting WSAD into translation mode kills the wheels. What's the cunning plan for this scenario? If it's intentional, it might be worth updating that wiki. OTOH, the changes to docking mode had no need to disable wheel steering, it's completely unrelated. Especially since wheels can now have their own keybinds. So It certainly still feels like a bug to me.
-
An old KSP player needs yor help!
steve_v replied to manuelasa1999's topic in KSP1 Gameplay Questions and Tutorials
Reason: IIRC it causes graphical anomalies on Intel GPUs. And doesn't work anyway. -
Yeah, in some bizarre inversion of reality, here's a game that has more going for it on GNU/Linux
-
Hear hear. I'm pretty sure everyone loves mods Just remember that they're all gratis, and the authors are doing support of their own free will. Do not antagonize the modders, lest the modders go away and we all suffer.
-
There is one other small issue I have encountered... Ensure you start KSP from the KSP base directory. Steam should do it for you, but if you make a shortcut to the binary ensure you set the "working directory". Not serious, but it breaks mods with native libraries, and can cause some files to turn up in odd places. Other than that, pick the most favourable answer to all your questions and you'll be right on the money Also check out The Linux Thread, and The Other Linux Thread as the OP in particular has a bunch of useful info. - - - Updated - - - LC_ALL is only needed for certain locales, specifically those that swap '.' and ',' in numerical fields. (Unity, please fix) But it shouldn't do any harm. That (old) phoronix article isn't exactly a glowing review of threaded optimisations... YMMV on that one. For me it makes zero real world difference.
-
Sure, patch the bugs. But if they didn't slip through testing in the first place this whole scenario is neatly avoided. I boycott Adobe on all levels, for this reason and several others.