Print

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

[AnXel LG]

You'll have to go into the mod folder, then data>wolrd>factions, then open the ".faction" files and lower the rates you see there to ensure they're in line with the new vanilla weights. I'd probably suggest removing the Niagara from the priority ships and see if that fixes the issue (haven't tested myself, but worth a try)

Works well, thank you! I had to do a lot of tuning including with other mods to make things look like I wanted, but that's probably just my own standards and the mod loadout I've got.

Wait, What??? I wonder what you guys consider an "adequate spawning rate" because we clueless mortals are bound to get things going downhill if we mess with game files. So PLEASE, some RECIPE for adjustments would be VERY MUCH appreciated. Take pity on us, you GODS'N GODDESSES of coding 

From what I see, the big problem is just factions having Niagaras and such shoved in the "prioritize" category. This means that especially for factions that don't have other prioritized ships there these ships will just be far too common, so commenting those lines out with a # solves most of the problem. The other thing to keep in mind is that most ships have all their probabilities sum to 10, which means that if you want them to be less common just lower those probabilities a bit.

Thanks for the tip. I'll take a careful look at it and tinker myself a little bit, see what I can do to fix the Niagara spam and tune it down in Luddic fleets

[MnHebi]

https://drive.google.com/file/d/1eXKtI2zVEmM2BxOEH-Ythmvjya5UjtAH/view?usp=sharing
Updated for 0.97, no changes to source code, just updated version info. Commented out priorityships from all factions.

[AnXel LG]

https://drive.google.com/file/d/1eXKtI2zVEmM2BxOEH-Ythmvjya5UjtAH/view?usp=sharing
Updated for 0.97, no changes to source code, just updated version info. Commented out priorityships from all factions.

  YOU ABSOLUTE LEGEND!!! Thanks a lot man.  I ended tweaking it myself and is working fine at the moment, but I'll take your lead right now.

[Bastion.Systems]

Thanks for that, I tried to just lower rarity value in ship_data.csv and wondered why it didn't seem to have an effect.

[Lance]

https://drive.google.com/file/d/1eXKtI2zVEmM2BxOEH-Ythmvjya5UjtAH/view?usp=sharing
Updated for 0.97, no changes to source code, just updated version info. Commented out priorityships from all factions.

Warning, i havent yet identified why, but this bootleg seems to behave very weirdly on game startup. Random corruption crashing the game after 2 seconds. The problem is the randomness, if it loads fine once, it loads fine for a long time and the game is totally playable but it will not load again after a while if memory has been dumped.

it could be file corruption or maybe i didnt delete another bootleg related to it, so if you dont have problems with it, it's fine.

[Phenir]

https://drive.google.com/file/d/1eXKtI2zVEmM2BxOEH-Ythmvjya5UjtAH/view?usp=sharing
Updated for 0.97, no changes to source code, just updated version info. Commented out priorityships from all factions.

Warning, i havent yet identified why, but this bootleg seems to behave very weirdly on game startup. Random corruption crashing the game after 2 seconds. The problem is the randomness, if it loads fine once, it loads fine for a long time and the game is totally playable but it will not load again after a while if memory has been dumped.

it could be file corruption or maybe i didnt delete another bootleg related to it, so if you dont have problems with it, it's fine.

No crash log?

[Lance]

the crash log changes based on the files corrupted, sometimes the log file contained oooOOOOoo stuff but nothing conclusive.
However it seems related to missions, but not specifically to the files named in this screenshot.
bootlegs from unofficials sources share the same problem.

[MnHebi]

That is not the log, its Starsector.log that popup mentions. And the fatal error there is clearly relating to the VIC mod, not this one. I haven't had a single problem with starting new games or loading games.
Also, it is not really a "bootleg" since it is done with permission, it is an as official update as it can get. Bootlegs are done without permission.

[Lance]

as i said, the changelog varies, even the targeted files vary in the screenshot. And it crashes randomly at start up.

It doesnt happen without torschships 0.95 nor it's bootlegs or your file
Once again, it could be related to something else.

Vic is shown on the screenshot, but sometimes it's pagsm, or something else first.
It also happens without vic, or pagsm. Or some others mods. Whenever Torchships is enabled, it happens randomly. Disabled; it doesnt happen.
However, usually a "mission" file is targeted... but it could be related to how the game parses the files.

sometimes the log file is not even updated.

If the log file was reliable for this specific problem, i would have shown it instead. It is not.

not this mod, after many tests, it still happen without it.

[MnHebi]

Well, I recompiled the jar, and updated mod version number, and uploaded it to GitHub now.
https://github.com/MnHebi/Torchships/releases/tag/0.18
Try that and see if that fixes your weird crash.

[Lance]

Dam sorry, after one more try, it did happen without this mod, my apology. I made you act, while i should have been clear that it could have come from my side.

The randomness screwed me, my deduction was based on a reboot/ load memory with another game/ test mod / reboot cycle, which takes a lot of time, and it never crashed without your mod until now. For such *** randomness i havent found a proper methodology yet.


edit: after many hours, it looks related to pagsm but not vic. It could be an interaction with other mods, pagsm has a lot of compatibility/ enhancement stuff. The randomness of the crash could depend of the load order of something... Weird ***.

Sorry for the waste of time, once again, i will ask about that on pagsm thread ;o

edit: no pagsm either. I start to wonder if it's hardware problem.

edit: it's cops that induces this random behaviour.