maddadicusrex Posted February 24, 2022 Posted February 24, 2022 (edited) I use Vortex. Concerning 1.56, did anyone else have an issue when downloading, the options for DLC and Vader support were blocked out from being toggled? Edited February 24, 2022 by maddadicusrex
panzer1701 Posted February 28, 2022 Posted February 28, 2022 On 2/24/2022 at 12:02 PM, maddadicusrex said: I use Vortex. Concerning 1.56, did anyone else have an issue when downloading, the options for DLC and Vader support were blocked out from being toggled? I have Vader Support, but DLC and Nightstrikers is blocked out and unable to be toggled for me.
EgoBallistic Posted February 28, 2022 Author Posted February 28, 2022 11 hours ago, panzer1701 said: I have Vader Support, but DLC and Nightstrikers is blocked out and unable to be toggled for me. The file dependencies are listed in the installer. You need both Nuka World and Far Harbor for the DLC option, and you need Nuka World for Nightstrikers. On 2/24/2022 at 1:02 PM, maddadicusrex said: I use Vortex. Concerning 1.56, did anyone else have an issue when downloading, the options for DLC and Vader support were blocked out from being toggled? The FOMOD files haven't changed since version 1.53, other than the version number in the info XML. 1
panzer1701 Posted March 1, 2022 Posted March 1, 2022 11 hours ago, EgoBallistic said: The file dependencies are listed in the installer. You need both Nuka World and Far Harbor for the DLC option, and you need Nuka World for Nightstrikers. The FOMOD files haven't changed since version 1.53, other than the version number in the info XML. But thats the odd part, I have Nuka World and Far Harbor, along with the NightStrikers mod installed. Im not sure why it isn't recognizing that I have the DLC
gabriella77 Posted March 1, 2022 Posted March 1, 2022 2 hours ago, panzer1701 said: But thats the odd part, I have Nuka World and Far Harbor, along with the NightStrikers mod installed. Im not sure why it isn't recognizing that I have the DLC I am actually having the same issue. Have all the DLC and the nightstriker mod but its not being recognised by the AAF Violate installer. Thank you for your time and great work.
panzer1701 Posted March 1, 2022 Posted March 1, 2022 I uninstalled and reinstalled everything and the same error is popping up. I don't know if its related but Atomic Lust is having an issue which you cannot install it via vortex unless you go in the FMOD and delete a line of code.
EgoBallistic Posted March 1, 2022 Author Posted March 1, 2022 6 hours ago, gabriella77 said: I am actually having the same issue. Have all the DLC and the nightstriker mod but its not being recognised by the AAF Violate installer. Thank you for your time and great work. Are you also using Vortex?
EgoBallistic Posted March 1, 2022 Author Posted March 1, 2022 (edited) OK so the problem is the new version of Vortex. See this post on the Vortex forums. In a nutshell, Vortex 1.55 will never report a DLC esm as "Active", so FOMODs that require that will fail to install. This is fucking stupid. When specifying a dependency, you have to give it a required state. That state can be "Active", "Inactive", or "Missing". If I put it as "Inactive" then it breaks compatibility with other mod managers, because they will see the esms are "Active" and will refuse to enable the option. So right now I would have to either remove the requirements for the DLC, or rewrite my fomod with negative "Missing" conditions. This is dumb. To paraphrase Michael Bolton, "Why should I change my code? I'm not the one who sucks". Edited March 1, 2022 by EgoBallistic 3
EgoBallistic Posted March 1, 2022 Author Posted March 1, 2022 According to the Vortex github, this will be fixed in the 1.56 version of Vortex. 3
izzyknows Posted March 1, 2022 Posted March 1, 2022 3 hours ago, EgoBallistic said: This is dumb. But not surprising... coming from the same idiots that claim all rights to anything you upload "forever". 3
deathmorph Posted March 2, 2022 Posted March 2, 2022 (edited) 20 hours ago, EgoBallistic said: According to the Vortex github, this will be fixed in the 1.56 version of Vortex. fine, just wait and see I hope reinstallation while the game is running is no problem? I had to reinstall everything because I was experimenting too wildly ^^ Spoiler PS: Oh, 6 hours of installation and I can't start a new game or load saves. I'm beginning to suspect that Vortex 1.5x is shooting up my installation. It works freshly installed, but as soon as mods are installed with the new Vortex, the game crashes. Even if the mods are uninstalled via Vortex and started without mods. I have now downloaded 1.4.14 and hope that this will fix the problem. Edited March 2, 2022 by deathmorph
vaultbait Posted March 2, 2022 Posted March 2, 2022 16 hours ago, deathmorph said: fine, just wait and see I hope reinstallation while the game is running is no problem? I had to reinstall everything because I was experimenting too wildly ^^ Reveal hidden contents PS: Oh, 6 hours of installation and I can't start a new game or load saves. I'm beginning to suspect that Vortex 1.5x is shooting up my installation. It works freshly installed, but as soon as mods are installed with the new Vortex, the game crashes. Even if the mods are uninstalled via Vortex and started without mods. I have now downloaded 1.4.14 and hope that this will fix the problem. Note that Vortex 1.5.6 is available now and claims to have fixed the problem in its changelog. 1
deathmorph Posted March 2, 2022 Posted March 2, 2022 I will make one last attempt ... Spoiler ... unfortunately the installation with 1.4.14 was also unsuccessful. Unfortunately, I can't understand the error either, because at a certain point in the mod installations, Fallout no longer starts and I land on the desktop without errors. It can't actually be a mod, because if I deactivate or uninstall all mods, then I still can't start the game.
vaultbait Posted March 2, 2022 Posted March 2, 2022 2 hours ago, deathmorph said: I will make one last attempt ... Hide contents ... unfortunately the installation with 1.4.14 was also unsuccessful. Unfortunately, I can't understand the error either, because at a certain point in the mod installations, Fallout no longer starts and I land on the desktop without errors. It can't actually be a mod, because if I deactivate or uninstall all mods, then I still can't start the game. Try having Steam validate/repair your game installation.
izzyknows Posted March 3, 2022 Posted March 3, 2022 4 hours ago, deathmorph said: I will make one last attempt ... Hide contents ... unfortunately the installation with 1.4.14 was also unsuccessful. Unfortunately, I can't understand the error either, because at a certain point in the mod installations, Fallout no longer starts and I land on the desktop without errors. It can't actually be a mod, because if I deactivate or uninstall all mods, then I still can't start the game. Wouldn't hurt to check your drive for errors too.
deathmorph Posted March 3, 2022 Posted March 3, 2022 8 hours ago, vaultbait said: Try having Steam validate/repair your game installation. done, negative 6 hours ago, izzyknows said: Wouldn't hurt to check your drive for errors too. done, negative Spoiler I reinstall FO4, all fine. Installation with Vortex, 226 mods. At some point during the installation, I can no longer load a save or create a new game. I uninstall all mods and also vortex, the error remains. I manually install only one file for Buffout and put two things in the ini's - the hair-glitch and Classic Weapon Holster Patch for DFS. It started after installing the vtaw creation pack and updating the vortex. hence this guess. I can no longer imagine that this is the cause. I'm at a loss as everything was going fine for months. Sorry for OT.
izzyknows Posted March 3, 2022 Posted March 3, 2022 32 minutes ago, deathmorph said: done, negative done, negative Hide contents I reinstall FO4, all fine. Installation with Vortex, 226 mods. At some point during the installation, I can no longer load a save or create a new game. I uninstall all mods and also vortex, the error remains. I manually install only one file for Buffout and put two things in the ini's - the hair-glitch and Classic Weapon Holster Patch for DFS. It started after installing the vtaw creation pack and updating the vortex. hence this guess. I can no longer imagine that this is the cause. I'm at a loss as everything was going fine for months. Sorry for OT. Do the old 50/50 method to find the corrupted mod. Load 1/2 your mods, start a new game and test. IF everything is fine, load 1/2 of the remaining mods and repeat. When shite goes south, you will have a pretty good idea which group the little buggers are in. BTW, do not use Buffout during the testing, it's nice, I guess, but it can hide issues that actually need to be fixed and not bandaided. And yes, your perfectly working mods can become corrupted out of nowhere.
deathmorph Posted March 3, 2022 Posted March 3, 2022 Thank you, that's exactly what I'll do. But there is still the question why after uninstalling everything the base game still doesn't work. So there has to be a mod that alters the base game. But I'm going to take a week's break from Fallout, that was too much frustration in the last few days.
asdfer1234 Posted March 4, 2022 Posted March 4, 2022 10 hours ago, deathmorph said: Thank you, that's exactly what I'll do. But there is still the question why after uninstalling everything the base game still doesn't work. So there has to be a mod that alters the base game. But I'm going to take a week's break from Fallout, that was too much frustration in the last few days. Do remember that Fallout 4 can be quite screwed up even played vanilla... XD
deathmorph Posted March 5, 2022 Posted March 5, 2022 I have found the cause. The mods aren't the problem. It is body slide. Once I've made a body customization, I can't start a new game or load a save anymore. Now I have to see how I can fix this and then I can finally play again.
DerpCake Official Posted March 5, 2022 Posted March 5, 2022 (edited) Hello yall, new on the scene here. Very dumb kinda stupid questions. Too lazy to read through all this so figure id just ask here. Is the camera meant to be locked during Violate scenes (because I can only turn it hardly and it wont zoom in or out)? Is that cause of AAF itself? Violate? or the animation mods themselves? If not how can I fix this bug? TFC also doesn't work and the camera is still locked in place . It also locks my movement controls if i access tfc during animations. Have tp restart from desktop to fix the problem after the animations. I use the nexus mod manager. Mods great but there's no free camera access (if the mods support it). Could use a response, thanks. Edited March 5, 2022 by DerpCake Official
EgoBallistic Posted March 5, 2022 Author Posted March 5, 2022 4 hours ago, DerpCake Official said: Is the camera meant to be locked during Violate scenes (because I can only turn it hardly and it wont zoom in or out)? That is not normal, no. Violate prevents you from moving but not from looking around, and during animations you should be in free camera mode. If that is not happening, most likely the problem is the F4SE plugin that comes with AAF. You should be running the latest versions of Fallout 4, F4SE, AAF, and Violate. Any other combination is going to cause problems like you are seeing. 1
jarno5 Posted March 6, 2022 Posted March 6, 2022 Hey Ego, i was wondering if it would be possible to make some kind of check to see if there is an ongoing abduction, and make it so a new abduction scene would not be possible until the boss chest is cleared (either looting it or resetting it) I had this scenario in the past where i would escape the abduction scene to try and get some loot in order to get my stuff back. In the proces another violation occurred and again, got abducted while there was still an boss chest left to raid. This resulted in multiple boss chests and the RSA mod could not handle that very well. Solution now is to manually set the abduction chance to 0 in MCM whenever an abduction is stil going on. If a check could do this in the background, that would be a timesaver 1
DerpCake Official Posted March 6, 2022 Posted March 6, 2022 (edited) 5 hours ago, EgoBallistic said: That is not normal, no. Violate prevents you from moving but not from looking around, and during animations you should be in free camera mode. If that is not happening, most likely the problem is the F4SE plugin that comes with AAF. You should be running the latest versions of Fallout 4, F4SE, AAF, and Violate. Any other combination is going to cause problems like you are seeing. Found the problem, already fixed it. My custom keys for movement (which by default are also the free cam keys) were the arrows. Apparently, the input of the camera during animations registers for all keys that you customize except the arrows for somewhat odd reason. If I had to take a guess, this has do with the fact I'm using bootcamp on mac to run windows and its the drivers code not connecting to the mods camara setting to the input of arrows for some dumb reason, as stated before works well with any other customized keys. So I just changed the movement keys. I'll just find a mod that allows me to swap key presets with a hot key. I'm sure i'll find one out there on nexus that works. Appreciate the quick response. Edited March 6, 2022 by DerpCake Official 1
EgoBallistic Posted March 6, 2022 Author Posted March 6, 2022 9 hours ago, DerpCake Official said: Apparently, the input of the camera during animations registers for all keys that you customize except the arrows for somewhat odd reason. Yeah, that's a limitation of the F4SE plugin that comes with AAF. There are ways to remap the keys, with a mod or a third-party hotkey app, but I don't use those myself so I can't offer any suggestions.
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