showler Posted August 13 Share Posted August 13 I fear you have misunderstood what was intended to be fixed with the update. I see no mention of removing the blue "no metadata" messages. They were added on purpose and removing them would seem to be contrary to that purpose. You've been told the way to make them go away. I don't expect the Vortex team to create another way to remove them. Link to comment Share on other sites More sharing options...
BarbarossaKain Posted August 14 Share Posted August 14 "I fear you have misunderstood what was intended to be fixed with the update. I see no mention of removing the blue "no metadata" messages. They were added on purpose and removing them would seem to be contrary to that purpose." My understanding from reading the NAGEV's (Staff) post in the thread above was that this issue was to be addressed in a Hotfix. So now we are RetConning what happened, and the "Bug" is a "Feature?" Link to comment Share on other sites More sharing options...
showler Posted August 14 Share Posted August 14 Look at the Github for the commit that is in the hotfix. It says "fixed inability to filter by relevant loot messages". What part of that suggests that removing the blue banners is the intent? Consider that they added the blue banners for a reason. Why immediately remove them? Consider that they are, in fact, a cosmetic concern and never actually stopped the sorting from working. And Consider that the way to remove them was given to you. There's no "retcon". You misunderstood. Link to comment Share on other sites More sharing options...
BarbarossaKain Posted August 14 Share Posted August 14 Well... um... they just released another update. I downloaded and installed, and, Low & Behold! They fixed the issue. So... Since commenting on this matter is obviously important to you, I wait with bated breath for you to explain to me why the Devs took the time to remove the blue banners. Which... (if you had taken the time to scroll up and read through the entire thread) is what NAGEV stated that they were going to do last week in the first place (though obviously not to the schedule they had anticipated originally it would seem). Link to comment Share on other sites More sharing options...
showler Posted August 14 Share Posted August 14 On 8/7/2024 at 2:19 AM, Nagev said: Hi there - first of all, that enhancement is cosmetic, LOOT will still sort your plugins according to the masterlist they provide and your personally defined userlist as it always has. Can you give me an example of a plugin that exists in the LOOT masterlist and Vortex is complaining about it not having metadata? On 8/7/2024 at 3:20 AM, Nagev said: Hi there - I guarantee that all of the patches you just posted in your snippet DO NOT have masterlist metadata. To be clear - we are still investigating any potential issues with sorting as part of the 1.12.0 release, but you're latching onto a 100% cosmetic enhancement which has nothing to do with any sorting failures. On 8/7/2024 at 4:09 AM, Pickysaurus said: If you want to check if a plugin exists in LOOT, you can enter it's name and select the game you're playing here: https://loot.github.io/search/ I think the confusion might be that none of these plugins had LOOT info, but Vortex was not showing this message in the last version. This was an enhancement to better inform users that LOOT is not doing anything specific when sorting these (it just uses the master data). On 8/7/2024 at 5:05 AM, Nagev said: @LeapinL - as I mentioned, that message is purely cosmetic and will not affect your LO in any way - what concerns me in your reply however is your statement that almost all groups changed to default, 1.12.0 has no userlist (grouping information) enhancements in place and should have never caused any of the groups to change to default; are you certain that change occurred as part of the update? Can you please send me your userlist.yaml file which can be found inside your staging folder. If privacy is a concern, just send it to me through a forum message. On 8/7/2024 at 8:47 AM, Nagev said: Update - the fix for the filtering issue has been committed a few hours ago https://github.com/Nexus-Mods/extension-plugin-management/commit/7f5e044d101083ad0183dd0552e6e23112c5a2ec But unfortunately the hotfix release has been pushed to tomorrow morning as we had to make sure the sorting mechanism is functioning as expected (which it is, aside from some parsing issues for Starfield which are still ongoing) Sorry to be the bearer of bad news, was really hoping to release it today. FYI - one way to get rid of the metadata message is to assign it to a group. 'Default' would do. That way even though the LOOT masterlist doesn't have metadata for your plugins, your userlist _will_ and the message will go away. On 8/7/2024 at 11:41 PM, Nagev said: Hey @imprimis432, The 'concerns me' message was directed at LeapInL which suggested that his assigned groups (manually selected) had been reset to their default values as part of the update. As vortexposer stated; Vortex has mechanisms in place to maintain the assigned groups even through Vortex uninstallation, and that piece of functionality hasn't changed in years which is why I found it odd that he may have went through that. I see nothing wrong in the snippets you sent - as you can see, the plugins which have a manually selected group (the bold ones) no longer show the "no metadata message", while some of the others that have the default LOOT assigned groups (italic, slightly faded) have it. Again, this is a purely cosmetic feature and if the message is displayed, it simply means that there is no metadata to sort by, which is expected for most plugins, ESPECIALLY newer ones that have yet to be added to the masterlist. I'm happy you've got your fix, but I dare you to point out where Nagev said any such thing. This is a new decision on their part, not fulfilling a promise from last week. Link to comment Share on other sites More sharing options...
Nagev Posted August 15 Share Posted August 15 Hey all, First of all, apologies for not pushing the 1.12.1 update last week, we were investigating reports of sorting errors which AGAIN are completely unrelated to this specific piece of functionality. Unfortunately the investigation had stretched for too long and we were unable to release the hotfix before end of the working week. Due to some crossed wires you were not informed of the delay, we apologise for that. the "No metadata" messages which AGAIN are absolutely cosmetic and have absolutely no effect on sorting; were initially supposed to be displayed in both the inline view for LOOT messages/blue banners and the plugin panel. 1.12.1 aimed to provide users with the ability to filter out non-relevant LOOT messages through the plugin flags column by selecting the "LOOT messages" value, as several of you have highlighted that the message is hindering overall useability of the plugins page when attempting to ensure you have a working setup. Unfortunately the ability to filter did not seem sufficient as many of you are actively using the inline view of LOOT messages and prefer a wider perspective of your plugins without having to worry about applying filters to your table columns. This led to a decision to hide the message in the inline view as part of the 1.12.2 hotfix. The message is still present in your plugin panel whenever there is no metadata to sort by, which AGAIN is completely normal and expected 99.99% of the time. In regards to sorting issues - in 1.12.0 we updated Vortex's libloot library to 0.23 - it appears that libloot is unable to parse certain plugins - mostly (but not exclusively) Starfield ones. If you're unable to sort your plugin list - look through Vortex's log files - libloot should highlight exactly which plugins it's unable to parse. Disabling those plugins will allow you to sort again. This is obviously a temporary solution while we wait for a new version of libloot which fixes this issue. Regarding groups being reset/missing - this appears to happen due to Github being inaccessible when trying to pull the up to date masterlist on Vortex startup (there were some Github outages in some regions). We're currently looking at adding a fallback mechanism to ensure Vortex doesn't get confused if it fails to find the masterlist. If you're affected by this (@LeapinL) - wait until Github connectivity is restored, and Vortex will re-establish your groups. Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now