Configurable Nukes & ICBMs


Makes most/many aspects of the atomic bomb configurable, and affected by quality, as well as allows for the weaponization of rocket-silos: introduces an atomic warhead, ICBMs (Intercontinental Ballistic Missiles), IPBMs (Interplanetary Ballistic Missiles), and ISBMs (Interstellar Ballistic Missiles): why shouldn't rocket-silo rockets be used offensively?

Content
4 days ago
2.0
900
Combat Circuit network Manufacturing Cheats

b [0.7.3 - Fixed] Crash on rocket launch, except when launching at/near silo

https://i.imgur.com/oCD0CIx.png - When attempting to launch an ICBM, I get the following error; I get this error regardless of where I launch on the map, with the exception of launching literally on top of the silo. If I do that, then the launch proceeds as normal.

Let me know if you need more detailed logs.

Hello! Apologies for the issue, but thanks for the report. I'll definitely look into it and see what I can find.

Few questions though, if you don't mind:

  • Are you playing Vanilla, Space-Age, or with Space-Exploration?
  • What surface/planet is the silo on?
  • What are the coordinates of the silo?
  • What (if any) other mods do you have installed?
  • Is this true for any rocket silo, or only a specific one?
  • If you try launching it via a circuit-network, does it have the same result?

Space-Age
Nauvis
395.5/285.5
I have a few mods that affect silos, but I tested without those mods and got the same error.
I haven't tested other silos, I can do that in a bit.
I haven't tested launching via a circuit.

7 days ago
(updated 7 days ago)

Thanks for the quick response! I'll be curious to know if it occurs with other silos, or when launching via a circuit-network.

That said, have you changed any of the startup or runtime settings by chance? If so, does the error still occur when they are set back to their default values?

Also, forgot to ask above: does this error occur when no other mods are present other than this and "base"? Does it occur with just "base", as well as "space-age" and its dependencies?

And lastly, if you set the "Current logging level" setting to Warn, it should print out some extra relevant information in regards to what values it's actually using that are resulting in this error. The information should be printed to the Factorio log output file (if on a Windows machine, likely will be here: C:\Users...\AppData\Roaming\Factorio\factorio-current.log)

Would be looking for these lines:

  • Log.warn("rand = " .. rand)
  • Log.warn("threshold = " .. threshold)
  • Log.warn("deviating from target: " .. i)
  • Log.warn("deviation_limit = " .. deviation_limit)
    • And the Log.warn line immediately after this one

So, I've figured out how to recreate an error that, while not exactly the same one you reported, I believe to be related to the root issue you're experiencing. Currently still investigating.

Any updates? I got busy but I can try and provide those logs.

So, I've certainly found a gap in my logic with the "Guidance systems targeting deviation modifier" setting. Have you changed that setting by chance? Essentially, some values are going negative when they're not supposed.

Either way, I'm working on a fix that should hopefully correct that issue, and hope to have an update out as soon.

I haven't changed that setting, but I might try setting it to 0 and see what happens.

Also even on Warn logging level I only get:

Error while running event configurable-nukes::on_cargo_pod_finished_ascending (ID 11)
real number expected got inf.
stack traceback:
[C]: in function 'random'
configurable-nukes/scripts/utils/ICBM-utils.lua:225: in function 'on_cargo_pod_finished_ascending'
...gurable-nukes__/scripts/services/rocket-silo-service.lua:70: in function 'on_cargo_pod_finished_ascending'
...e-nukes__/scripts/controllers/rocket-silo-controller.lua:331: in function 'func'
configurable-nukes/scripts/event-handler.lua:69: in function 'process_event'
configurable-nukes/scripts/event-handler.lua:86: in function <configurable-nukes/scripts/event-handler.lua:80>
412.716 Info AppManager.cpp:352: Deleting active scenario.

On launch.

7 days ago
(updated 7 days ago)

With the release of version 0.7.3, this should hopefully be fixed.

Please do let me know if it continues, or if you encounter any other issues.

Yep it works, thanks you!

New response