Fractal Softworks Forum

Please login or register.

Login with username, password and session length
Advanced search  

News:

Starsector 0.97a is out! (02/02/24); In-development patch notes for Starsector 0.98a (2/8/25)

Pages: 1 ... 8 9 [10]

Author Topic: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"  (Read 145577 times)

EnigmaniteZ

  • Commander
  • ***
  • Posts: 161
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #135 on: October 14, 2024, 05:34:08 AM »

just to bring up what I mentioned on the VRI discord:
the volantian automation crash is NOT platform dependent, it's because of how it is coded.
the code uses a fixed table to select the 'core' cosmetic, based on hull ID. the game returns hull IDs differently (again, not case sensitivity here), problem of course being that there are hull IDs popping up that arent on the list. instead of checking for null, the code just goes...and crashes. the fix requires recompiling the mod. the source code is in /src/data/hullmods/VolantianRemnantConversion.java. the function in question is applyEffectsAfterShipCreation.

a 'reasonable' fix is to add a check for null...but since the 'core' visual looks awful on most ships (as in: it obscures the entire model on smaller ones) I ended up  just removing the visual application entirely. to do so, just comment out everything within the function...or remove it. commenting is more recommended. then recompile.
Logged
Also known as: Khe, Kherae. Pros: tend to be an optimizer and a fixer. Cons: ADD (Is that a squirrel over there?) and severe memory issues (as in: I'm the last 10+ years)

Dear fellow coders: please use more null checks...

MakoMakoMan

  • Ensign
  • *
  • Posts: 12
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #136 on: November 14, 2024, 05:13:46 PM »

I suppose this is a strange thing to ask but is there a way to "kneecap" this faction? It is grossly overtuned in the sense it curbstomps every other faction after I allied it, I had to revert some of its conquests to revitalize factions I wanted to wage war against because VRI had swallowed up two factions and was on the verge of capturing the last market of a third one I really wanted to fight to syphon their blueprints. I know I can always just give back markets again but I'd like to stop VRI from taking so many markets so quickly.
Logged

Mekis

  • Ensign
  • *
  • Posts: 2
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #137 on: November 30, 2024, 04:17:52 AM »

Is Espoz still incredibly bugged for anybody else? The Hedgie and Independent colony there function as normal but any time I try to settle more than one planet there it bugs out my entire colony roster. I also flat out can't settle the Aberdeen world.
Logged

Uther Phobos

  • Captain
  • ****
  • Posts: 309
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #138 on: December 03, 2024, 07:04:27 PM »

Is Espoz still incredibly bugged for anybody else? The Hedgie and Independent colony there function as normal but any time I try to settle more than one planet there it bugs out my entire colony roster. I also flat out can't settle the Aberdeen world.
That's because it creates the random planets twice with the same settings, so they share IDs which causes things to break. You can fairly easily fix this in the save by just making sure each individual planet has its own unique ID. You might have to re-settle broken colonies though.

On the upside that means the system has more planets than normal.

No idea what's going on with Aberdeen though.
Logged

1nnovation

  • Ensign
  • *
  • Posts: 1
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.1 "Unforeseen Nyansequences"
« Reply #139 on: January 05, 2025, 12:29:53 AM »

From what I can gather, there is a bug in the Colony Crisis event. The VRI Incursion should only occur if your colony is within 10 Lightyears of one of theirs. But for some reason it triggers even if the nearest VRI colony is more than 10LY away, and once enough crisis points have accumulated. The game crashes.

Wow, the faction is so powerful that if you fail to stop their plans they collapse reality itself lmao
Logged

Vaelophisnyx

  • Lieutenant
  • **
  • Posts: 65
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #140 on: January 12, 2025, 11:41:52 PM »

is there a copy of this from before 0.6 was dropped? Would like my VI BG ships back while I wait for what's coming >:/
Logged

BlasingIce

  • Ensign
  • *
  • Posts: 7
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #141 on: January 28, 2025, 07:40:13 PM »

Looking forward to non-nexerelin version!
Logged

toynbeeidea

  • Ensign
  • *
  • Posts: 5
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #142 on: January 30, 2025, 10:56:59 AM »

Mod is not loadable in Linux.  A number of files are capitalized in the filenames, but the game is looking for non-capitalized versions.
« Last Edit: January 30, 2025, 10:58:57 AM by toynbeeidea »
Logged

Bald_Greg

  • Ensign
  • *
  • Posts: 22
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #143 on: February 14, 2025, 02:38:46 PM »

Yeah VRI does not like arkships (crashes my game as soon as it moves close enough, it's a mobile colony)
Logged

Glissa

  • Ensign
  • *
  • Posts: 4
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #144 on: February 24, 2025, 06:13:23 PM »

Mod is not loadable in Linux.  A number of files are capitalized in the filenames, but the game is looking for non-capitalized versions.

To expand on this, below is a list of items I found which are affected. Changing file names as indicated corrects any issues. -

Code
Volantian Reclamation Initiative/graphics/ships/Caelum.png > caelum.png
Volantian Reclamation Initiative/graphics/shaders/chromatic/chromatic_VRI_material.png > chromatic_vri_material.png
Volantian Reclamation Initiative/graphics/shaders/chromatic/chromatic_VRI_normal.png > chromatic_vri_normal.png
Volantian Reclamation Initiative/graphics/shaders/chromatic/chromatic_VRI_surface.png > chromatic_vri_surface.png
Volantian Reclamation Initiative/graphics/shaders/sentinel/sentinel_VRI_material.png > sentinel_vri_material.png
Volantian Reclamation Initiative/graphics/shaders/sentinel/sentinel_VRI_normal.png > sentinel_vri_normal.png
Volantian Reclamation Initiative/graphics/shaders/sentinel/sentinel_VRI_surface.png > sentinel_vri_surface.png

Please check for your next release if you have time.
Logged

Reshy

  • Admiral
  • *****
  • Posts: 1202
  • White
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #145 on: February 27, 2025, 07:21:10 PM »

Huh, why does the VRI have genetech as a banned commodity?
Logged

dae

  • Ensign
  • *
  • Posts: 9
    • View Profile
Re: [0.97a] Volantian Reclamation Initiative 0.6.2 "Answer Of Disloyalty"
« Reply #146 on: March 03, 2025, 09:25:23 PM »

Getting a consistent crash when controlling an arkoship from Arthr's Ships n *** - seems to be related to VRI's coding relating to conflicts + revanchism

Code
2318793 [Thread-2] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.NullPointerException: Cannot invoke "com.fs.starfarer.api.campaign.StarSystemAPI.getHyperspaceAnchor()" because "system" is null
java.lang.NullPointerException: Cannot invoke "com.fs.starfarer.api.campaign.StarSystemAPI.getHyperspaceAnchor()" because "system" is null
at com.fs.starfarer.api.impl.campaign.intel.RevanchismVolantianHostileActivityCause.getProgress(RevanchismVolantianHostileActivityCause.java:93) ~[?:?]
at com.fs.starfarer.api.impl.campaign.intel.RevanchismVolantianHostileActivityCause.shouldShow(RevanchismVolantianHostileActivityCause.java:73) ~[?:?]
at com.fs.starfarer.api.impl.campaign.intel.RevanchismVolantianHostileActivityCause.getMagnitudeContribution(RevanchismVolantianHostileActivityCause.java:144) ~[?:?]
at com.fs.starfarer.api.impl.campaign.intel.events.BaseHostileActivityFactor.getEffectMagnitude(BaseHostileActivityFactor.java:105) ~[starfarer.api.jar:?]
at com.fs.starfarer.api.impl.campaign.intel.events.HostileActivityEventIntel.getTotalActivityMagnitude(HostileActivityEventIntel.java:692) ~[starfarer.api.jar:?]
at com.fs.starfarer.api.impl.campaign.intel.events.HostileActivityEventIntel.getTotalActivityMagnitude(HostileActivityEventIntel.java:685) ~[starfarer.api.jar:?]
at data.scripts.campaign.fleets.UW_CabalFleetManager.getHALevel(UW_CabalFleetManager.java:183) ~[?:?]
at data.scripts.campaign.fleets.UW_CabalFleetManager.getDesiredNumFleetsForSpawnLocation(UW_CabalFleetManager.java:137) ~[?:?]
at com.fs.starfarer.api.impl.campaign.fleets.DisposableFleetManager.updateSpawnRateMult(DisposableFleetManager.java:163) ~[starfarer.api.jar:?]
at com.fs.starfarer.api.impl.campaign.fleets.DisposableFleetManager.advance(DisposableFleetManager.java:146) ~[starfarer.api.jar:?]
at data.scripts.campaign.fleets.UW_CabalFleetManager.advance(UW_CabalFleetManager.java:93) ~[?:?]
at com.fs.starfarer.campaign.CampaignEngine.advance(Unknown Source) ~[port_obf.jar:?]
at com.fs.starfarer.campaign.CampaignState.advance(Unknown Source) ~[port_obf.jar:?]
at com.fs.starfarer.BaseGameState.traverse(Unknown Source) ~[port_obf.jar:?]
at com.fs.state.AppDriver.begin(Unknown Source) ~[port.common_obf.jar:?]
at com.fs.starfarer.combat.CombatMain.main(Unknown Source) [port_obf.jar:?]
at com.fs.starfarer.StarfarerLauncher.super(Unknown Source) [port_obf.jar:?]
at com.fs.starfarer.StarfarerLauncher$1.run(Unknown Source) [port_obf.jar:?]
at java.base/java.lang.Thread.run(Thread.java:1447) [?:?]
Logged
Pages: 1 ... 8 9 [10]