DarkDominion

I was never rude, so I'll give that advice back at you. You did not mention 'sometimes'. You never implied that there were more options. By mentioning only one of many outcomes you imply that that's the only way to use flags, which is false. But it's OK, no need to apologize I guess, well, maybe for showing so much entitled behaviour. Now, go away please ? Thank you !

don't be rude and stay out of other people's conversation please ? thank you. and yes it does.

Yes you did Sjeez, my first post was on the 25th of may and then after three months you showed up. Please get your timing correct I think you should get off your high horse and leave me alone if you have nothing meaningful to contribute to the matter

It happened three months ago, I can't remember, haven't done a lot of modding since Oh but it IS relevant, because we didn't have that stupid ambiguous warning That's not confusing at all since I've used FOMods for years and all without a fancy automaton thingy, but what's interesting is the part : " It used to be necessary to add a special option (flag) to the file to install plugins in Vortex. This has been deprecated and shouldn't be used anymore." You see, I didn't get that memo apparently. How was this information spread, because without this crucial part the whole warning is totally useless since the warning itself doesn't say anything about what is deprecated and what action people should undertake to make it work Also, a flag in a FOMod installer can also be a sort of a switch to help you guide through the more bigger FOMod installers. The flags are not necessarily only for installing plugins

I know all that, I use FOMod all the time or create them for other mod authors. I have never had a message saying I should change my FOMod because it's outdated. Ever. And where is the MO2 way different from the Vortex way of using a FOMod ? This : " the mod that produced this message still has the configuration options (a.k.a. "flag") that differentiate the plugin install between Vortex and MO2. " is Chinese to me. " whereas the old Vortex option can cause problems. " What old Vortex option ? What problems specifically are we talking about ? " but sometimes it is not able to correct the install for various reasons. " It would be a first to have a FOMod fail because of shenanigans like this, never encountered any of this. " It is certainly confusing, but the message is helpful in letting you know that there may be an issue with the mod and what to do about it. " It sure is and no, it does not help at all, it confuses people even more.

" Deprecated Fomods Vortex detected 1 FOMODs which are using the deprecated Vortex plugin option. This option is no longer required and will cause the FOMODs to deploy incorrectly. Vortex will attempt to fix the FOMODs for you and it is recommended to inform the mod author to change his configuration file and remove the Vortex flag. Alternatively you can re-install any affected FOMODs manually and select the MO2 plugin option instead. " Can someone explain this to me ? - Which mod ? - What Vortex plugin option exactly are we talking about ? - We have to manually click the "fix" button for the file te be installed, else it will just "sit" there. - Aren't all the mod authors brought up to date of this issue, because we need to inform the mod author about this - What is a Vortex Flag ? - What's the difference with the MO2 plugin option ? This is all very confusing and unnecessary imho cheers -=DD=- [edit: fixed typo]

Maybe tell Vortex to specify what primary tool it's talking about, like : "Script Extender for (Game) is No Longer Available, Quick Launch Has Reverted to the Games Executable" it'll stop te confusion

Hello, a quick question please : Is First Person View incorperated in this update ? Cheers -=DD=-

Ah, that I did not know Sorry @Picky Thanks for the elaboration @Tannin I'll correct my posts Cheers all, and thanks for the efforts and fixes !

What I did : Download Microsoft .NET Framework Repair Tool and run it. Download .NET Framework 4.8 Runtime and install it if necessary. Download .NET 6.0.7 (latest version) If I understand correctly : you need .NET 6.x.x runtime Hope this helps ? Cheers

Hey Picky, sorry for the late reply :smile: I did not get a warning that my .NET 6.0.0 version was outdated too old for this new Vortex release ( not sure if it's only the Beta btw ). But it's fixed with installing .NET 6.0.6 And yes, I did submit a ticket to support for this issue, with the exact text as in my OP. I did not submit a ticket for the skse_64 2.1.5. version warning but I saw you already posted the issue on GitHub, thanks :wink: There was an update which fixed the "no message on .NET installation" issue and the "skse_64 2.1.5." issue : Cheers -=DD=-

Fixed in Vortex 1.6.2 Beta ---------------------- Released on 7/12/2022 Electron 19.0.7 Node 16.14.2 Chrome 102.0.5005.134

Install exactly this file : .NET 6.0.7 [ EDIT : 6.0.7 is now the newest version ]

Good evening Also posting this separately because it's a "new" issue for a newer version. Vortex 1.6.1 Beta Released on 7/7/2022 Electron 19.0.7 Node 16.14.2 Chrome 102.0.5005.134 Trying to install a new mod makes Vortex flash with a white screen and it restarts immediately. Mod is still trying to install : " Installing Bretonnia - New Breton Presets (.esp)-70820-1-0-1657051954 - Preparing.... " (or any other mod) A warning then says : " Vortex restarted after a crash, sorry about that. " Also this : " The last session of Vortex logged an exception. Please visit this thread for typical reasons causing this. Please report this issue only if you're sure none of those reasons apply to you! " From the Vortex.log : Thu, 07 Jul 2022 16:26:08 GMT - debug: extraction completed Thu, 07 Jul 2022 16:26:08 GMT - info: listen pipePath=\\?\pipe\H1xKXFF4s9 Thu, 07 Jul 2022 16:26:08 GMT - info: listen pipePath=\\?\pipe\H1xKXFF4s9_reply Thu, 07 Jul 2022 16:26:08 GMT - debug: [installer] waiting for peer process to connect pipe=true, ipcId=H1xKXFF4s9 Thu, 07 Jul 2022 16:26:08 GMT - info: failed to grant access WinApiException: Unknown error Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected there Thu, 07 Jul 2022 16:26:09 GMT - info: there channel connected Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected reply Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected there Thu, 07 Jul 2022 16:26:09 GMT - info: there channel connected Thu, 07 Jul 2022 16:26:09 GMT - debug: [installer] peer connected reply Thu, 07 Jul 2022 16:26:09 GMT - info: from installer: Unhandled exception. Thu, 07 Jul 2022 16:26:09 GMT - error: render process gone exitCode=-1073741819, reason=crashed Actions taken : I've run the .NET Framework Repair Tool. After that I reinstalled .NET Framework 4.8 which was inconclusive because the Repair Tool already fixed that. Also repaired .NET 6.0 just to make sure Prior to this all Vortex was working well even after the latest Windows Update. So it must be something in the 1.6.1 Beta that's not working well ? Hope this can be fixed. Cheers -=DD=-

Good evening, When I install skse_64 ( version 2.1.5 ) for Skyrim Anniversary Edition ( version 1.6.353 ) the dependency symbol turns red for me. The message says : " Conflicts with Skyrim Script Extender 64 (SKSE64) <2.1.5||>2.1.5 " Seeing that I indeed have version 2.1.5 I shouldn't get this message because it isn't a lower version number or a higher version number. Could there be something wrong with the validation of the version number ? Thank you for your time. Cheers -=DD=-