Print

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

[Sludgecrawler]

Looks pretty
Looking forward to a Linux (Steam Deck) release!

[PasDeBras]

Tried the new launcher from my old SMOL config, works fine except i get ye olde battle camera not following the ship bug.
No idea what's causing it, launching the game from the vanilla launcher works just fine.
Maybe because TriOS doesn't port starsector.exe DPI scaling...
I don't know what else it could be.

Anyway, TriOS is unusable for me until this gets fixed, looks nice tho.

[Wispborne]

0.1.5
The Mod Profiles tab has been added, but the feature is too buggy to be enabled yet.
If you are having ingame issues when launching from TriOS, please disable the Skip Launcher option.

• Added
   
  • "Delete Mod" context menu item.
  • "Edit mod_info.json" context menu item.
  • "Open Folder" menu item now shows all versions installed.
  • "Dependents" info in the mod details panel, showing which mods depend on the selected mod.
  • About page on toolbar.
  • Shortcut to open Starsector folder on toolbar, which is getting a little crowded (but moved JRE tab off the toolbar, see below).
• Fixed
   
  • Chipper log viewer not correctly condensing consecutive lines.
  • MacOS LibArchive path (i.e. MacOS should work now).
  • MacOS grey screen if unable to create log file.
  • Now falls back to only console output if cannot create log file.
  • Also, now uses AppData on Windows and Library/Application Support on MacOS for the log file.
  • This avoids permissions issues to create the log file.
     
   
  • Freeze+crash when installing mods and the dialog came up (either multiple mods at once or reinstalling a mod).
  • Grey screen if using an old TriOS version after using a newer one that added a new setting.
  • Will reset settings to default if this happens, after making a backup.
   
  • Mod grid showed mods as Enabled incorrectly sometimes.
  • The "enabled" checked `enabled_mods.json`, but didn't check whether TriOS disabled the `mod_info.json` file.
   
  • Force Game Version didn't work for mods that were disabled and had multiple versions (i.e. had `mod_info.json.disabled-by-TriOS`).
  • Incorrect sorting in same cases (e.g. LazyLib `2.0` and `2.0b`).
  • Now sorts using `.version` file first, then by `mod_info.json`'s version with everything but numbers and periods removed, and finally by `mod_info.json`'s version without anything removed.
   
  • Toolbar icons needing to be scrolled to unnecessarily.
• Changed
   
  • Moved the JRE tab into the Dashboard.
  • Mods tab: in the version selector, versions are a different color if they are for a different version of the game.
  • Disabled mods with multiple versions will now use `mod_info.json.disabled` instead of `mod_info.json.disabled-by-TriOS`.
  • It's less obvious now why it's called `.disabled`, but it makes it cross-compatible with SMOL.
   
  • "Skip Game Launcher" is now disabled by default, since it can cause very weird issues.
  • e.g. zoomed-in combat, no Windows title bar, invisible ships.
   
  • Improved toolbar icons for game folder, changelog, and log file.

[Midnight Kitsune]

Just updated to SS .97 (finally) and that included my ~80 mods as well, so let me tell you about my experience with TriOS (TOS) step by step since I used TriOS from the start, blow by blow so to speak.
Game is installed on my OS NVME drive, so some issues I have have be because of this.

-For one, I used 0.1.4 as for some reason 0.1.5 is unavailable; it isn't on the github releases tab, the latest download tab, nor will TOS update to it. Don't know if this is a bug or if it is intentional.
+One thing I liked was that I could easily change the JRE version through TOS (after setting the compatibility option to run as admin). Loved this!
+Another thing I loved was the themes! Using THI one as it is the darkest that I could find. Would love to see a black and red one though!
--Sadly many themes don't work well with the VRAM estimator as about a third of the bars blend in with their backgrounds. The default theme works great for that though! (https://i.imgur.com/4Odi5YM.png)
+Speaking of the VRAM estimator, I like this feature as well. Although I couldn't figure out how to make it see my system's VRAM. Maybe add instructions on how to do that?
-One issue though that I ran into was that TOS, and all of its files, had to be in the root folder with the normal game's launcher to be able to change the VMPRAMS file due to file permissions issues. Made things quite messy in there. Before, I had it in its own folder in \SS\TriOS.
+Loved the ability to update the mods from the app right there! That will make things so much better and easier later down the line for the most part!
(+)StarModder support probably would have made things much MUCH faster to update if TOS had support, so I eagerly await the feature!
=The ability to filter via game version or filter and or sort by version checker support would be a nice addition
-I noticed that when I placed the mods' zip folders in TOS to update them, I ended up with both the old and new versions in there. Made things messy looking. Maybe an option to delete the old mods?
-I also ran into the issue that RegentMaxa ran into... Very annoying. It also reverted back to the default anytime anything changed with the mods, making mass mod_info changing a pain.
-One thing I noticed is that the Java 23 CLI window doesn't auto close when the game closes. Would be nice if it did as I do love having a "live log" right there, but I'm too lazy to close it. Just a thought.
-I have noticed that I get a crash now when not using TOS to launch the game. I suspect that this is due to using the Java 23 change but I would like to know if it is possible to allow the old launcher to work. Or at least make TOS close when starting the game. I like to keep things neat and tidy after all. If the error is due to the Java 23, then maybe place a warning about that on TOS Java 23 option.
The error I got when launching via the old launcher:

Spoiler

63493 [Thread-3] ERROR com.fs.starfarer.combat.CombatMain  - java.lang.UnsupportedClassVersionError: com/fs/starfarer/api/impl/campaign/rulecmd/ptes_riftGateDialog : Unsupported major.minor version 52.0
java.lang.UnsupportedClassVersionError: com/fs/starfarer/api/impl/campaign/rulecmd/ptes_riftGateDialog : Unsupported major.minor version 52.0
   at java.lang.ClassLoader.defineClass1(Native Method)
   at java.lang.ClassLoader.defineClass(Unknown Source)
   at java.security.SecureClassLoader.defineClass(Unknown Source)
   at java.net.URLClassLoader.defineClass(Unknown Source)
   at java.net.URLClassLoader.access$100(Unknown Source)
   at java.net.URLClassLoader$1.run(Unknown Source)
   at java.net.URLClassLoader$1.run(Unknown Source)
   at java.security.AccessController.doPrivileged(Native Method)
   at java.net.URLClassLoader.findClass(Unknown Source)
   at java.lang.ClassLoader.loadClass(Unknown Source)
   at java.lang.ClassLoader.loadClass(Unknown Source)
   at java.lang.Class.forName0(Native Method)
   at java.lang.Class.forName(Unknown Source)
   at com.fs.starfarer.campaign.rules.oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.getCommandClass(Unknown Source)
   at com.fs.starfarer.campaign.rules.oOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO OOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO.<init>(Unknown Source)
   at com.fs.starfarer.campaign.rules.Rules.o00000(Unknown Source)
   at com.fs.starfarer.loading.SpecStore.ÓO0000(Unknown Source)
   at com.fs.starfarer.loading.ResourceLoaderState.init(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(Unknown Source)

[close]

All in all, I'm quite impressed by TOS and I hope to see it succeed and be improved down the line!

[phonon5891]

Maybe it's just me, but TOS isn't (auto-)updating to 0.1.5, when in the past it properly updated from 0.1.0 all the way to 0.1.4. Everything's still working as before (Win, Java23, 6GB), so I'm reluctant to do a manual update and rather mention this here in case it's an actual issue.

[Midnight Kitsune]

Since TOS asks, the following mods' version checkers work in game but not in TOS:
Blackrock Driveyards: The one that I'm using is the one that is post in the comments, so the mod version is newer than version file expects
Interstellar Imperium, Ship/Weapons Pack, SpeedUp, Underworld, Audio Plus, Graphic Lib: Reports the mod is fully updated.

[Wispborne]

0.1.5 was pulled because a few people reported that it broke itself when it updated, though updating worked fine for others. Apologies for not updating the post here to mention that.
0.1.7 is building right now, and will release automatically in a bit.

# 0.1.7
- Added
  - New prerelease update channel.
    - Updates will go to the prerelease channel first, then to the stable channel after.
    - You can switch between channels in the Settings page.
    - This lets me test bug fixes and hopefully catch catastrophic bugs early.
- Fixed
  - Maybe fixed a crash due to Chipper's parsing thread and the UI thread fighting over the same file.
  - Mod ending up disabled after updating and enabling them.
  - Version checker wasn't ignoring mods without a .version file, so if it misidentified the highest version of a mod, which didn't have a .version file, it wouldn't look for a different version with one.
    - tldr: version checking is more reliable for certain weird cases.
  - Mods showing enabled in the Dashboard modlist even when disabled (happened when enabled in `enabled_mods.json` but the mod info file was `mod_info.json.disabled`).
- Changed
  - Condensed toolbar, which was getting bloated.
  - Renamed log file to `TriOS-log.log` instead of `latest.log`.
    - (will show up as only `TriOS-log` if you have file extensions hidden, which is the Windows default)

[Wispborne]

Just updated to SS .97 (finally) and that included my ~80 mods as well, so let me tell you about my experience with TriOS (TOS) step by step since I used TriOS from the start, blow by blow so to speak.

Alright, one by one. Thanks for mixing the good and the constructive criticism

-For one, I used 0.1.4 as for some reason 0.1.5 is unavailable; it isn't on the github releases tab, the latest download tab, nor will TOS update to it. Don't know if this is a bug or if it is intentional.
(see previous post, my bad)

+One thing I liked was that I could easily change the JRE version through TOS (after setting the compatibility option to run as admin). Loved this!
+Another thing I loved was the themes! Using THI one as it is the darkest that I could find. Would love to see a black and red one though!
--Sadly many themes don't work well with the VRAM estimator as about a third of the bars blend in with their backgrounds. The default theme works great for that though! (https://i.imgur.com/4Odi5YM.png)
The VRAM estimator in general needs more work - it's something I threw together early, then switched to more central feature and haven't come back to. The next step for it is getting the VRAM onto the Mods tab, like in SMOL. That should take case of most of the reason for the VRAM tab to exist in the first place.

+Speaking of the VRAM estimator, I like this feature as well. Although I couldn't figure out how to make it see my system's VRAM. Maybe add instructions on how to do that?
Ah, good idea. I tried to get the system VRAM but it's hard to do cross-platform, especially with MacOS, and wasn't worth the time. Simply showing instructions makes sense.

-One issue though that I ran into was that TOS, and all of its files, had to be in the root folder with the normal game's launcher to be able to change the VMPRAMS file due to file permissions issues. Made things quite messy in there. Before, I had it in its own folder in \SS\TriOS.
Bleh. Dunno what to say to that, Windows file permission stuff is always wonky. Running it as admin might help. Maybe.

+Loved the ability to update the mods from the app right there! That will make things so much better and easier later down the line for the most part!
(+)StarModder support probably would have made things much MUCH faster to update if TOS had support, so I eagerly await the feature!
Flutter has WebView2 support though a library, so it should work better than SMOL's. When I get to it.

=The ability to filter via game version or filter and or sort by version checker support would be a nice addition
Good idea. You can filter by game version, using the search box.

-I noticed that when I placed the mods' zip folders in TOS to update them, I ended up with both the old and new versions in there. Made things messy looking. Maybe an option to delete the old mods?
That's a feature, not a bug - TriOS manages multiple mod versions, so if something doesn't work, you can easily go back, and in the future you can swap between mod loadouts with different versions. That said, adding a "no multiple versions" mode is high on my todo list.

-I also ran into the issue that RegentMaxa ran into... Very annoying. It also reverted back to the default anytime anything changed with the mods, making mass mod_info changing a pain.
Never got around the saving UI state, another one on the todo list.

-One thing I noticed is that the Java 23 CLI window doesn't auto close when the game closes. Would be nice if it did as I do love having a "live log" right there, but I'm too lazy to close it. Just a thought.
That's more just the way Mikohime's Java 23 works. TriOS simply clicks the .bat file.

-I have noticed that I get a crash now when not using TOS to launch the game. I suspect that this is due to using the Java 23 change but I would like to know if it is possible to allow the old launcher to work. Or at least make TOS close when starting the game. I like to keep things neat and tidy after all. If the error is due to the Java 23, then maybe place a warning about that on TOS Java 23 option.
Exiled Space requires Java 8 or higher. Java 23 runs using a separate .exe (actually, a .bat file). If you run `mikohime_silent.bat` in your game folder instead of Starsector.exe, it'll work. That's the same thing TriOS is doing.

All in all, I'm quite impressed by TOS and I hope to see it succeed and be improved down the line!

Thanks! It's fun to work on, but the laundry list is so, so long.

Since TOS asks, the following mods' version checkers work in game but not in TOS:
Blackrock Driveyards: The one that I'm using is the one that is post in the comments, so the mod version is newer than version file expects
Interstellar Imperium, Ship/Weapons Pack, SpeedUp, Underworld, Audio Plus, Graphic Lib: Reports the mod is fully updated.

Double check with v0.1.7 that it's still an issue. If it is, can you send a screenshot of your Mods tab? Or just list the versions of one of the not-working mods that it has. For me, if I have GraphicsLib 1.8, it does let me know that 1.9 is available.

[Midnight Kitsune]

Nice to see a detailed response back!

(see previous post, my bad)
Yeah, I figured that something went wrong on the 0.1.5 version, so that makes sense

Bleh. Dunno what to say to that, Windows file permission stuff is always wonky. Running it as admin might help. Maybe.
Yeah, tried that and changing permissions on the file it was trying to edit. No dice sadly.

Good idea. You can filter by game version, using the search box.
Good to know. This also "holds in place", unlike the sort option. So it is a good secondary method to use until the UI state saving comes

That's a feature, not a bug - TriOS manages multiple mod versions, so if something doesn't work, you can easily go back, and in the future you can swap between mod loadouts with different versions. That said, adding a "no multiple versions" mode is high on my todo list.
Yeah, I figured as much later on. But that no multiple versions mode would be nice! Maybe even an "X mount of versions to keep" setting?

Exiled Space requires Java 8 or higher.
Wait, I thought .97 updated to java 13 or something? Is that not the case?

Java 23 runs using a separate .exe (actually, a .bat file). If you run `mikohime_silent.bat` in your game folder instead of Starsector.exe, it'll work. That's the same thing TriOS is doing.
Good to know, thanks! Was gonna ask about that!

Double check with v0.1.7 that it's still an issue. If it is, can you send a screenshot of your Mods tab? Or just list the versions of one of the not-working mods that it has. For me, if I have GraphicsLib 1.8, it does let me know that 1.9 is available.
Yup, still the same issue. Here is what I'm seeing: https://imgur.com/a/UI6N5Rk (It is an album)

[Wispborne]

We figured out a fix for the mods having a certificate error via discord DMs. It'll be in the next update.

[Wispborne]

0.1.8

Development note: the main priority is being a reliable mod manager. New features are fun, but getting the basics dialed in is more important, and so progress on big features is delayed in favor of hardening.

Changelog: https://github.com/wispborne/TriOS/releases/tag/0.1.8

Code

- Added
  - **Mod Audit Log** in the Profiles tab shows when mods are enabled/disabled and why.
  - "I don't believe you" option for if the TriOS self-updater says there's no update but you know there is.
  - Context menu option to change mod version on the Dashboard tab.
- Fixed
  - Version Checker updates failing if there was a certificate error (specifically sc2mafia.com).
  - When installing a new version of a mod while another version was enabled, **both would end up enabled**.
    - Now, the newly installed one will be disabled (unless you select Enable on the notification that appears).
  - **If a file failed to extract, the mod install wouldn't fail** and you'd have to check the log to know some file was missed.
    - Now, a dialog will appear with the error message as well as buttons to open the folders for manual install.
- Changed
  - Shiny new **version comparison** algorithm that takes into account dev/alpha/beta/rc, plus a ton of weird edge cases modders love putting in.
    - Nes and Timid, wtf.
  - When a mod is disabled, now sets all mod info files to `mod_info.json` instead of `mod_info.json.disabled`.
    - This **improves compatibility with MOSS and manual mod management**.
    - The only time `mod_info.json.disabled` is needed is when you want to enable one version and you have others installed.
  - Mod details panel is now **cooler** looking for mods with icons.

[Wispborne]

0.1.9

- Added
  - Troubleshooting option to redownload and reinstall a mod, if direct download is supported.
  - Prettified tooltips if mod has an icon.
- Fixed
  - Non-ASCII characters in file paths causing mod installation to fail.
  - Another source of error spam, hopefully.
- Changed
  - Dashboard mod listing now shows versions on the right, making the mod name easier to read.

[Wispborne]

0.2.0 prerelease-1
Linux users, see below.

- Added
  - Retain last N versions of a mod.
    - Keep only the latest version of a mod by setting this to 1.
  - Option to keep the same folder name when updating a mod.
    - This is the new default. It is useful for modders who create a dependency on a folder path and don't want that path to change.
- Fixed
  - Self-update failed if there were any non-ASCII characters in the TriOS or temp folder paths.
    - The Windows self-updater now works completely differently, doing an in-place update with no .bat script.
    - Windows, you so crazy.
- Changed
  - Incompatible mods are now dimmed on the Dashboard.

Linux release: https://github.com/wispborne/TriOS/releases/latest/download/TriOS-Linux.zip
Note: self-update requires a manual step. You need to run the self-update script in the TriOS folder yourself.

I might try to fix this sometime but honestly it took a lot of time to get it to that point. Might end up just giving you a button to open the folder with the script yourself and saying "go run this".

[Fantastic Chimni]

How does this delete the old mods and folders on windows systems? Does it bypass the recycle bin and just perma delete the files?

"Delete Mod" context menu item.

[Wispborne]

How does this delete the old mods and folders on windows systems? Does it bypass the recycle bin and just perma delete the files?

"Delete Mod" context menu item.

Never thought about it. It does perma-delete them.

I've changed that for the next release to have it send them to the recycling bin/trash instead. Thanks, ChatGPT, for writing that code for me...nasty stuff: https://github.com/wispborne/TriOS/blob/main/lib/utils/platform_specific.dart#L24