insomnious

I've just checked my end and it's not installing as it's not in the manifest. As I said, it's clunky UX which we are working on. https://github.com/Nexus-Mods/Vortex/issues/15531 Is the issue for Lies of Pi and it is in the queue for a re-check since you have uploaded a new version yesterday. As long as that all passes, we will add it to the manifest. Thanks insomnious

Hi @ChemBoy1 This happens because when you use the Mod Manager download button for an extension, the ID of the extension you'd like to download is sent and then looked up in the manifest file. If it isn't in the manifest file then Vortex can't download it. It works differently to how regularly download mods work. This is not an ideal UX but it is what we have at the moment until we get a chance to notify better what is happening. What ones aren't working / what one did you try? It might just have been missed or it just doesn't work well enough yet to be added to the manifest. We may still be going back and forth with the author. This is one of the reason we are now moderating game extensions until they can be confirmed to work. Thanks, insomnious

Hi all We’ve recently been inundated with game support extensions for Vortex and it’s made us take a step back to look at how we review these. We continue to have the issue with extensions being added that don’t work and don’t provide an adequate user experience but we do work closely with the authors to get these extensions up and running to a basic level as quickly as we can. This is time consuming with our limited resources and so if there are ways we can streamline processes, we are going to take them. The extension review process is important because until we have reviewed it, it can’t be manually added to our manifest file. This file is what Vortex uses to know what extensions are out there and what games are supported. We have a responsibility to Nexus Mods users that when they are using Vortex to manage their games, extensions make sense regardless of whether they are community created or built by us. The below changes are only applicable for Game extensions, and not for Themes, Translations or Tools. We are utilizing more of GitHub’s features to automate and streamline what we can. As we use GitHub for nearly everything Vortex related, we are now using it for our game extension reviewing. This allows us to have a transparent conversation from start to finish with the author and all under a single GitHub issue. Because of this, a GitHub account is now needed to submit an extension for review and we won’t automatically be checking every extension that is uploaded to the site. When the extension author is ready and they’ve uploaded it to Nexus Mods, they fill in a form on GitHub that signals to us that the review process is ready to start. The form has links to the new documentation to help package, test and submit the extension in order to cover as much as possible before we manually take a look. We will also be placing game extensions under moderation while we are reviewing them in order to minimize user downloads before we’ve had a chance to review. We will be contacting authors at this point as well so they are aware of what is happening and why. We’ve started the mighty documentation project of 2024! We know our technical documentation isn’t great but we have started the project to check everything and migrate it to GitHub Wiki so it’s all in the one place and not spread across 3-4 different places. This is going to take a while but it’ll be worth it in the long run. We hope these changes aren’t too disruptive and at no point do we want to dampen the passion people have for developing extensions or modding games. We believe these changes are for the best and will also provide better opportunities to learn how to develop for Vortex and provide a better experience for the user. Here are some links to what's been mentioned: Submit a game extension for review (GitHub Issue Form) How to Package and How to Test a game extension (GitHub Wiki) Example extension review (Alan Wake 2) with author conversation (GitHub Issue) Thanks and happy modding! insomnious and the Vortex team

Sorry you are still having problems @Nahaerya Could you send us your logs and state files if possible ? For logs, grab anything that is 'vortex.log', 'vortex1.log', 'vortex2.log' etc. from your %APPDATA%/Vortex folder. For state, go to Vortex > Settings > Workarounds and Create Backup at the bottom. If you could zip these up and send them to us, that would be great. DM me on forums or .insomnious on Discord. Regards, insomnious

Thank you for your kind words! It means alot. Happy modding!

Hi @Doternoob, sorry you are having problems. This is a known issue that was fixed in the latest beta update that went live this morning. I'd recommend switching to it (if you aren't already) so you can get your problem sorted. If you load Vortex and go to Settings > Vortex and then halfway down it says about Update. Choose Beta in the dropdown and update from there. Let us know how you get on insomnious

Hi @Zanderat, that issue is fixed in this beta. If you had a profile with all your mods disabled, it would cause all of your manual overrides to be removed and recalculated when profile is switched. Thanks

Hey there modders! We have released a new beta update to Vortex (v1.11.0-beta) and it's chock full of fixes and improvements with the highlights being: Collections Straight from two of the most requested features on the Feedback board, comparison of patches and installer choices during installation. Vortex now compares the options the user selected for the currently installed mod against those packaged by the curator of the collection they are downloading. If the two sets of choices do not match, the user can select if it should be installed as a variant and/or replace the currently installed version. File-Based Load Ordering with a sprinkle of Baldur's Gate 3 We've put in a lot of work to make the File-Based Load Ordering more performant in the core app with a lot of the feedback coming from the Baldur's Gate 3 community. We've had to wait to push the game extension update until the core was ready but we now have a more performant load ordering, PAK file reading, caching etc. Along with these changes, collection installations are now quicker because of it. Update Workflow The last couple of years there has been a lot of feedback around our update workflow, primarily to do with the visibility of changes and the forced downloading. We also have a problem where there is a lack of info about what being on the Beta update channel actually means. To combat this, we've rewritten our notifications, added some info dialogs when swapping update channels as well as turned off force download of updates (unless they are hotfixes and need to be pushed out for security\stability reasons). We are going to be more thoughtful with our versioning from now as well, and will only be hotfixing (and auto downloading) when absolutely necessary. A few extra bonuses of this are we can now show correct changelogs of current and previous versions (renamed as 'What's New') that can be seen before an update kicks off. All of these changes have been tested in house for several weeks but still may not be perfect - it is a beta after all! As soon as these updates are confirmed to be stable then this update go out to everyone. Thanks insomnious and the Vortex team --- Full Changelog New update workflow to better communicate What's New, minimize auto downloading (unless critical hotfixes) and more information when swapping update channels. Fixes #15363 (API) Fixed performance degradation when downloading collections for games that use the file based load order system. Fixes #15395 (Stardew) Fixed SMAPI update notification appearing while managing other games (Collections) Added comparison of patches, installer choices, hashes when installing. Fixes #15396 (Collections) Updated styles to fix update changelog bounds (Collections) Better logging when profile switching (Collections) Fixed rare crash where game version was being compared (Collections) Improved error handling when displaying instructions. Fixes #14570 (Collections) Instructions textarea now fills available space. Fixes #15394 (Collections) Override overflow now scrolls vertically (BepInEx) Fixed download issues caused by package resolution applying the new archive format to 5.x.x versions of BepInEx (Dependency Management) Suppress error report when user cancels purge (Dependency Management) Fixed file overrides being cleared when switching to an empty profile (Dependency Management) Fixed rare issue where it was possible for mods to fail deploying certain types (Plugin Management) Fixed long delays when ascertaining if a plugin is marked light (Baldur's Gate 3) Performance improvements when installing collections and using LSLib (Baldur's Gate 3) Added caching to PAK reading (Baldur's Gate 3) Added a better .NET error catch and shows a fix dialog. Fixes #15391 (Announcements) Restyled announcement dashlet (Mod Management) Underscores in archive names no longer cause installation issues. Fixes #15396 (Theme) Fixed layout issues with Contrast and Compact theme (Theme) Added a Classic theme that uses the old colors Updated Log format Updated dev bootstrap script Updated Electron and Node

You can install 'over the top'. Settings are saved in AppData and won't be removed. You won't want to downgrade once you've updated to 1.10 as there is ALOT that has been updated.

Our digital certificate has renewed since you last installed a version and the auto-updater is just being overly careful. If you download the latest version from the site and manually install it, then all will be fine. https://www.nexusmods.com/site/mods/1?tab=files Any problems, give us a shout. insomnious

Please check out this forum post for more information on the LSLib issue that cropped up over the weekend. If that still isn't working, try a purge and deploy, and if you are still having issues, give us a shout here or preferably on Discord so we can chat properly. Thanks, insomnious

Hi everyone, Please see this post for a workaround and a direct link to install .NET 8. Thanks, insomnious

Hi everyone, Please see this post for a workaround and a direct link to install .NET 8. Thanks, insomnious

Hi everyone, Please see this post for a workaround and a direct link to install .NET 8. Thanks, insomnious

Hey everyone It's been discovered over the weekend that a recent update to LSLib\Divine now requires .NET Desktop Runtime 8 to be installed which we didn't know about, nor did it get mentioned in the changelogs since it went pre-release in December. We are working on a fix as we speak but until then, please follow the below steps to get yourselves back up and running. Close Vortex Download and Install .NET 8.0 Desktop Runtime from Microsoft Restart computer Open Vortex Any issues, please give us a shout here or on Discord. Regards, insomnious