TheShadow1138

Members
  • Content Count

    410
  • Joined

  • Last visited

Community Reputation

190 Excellent

3 Followers

About TheShadow1138

  • Rank
    Sr. Spacecraft Engineer

Recent Profile Visitors

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

  1. Glad to hear. What was the underlying issue, and how was it fixed if you don't mind my asking. I haven't tested my own mod in 1.10+, and haven't had any reports, but I'm not sure if its because everything works fine, or the size of my user base and I'd like to know how I might go about fixing any issues, if there are any.
  2. I've never used JNSQ myself so I tuned the rockets to the stock scale, or at least I tried to, so they would behave as close as one might expect. You are, of course, welcome to try. If you do decide to try, let me know the results (good or bad). I've only really glanced at JNSQ a couple of times because I'm not sure how my laptop would like it. I may give it more of a once over and see how much work it would be to make the parts usable with JNSQ. If I were to do it, I could always include a compatibility patch.
  3. You will need to add struts. I had hoped that the decouplers would keep you from needing struts, but they are still necessary. There are craft files included in the download if you want to use them instead of building from scratch. There are also sub-assemblies of the launch vehicles included so that you can build your own spacecraft to launch. Just adding struts to the top and bottom, where the decoupler model hides the struts should fix the problem if you want to build from scratch. Hope that helps.
  4. I will give it some thought, but I make no promises. I don't use RO or RSS myself, so I would have to download them just to do this. I'm quite busy with school at the moment, so I don't have time to work on the mod. Again, I make no promises that this will happen. Unless I'm mistaken, only you and one other person have asked for RO and/or RSS compatibility, but I will at the very least look into it.
  5. Are you playing a career game, or sandbox? I think I made sure the tech nodes referenced in the part CFGs were correct, but I'm not sure. So if you're playing a career mode game either you haven't unlocked those nodes in the tech tree, or I don't have the tech nodes referenced correctly in the CFGs. If you're playing in sandbox I'm not sure why you're not seeing all of the parts. You could try deleting ShadowWorks, and reinstalling fresh. If you got the mod through CKAN, I have no control over what it downloads, and I would suggest downloading from Spacedock, if you didn't download from there in the first place. You can check your KSP.log file by opening it in NotePad, TextEdit, or your preferred text editor and look for any warnings or errors connected with ShadowWorks parts that you know are not showing up. If you can find nothing in your KSP.log, you could post the file to DropBox, or something similar, so that I can take a look at it. There's not much else I can tell you with the information you've given me at this point. First check to make sure you installed the mod correctly, try re-downloading from Spacedock, deleting your current install and re-installing from the fresh download, and check your KSP.log file. I hope that helps.
  6. There are no RSS configs included in the download. The mod is balanced for Stock KSP. I do not use RSS myself, and don't really have the time for the foreseeable future to download it to try and make configs. I don't know if anyone else has made any either. If you, or anyone else wants to make configs for RSS, I'll gladly post a link in the opening post. Sorry.
  7. I don't know of any mods that interfere with mine. To post a screenshot you need to upload it first to an image hosting site like imgur.com, then copy and paste the URL of the image and in the forum here click the "Insert Image from URL", paste the URL into the window that pops up and it should put the image in your post.
  8. Try going in to KSP's Settings -> Graphics and setting "Reflection Refresh Mode" to "Low" if it is set to "Off". When I was making my reflective Orion capsule I discovered that it was shiny in the VAB, but dull black on the launch pad. When I changed "Reflection Refresh Mode" to low instead of off, it was shiny and reflective in the VAB and on the launch pad.
  9. The white Orion variant does not have a normal map if that's what you're asking. The textures were almost entirely remade for the ShadowWorks 2.0 update. Without seeing a screenshot of what you are seeing, there's not much else I could suggest except to select a better texture quality in KSP's Settings. Of course, for all I now you're using the highest settings for graphics. If you can, post some screenshots of what you're seeing so we might be able to figure out what's going on for you.
  10. Great! Glad it's working. I tried to make installing manually as easy as possible. Also, no dependencies, but there are ModuleManager patches for RealPlume and MOARDv Avionics System glass cockpit (the RPM replacement). So, if you have either of those mods installed you'll have glass cockpits for the Osiris (Orion) capsule and Horus (Altair) lander, and/or nicer looking plumes. Happy launchings!
  11. I'm not sure why CKAN is complaining. I don't use CKAN, and have no control over what it does with my mod when it's trying to install, and have no idea how it handles installing the ShadowWorks folder in GameData and dealing with the CraftFiles folder. There aren't any plugins in the mod, so there shouldn't be anything that would identify the craft file as ShadowWorks (except for the file name). It may be better to download the mod directly from Spacedock, and just overwrite (not merge) the ShadowWorks folder in you GameData with the one from ShadowWorks 2.0.3. The craft files did not change from version 2.0 to 2.0.3, so you wouldn't need to worry about reinstalling craft files or anything like that. I would say that if CKAN complains about something, try installing manually, just in general. I hope that gets you up and flying.
  12. Thanks again for your help. Once I figured out the problem, it was actually a pretty easy fix.
  13. I believe I'm experiencing the same issue on OS X El Capitan. I run in windowed mode at 1280 x 800, which was sufficiently large in 1.7.x, but in 1.8 the window is annoyingly small at the same resolution. Apparently it is halving the window size as setting the resolution to 2560 x 1600 gives a window the size of 1280 x 800. The only workaround I've found thus far is to set the resolution to 2560 x 1600 , and the UI scale to 1.5. The only issue I can find with this is a drop in fps because it seems to behave as though it is displaying at 2560 x 1600, but is shrunk down to about the 1280 x 800 size. 1.7.2 runs smoothly at 1280 x 800 on my late 2015 MacBook Pro, and the high screen resolution is the only difference between the two instances.
  14. Version 2.0.3 Hotfix This update fixes the new issue introduced by 1.8 with parts that use "Bumped..." shaders, but do not have a normal map behaving as though they have a messed up normal map. Prior to 1.8 KSP appeared to simply ignore the lack of a normal map, but alas no longer, so I have added a flat normal map to those parts so that they now look as they should. Many thanks to @Tibozeboss for bringing these parts to my attention and helping me narrow down what the problem was. The change log is below, and the OP has been updated. Changes 2.0.3 -------------- Hotfix * Re-exported the following parts to add a basic flat normal as KSP apparently no longer gracefully ignores no normal map for "Bumped..." shaders. * EUS * EUSDecoupler * ICPS * DCSS5m * DCSS5mDecoupler * DCSS4m * DCSS4mDecoupler * AresI * AresIIU * AresIDecoupler * Pyrios * PyriosNoseCone Everything should be back to looking normal.