steve_v

Or someone has a dynamic IP and just gets this crap inflicted on them randomly because "oh noes, suspicious activity". CAPTCHAs are nothing more than webhosts trying to roll out "protection" for their sites for zero effort on their end. Can't be bothered culling bot accounts or binning spam? Use CAPTCHAs. Too lazy to set up a proper password policy? CAPTCHA on the login page. Don't want to deal with disgruntled customers? CAPTCHA on the ticket system too... Extra points if it's so hard they give up without posting. They're not particularly difficult to thwart, and I personally find it extra delicious to use google's own speech recognition tech to do so.

Ahhhhh! My eyes! It Burns! This new theme is horrific, please put it back. On that note, preferably back to pre-IPS - where we had an editor that worked, a UI that doesn't need a bunch of element blocking rules and script hacks to remove all the annoyances and pointless animations, and the thing didn't cripple mobile devices with the pointless "infinite scrolling memory consumption" type activity page.

Both spellings catch that thread for me, as both spellings appear in it. The 'murican version lands at the bottom of the page though, as it's not the spelling used in the title. Taking the most common search engine in the known universe (google) as an example, it really isn't. Google behaves exactly the same as the forum search, and only matches because there are some posts to that thread that misspell "colour". "Textures Unlimited Recolour Depot" site:forum.kerbalspaceprogram.com" matches on the thread title, while "Textures Unlimited Recolor Depot" site:forum.kerbalspaceprogram.com matches a post on page 50. IMO, if 'muricans want to randomly drop letters from the Queen's English, that's their concern. The thread author uses "colour", so that's the correct spelling in the context and the spelling one should use to search for it.

...You would be completely misunderstanding what I said. "Move the main gear closer to the CoM so you can rotate easier" obviously doesn't apply to a taildragger. A taildragger with the rear wheel not at the rear is, frankly, kinda ridiculous. It's neither a "conventional" taildragger nor a "modern" tricycle layout, and it would include the worst properties of both for no real benefit. My point was that if you were to convert your design to a tricycle layout (ya know, with the single steerable wheel at the front and the two main gear just behind the CoM), you'd have a craft that sits level on the runway, doesn't try to faceplant under braking, has overall better ground clearance... and needs careful handling to avoid tailstrikes - tailstrikes that would be much easier to avoid if you swapped out that tail connector for the raised one. That's "careful handling", not "a no-go". As evidenced by the now multiple reports of successful flights with very minor modifications to the OP's (second) craft, going to a completely different gear layout wasn't required. In fact the only situation I would consider a taildragger to be the optimal solution is where you absolutely need that extra ground clearance for a big propeller up front. Good advice for a spaceplane (though you can land a lot faster once you get the hang of it), but for a trainer/science gatherer, which is kinda what you're building, I'd try to land as slow as possible. Controlling your horizontal speed in stock aero is extremely easy as any hard manoeuvring will create vast drag - as will deploying gear or opening cargo bays. Figure out what your stall speed is (by trial and error), then add ~15m/s and use that as a target for sea-level landing. I suggest a combination of watching the vertical speed part of the altimeter and your shadow on the ground to judge vertical speed, and trying to keep it under 5m/s as you touch down. The lower your vertical speed the less suspension jank and random bouncing you'll need to deal with. Apply brakes only when on the ground, and keep wheel steering locked unless taxiing. For reference, my early career aircraft can generally land at <60m/s, which also happens to make doing those rough terrain science gathering missions without parachutes viable. If you stall before that, I'd suggest adding more wing.

Odd all those real-world aircraft (and pretty much every design, delta or otherwise, I've ever flown in KSP too) manage it then, isn't it? Avoiding tailstrikes with tricycle gear is simply a matter of ensuring you have sufficient clearance for the AoA you need at your design V1 speed. This is one of the reasons almost all RL aircraft have a raised tail, and exactly what the type-b tail connector is for. Trading up those fixed gear for something not borderline-unusably-horrible would also help. Between the stumpiness and the janky suspension, I consider those the two most useless and rage-inducing parts in the entire game. Sure, you could just build a taildragger... But then you are trading a tailstrike problem for a faceplant problem. Thankfully KSP doesn't also have the visibility and passenger comfort problems, which are the real reasons taildraggers are less popular than they once were. That design you have there could just as easily have tricycle gear and achieve the same AoA without a tailstrike anyway... So long as one isn't completely ham-fisted with the control of course.

Or Is as close as you will currently get AFAIK.

Citation needed. Meh, not that far off a GTX295, GTX480 or Vega64 though. Performance per watt actually looks quite respectable. Given the shambles of a launch, not all that surprising. This sounds like a power delivery/board design issue, and there are very few cards in the wild so far. By the time normal people can buy one this will likely be sorted. Maybe. Personally I'm not ready to attribute complex motivations to something which can be adequately explained by garden-variety incompetence and bureaucratic bungling just yet... If and when the fabled Navi2 actually makes an appearance and gets some benches in, that'll be the time to make educated guesses.

I know what FMOD is, but I've not seen that error before. Probably. For the logs:

Yeah, pretty much the same CPUs but with a slightly different socket to make them incompatible with desktop parts. The usual Intel "make Xeon special" shenanigans. Plus the coolers mount to the case rather than the board, so you have to break out the machine tools to fit them in a non-server case. I know, I've been there. LGA2011 is a far more sane proposition.

Not while moving, no. The tooltip (or wiki) doesn't say anything about recharging while also running the motors, and the system check said everything was fine... If "use batteries" means to use batteries at night when there's no solar power, the craft would have to stop to wait for sunlight. I assumed it would also stop to wait for recharge, as that would be the logical behaviour. You're right on that option being the reason for stopping though. IIRC I only turned it on because the rover stopped, the message said "insufficient power", so I said "use batteries while they last then, just move already". But then that was all masked by the NRE stopping BV anyway. The joys of dealing with two problems at the same time. There is, but that reason is simply "insufficient power", not "insufficient power to drive and recharge batteries at the same time"... The "system check" tells me that there is sufficient power for a reduced speed even with "use batteries" on, so confusion ensues. Regarding that exception, I can't reproduce it now in my main install. It's either caused by some unknown thing some other mod did at some point in that session (what fun that'll be to find), or it's a symptom of the same old memory leak that makes the game wig out in weird ways after it's been running a few hours. KSP was sitting at 24GB resident at the time.

If I limit myself to PC only, and just what occurs to me off the top of my head (i.e. refusing to look at my archive): Doom & Doom 2 (plus zillions of user WADs)* Heretic Hexen Strife Quake Marathon trilogy Descent 2 Freespace 2 Warcraft 2 Total Annihilation* Carmageddon* Baldur's Gate*, IWD etc NWN & NWN 2 Diablo & Diablo 2 MOO & MOO2 Homeworld & Homeworld 2 ... *Played in the last month. TBH, next to the gameplay of the classics, I find most modern games and their shiny graphics end up being a bit forgettable.

Router yes, webserver yes, VPN... Maybe. The crypto load for a decently fast VPN server is non-trivial, and I bet the RPi CPU would bottleneck throughput, especially as (AFAIK) it lacks AES-NI or any other acceleration.

I get an involuntary twitch every time I see a tower case sitting on a carpeted floor. 32nm covers everything from Westmere through Sandy Bridge, and you most definitely want the latter. The old LGA771 Westmere (AKA Nehalem-C) machines are dirt cheap now, but they're power hogs and have DDR2 RAM and very special cooler mounts. The "v2" bit confuses me slightly, I'm guessing you mean E5-xxxx v2, which is a 22nm Ivy Bridge EP (LGA2011) part. $100 is a steal if that's what they are... I can personally vouch for the Supermicro X9 series (say a X9DRL-IF) and something like the Fractal Define R4 making a very nice, very quiet ZFS NAS box. If you're just hosting some blog pages, sure. There are other (and more CPU/RAM intensive) uses for a server than that though. As mentioned, my primary home (file/web/VM/various other stuff) server is a dual socket (16 physical cores @ 3.1GHz) Xeon with 64GB RAM. Can't really do that on an ARM based SBC. Nor can you realistically connect 16+ HDDs to one... RPis are cool and all (I still have a Mk1 around here somewhere), but they're more hobbyist toys than real servers IMO, and too slow or I/O limited for a great many applications.

Craft (requires Breaking Ground and Near Future Exploration, has clipping problems without ReStock). Save (may contain cruft from removed mods).

The Xbox 360 was an essay in why finalising the trendy case design before the internal hardware is a terrible idea. MS managed to create a product that was both excessively loud and excessively hot, the result being one of the worst reliability records of any console in history. Apple was obviously asleep during this class, and are still making machines that prioritise case design over functionality... Paradoxically, people are still buying such products. Once upon a time, the entire CPU heatsink/fan assembly fell off my: ... And absolutely nothing happened. The thing ran like that for at least a week before I noticed (basement dial-on-demand router and voice-to-email answering machine). Guess those glacial MP3 encoding jobs were infrequent enough to not crash it, or the basement cold enough. Ahh, the all-in bass-ackwards rookie cooling configuration. A true classic. Honestly, I don't understand how people (even some "professional" system builders) manage to get cooling so completely wrong so often. Fans all facing in. Fans all facing out. CPU cooler opposite case airflow. No case airflow. Fans to nowhere. Bottom intakes with no case feet. Common sense does not seem to prevail. Air goes in at the bottom, out at the top, hot things are in between. Simple, no?

In a datacenter or dedicated server room, that kind of thermal engineering is highly effective. For home use, the answer is a realistically sized chassis and reasonably quiet (read "large diameter low RPM") fans. In both of those situations it's extremely rare to see any CPU above 70C (Tcore), even under continuous full-load and less than ideal ambient. Laptops and portables on the other hand often run at 90+, because manufacturers consistently overstate performance and underengineer cooling solutions in the name of form factor. This would be fine if they also tweaked the system to throttle at sane temperatures... which they consistently don't. So when you actually use that advertised performance, they cook. Take one surplus Supermicro ATX board. Remove insane CPU coolers and replace with 120mm towers, Noctua fans and custom mounting hardware. Place in "silent" desktop mid-tower case. Profit. 64GB ECC RAM, 2x 8-core 3.1GHZ Xeons, 8x 3.5" and 8x 2.5" HDDS (~40TB total), all in a package quiet enough for a bedroom or HTPC (Xeon box #2). The joys of scrounging ex-server parts to take home... Thermally limited burst performance certainly has it's place, but if that's what you're going for you need to take continuous load scenarios into account as well. Personally I blame Apple for starting and perpetuating the thinness wars, it's got to the point that it's extremely difficult to find a laptop with competent thermal design at all, let alone a reasonably priced one. A Macbook Air is a bad idea in general. Pretty much anything not-Apple will have better thermal and power management for the same price, because you're not paying for the hipster appeal. Say what you will about innovation and all-American design, Apple have a long history of terrible thermal design, fragile products, and liquid-poor serviceability. If you really want rackmount, you're kinda screwed. The only place you're likely to find 3.5" bays is in a 4U server, and those tend to be either very expensive or very old. The industry loves density and all that. Otherwise, see above regarding supermicro ATX boards and non-server cases/coolers. Maybe hit up ebay for ex-server parts and roll your own? Hell, for a router you don't really need server-grade hardware at all, just slap a couple PCIE NICS in any old post-2012 board. FWIW, my home router is one of these. I wouldn't run PFSense on it though, the BSD intel NIC drivers suck donkey balls. IPFire does gigabit routing/firewalling on it with ease, but VPN at that bandwidth will obviously require more CPU. I tried to like PFSense, but performance really does suck when compared to a GNU/Linux based router distro, at least on low-power hardware. So does the non-journaling non-power-failure-tolerant UFS filesystem it uses, though I hear it can do ZFS too now... at the expense of even higher system requirements.

With only BV, NFE (needed to load vessel), B9PartSwitch, and ModuleManager installed, I no longer see that NRE. The behaviour I enquired about remains: "Rover stopped" message appears immediately upon switching away from the craft, no progress is made. KSP.log Player.log I'm still investigating that log error I posted, it does appear to be a mod interaction.

Excellent. Makes an otherwise pretty crappy probe core useful. I do, though I was kinda hoping you'd get enough from the log to avoid all that. I'm not running any mods I haven't successfully with BV before, but if that's what it takes then that's what it takes.

The only thing more obnoxiously loud than a 2U cooler is a 1U cooler... But it's a Dell, isn't it? Ick. Supermicro all the way.

Sweet music it is CPU1 Temp | 60.000 | degrees C | ok CPU2 Temp | 60.000 | degrees C | ok System Temp | 51.000 | degrees C | ok Peripheral Temp | 47.000 | degrees C | ok PCH Temp | 56.000 | degrees C | ok P1-DIMMA1 TEMP | 58.000 | degrees C | ok P1-DIMMB1 TEMP | 54.000 | degrees C | ok P1-DIMMC1 TEMP | 52.000 | degrees C | ok P1-DIMMD1 TEMP | 55.000 | degrees C | ok P2-DIMME1 TEMP | 55.000 | degrees C | ok P2-DIMMF1 TEMP | 59.000 | degrees C | ok P2-DIMMG1 TEMP | 60.000 | degrees C | ok P2-DIMMH1 TEMP | 59.000 | degrees C | ok FAN1 | 2850.000 | RPM | ok FAN2 | 2850.000 | RPM | ok FAN3 | 1950.000 | RPM | ok FANA | 1200.000 | RPM | ok FANB | 1200.000 | RPM | ok A pair of 92mm Nidec UltraFLOs at 2850RPM is, uhh, moderately loud? Flat out at 3800RPM is... Louder. Never seen it get there though. Still pretty quiet for a dual-socket server though, the 2U coolers I took off it rev to 8400RPM... Ed. 550W, without a GPU in sight... welp. My power bill will love me.

Pretty sure it's just the included BV controller part, the probe core is an octo, and I haven't patched it for BV nor does it show in it's PAW. On closer inspection, I see: [LOG 06:15:19.114] [HighLogic]: =========================== Scene Change : From FLIGHT to FLIGHT ===================== [LOG 06:15:19.127] Camera Mode: CHASE [LOG 06:15:19.128] [ApplicationLauncher] SetVisible: [LOG 06:15:19.132] ScaleModList: listSize 410 maxListSize 573 [LOG 06:15:19.132] ScaleModList: listSize 410 maxListSize 573 [LOG 06:15:19.132] ScaleModList: listSize 410 maxListSize 573 [EXC 06:15:19.146] NullReferenceException: Object reference not set to an instance of an object BonVoyage.RoverController.Update (System.Double currentTime) (at <32eb7dad6e444dd78672072e1a996b3c>:0) BonVoyage.BonVoyage.Update () (at <32eb7dad6e444dd78672072e1a996b3c>:0) UnityEngine.DebugLogHandler:LogException(Exception, Object) ModuleManager.UnityLogHandle.InterceptLogHandler:LogException(Exception, Object) UnityEngine.Debug:CallOverridenDebugHandler(Exception, Object) [LOG 06:15:19.300] -INFO- Tac.LifeSupportController[FF847CA2][20014.08]: OnDestroy So something is borking. Full log here.

Yes. No. No. A "blue screen" (or BSOD) is a generic term covering a multitude of fatal Windows errors. Don't be ridiculous. Why should a game, of all things, nanny broken hardware? Monitoring hardware is the job of the hardware monitoring ASIC or microcontroller (like this one), and sometimes the OS or BMC. Individual applications have neither the need nor the privileges required to access or control hardware limits. Monitoring hardware temperature isn't the applications job (and would mean including drivers for a multitude of systems), and changing hardware limits or cooling targets would require interfering with the BIOS or CPU microcode, which no game could or would even attempt. Now you're really grasping at straws... And you should probably quit while you're ahead well, something anyway. My overclocked and still perfectly operational machines might beg to differ, a couple of them are going on 20 As long as you're not pushing silly voltages or running silly hot, overclocking is just "re-binning" the CPU anyway.

Is it intended that a rover with insufficient power generation to drive continuously (but plenty of battery) stops immediately on scene change? The "Insufficient power, average speed reduced by x%" message in the control panel suggests that the average speed will be, well, simply reduced. As in, not zero. Yet I get a message stating the vehicle has stopped, and the controller shows as "idle" as soon as I switch away from it...

Hardware problem. Hardware problem. Hardware problem. Still not seeing what this has to do with games or any other application, and as I said, I'm done arguing about it. If you want to continue believing that your shoddy or ill-maintained hardware dying on you is somehow the fault of a game developer, you're welcome <snip>

I'm done here. TBF I probably shouldn't have let myself get sucked into this old argument to begin with, it's one of those myths that get regurgitated in "gamer" circles fairly regularly and it seems to yank my chain every time. KSP may have 99 problems, but damaging hardware isn't one of them.