Stone Blue

@Elon's Musk Please see my reply on the MAS thread. Now, after reading the info you posted here, (a little different than in the MAS thread)... yeah, this sounds a LOT lie the issue i found with RevIVA & MAS. Do all I suggested on the other reply, and again, remove RevIVA, and check that Advanced Cockkpit/Main Bus switch thing I mentioned. Then, please post new KSP.log in the MAS thread. i want to see if it is indeed RevIVA related. If so, i hopefully have fixes submitted to MOARdV for it.

@Elon's Musk First off, you have several copies of outdated versions of ModuleManager. You also have a copy of MiniAVC installed. Thats been known to be broken for awhile. Best to remove it. These may not be specifically reltaed to this issue, but worth probably addressing. Also, I see some sounds not loaded/found, from Advanced Cockpit mod?.. I'm not familiar with that mod, but the errors *are* related to ASET Props, and could makke some of those props non-functional/unresponsive. One of them is a Main Bus switch... I dont remember if that is the main power switch that Manul mentioned above, but if it IS, and the prop is not working, that could very well be the culprit. You can either try removing Advanced Cocpits, *or* look for the "requires powerOn" type of key (not the eaxct name, I cant remember it), in the IVA cfg for that cockpit, and set it to "false", if its not already, & see if that fizes it. It also looks lie RPM is not liking that there is no internal model found for the OPT J-HT cockpit..?? [LOG 12:56:02.599] Part Name: OPT J-HT Cockpit (M) [ERR 12:56:04.902] [RasterPropMonitorComputer]: UpdateLocalCrew() - no internal model! [ERR 12:56:04.950] [RasterPropMonitorComputer]: UpdateLocalCrew() - no internal model! [EXC 12:56:05.086] NullReferenceException: Object reference not set to an instance of an object AvionicsSystems.MdVTextMesh.OnDestroy () (at <2bb05d285e56479a9e9bde992b09bb1d>:0) [WRN 12:56:05.613] InternalModel error: Part Crew capacity is 8, but 10 seats are defined in internal model Also this OPT cockpit: [LOG 12:32:51.153] Unpacking OPT-J-HT-Sea [ERR 12:33:20.851] [RasterPropMonitorComputer]: UpdateLocalCrew() - no internal model! Theres also this err, related to MAS & OPT: [LOG 12:29:38.467] [FlightIntegrator]: Reloaded drag cube for zeroed cube root part j.6m.cockpit on vessel OPT-J-HT-Sea [LOG 12:29:38.468] [FlightIntegrator]: Vessel OPT-J-HT-Sea has been unloaded 1.79769313486232E+308, applying analytic temperature 305.203620590636 [WRN 12:29:38.469] BoxColliders does not support negative scale or size. The effective box size has been forced positive and is likely to give unexpected collision geometry. If you absolutely need to use negative scaling you can use the convex MeshCollider. Scene hierarchy path "internalSpace/MAS_JHTIVA interior/MAS_ASET_COMM_Radio/model/ASET/ASET_Avionics/ModernPack/ASET_Comm_Radio/ASET_Comm_Radio(Clone)/ASET_Comm_Radio/ASET_COMM_PTT_ColliderObj" Looks lie there may be some issue, with some MAS modules being added, and it seems to be upsetting the module index on a/some part (s). The KSP module index is very fragile, unfortunately. When this happens, its usually due to some mod adding/deleting/moving part modules. There are some other MAS/OPT related errs, as well. I see you also have RevIVA installed. I had recently come across a patch issue with MAS and RevIVA cfgs, which I have submitted PRs to MAS, that will hopefully fix the issue. Do me a favor and uninstall RevIVA, and poke the MAS/OPT ivas w/o it installed, then post a new log. As a final note, the OPT IVAs *are* in sad shape. They do need a lot of work, possibly to the point where they may just not be useable at this time.

@NippyFlippers I thin you just need to play with the _Opacity value on the material? As to the Alpha channel, I believe all the values I've ever seen are either "0.0" or "1.0"... Also, if you havent figured it out, i think you want the KSP/Alpha/Transparent/Specular shader. You shouldnt need to have to have a specular map/texture. Just play with the _Shininess value, for the, well, "shininess" Also... Looing pretty good so far

Just note, that idk if there *could* be any potential conflict with Through the Eyes

@Doggo mebbe look into this mod?:

Mebbe check out how @Climberfx did their's, with this? vOv https://youtu.be/S6yXh4HxbGY?t=1439

MOARdvPlus uses a very old FASA internal model. IIRC, BDB has its own, newer IVAs, and IMHO, the time would be better spent populating the new BDB models with MAS props, than supporting FASA ivas that may not even fit with the new BDB models.

If you mean the ".0", I've noticed its KSP-AVC that seems to be parsing that out... I've seen it on other mods

Dammit, Jim!! My 1st mis-post, messing up by ass-u-ming this was KSP *1* related... lol

AirPark mod?

it *could* also be the culling masks on the lights/parts are incorrect? vOv

@Linderoth For ASET Props & ASET Avionics, you want the ASET Consolidated versions. Those two packs do nothing by themselves. They are libraries of props, "items" that get placed into IVAs. RPM & MAS are the mods that make them "work", and "do things". (Both RPM & MAS do have their own smaller libraries of props included in them, as well as some basic, example IVAs) DE_IVA Extensions & MOARdV Plus, are finished IVAs. these are mods that are basically the "maps" or "container", of where people have placed all the props.

hmm.. how did I miss this originally? @Fishfinger are you still around? I might be able to help with the issue.

what HebaruSan said above... it ended up that Spanner decided to leave the community, IIRC, and basically we are left with:

Hmm.. changelog is pretty thin... Why?.. whats the difference?

Yes, you need to extract all the files. Even though some of the files in JSI Part Utilities are title "rasterpropmonitor", the only thing the files in PartUtilities and RPM have in common, is the shared /JSI/ folder. Otherwise ALL the files from the RPM mod, and the PartUtilities mod are exclusive to each mod, now. And yes, ERS and JSI PartUtilities work fine in 1.12.5

Mae sure you have actually placed some of the camera parts on your craft. Then, it should just be a matter of hitting the "EXT CAM" or External Camera button(s) on the MFDs.

For IVAs, *generally*, I see you want root object at 0,0,0 rotation. Then an empty child right below it, for the rotation. Try -90° on X, 180 on Y. You want it oriented in relation to the external, so the front points out the *bottom* of the exterior part (thats the -90 on X)... then rotate Y 180, which should spin it lengthwise, so the IVA is now upside down in relation to the exterior part. IIRC, this is also using X/*Z*/Y cood system.

@nascarlaser1 I assume you've read the wiki on the repo?

I havent used Linux in a few years... Tho i *did* use Blender with it at the time... I have no no idea

Well, you never said what version of KSP you upgrading *from*... Also, that tree listing doesnt show a /GameData/ root folder..?? You also, for one thing, have an "/Extras" folder, for Restock... that would need to manually be adjusted for that stuff to end up somewhere in the actual "/Restock" folder, I believe vOv You also have an outdated (tho not very) ModuleManager version

@Krazy1 yes, "SyncModuleControlSurface" is a module from Atmosphere Autopilot. IIRC, there *always* may have been a conflict when having AA *and* MJ installed at the same time? I cant remember, but I wouldnt be surprised.

@Hippodingo Wow!... NICE!

...*OR*... some other mod, could have patched in MJ modules, or "cloned" a part using them

What version of RPM and DE_IVA are you running? I would double check them, as I seem to remember this issue (or at least one regarding DE_IVA & ResearchBodies Telescope part), being fixed in a very recent update of either RPM or DE_IVA. If after verifying you have the latest updates of all three mods (ResearchBodies included), you still have an issue, come bac and post links to your *full* KSP.log Instructions on how to do that, here: