|
Post by Emma on Jun 6, 2016 9:26:48 GMT
No, don't use a console command. That will change the quest stage, but the events triggered by the quest stage is not in the quest entry, it's in the dialog entry that triggers the quest stage.
Go to Vilja's off-topic section and tell her that there are parts of her quest that you have already done. This will bring Beata to the BAnnered Mare, and through dialog with her, you can move on with the quest. Just be aware that you have to click through various dialogs with her before you can talk about the bards quest.
|
|
|
Post by dgenem on Jul 1, 2016 23:37:33 GMT
I forgot to mention I have done that. It only gives me the option to tell her we already got two of the books. Then after some time, I get the notice from Vilja about the letter from Wilbert and it starts all over again. Then I talk to Wilbert, and no options. Reset again, talk to Vilja, talk to Beata, two books again, wait then letter again. It is a never ending loop with zero progress. I don't know what happened.
There is ONE thing I have done differently on this character than the last. I changed the timescale from 20 down to a slower pace. Usually around 2. I'll leave it at 20 this time see if it by some chance clears.
|
|
|
Post by dgenem on Jul 2, 2016 2:44:52 GMT
Okay, fixed it this time. I had to change use set timescale to 20, then talk to Beata, and tell her "That's all!" I forgot the "That's all part before. Waited it out and got the letter, then the quest actually started with the marker, and Wilbert is working as normal. Just to test, I did it again at timescale 2, including the "That's all" and it failed again. So I am pretty sure it was the timescale that screwed it up.
|
|
|
Post by Sniffles on Jul 2, 2016 9:07:32 GMT
Emma, Wolf and Amgepo have all mentioned timing repeatedly about Vilja. Seems like a real bad idea using a mod that messes with it.
|
|
|
Post by dgenem on Jul 13, 2016 22:13:39 GMT
Emma, Wolf and Amgepo have all mentioned timing repeatedly about Vilja. Seems like a real bad idea using a mod that messes with it. I was not using a timing mod. I was using console commands to change it. I just hate the way time flies by sometimes when you are trying to get a bunch of things done at once. So I was always adjusting it. Then I learned later that a lot of things can get screwed up that way. Vilja is working just fine now. Although it took me a while to learn about mixing armor and clothing in her wardrobes. Seems to cause some confusion here and there. It does not help that I have 250 active plugins either. And I keep modding or enhancing other people's mods. Trimming them down and merging some to keep me under the 255 limit. Thank Talos for ENB. But darn, does my game look good, and rarely crashes. That reminds me if you ever need male voiceover work or some audio cleaned up, I'll volunteer. Just send me a script or what needs to be processed for effects or cleaning. I can do pretty well and have plenty of tools and knowledge for audio effects, keeping it from being overdriven, and balanced. I learned from professionals in studios in the 80's using analog equipment. I need to contribute to TES somehow one of these days! Anyways, BIG thanks for the best follower mod out there! Sofia is my second, just because she is CRAZY!
|
|
|
Post by Sniffles on Jul 14, 2016 0:50:52 GMT
I mucked up the timing and couple of times and learned my lesson. Saved games are your timing, the safe timing. Going through everything multiple times until everything is dealt with satisfactorily. I'm having to do that with my present play through.
Emma did such a fabulous job with Vilja's voice acting. My techy and a sound engineer friend of his were very impressed. The engineer could tell it wasn't done to studio specifications but was still near perfect. Her earliest efforts used a crappy microphone but she corrected that. The engineer pointed out it's like giving strawberrys to a pig. Vilja sounds better than the game itself.
|
|
|
Post by yandere on Nov 13, 2023 20:27:12 GMT
Did you ever figure out this issue? because I'm having the same issue.
|
|
|
Post by Sniffles on Nov 13, 2023 23:03:15 GMT
Did you ever figure out this issue? because I'm having the same issue. What specifically do you want to know?
|
|
|
Post by yandere on Nov 16, 2023 9:22:05 GMT
Did you ever figure out this issue? because I'm having the same issue. What specifically do you want to know? I'd hoped to find more information on the cause and potential troubleshooting for the Vilja Joining the Bard College quest not starting, despite getting the dialogue for Wilberts letter again and again. But it seems to have fixed itself , after getting the Amulet from Vilja that her mother sent her, and getting the Wilbert letter dialogue again, the quest started. So the mod seems to have fixed its own issue. Just needed Vilja to develop amnesia about Wilberts letter multiple times so she asked me to go with her on multiple occasions XD
|
|
|
Post by yandere on Nov 17, 2023 14:30:58 GMT
Did you ever figure out this issue? because I'm having the same issue. What specifically do you want to know? Actually I made a discovery. A reliable means of fixing the bug, and it's odd. So I spent half an hour testing this, as I had to revert to an older save before I had "Vilja Joining the Bards College" active due to installing and uninstalling mods. Specifically Vigilant, Beyond Reach and Darkend. Now here's where it gets interesting. I tried to just wait and trigger the quest, nothing. Bug reappeared. So I thought that's odd... okay, so what have I done differently? Suddenly it hits me... "Wait ! Beyond Reach and Vigilant are easily 3 Gigabytes of data.... it couldn't be..." But it was. Installing Beyond Reach and Vigilant, 3 GB of extra data load for the game to need to load, somehow allowed me to talk to Vilja and get the Bard College quest to activate on the first try. I think that this bug, while likely rare, is caused by an error in the speed of loading game data. That somehow prevents the quest trigger from being registered. Because when it has more to load, then it reliably activates the quest in my testing. When the game doesn't have enough to load and process, there's a possibility the quest won't trigger; A guarantee in my case. A THICC modlist is now going to something I recommend someone have if they plan to use Vilja in order to avoid this bug. Potential workaround: (?) Install a mod totalling around 3 GB then remove them after triggering the quest. Just thought I should mention my discovery
|
|
|
Post by Aatrnasyn on Nov 17, 2023 18:24:56 GMT
Did you alter the timescale? "show timescale" in console? Timescales lower than 10 are also known to cause script issues. "set timescale to 10"
|
|
|
Post by Sniffles on Nov 17, 2023 22:32:18 GMT
What specifically do you want to know? Actually I made a discovery. A reliable means of fixing the bug, and it's odd. Suddenly it hits me... "Wait ! Beyond Reach and Vigilant are easily 3 Gigabytes of data.... it couldn't be..." But it was. Installing Beyond Reach and Vigilant, 3 GB of extra data load for the game to need to load, somehow allowed me to talk to Vilja and get the Bard College quest to activate on the first try. I think that this bug, while likely rare, is caused by an error in the speed of loading game data. That somehow prevents the quest trigger from being registered. Because when it has more to load, then it reliably activates the quest in my testing. When the game doesn't have enough to load and process, there's a possibility the quest won't trigger; A guarantee in my case. A THICC modlist is now going to something I recommend someone have if they plan to use Vilja in order to avoid this bug. Potential workaround: (?) Install a mod totalling around 3 GB then remove them after triggering the quest. Just thought I should mention my discovery This is what my tech friend alluded to. The antique game engine unable to keep pace with the modern computer operations. This can be tested with autosaves. They are all corrupt and snowball into crashing the game. He took it to the extent with getting auto saves to always crash the game. Insufficient time allotted to the block of data.
So you forced the game into thinking it had a much larger block of data to write to and from memory. He also tested autosaves producing cumulative data errors. His conclusion was never use autosave as errors add up and remove the PC from dynamic areas where activity is going on the saves cannot record. I followed his suggestions and 90% of my game crashes instantly stopped.
I had Vilja's quests stopped dead, Night Out active and refusing to complete. I reverted to before her asking, ran the saved game cleaner twice, removed dynamics, other followers with scripts constantly running, did sterile no dynamic manual saves.
Then, rigidly following his rules, what took up to 100 hours of Vilja's various quest progressions, we went through Donkey Tail cure, Bards College, learning chants, and the entire romance from Night Out to getting married, in a total of less than 7 hours of game play time.
He quest progression went so fast I was confused and had trouble keeping up with events. In less than a half hour of game play she would fire off another "There is something I would like to talk to you about." I had three go off in a little over 20 minutes.
But what was flat out amazing for me was in the Bee and Bard after the wedding there was loads of dialogue I have never seen before. Every member of her family had several comments as well as five or six regular NPCs of the Inn having comments. I was "Where in heck did all this come from?" I had done the wedding and celebration several times in the past and had never encountered so much. And then on top of everything, instead of asking her to leave and her wanting to stay longer, I let the game run in that crowded area for about 15 minutes and she came up and asked to leave!
The tech also found another issue. After playing for a while and moving from area to area, the game would suddenly freeze or drop to desktop. He forced the game into the freeze condition then cheated. He had the game running on a 'terminal' computer slaved to a server. He had the server check the terminal for the error and found the memory was full and a DLL the system required was unable to load. He suggested in moving through multiple cells to always make a safe save and shut down the game and reload every 20 minutes or so. In his words, "Pamper the OS and give it room to work."
|
|