Jump to content

JohnnyPanzer

Members
  • Posts

    179
  • Joined

  • Last visited

Everything posted by JohnnyPanzer

  1. Yaaaaay! Very true. I also use a patch to fix it, and when I forget to copy it over to new installs it's almost second nature to move the heat shield down.
  2. Doh! I should've read the FAQ, my bad. Also, I hope it didn't come off as a complaint, I was just curious. But yes, the command pod is included in the PartOverhauls zip I've always been downloading from way back when it was released. I agree that the actual style of the original pod is very nice, which is why I enjoy the overhaul immensly. It's basically the same exact pod, only higher detail and much better textures. It's this one: https://kerbalspaceprogram.com/files/PartOverhauls.zip https://imgur.com/a/NvEs4#mYDWSeL EDIT: But yeah, I get why you'd skip the boat tails due to iffyness in getting them to work. I mean, I know for a fact that you know a lot more than I do about MM patches (because you've actually helped me out a couple of times in the past ), but having something of an obsession with getting the overhauls to work, I have noticed that as soon as a good integration patch comes along, it gets borked by the next update to either the game or MM. Currently the PartsOverhaulIntegration mod is doing a wonderful job. It adds all the porkjet parts, removes the originals (so no messy part list) and even renames the bare/boat-tail versions of the engines with A and B, and the contracts picks up on it. So you'll always know which version of the engine the contract requires. The drawback, needless to say, is that it lacks your amazing skins, as well as your other parts. So right now I'm trying to combine the best of your two mods in my personal install, and if possible "compile" it into it's own, single mod folder (something like gamedata/porkjetCombined) and save it for future (personal) use. I guess my point is that I find it equally hard to live without either one of your mods, but they don't play well together per default, so I need to find a solution that works for me. I know for sure that I feel robbed every time I build a small rocket and I don't have access to your amazing textures.
  3. I love the skins, and I love the 1.8 parts, but I always end up trying to mix and match with PartOverhaulIntegration due to the omission of the overhauled Mk1 pod and the boat-tails. Any particular reason you didn't integrate them? The pod in particular, the old one looks like it's running on a broken graphics card compared to Porkjet's gloriously overhauled version. I'm not trying to look a gift horse in the mouth, I very much enjoy the hard work so many modders have put into trying to keep Porkjet's overhauls alive. But it is a tad frustrating that it keeps being one of those things where each attempt either ommits certain parts, adds some cool feature that the other mods don't (like the skins in this one, great job on those btw!) or has all the goodies but then simply leaves the old parts to clutter the item list. It's my own fault for not saving my homemade solutions though. Every time I do a fresh install I end up downloading all the integration attempts and then spend a few evenings trying to copy files back and forth, edit .cfg files, write my own patches and then promplty forget to save it all as a clean, easy to extract package for next install. Rince and repeat... downside of being an idiot I suppose.
  4. Hey. I'm keen on unlocking all the extra bases through funds and discovery in career mode, but as I looked through the various configs affecting KK, I realized I had no idea what I would need to change in order to not have everything unlocked and payed for by default. Any tips on what settings I should change? Oh, and thank you for the great planet pack, I always enjoy going back to Gael!
  5. Ah, thank you, that explains it. I'll poke around in the GPP config folders a little while to see if it's easy enough to change, otherwise it'll have to do.
  6. I'm using KK with Galileo Planet Pack for a brand new 1.4.5 career, and no matter what I change in the settings all the launch sites are unlocked per default. Any idea if this is due to a known issue with KK, KK+GPP or simply me being an idiot (pretty likely to be honest)? I have a lot of other mods installed, but before I start removing them one by one I figured I might as well ask. So, in short, I can't get the 'career' part of KK to work. All bases are open and payed for form the start, and changing career settings for KK does nothing to remedy the situation. It's a shame, since I was excited about slowly unlocking new sites as I progress through my career. (Great job all the same, I truly enjoy all the aspects of KK)
  7. Here's the finished lineup of 1.2, in all it's reduxed glory. As soon as I've playtested the balancing changes and finished a small KSPedia entry, I'll release the update. Should be within the week.
  8. The update is coming along nicely. All the old parts have recieved the "redux" treatment and are looking a lot better, and I feel like I'm pretty satisfied with the way the rebalancing is going. Without going into details, the new setup will see the three black & white probes function exclusevily as com relays, while the orange BB probe will fill the exploratory role, with a small range of optional equipment. For this purpose, I recently finished the last optional direct antenna for the BB-series, pictured below. I've begin work on a scaled down version of the resource scanner, and once that is finished I might just call it a day. We'll see. Anyway, here's the new K-Sat BB-COM D3:
  9. Work has begun on the next update which will include a complete rebalancing of old parts and several new parts, as well as an overhaul of the part quality. As part of the rebalancing, the BB-series now requires new parts to be able to perform it's role, and two of those are allready finished. The BB-888 was also the first model to recieve the 'redux' treatment. I've been extremely stingy with polycounts and texture sizes, and not very efficient with the way I packaged the parts. Therefore, I've been able to double both polycount and texture size without much of a performance hit. More or less all parts will recieve this treatment, and all new parts are produced with the new quality in mind. So without further ado, allow me to present a very small sample of what K-Sat 'redux' will bring. The new parts shown is the Medium Range Dish 'K-Sat BB-COM D2' and the Short Range Antenna 'K-Sat BB-COM O1':
  10. Had a look and as far as I can tell it should work just fine. It has some patches for other mods that loads before this one, but none of them messes with the ability to store ore in the converter, so I can't see that it should matter.
  11. If it uses the regular converter module, it should be compatible. It's possible that patching order needs to be changed on my end, since this mod basically looks for any part with a converter module and then patches it. If Stockalike Mining Expansion loads after this mod, it wont get patched. I'll look into it.
  12. New build is up. Nothing major, the old build should've worked with 1.3.1, but I've made some changes in the folder structure as part of another mod update. Changelog: -=::::::\1.2/::::::=- -Included MiniAVC support -Included support for Decal Stickers -Changed folder structure -Updated version number for KSP 1.3.1
  13. A small gremlin managed to crawl inside one of the .cfg flies and added a typo. That typo is now fixed. This patch is pretty much optional if you don't mind the lowered cost of the LO-242, no other changes were made. Changelog: -=::::::\1.1.1/::::::=- -Fixed a typo that lowered the cost of the LO-242 by almost 75%.
  14. Mod Updated for KSP 1.3.1 Changelog: -=::::::\1.1/::::::=- -Included MiniAVC support -Included support for Decal Stickers -Updated all antennas for KSP 1.3.1 -Updated the MM patch for Remote Tech 1.8.9 -Changed folder structure -Changed category for the inline battery, from Utility to Electrical -Made the small dish (PzL-COM D1) physicsless -K-Sat PzL-BB 888 *Added "Marble" to the name *Added internal launch antenna *Added hibernation option *Added KerbNet access *Changed RT omni range to 2.5Mm -K-Sat PzL-LO 242 *Now allows surface attachments (on it, not with it) *Added "Lancelot" to the name *Added internal launch antenna *Added hibernation option *Added KerbNet access *Changed RT integrated omni range to 150km -K-Sat PzL-LO 1138 *Added "Cobra" to the name *Added internal launch antenna *Added hibernation option *Added KerbNet access *Changed RT dish range to 90Mm *Changed RT integrated omni range to 150km -K-Sat PzL-LO 1142 *Added "Crabhead" to the name *Added internal launch antenna *Added hibernation option *Added KerbNet access *Changed RT dish range to 50Gm *Changed RT integrated omni range to 150km
  15. Every time I start a new install of KSP, this is the mod I forget to include, but it's also the one mod that I have used in all installs since it came out. It's an absolute life saver. Thank you a million times for your work! Also, I now have a post-it glued to my monitor, that says "KSPRescuePodFix! Come on!"
  16. Sorry for the delayed reply, I haven't played KSP for some time. I'll see what I can do, I'm very busy IRL at the moment, and I'd like to include some balance changes while I'm at it. But if I have the time, I'll try to release an interim patch this weekend with nothing but the config changes needed to make it run on 1.3.1 Thank you for your continued interest. I know it kinda sucks when mods go dark, but that's life I guess. Stupid adulting getting int he way of all the fun.
  17. Here you go. The problem with that solution is that it will mess up both engine upgrades and all contracts involving those parts.
  18. Right click on it in steam. Under "properties" there should be some options for betas. Old versions can be found there I believe. Going from memory. In the future, copy the whole directory from steam and mod/play the copy. That way you'll always have a clean install on steam and your modded game will not break from updates.
  19. I have no use for this update, but I'm glad they made the game accessable for all the potential players who, for whatever reason, are unable to pick up a second language. I can still play on my 1.2 install, so the hassle this update causes for me is insignificant compared to the service it provides for many, many others. Besides, I've been meaning to re-balance and update my own mods for a while, as well as make some new ones. This seems like the perfect time to download a clean copy of 1.3 and use it for testing. But I doubt I'll update my "for playing"-install until all mods I use require me to.
  20. Yeah, it's a bit difficult to get hyped over an update that will not bring a single feature I need or want, yet is bound to break at least some of my mods and introduce a few bugs. For all intents and purposes, for anyone fluent in english, 1.3 boils down to a free period of pain in the neck. Still, I don't mind it if it helps people who were previously unable to enjoy the game. Good for them. But it is certainly the first update I'm not looking forward to and would opt out of if it wasn't for future compatibility issues.
  21. Glad I decided on reinstalling the bundled Kopernicus after all then.
  22. Just a heads up, the installation instructions for GPP Textures on your github page reads: Open the zip file and drop the GPP_Textures folder into your GameData folder But the zip file is correctly nestled as GameData/GPP/GPP_Textures. This is bound to cause some people to place the GPP_Textures folder incorrectly (i.e. directly inside the GameData folder) and then ask for support. Updating the instruction might be a good idea.
  23. Roger that. Come to think of it, since you're kind enough to provide the bundle I'll just reinstall kopernicus and moduleflightintegrator nice and clean while I'm at it. edit: For future reference (in case someone stumbles in and wonders what sort of manual fix I was talking about), by "manual edit" I meant that I followed these instructions: But again, I just gave kop/mfi a clean install. Might as well.
  24. Just to be extra clear, considering that I allready have the kopernicus .dll installed correctly and manually edited the suggested solar panel fix a few days ago (as well as the extra } in the asteroids cfg), the only thing that should need a clean install in order to work with my current save is GPP+textures, correct?
  25. Thanks. I keep missing things like that since I most often visit the forums via mobile. No sigs on mobile. I believe the blue nebula skybox I'm currently using is one of his, but if that's the case I must've missed that greenish one.
×
×
  • Create New...