RookFett

I don't believe so - since there are no errors suggesting that. going to try to some more troubleshooting - been logging what I have been doing, so not much left. No Joy - Fresh copy of KSP 12.2, steam validated. V112.0 and V112.0.1 bleeding MKS used - only MKS/USI/Vessel mover mods installed. Still getting Null Ref WOLF.WOLF_CrewTransferScenario.OnDestroy and (OnAwake). I did everything I can think of - still cant get crew transfer menu to show up. Made three depots, shores, KSC, Orbit. Setup a crew transfer between KSC and Shores - 2 pax each way - zero cost. Used the Wolf Terminals 10m - with power, put Kerbs in the terminal, click the PAW menu for crew transfer, nothing pops up. Null Ref shows when I had troubleshooting turned on in the cheat menu (log errors to screen). Check of the logs shows the same error I have been seeing. BTW - part of my testing was to see if having zero cost routes was causing the issue, it is not, even routes with transport costs will cause the menu not to show. Here are my Log Files from my last play test. Guess I will wait till either @RoverDude or @DoktorKrogg have anything to say about this - I might be pulling the wrong version or something - not sure. Is anyone using the new Wolf stuff have this working? if so, what versions of MKS are you using?

Running all the pre-release/cutting edge programs - i am a testing fool. KSP is 12.2 - only mods are hyperedit, vessel mover. Wolf version is 112.0 - 2021.09.19 Can't seem to get the Crew Transfer menu to open - and the Null reference is showing in the KSP.log about WOLF.WOLF_CrewTransferScenario.OnDestroy.

Any news on the Crew Transfer menu not showing when trying to transfer crew? Getting Nulls in the log.

from the OP: Under no circumstance is this mod, or any derivative of it, authorized to be released on CKAN or any other mod management tool without my express written consent

No patch that I know of - however @RoverDude has acknowledged he has some fixing to do on them.

If your subscribe to the repo, you get emails on the updates: 112.0.1-bleeding edge 1 - but only MKS is updated in this release, the pre-release you found is the full USI package.

I did some more testing - initial setup: Setup 4 depots - KSC, Shores, Flats, LKO. initially setup cargo routes first. KSC connects to shores and LKO. Shores connects to flats. LKO connects to flats. I used hyperedit / vessel mover to move stuff around, so this will make all routes zero cost. used the cargo routes to add habitation and life support to all depots for the crew terminals. Then I tried to setup once I connected the terminal to the depot, if I tried immediately to start a route, I will get the error as you state. however, if I save and exit to main menu, and go back into game, I can now start the pax route. It did this for every route I made. I stumbled on this because I was exiting to the main menu screen to look at the save file - and it worked. Btw the save file did show the terminal I was trying to connect to, but again, had to reload the save to see that terminal, speculating something is not reading in real time. I did not try to change scenes during this - this may let it read that you have terminal in the biome. Found if you switch scenes between connecting the terminal to the depot and trying to start a route will allow you to start the route, and you wont see the error of a terminal not in 500 m. With all that, still can’t get the terminal crew menu to pop up from the terminal PAW, and the save shows the crew routes as boarding. Which prevents actually moving crew. In the Wolf dashboard, there is a button for Crew in the Depot tab, but nothing appears for it to show anything. running pre-release constellation with bleeding edge MKS, with latest version of module manager, hyperedit, vessel mover. errors seen is the null ref in KSC.log about the crew module. Saw that this was reported in April - so I closed my ticket - awaiting fix... will be writing up another trouble ticket on the “can’t connect” error - all ready have one in for the PAW menu

That occurs for me. If I start the route in shores first then move to KSC - it works most of the time. But sometimes it says the error. I haven’t found a pattern to this one, yet. looking into the save file - I can see the routes set up for crew, but since I can’t open the crew transfer menu, can’t move them. only error i see is the crew module null reference in the log.

So I cant get the wolf terminal window open - suspect a bug, so I opened a ticket at github. (Saw a null ref in the log about crew transfer) Cant transfer crew - but cargo is working as intended.

The route is based on mass, as you lose mass, the cost (transport) goes up. So a multistage will shed more mass, causing it to increase the cost to get to orbit. A spaceplane will only lose mass as it burns fuel, so if you replenish it in orbit before completing the route. it will add that mass back, making the cost go down. Been sandboxing the bleeding edge MKS/USI stuff, and after setting up a crew route between KSC and Shores, I cannot get the PAW crew transfer window to open. What is suppose to open when you click that? anybody have it working - can you share a screenshot? I have cargo routes up and running - but the crew transfer is just sitting there, not working - I put in kerbs, but they do not transfer. (zero cost routes using electric rovers) - but I did make one route (1 TC) to see if that changes something -- it did not. (this is running only hyperedit, USI, and vessel mover mods)

@RoverDude will the Konstruction parts allow for lifting heavy objects in the new stock construction mode in future updates, as they did with the KIS/KAS mods? I am running the cutting edge Constellation package, and it doesn't seem to be doing it.

remove it using ckan and re-install - Roverdude made an error in the first iteration - you might have that saved in your storage. (if that doesn't work - remove it with ckan - then manually install using the link - see if that helps)

You have to download the firesplitter fix that Roverdude posted - it will fix that issue. Fix

Your fine - those are in the full ground construction install - missing in the "core" ground construction MKS gives. (you can get them from the ground construction zip and install them yourself - i haven't seen any issues not having that other than that error)

Did a search in this thread - are replacement parts and the break down of Life support working, testing stuff and can't seem to get that to show up. any pointers?

@RoverDude Nice intro to WOLF last night on Twitch - look forward to trying it out and killing kerbals! Thanks for the effort on improving the game play.

Hoping any day now

Works in game now --- moving on

Concur - i tried to use the two files - Release | Bin - firespitter.dll and firspitter.pdb (they are newer) - but seem to have the same error.

* Grab * thanks!

It's not out yet - and the firesplitter core should be compatible with 1.7.3 - Still working on my vids - ironing out the vids now in premier .

Sweet - making some tutorial vids with USI/MKS/LS - going through the scripts now for taping - all the functions other than the container issue seem to be working 100% - so yay!

Will that show up on Github?

Ah - was looking at MKS for the issue - not stock - thanks for the heads up

Weird issue - went through the thread and Github and didn't see anything matching this, but since I've upgraded to the latest and greatest USI/MKS/LS - my PAW for changing the cargo for containers seems to add the next selection to the existing window, so if you click it once, two cargo's (original and next selection) show, with each click showing up as you go through, next or previous. Only MKS/USI/LS mods installed - with full ground support and configurable containers. (next step is to remove ground and config containers since they are 1.7.2) - KSP 1.7.3 MH 1.7.1 BG 1.2.0 installed. Whatever is on the top of the list is selected when you exit the PAW - is this how it works now? Before I dig deeper, I would like to know if anyone else is seeing this? Example: Opening PAW for container - after selecting "next cargo" Shows both cargo's selecting Previous Cargo: and previous again: if I exit out of the PAW - whatever is on top of the cargo list is selected for the container (i opened the PAW again): No errors appear on screen, but I did see this in the KSP.txt: [LOG 12:44:19.376] [MessageSystem] Save Messages [LOG 12:44:19.384] Game State Saved to saves/default/persistent [WRN 12:44:38.806] *PartUtils* Unable to find UIPartActionWindow list [LOG 12:44:38.806] no UI to refresh [LOG 12:44:40.966] deleting part C3.Kontainer.01 [WRN 12:44:41.690] *PartUtils* Unable to find UIPartActionWindow list [LOG 12:44:41.691] no UI to refresh But this happens when I exit the VAB - so I don't *think* that is pointing to any issue here. (going to remove all the mods on a fresh install and just add the MKS bare minimum to see if it happens)