Jump to content

DemonEin

Members
  • Posts

    23
  • Joined

  • Last visited

Everything posted by DemonEin

  1. I don't understand your question. There is no replacement for the (old) Mk1-2 pod, but there is one for the Mk1-3.
  2. To use cameras, you need a camera mod such as Hullcam VDS. Are you using a particular camera mod? They are dependencies of dependencies.
  3. Try adding the mod dependencies one at a time to figure out which one breaks the game. Log files are also useful.
  4. At this point, with KSP 2 around the corner, I am not developing any new content since it would lose relevance pretty soon. I was going to, but that was just before KSP 2 was announced. I'll keep maintaining what I have though
  5. Check your RPM installation. The most current version for RPM is the one adopted by @JonnyOThan in this thread. Install that one if you currently have the old RPM installed. If you have the new one installed, try the old RPM found in this thread. Try both and let me know what happens. I don't think it would be an issue, but you should uninstall all other mods that are not dependencies of this mod or RPM before trying different RPM versions. As for vessel viewer lag, that's something I have experienced myself, and just seems to be what happens when viewing complex ships. Let me know what happens
  6. To be honest I don't know. I could very well be an ASET issue instead. I don't know enough about the inner workings of RPM and RPM-enabled props to really say.
  7. Technically this is an RPM issue, and I believe it doesn't support Kerbalism. Kerbalism changes the way electricity works which breaks RPM's electricity indicators.
  8. ASET Props isn't the problem so much as RPM is the problem. MAS works for 1.8 and uses ASET props. Presently I can't justify adopting RPM to make it compatible but of course someone can always do that if they want. It's always a shame when old projects get outdated but hey, that's what happens.
  9. Figuring out how to make a mod is as much a part of modding as is making the mod itself. This video might help you get started for editing IVAs. Most of it isn't important to this type of IVA creation, but the video gives an idea of how IVA development works. Take a look around the forums for any other resources you can find. Good luck!
  10. I did consider using the ASET HUD, but I decided against to prevent having an additional dependency. If you want, you can go ahead and use part tools to switch out the HUD. It shouldn't take too long, because you only need to do it with 2 cockpits (iirc).
  11. Good to know. Not much I can do, but hopefully others don't get the same problem. Replacing the life support screens would require changing the arrangement of the props around the life support screen, which would be annoying for all the pods but you could do it. The proper way would be to use Part Tools to modify each internal by removing the life support screen, adding an MFD correctly positioned and scaled, and adjusting the surrounding props accordingly. Alternatively, you could try to hack it by using ModuleManager to change the name of all life support screens to an MFD name. The MFD wouldn't be scaled correctly and might overlap with other props, but it could work well enough to be worth the reduced hassle.
  12. Do you have ToolbarController installed? If you do, then I don't know what else to do, sorry. Anyone else should let me know if they have the same problem. RasterPropMonitor integrates with a few other mods to bring you functionality on the other screens (for the map, use SCANsat, and for cameras, use Hullcam VDS). These mods are optional but they add functionality, and there are more mods that also integrate with the MFDs. More information on the MFDs can be found in the RPM forum thread and other RPM sources. Unfortunately, I don't think there is a way to add maneuver nodes while in IVA. Thanks for your interest, and have fun!
  13. I wish I could help you with that, as I haven't noticed so extreme performance issues on my machine, and I have no idea why it is so bad for you. Are you using any others mods besides the dependencies? It might also be nice to know your system specs. I don't know if I will be able to do anything, but I would be interested to know any additional details. Check your installed versions of all the dependencies, especially ToolbarController, because it was updated at one point that changed how it interacts with the unBlur mod which might have something to do with your problem. If that doesn't work, send me a screenshot so I can have a better idea of what you're seeing.
  14. I think it should. It won't do anything to saves, so there is no risk in trying it at least. Let me know how it goes!
  15. Fixed in version v.1.0.2, just released! Thanks, and have fun! Check the readme on GitHub.
  16. Take a look at Hullcam VDS. It adds a bunch of cameras, and it's a mod I personally use in conjunction with this one. Sidenote, I've been delayed from making progress for a bit, but soon I'll be able to fix the major bug I'm aware of and look at doing the DLC pods
  17. TAC Life Support, USI Life Support, and Kerbalism are what I am aware works.
  18. Thanks for the report, I appreciate it. After the weekend I'll be able to take a look at it and make a fix. If you're curious, he is what's going on (almost certainly): Every (stock) IVA has a number of colliders that, when double clicked, move the camera to another angle. Those buttons don't work because there is camera trigger collider on top of the button collider, which means when you click you will activate the camera trigger instead of the button (of course, the camera will only change if you double click). As you can imagine, this can be a real issue when making IVAs. Removing the window camera modules is exactly what I tried to do to fix this, but it seems that the colliders are still there even after removing the trigger modules (you should find that the camera angle won't switch anymore, though). Currently I have no idea where the collider information is stored in the game files, so I've simply been working around it. For each IVA I tried to check if I would have collider issues, but I guess I missed this one. To fix the Mk2 Lander Can, I will have to move things around so that there is nothing interactive under the camera trigger colliders. I think™ it can be done reasonably cleanly. Also, for anyone hoping for Making History IVAs, I'll do those too . I'm thinking I might try basing the IVAs off their historical counterparts instead of my previous style, really I won't know what will work best until I get down to it. If you have any thoughts let me know!
  19. Thanks! I never realized there were supposed to be more sounds. Personally, I don't think the visual of the prop adds to the IVA, so I'm making it present but invisible: @INTERNAL[DE_*]:AFTER[DE_IVAExtension] { +PROP[Primitive_BOX_Beveled_Black] { @name = gpws10 } } (it just gets created inside an arbitrary black box in the IVA) I like your solution to adding props to all the IVAs at once, and it might come in handy in the future. I put up a new release on github. Thanks again, and I'm glad you like the mod!
  20. Only one interior would be loaded, there shouldn't™ be any conflicts. If you want to be sure that alexustas' IVAs are loaded, you can go to GameData\DE_IVAExtension\Parts and delete the .cfg file for each pod you don't want my IVAs for (I recommend saving the files somewhere else so you can easily put them back). If the IVAs you prefer load automatically, there is nothing wrong with leaving things as they are.
  21. This mod has been adopted by @JonnyOThan, see the new thread for the new version of this mod DE_IVAExtension v1.0.2, created by DemonEin July 25 2019 (last updated August 20 2019) Have you seen some of the amazing IVAs built by the community and wished that all the stock cockpits were that functional and good looking? DE_IVAExtension is a mod I put together to add advanced IVAs to every stock pod in the game. Features -All stock command pods have an advanced interactive IVA -All IVAs have a similar layout and (almost) identical features for ease of use -if using the mod ProbeControlRoom, there is a new mission control room in the same style as the other IVAs Dependencies ASET Props Pack v1.5.0 ModuleManager v4.0.2 ToolbarController v1.8.2 ClickThroughBlocker v0.1.7.2 For KSP 1.8.+: [1.8.x] - RasterPropMonitor (adopted) For KSP 1.7.3 and older: RasterPropMonitor v0.30.6 Supported Mods ProbeControlRoom v1.2.2.12 Special Thanks Thanks to @alexustas, creator of the amazing ASET Props Pack which this mod is based on, and of course his beautiful ALCOR capsule, from which much of the prop layout was shamelessly taken Thanks to @MOARdV, creator of RasterPropMonitor, which makes the IVAs interactive in the first place. A Word on RPM and MAS I am aware that RPM development has stopped and that MAS is the up to date method for interactive IVA. The goal of these cockpits is to be simple to use, which can be accomplished just fine with RPM. If there would be value in changing the IVAs to use MAS rather than RPM, let me know, and I will consider making the change. Additionally, if there are any problems with RPM itself when using this mod, let me know, and I'll see what I can do. Download GitHub: https://github.com/DemonEin/DE_IVAExtension/releases SpaceDock: https://spacedock.info/mod/2193/DE_IVAExtension Also available on CKAN (thanks to@HebaruSan) License This project is licensed under the Creative Commons Attribution-NonCommercial-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/ This is the first mod I have made for KSP. Let me know what you think, and of any feedback you might have. There are some improvements that could be made, so if you have ideas for further development, definitely let me know!
×
×
  • Create New...