Red Dwarf

Solved one problem, only to be confronted by a new one It looks like there is a tunnel in the model which would allow for moving through to the attached crew tube, but the internal wall texture is blocking access to it. This is the only thing that's changed from the previous cfg. If making this work goes beyond cfg editing, it's probably a lost cause for me to do on my own.

Is the highlighted line the only thing controlling whether a hatch can be moved through? I've been doing my testing on the short 3.75m hab from SSPX. I've figured out how to correctly place the attachment node, but the hatch is still registering as obstructed. In the hitchhiker, the eva option is replaced with an "open door" option. This is the edited cfg. I basically just copied the highlighted lines from the hitchhiker cfg and changed the names/parameters to match the new model.

Is it possible to add attachment nodes through cfg editing? I've noticed that the stock hitchhiker and lab parts have nodes on their external doors that are compatible with freeiva, and it would be really useful if I could add that functionality to other parts.

Is there a way to manually activate a strategy even if the requirements aren't met? Maybe through editing the persistent file for the save? I accidentally did a manned Mun flyby before accepting the Mun program strategy, and I can't figure out how to undo that progress.

I've honestly found the pace of science unlocks pretty reasonable. That being said, I am running full near future/far future, also I have unlock costs on as well.

Not sure if this has been asked already, but how does this mod interact with Bluedog's contract system? I was looking at the contracts added by Bluedog, and they seem to use stock tech tree nodes as criteria for when the contract can be accepted (for example, one contract required that "Miniaturization" be researched before it would be made available). Since Skyhawk changes those tech nodes, will I ever be able to accept those contracts?

Scatterer version is 0.0772. Apparently the .08xx releases of scatterer are incompatible with AVP, so I haven't updated yet.

So for the past little while I've been trying to iron out an issue caused by the way Astronomer's Visual Pack applies Scatterer to OPM, specifically Thatmo. Using this combination of mods, from a distance Thatmo is this lovely blue color. However, as you approach the atmosphere abruptly changes to Thatmo's default coloring. I'm trying to get it so Thatmo stays blue in all situations, rather than just at a distance. This doesn't happen around any other planets, and checking the debug menu didn't reveal any obvious errors, so everything seems to be working correctly. It's just that some key variable somewhere is labelled incorrectly. My understanding of this is that because Scatterer doesn't natively support OPM, AVP has to tell it how to render the atmospheric haze. It's doing that properly for scaled space, but isn't doing so in macro space (or whatever the opposite of scaled space is idk), and so the atmosphere defaults to OPM's normal settings. I'm certain the solution is in the Thatmo CFGs in OPM and AVP. The problem is, I'm not very experienced at working in the guts of mods like this, and I'm not sure what any of the variables refer to or what they do. Like, I have no idea what PQS deactivateAltitude is, but I know it has to be relevant because the value of that variable (218400) is the same as the altitude at which the change happens. This is everything that I think might be relevant from Thatmo's KopernicusConfig CFG in OPM. And this is Thatmo's Scatterer Atmo CFG from AVP. I really don't know the best way to approach this. I'm really just guessing at what most of these variables actually do, and changing values at random hasn't seemed to have any visible effect. Does anyone know what might be happening here? Is there a way to fix it?

I've been having an issue with scatterer and opm, where the atmospheric haze around Thatmo will disappear past a certain threshold (about 300km). Testing showed that it was AVP causing this behavior, but poking around in the Thatmo Atmo (heh) cfg hasn't been super productive, since I can't tell what most of the variables actually control. I'm including that cfg if anyone wants to take a look at it and see what dials I need to turn to stop this from happening.

Still seem to be having problems around Vant. It's still janked, but it's a new texture now. Latest patch, no other mods.

Is it possible to transplant conversion modules from one part to another? I want to move the fertilizer production away from the ISRUs and into the SSPX Aquaculture lab, to give it some functionality outside of being a resource recycler.

Certainly possible, I only have a couple hundred other mods going at the same time. Really though, the only likely candidate I could think of causing this is either stock (as WarriorSabe suggested), or CTTP, which is bundled with OPM. I don't see how it could be that last one though, since I assume you're also using that.

Just tested, and nope, the speckle persisted across both quicksaves/quickloads and hard saves/loads.

I've noticed some weird graphics stuff around Vant. Somewhere between 210 km and 200 km, the surface texture switches from the grey visible in the map view to a really intense speckled pattern. The pattern rescales itself as you get closer to the surface, maintaining the size but reducing the resolution. This happened in both 1.1.6 and the most recent release, was wondering if I had just installed something wrong. Zoomed out just past the threshold: Zoomed in just inside the threshold: The surface texture is pretty crunchy.

The nullref issue has also been raised in the SSPX thread, with both mods isolated to just them + respective dependencies. This interaction also seems to prevent labs from transmitting their accumulated science.