Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[SwaggyCthulhu]

Code

396379 [Thread-3] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.IllegalArgumentException: Color parameter outside of expected range: Alpha
java.lang.IllegalArgumentException: Color parameter outside of expected range: Alpha
	at java.awt.Color.testColorValueRange(Color.java:310)
	at java.awt.Color.<init>(Color.java:395)
	at com.fs.starfarer.api.impl.combat.DroneStrikeStats$DroneMissileScript.advance(DroneStrikeStats.java:68)
	at com.fs.starfarer.combat.entities.CustomCombatEntity.advance(Unknown Source)
	at com.fs.starfarer.combat.CombatEngine.advanceInner(Unknown Source)
	at com.fs.starfarer.combat.CombatEngine.advance(Unknown Source)
	at com.fs.starfarer.combat.CombatState.traverse(Unknown Source)
	at com.fs.state.AppDriver.begin(Unknown Source)
	at com.fs.starfarer.combat.CombatMain.main(Unknown Source)
	at com.fs.starfarer.StarfarerLauncher.super(Unknown Source)
	at com.fs.starfarer.StarfarerLauncher$1.run(Unknown Source)
	at java.lang.Thread.run(Thread.java:748)

Just in the last day I updated Gensoukyou Manufacture (https://fractalsoftworks.com/forum/index.php?topic=28396.0) to its latest release, which necessitated the installation of BoxUtils. I also installed Orky Sector (https://fractalsoftworks.com/forum/index.php?topic=29956.0). Those are the only recent updates to my modlist, and I'd never experienced this particular CTD before making these changes.

The crash only occurs during combat. I have yet to use, or encounter any Gensoukyou Manufacture content in-combat, so I doubt that mod's the culprit. I have been using Orky Sector ships and weapons, but I've failed to notice any connections between that mod's content and the crashes. I think it's either Orky Sector or BoxUtils, but I'm not savvy enough to extrapolate anything from the log. Some guidance would be appreciated.

These are the mods I've had enabled while experiencing the issue:

"console_additions",
  "aria",
  "armaa",
  "zzarmaa_anime",
  "AttunedDriveField",
  "battletechportraitpack",
  "yrutl",
  "CJHM",
  "clearCommands",
  "chatter",
  "timid_commissioned_hull_mods",
  "lw_console",
  "consolegalaxy",
  "dmodservices",
  "dex",
  "EmergentThreats_Vice",
  "EmergentThreats_IX_Revival",
  "fleet_journal",
  "furryPortraits",
  "FantasyM",
  "HMI_SV",
  "HMI",
  "IndEvo",
  "Imperium",
  "timid_xiv",
  "knights_of_ludd",
  "lost_sector",
  "lw_lazylib",
  "lunalib",
  "exshippack",
  "MagicLib",
  "Mayasuran Navy",
  "Mimikko",
  "nexerelin",
  "yrex",
  "looted_sector",
  "particleengine",
  "planet_search",
  "assortment_of_things",
  "RetroLib",
  "roider",
  "secretsofthefrontier",
  "swp",
  "mayu_specialupgrades",
  "supportships",
  "Terraforming & Station Construction",
  "timid_tmi",
  "underworld",
  "uaf",
  "US",
  "unthemedweapons",
  "vulpoids",
  "whichmod",
  "whichtmi",
  "XhanEmpire",
  "yrxp",
  "BoxUtil",
  "shaderLib"

Thanks.

[Histidine]

The crash is from the Termination Sequence ship system ('drone strike'). Eyeballing the code, it looks like it should only happen if the fake missile used for the system has... negative range?
Anyway see if the crash happens with any ship in your fleet or that you've been fighting, that has that system.

[SwaggyCthulhu]

The crash is from the Termination Sequence ship system ('drone strike'). Eyeballing the code, it looks like it should only happen if the fake missile used for the system has... negative range?
Anyway see if the crash happens with any ship in your fleet or that you've been fighting, that has that system.

Thanks for the tip.

There are modded tempests in my fleet, but I've played with them semi-regularly over the last IRL year, and never experienced any issues. Now I'm suddenly getting this color parameter CTD in every other battle. None of the fleets I've been fighting immediately before a crash have had the drone strike system. I assume some recent change in my mod list has affected that ship system, and the ships' parent mods aren't to blame.

I tested all of the ships in my fleet with drone strike individually, but none of them caused a crash, or exhibited any issues in the sim. The ship system seems to work normally.

None of the ships in my fleet with that system have any hullmods installed that should affect missile range, and I don't even know if normal missile hullmods affect drone strike stats. Also, I don't have any mods installed that should affect missile stats globally. Do you know if fighter wing range mods might affect drone strike missile range? I do have modded hullmods installed that impose heavy wing range maluses.

Why would the missile range being bugged into the negatives specifically cause a color parameter CTD?

I'll post the next crash log here if it's any different than the last.