• Content Count

  • Joined

  • Last visited

Community Reputation

36 Excellent

About DerGolgo

  • Rank
    Spacecraft Engineer

Recent Profile Visitors

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

  1. Again, thank you. For the mod, and for your fortitude in traversing these obstacles, surely placed there by some angry Database God. Sometimes, I do think "MySQL" is not so much a technical term as an explanation, not unlike "My Lord!".
  2. @Lisias, thank you for your great work! Tweakscale is one of my absolute favorite mods. When AVC just gave me the great news, I went straight to GitHub. I'm sure you are well aware that, as of just now, you had only released the source code there, and that you were just about to release the binary. But just in case there was an (entirely understandable and human) oversight, I thought I'd report this "issue".
  3. I was on a Kerbal brake for a few months, basically between 1.6.something and 1.7.3. Now I'm playing again, and find this mode no longer functions. This makes me sad. If anyone who actually knows how any of this works was to revive it, I would greatly appreciate it!
  4. Thank you for your efforts! Output log: ModuleManager.configcache:
  5. Hiya, been having a problem and have narrowed it down (ish) to FuseboxContinued. Not asking for help, just reporting what happened, in case it’s of relevance. @linuxgurugamer, you are a god among gamers, and I’m pretty sure this here mod isn’t really the cause of the problem, but just a catalyst. Some number of mods not playing nice with each other, and FuseboxContinued is just the one that’s making an underlying problem visible. I'm offering this here just in case it's helpful. Situation: new system, new everything, and my very, very, very, very modded, fresh KSP install. All mods latest versions, near as I can tell with the aid of AVC and Spacedock’s subscription thingy. Problem: load game, and see this here (screenshot): Not visible in this shot are struts, which appear in some views (darkened, obviously). Output log for that boot: Removed mod after mod, trial and error, and eventually narrowed it down to FuseboxContinued. When I start the game without it, everything looks as it should (apart from the many error messages). Screenshot: Output log: This is with a number of mods still in quarantine. When I boot the game with all the mods I tell myself I need, so long as I don’t include FuseboxContinued, things appear as they should (with a pile of error messages, obviously, but so long as the game works, I’m cool with it). I’ve jammed all my usual mods back into GameData, and added AmpYear, since I intent to finally play a little now. Just in case anyone cares to see that horrorshow: Screenshot: Output file: Please ignore the errors where ReStock found some unexpected folders. I had tried to manually fix some of the missing part errors earlier. Like I said, not asking for help, it seems to be working (-ish) now, so I’m cool satisfied with the situation (when hell freezes over, I’ll be the one sitting in the puddle of lukewarm water, that’s how cool I am). EDIT: now that I can see all sorts of parts in the editor, I notice the dozen or so other mods that don't seem to be working. So I'm still trouleshooting, just in case anyone was wondering what I don't notice all the stuff what's missing.
  6. Apologies for the threadjack, but after looking over that steak recipe once more, I couldn't help myself.
  7. Woohooo! Thank you, @Nertea! Just one question. When I download Near Future Spacecraft off of SpaceDock, and extract it. In ...\Near_Future_Spacecraft-1.2.3\GameData, there's this image file. Just sitting there, right below the Module Manage .dll. Filename "Oven-Baked-Chicken-24.jpg" Now, I like chicken, oven-baked or otherwise. I'm just a little bit confused as to how it pertains to KSP. Is it space-chicken?
  8. I don't suppose this will work in 1.6.1. Is there an update in the works? Or a viable alternative, a real-solar-system mod for the current game?
  9. The only indication I can find as to how I got them is the folder creation date. All are from the 12th, this month. I swear, I can't even remember ever installing them. Must have just zipped by, thought "Ooooh, shiny!", installed them, and then forgot all about it. The files themselves have no indication of authors in them. The folder names are: TexturesUnlimited_KRE TexturesUnlimited_NearFutureSolar TexturesUnlimited_ProceduralFairings TexturesUnlimited_TundraExploration I've just searched for all four in Add-On Releases. Literally the only result is a comment by @Mecripp, here: No clue whether he is at all involved in the creation of the patch or is just another user (though a happier one than I, it appears).
  10. I had been pretty sure I had installed no such patches. But while I was making that list of folders, I found that I had installed extra textures for procedural fairings, and for near future solar panels. It seems to work now. Thank you.
  11. @Shadowmage, I apologize, I didn't mean to suggest you should do support for other people's mods. Since the issue here only appears when I load the game with TU and affects parts from two different mods (Procedural Fairings and Near Future Solar), written by different people as far as I can see, I thought any single cause would likely be on some more fundamental level, most likely my own incompetence. I don't suppose there's a complete-ish list of mods that use TU anywhere?
  12. So I'm using a bunch of mods that have Textures Unlimited as a dependency. And I'm sure it's a great and glorious mod. Pretty much all I notice of it, though, is pretty dark. Specifically Procedural Fairings, which I use a lot, from the fairing bases to the fairings themselves. As you can see here, the fairings look pretty dark when I try and launch: While, in the VAB, they don't look like that: But what does look like that in the VAB is the fairing base, and the Near Future Solar solar-panels. I looked through this thread, but couldn't find a solution. I'm visually handicapped, so it's quite plausible that I might have overlooked it. In which case I apologize for cluttering up the place, but would humbly request to be pointed at said solution. In case I didn't, but am just doing something wrong (most likely, actually). What am I doing wrong? Is Textures Unlimited looking for some manner of light/shade/reflectivity maps for the affected textures and, failing to find such, can only present the affected surfaces as though in darkness? Or is it just some setting that I've buggered up? Here be my graphics settings: Using DirectX 12, btw., too many crashes and bsods in OpenGL mode. I have tried, on a few occasions, to start the game without Textures Unlimited. Stuff looks normal, though I suspect I'm missing something. As you can deduce from my graphics settings, I'm not so bothered about getting the most luxurious optics. Is that my only option, just starting the game without it? Thanks in advance for any advice and help!
  13. Ugh. The driver removal tool seemed to have removed some remnant of the old Nvidia drivers that, it appears, was also used by the AMD drivers. So I uninstalled the Radeon drivers and software, and reinstalled (no "Repair" option, and it wouldn't install on top of an existing install of the latest version). I reverted all my mods to the state I had found and enjoyed for a number of hours only yesterday. Now, when I start the game in DirectX, I get to the VAB, and when I start doing anything, it crashes. When I start the game with -force-glcore, I get to the VAB, and when I start doing anything, just happened twice: IRQL_NOT_LESS_OR_EQUAL Yes, a replicable BSOD, twice with the same error message. No mention of "DRIVER_...", and of no files, either. I have decided that I will now do the other thing you recommended, @4x4cheesecake, I will install fresh. I will obviously backup my saves and GameData, except for the module-manager cache files. There will be a test drive with the unmodded game, in DirectX and in OpenGL modes respectively, and then I will go back to my profusion of mods. If I still get only crashes or BSODs, that would be worthy a new question (which is why I've marked this answered - the missing parts issue was resolved, after all). Thanks for the advice, @4x4cheesecake! Postscript: I failed to backup the output logs after the crashes in DirectX mode. Yes, I know, ¡Dŭh!. But in case anyone needs to prove to themselves that they can really, really focus on something that's upsetting some dude in Germany on a very non-existential level, here are the crash-dumps of the last two "mere" crashes: Here is the output log, such as it is and as I found it after the latest BSOD: And just in case, the KSP.log:
  14. I do have a laptop. But that is so anemic, it can barely run windows. Installing KSP would be pointless, even without any mods. I'm now looking into downgrading to mod versions that worked the last time. Thanks for the help, though!
  15. After successfully starting up the game yesterday, and playing with no significant issue for a few hours, I had just left it running. After reading your suggestions, and because one or two other mods weren't working right, I shut the game down. Updated ClickThroughBlocker, took out AmpYear, put in Fusebox. Restarted the game. Play for maybe two or three minutes. And the system just bricks. The screens remain on, frozen, and that's it. System responds to nothing at all. When I hit the power button on the case to power down (so as to power up again), instead of having to wait five seconds, it powers down instantly. So I conclude something excrements itself deep down in there, that's the chipset/bios/power-supply business. After I reboot, I take out Fusebox again, update the mods that hadn't been working right, put Ampyear back in, start it up again. I make it all the way to the VAB (with QuickStart first taking me to the Space Center). BSOD. DRIVER_IRQL_NOT_LESS_OR_EQUAL This time, I got a filename: WppRecorder.sys Googling it tells me little about it, other than that there appear to be a number of fraudulent looking "repair tools" available. And that it appears to have been mostly associated with Windows 8 woes. Searching my harddrive tells me there are two instances of the file. One in System32, one in some AMD64 related sub folder (judging by the folder name) of WinSxS. I know for a fact that this is the first time I've seen this filename. And yet, off I go, a googlin'.