when expeditions with drone or colonist by rocket, rocket do not lunch and cancel button disappear bug.

the log points to a specific code for this mod.

[LUA ERROR] PackedMods/2619013940/Code/BLR_1Init.lua:740: attempt to call a nil value (method 'HasDestination')
(1080): method Find
Mars/Lua/Buildings/CargoTransporter.lua(70): <>
Mars/Lua/Buildings/RocketExpedition.lua(509): <>
[C](-1): global sprocall
D:\Program Files (x86)\Steam\steamapps\common\Surviving Mars\CommonLua\Classes\CommandObject.lua(118): <>
--- end of stack
time 0:08:47:688

Make sure you have the latest version of the mod.

thanks. it works well.

I can't seem to launch the asteroid lander with the mod enabled when there are any RC Rovers as cargo. If I remove the rovers from the loadout, it launches. Also if I disable the mod in the config menu it launches also.

Originally posted by Synoxys:

I can't seem to launch the asteroid lander with the mod enabled when there are any RC Rovers as cargo. If I remove the rovers from the loadout, it launches. Also if I disable the mod in the config menu it launches also.

I am not able to reproduce this. If you have the rovers, and they are idle, they will be taken.

I tried again in a new save and it worked this time. Perhaps something was wrong with my old save. Thanks for the reply!

I ran into this bug as well. This mod worked great on my last save but on the newest one (I added a few mods) it caused the same issue @Synoxys was having. I'm not completely sure of the cause but I think it has something to do with the wasp drones Japan uses. I believe this because the only mod I installed for the new save that affected drones is one that grants wasp drones to every faction. Disabling that mod didn't fix this issue but disabling Better Lander Rockets did.

To give more details on the problem: I could fill landers and launch them. They would land on the asteroid and then wouldn't deploy their drones. This resulted in them being stuck on the asteroid. I tried sending another lander (imagine getting that approved lol) with nothing but some drones and an RC - the RC was able to deploy but the drones were still trapped.

The mod I'm referring to: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1592984375

Things I tried (Confirming a lander failure with each attempt)
-I disabled that mod
-I made sure all drones that went with the lander were normal drones
-I re-enabled it and switched all the drones on the map to non-wasp drones
-I disabled the mod after making sure all drones on the map were non-wasp drones

The only fix was disabling Better Lander Rockets. The landers now work as intended. I tried all the stuff above first because I know Better Lander Rockets worked on my last save, but yeah - something about this mod seems to break landers, but only sometimes?

Let me know if there's any way I can help!

Originally posted by A Magnet:

I ran into this bug as well. This mod worked great on my last save but on the newest one (I added a few mods) it caused the same issue @Synoxys was having. I'm not completely sure of the cause but I think it has something to do with the wasp drones Japan uses. I believe this because the only mod I installed for the new save that affected drones is one that grants wasp drones to every faction. Disabling that mod didn't fix this issue but disabling Better Lander Rockets did.

To give more details on the problem: I could fill landers and launch them. They would land on the asteroid and then wouldn't deploy their drones. This resulted in them being stuck on the asteroid. I tried sending another lander (imagine getting that approved lol) with nothing but some drones and an RC - the RC was able to deploy but the drones were still trapped.

The mod I'm referring to: https://steamhost.cn/steamcommunity_com/sharedfiles/filedetails/?id=1592984375

Things I tried (Confirming a lander failure with each attempt)
-I disabled that mod
-I made sure all drones that went with the lander were normal drones
-I re-enabled it and switched all the drones on the map to non-wasp drones
-I disabled the mod after making sure all drones on the map were non-wasp drones

The only fix was disabling Better Lander Rockets. The landers now work as intended. I tried all the stuff above first because I know Better Lander Rockets worked on my last save, but yeah - something about this mod seems to break landers, but only sometimes?

Let me know if there's any way I can help!

Did you try a new game without any new mods?
Like I said I cant replicate this issue, and I dont use any other mods but my own, so its a whatever you added after the fact that.

Choggi and I talk all the time. I know how his mod works. It does not "grant" access to wasp drones to other sponsors. What it does is intercept the code to use the asset class shell. The sponsor still thinks its using what its using before.
I suspect the code for respawn, which is how the drones are "released" on landing is being interfeared with the intercept of my code.

I'll check with Choggi if there is something we can do to make some cooperating code but at this time I suggest not loading both mods together.

I'm getting this issue as well, however it's also happening without ChoGGi's mod, and on NASA Sponsor.

The issue was that it wasn't even picking up the Prefab'ed Asteroid Mining facilities.

I've tried several things, only disabling the mod seems to fix this, I've pinged you on Discord with the error I'm getting, even pinged it at ChoGGi.

Originally posted by McKaby:

I'm getting this issue as well, however it's also happening without ChoGGi's mod, and on NASA Sponsor.

The issue was that it wasn't even picking up the Prefab'ed Asteroid Mining facilities.

I've tried several things, only disabling the mod seems to fix this, I've pinged you on Discord with the error I'm getting, even pinged it at ChoGGi.

Thanks for the log file.
I dont get those errors so it seems like something may be stepping on lander code.

In any case I added some checks to prevent that condition.
New mod on the workshop, just make sure you get v1.5.1
Let me know what happens and if any new errors crop up in your logs.