beebophuckleberry

I’m not so sure the manifest was damaged. I closed Vortex and restarted the PC rather than restoring from backup. After a restart I clicked deploy and everything worked fine. If the manifest was corrupted or damaged then it shouldn’t have worked. I don’t know what happened, but at least it’s working now. How often does vortex create a back up that you can restore from?

Last night I installed a handful of mods that had updates. Everything was fine. Today I updated one mod and then this popped up... What happened?

This was the first time it happened to me. Hopefully it was just a temporary mishap. I'll find out when Embers releases the next update. So far, I have not had this issue with any other mods.

Edit: Oops

This isn't a serious issue, but I thought I'd post it here anyways. The little bell in the upper right corner that shows you alerts has a visual bug. The text overlaps the green area. See image.

I'll update this in case my information can help someone else. I found a workaround. I installed and enabled Embers XD, but I didn't deplay. Instead, I closed Vortex then reopened Vortex. When Vortex restarted Embers XD showed all the usual conflicts and I was able to set the conflicts, deploy, and sort the plugins. Everything working fine now. Dunno why this is happening but it only seems to be happening with Embers XD regardless of which version I use.

I updated Embers XD today. Embers always has file conflicts that I need to set. But, after updating the mod and installing it there are zero conflicts. I thought it was a issue with the current Embers release so I uninstalled the new Embers version 3.0.3 and reinstalled the last version that worked (3.0.2). But, there are still no file conflicts. Any ideas what is going on? I know Vortex just updated to version 1.11.6. Is there a issue with the latest Vortex update?

Hey @insomnious, It's version 1.10.8. The pictures I posted are from the default theme with dark mode turned off. Besides turning off 'Dark Theme', everything else is the same settings as default. I double checked the colors and they are still the same as default. Here is a snippet of the colors.

Thanks for this. Cloned themes are now deleted

I created a couple of new themes to test different colors in effort to make some text easier to read. But now I can't remove any of the 'test' themes I create. When I select to remove the theme it simple isn't removed. By clicking the remove button the theme reverts back to default but it doesn't actually remove the theme you tried to delete.

Just wanted to add that the current color scheme makes some text hard to read. I turned darkmode off and that helped, but it's still difficult to read some of the notifications that pop up. When you highlight a mod it's also hard to read. The text on some notifications looks very thin. Below are a few examples;

I'm looking for a mod that lets me travel to a pocket realm. I want to turn this little realm into a place where I can relax, do some crafting, sleep, eat, etc while being in it's own contained zone. If any of you played WoW and have been to GM island... I want something kinda like that. A little island with only a structure, few trees, etc. I think I can tweak it on my own in CK to add crafting, beds, etc. I have a mod called Haven Bag. It lets me enter the bag like it's a genie bottle. It's a little pocket realm with a bed, crafting stations, and some resources. I want something like Haven Bag but instead of going into a bag you go onto a island. Hope this makes sense :) Anyone aware of a mod like that? Or, aware of a small island mod that I can then edit in CK? Thanks in advance.

lol, it's funny reading all your unhelpful responses. You came here to criticise and offered nothing in return. All I can do is sigh and remember that our species is full people like you. I shouldn't have to explain a idea that Vortex already thinks is a good idea. For example; Vortex already shows you which messages are suppressed and allows you to reset those preferences. So, obviously, the Vortex team thinks this is a good idea because they have already implemented the feature; however, somebody didn't apply this feature to the purging notification. One of you said purging is harmless. Incorrect. Vortex is not perfect (which is obvious from all the updates and bugfixes, right?). Purging is not perfect. In rare cases links can be left behind and cause issues. This risk increases depending on what Vortex settings you have selected such as the deployment method option. You ever had a link left behind and then had to hunt down the mod? I did. Had to reinstall over 2000 mods. All of which happened because the purge button got pressed instead of deploy. Could have been avoided if the suppressed notification was still available. Purging is harmless you say? I disagree. I think it's mostly harmless, but has the potential to screw things up in a bad way if links get left behind. Also, purging takes time. If you accidently purge then you also have to deploy again. This takes my build almost 3 minutes to do. Sit down and watch the clock for 3 minutes. It's a long time to wait for a button you didn't even intend to press. And, it's a button that could potentially provide a confirmation warning; however that notification was suppressed at one point and now can not be unsuppressed. One more thing, if purging is no big deal as you all say then why even have a confirmation in the first place? Hmmm? I'll tell you. They put the confirmation there as a courtesy notification so you don't do something you're don't intended to do. So, it's a big enough deal for your devs to implement a warning in the first place. Right? Anyways, having a confirmation before purging will not only save time but reduce risk of errors. Showler is the only person to reply with a decent response. Thanks Showler.

Great suggestion. I didn't consider the suppressed messages. I did check. No messages are being suppressed.

On more than one occasion I've accidently clicked purge mods. Purge mods is directly adjacent to deploy. Also, deploy and purge have icons that resemble each other. Please change this. Or, create a extension that allows us to add confirmation, relocate, or hide the purge button.

Vortex allows you to view conflicts to easily see what nifs or textures are overwriting eachother. You can open the nifs and textures to view them in nifskope or paint. Lately, when I open a nif, the textures aren't applied. Every nif in nifskope is purple. This didn't use to happen. In the past I was almost always able to view the nif with textures. This isn't just one or two mods doing this. This is every nif. It's worth saying that the game is fine and all textures appear on the nifs in game. It's also worth saying that in the recent past, after a Vortex update, I wasn't even able to preview any nifs with nifskope when doing it through Vortex. Then, after one of the recent updates, it started working again but without textures. Any ideas what changed?

Perfect! Thanks Picky. I realize this 'Lets Get You Set Up" was for beginners getting started. But, I actually used a few of those boxes in 'Lets Get You Set Up' regularly. One last thing before I do this. I want to keep my load-order settings and my overwrite settings. Those are the only two settings I really NEED to save. EDIT: There are two file locations in AppData. One in local and another in roaming.

Thanks for the reply. I don't know what a MOPY is. But, I fixed the issue. I too was using the standalone. I installed it in it's own folder and had to select SSE everytime. Afterwards, I used the installer and it installed WryeBash into the SSE folder. Now WryeBash opens into SSE without having to select anything.

Thanks for the reply. How do I reset Vortex?

I reinstalled Wrye Bash recently and now when I open it I have to select SSE everytime. Before, it used to launch right into SSE. I'm pretty sure there is a command line that will fix this. But, for some reason Google is not providing the answer. Help plz.

There is a dashlet on the dashboard called 'Lets Get You Setup'. It used to have several selections when I first installed Vortex years ago. I want to reset it back to default. How do I do this? This is the dashlet I'm speaking of;

Thanks for the feedback fellas. I'll extract the bsa files, put em in a archive, then view the conflicts. If I'm understanding everything correctly, then I should be able to identify ALL loose files that are overwriting the bsa files. Afterwards, I can remove those loose files and hopefully the files in the bsa will not be overwritten anymore. Thanks again for all the feedback. It helps alot.

I have a problem right now with a arrow mod. The arrow mod has a esp and bsa. Because of this, loose files simply overwrite and there isn't a option to sort bsa/loose file conflicts. I'm in discord right now trying to get help. They mentioned that MO2 will show you which loose files are overwriting bsa files. As long as I've used Vortex I've never seen this which brings me to my question... Is there a way to see which loose files are overwriting bsa files in Vortex?

I'm very happy to report that changing the deployment method back to Hardlink has fixed the issue. Nothing is coming up redundant anymore.

I looked for all three of the file locations you mentioned. Found two, but the third did not exist on my system. The two that did exist did not appear to have anything unusual. I decided to take a closer look at Vortex settings to see if there is ANYTHING out of place. I noticed that deployment method was set to 'Move deployment (Experimental!)'. I don't remember changing this setting, but at some point I must have changed it. It has now become my prime suspect because, not only does it say 'experimental!', but the description of this option says it actually puts the files in the destination directory. I'm assuming this means it's actually putting files into the install directory? Nonetheless, I'm going to do another clean install and purge everything. I'll change this Deployment Method option while I'm at it and see if it helps.