Micro753

I don't know about repairs, but you can edit the vehicle via the KCT menu, and then tell the part to be replaced with a new one.

Is there an easy way to make the part failures show up in the flight log? I'm trying to do a career playthrough with only IVA (using raster prop monitor), and I can't find anyway to see what part failed and in what way. This would make the flight log actually useful.

@linuxgurugamer I found out why my attempt at fixing the docking port cameras wasn't working. I was using ModuleDockingNode as the camera container because that's what the Squad files had as the module name, but apparently it needed to be dockingNode instead. I added this to a cfg file and the docking port cameras are working again: This cfg also works even without hullcam and only rpm.

@linuxgurugamer I’m having some issues with this mod and RasterPropMonitor. It seems like the cfg files might need a look over to update them for the latest rpm? I’ve been trying to figure it out myself, but everything I’ve tried has either not worked at all or caused a bunch of errors in module manager. The camera filters (e.g. night vision) don’t seem to work at all when viewed through the rpm screen. The docking port cameras don’t work at all with rpm. I don’t see anything in the cfg files that adds an rpm module to the docking port parts, so I tried fixing this myself by making a module manager patch file, but I couldn’t get anything to work. I found a fix. See below post. Only the forward facing camera of the booster cam works with rpm. I’m pretty sure the reason is that both the forward and rearward cameras are being given the same rpm Camera ID. If multiple cameras are assigned the same ID number, rpm will only detect one of them. The Booster Camera's cfg file has a comment saying this is a known issue with no current workaround. The night vision camera works fine when viewed using the ‘=’ key, but is rotated 90 degrees when viewed in rpm. The camera’s viewpoint is also too far back, causing your view to be clipping through the camera’s model. The rotation is an easy fix. In rpm2-hullcam-models-as-external-cameras.cfg, change the night vision camera’s rotation to “%rotateCamera = -90,90,0”. For some reason %translateCamera doesn’t seem to do anything, so I don’t know how to fix that part. If you right click a kerbal, there’s an “activate camera” button and an “enable camera” button. The camera is really easy to bug out by clicking activate, then enable, or using ‘=’ and ‘-’ after clicking one of the options. Log file: https://www.dropbox.com/scl/fi/bicb9081xln4wxgqdj2hj/Player.log?rlkey=agrz36i6zt6zd1ckmdid4ud1o&dl=0 This next issue went away when I deleted all mods and reinstalled only rpm, hullcam, and module manager, so this one is a mod conflict, but I have yet to track it down. The booster cam’s rearward camera was rotated to point in the same direction as the forward camera. I don’t know how that happened, and I’m still trying to recreate it. If I find out how that happened, I’ll post here.

Edit: Disregard. Reinstalling a second time fixed the issue? It's weird that the issue happened to me on two different clean installs of KSP. Third reinstall fixed everything somehow.

@Serenity Thank you! I have no idea why that worked, but it did.

When I enter IVA, the ground has parts that start flickering. I've never seen an issue like this before, even on heavily modded games, and this is my first time in 1.12. I'm playing on my Blender machine with a 5950X CPU, a 3090 FE GPU, and 32GB of system memory. I deleted the entire game folder and reinstalled via steam to ensure I didn't have any remnants of mods and the issue persists. Kinda hard to show in a screenshot, so I recorded a video instead. In the video, I launched the Osprey stock vehicle and flew it to the island runway. Can anyone else replicate this, or is it just me? Log and video link: https://drive.google.com/drive/folders/1GK2fRhP541kgrI3tKiHWPEYinTOtVYlE?usp=sharing

That was the problem, thank you for your help. I reported the problem on the ASET thread.

Quick bug report: I was trying to fly an all IVA mission, so I was trying to use the lat/lon readouts to help navigate, but they only got me confused until I realized the cardinal directions were wrong. I asked in the RPM thread, and Manul found the problem to be a cfg file from ASET. So, I opened ALCORAscDes40x20.txt and changed it to this: That fixed the problem.

I was trying to fly an all IVA mission in 1.8.1, so I was trying to use the lat/long in the ship window. After getting really confused, I realized that lat was showing E instead of N and W instead of S, and long was showing N instead of E and S instead of W. I have tons of mods installed, many of which are related to RPM, so I don't know if this is a conflict or a problem nobody's noticed before. Can anyone else replicate this, or is it just me?

It works fine on your computer? How much memory does your computer have? I was trying this on my rendering desktop, which has 64 GB of memory. I'll try to find one of my old gaming laptops and see if it behaves any differently. I wish I knew coding so I could try to track down the problem myself.

Ok, so I had a few dozen addons (a few for textures, most of the rest for architecture modeling), and I thought there might be an issue caused by compatibility or settings files. I backed-up all of my projects and purged everything Blender from my C:\ and D"\ drives. After that, I tried installing Blender 2.80 instead of 2.82, and that time there were errors when I pressed the "Install KSP Shader Presets." I uninstalled 2.80 and installed 2.82 instead. This time, I installed it on my D:\ drive, which is where my KSP is installed. It still gave errors, but they look slightly different than last time. After that, I tried deleting all of the mods in my GameData folder, just in case one of those were somehow causing the problem, and the error still happens. I'm at a loss on what to try next.

I tried to find a log file in case that would help, but I can't find one anywhere. I have Blender 2.82 installed both regularly and through Steam, and the error happens on both. Do you have anything else I could try to maybe narrow down where the problem is?

Blender gave me some errors when I tried to import a .craft file. I'm using Blender 2.82 and the version of this that you updated 20 hours ago. The .mu import works, just not the .craft. I did set the GameData directory, so I'm not sure if I missed a step or did something wrong. I tried with one of the stock .craft files as well, and same thing happened. Only other thing I can think of is that KSP is on D:\ instead of C:\

This is my first time using unity and had a few problems. I'm hoping someone here might be able to help me. I installed Unity and the KSP part tools, and I can view, edit, and add props in the IVAs. My problem is I clicked the "save project" option, but it doesn't seem to save anything; when I reopen the project the next day, it opened the generic project start scene, with a light and camera. Is there a different option I need to click instead? My other issue is I can't figure out how to create the IVA cfg file so I can put it in the game. It's probably really obvious, but this is my first time trying any kind of modding, so any help would be really appreciated. (Also any pointers or tips would help too.)