ripple

Audition clips received and thanks for the auditions.

As Rhowinton says. There are many tutorials for making NPC followers -properly- using the CK.

If you are interested in auditioning for a role, please record the sample dialogue for that role, and upload it to a sound streaming site (like SoundCloud) or free file sharing site and send me the links. Please keep in mind that for the 'final product', the sound file must be in WAV format, mono, 44100 Hz. - you may audition for multiple roles. - for each of the following characters, the total workload is around 10 to 20 lines of dialogue. - tentative deadline for submission of audition clips is April 5, 2014. = Jack Nord = Voice Type: male, teen - young adult (character is 15 - 18 years old), Nord/'Eastern European' accent Sample dialogue: "Sorry, but I just want to be left alone." "Such cruelty...who would do a thing like this?" (scared tone) "Sure, I can help you. What do you need?" = Jack Imperial = Voice Type: male, teen - young adult (character is 15 - 18 years old). Sample dialogue: "Sorry, but I just want to be left alone." "Such cruelty...who would do a thing like this?" (scared tone) "Sure, I can help you. What do you need?" = Jane Nord = Voice Type: female, teen/young adult (character is 15 - 18 years old), Nord/'Eastern European' accent Sample dialogue: "Sorry, but I just want to be left alone." "Such cruelty...who would do a thing like this?" (scared tone) "Sure, I can help you. What do you need?" = Jane Imperial = Voice Type: female, teen - young adult (character is 15 - 18 years old). Sample dialogue lines: "Sorry, but I just want to be left alone." "Such cruelty...who would do a thing like this?" (scared tone) "Sure, I can help you. What do you need?" = Child = Voice Type: female, character is 8 - 11 years old. Sample dialogue: "My grandmother hasn't been feeling well for a very long time. I really hope she gets better soon..." "She's my best friend!" (sad) "I miss my mother..."

Be careful about uninstalling mods in the middle of a playthrough. All mods will leave something behind in your save game when uninstalled, and while most of the orphan junk tend to be relatively harmless and usually 'fixed' after a complete cell reset, 'script intensive' mods can caused nasty things like broken OnUpdate events to be baked into your save game that leads to spamming Papyrus logs and 'corrupted' saves (I didn't notice anything like that in your previous Papyrus logs). If you are planning to start a new game, I would advise finalizing a list of mods that you fully intend on using and will not install mid-playthrough. You can use this opportunity to 'mess around' and stress test your mods and the game. You didn't mention any performance issues so I'll dispense with suggestions about how to stress test performance (since that doesn't seem to be an issue for your setup). Just remembering that it's always far easier to add mods than to remove them. Adding mods is not a problem, but things tend to go to hell in a hand basket when the user starts to yank mods out of the load order mid-playthrough.

I have around 180 or so plugins in my load order, my PC is 4+ years old, and I average around maybe...1 CTD every 3 months (I play in 'bursts', but total play hours would average to about 2-6 hours a day, longest continuous play session might be 8 hours, with some breaks in beween). You just have to be meticulous about maintaining a clean and well organized modded installation, be mindful of the quality of mods you install (I always look through plugin records of mods prior to installing those mods, and check their scripts if source files are provided, even open up meshes in NifSkope to make sure they are not faulty), and learning to use the modding tools available to you, like BOSS, TES5Edit, and Wyre Bash, that are intended to make the process easier and more efficient.

No problem. But rather than PM me, just track this thread or use your posting history (which you can find under your account profile), and provide an update here if the same issue appears. This will push the thread to the top of the forum, and will also notify me that I thread I had replied to has been updated with new post. It will allow me to skim the previous conversation to refresh my memory of your issue, and might provide useful information for anyone else who might be lurking and reading this thread because they are experiencing similar issues. I don't know why your mesh LOD is reset to that value (it's not the default game value on my end). But probably not a serious issue right now. Incidentally, which mod manager are you using?

Actually, those are deleted references, which will be undeleted and set to 'disabled' when cleaned via TES5Edit, so that if a mod loaded later references that record, it will not potentially cause CTDs.

There are a number of 'Skyrim modding myths' floating around the internet, in spite of best efforts to stamp them out. Cleaning plugins will have no adverse effects on plugins as long as it is done properly. Stick to cleaning the plugins I mentioned (those identified by BOSS as containing 'dirty edits', and where BOSS has not explicitly stated the 'dirty edits' are intentional). The link the BOSS log contains the instructions for proper cleaning, video and text. You are not bursting anyone's bubble, but you are perpetuating yet another 'Skyrim modding myth', which is that BOSS 'mess up' load orders. BOSS provides a template load order based on community input that, 99% of the time, works better than any random load order you will find from unverified sources on the internet. It's fine for more experienced users to modify BOSS established load orders, especially to accommodate plugins not recognized by BOSS (which is necessary), but a heavily modded load order without the assistance of BOSS is almost guaranteed to be a disaster.

Don't know anything about your ENB issue, but CTD during the logo screen is typically a mod dependency issue, which means you are trying to load a plugin that is dependent on a master which is missing from your load order. You can find out which plugin it is and which master it's missing by using Wrye Bash, or loading all of your plugins in TES5Edit. If TES5Edit stops loading and bounces an error message, the plugin that halts the loading and generates the error is the plugin that is missing a (or more) master. While we are on the topic of TES5Edit, you should download it from the link in your BOSS log, follow the instructions on the same page, and clean the plugins flagged by your BOSS log as containing 'dirty edits' (except the plugins where BOSS explicitly states it's not necessary), including the DLC and update esm's. You will need to remove identical to master entries as well as undelete/disable deleted references.

Oh, I never knew what was wrong to begin with... :smile: You don't have to reinstall Skyrim. The worst case scenario here is that you may need to uninstall a ton of mods and start a new game. But before you do that, it will help to figure out exactly what the is the cause of the problem. Otherwise the problem may reoccur even if you start a new game. Try this: 1) load all of your plugins in TES5Edit (including the ones not recognized by BOSS). 2) click and expand Skyrim.esm. 3) click and expand 'global.' 4) Look for this setting: WiWaitDragonThis is the setting that controls the timer between dragon spawns. See if there are any plugins which contain an override of this value (the entry will be colour coded, and when you highlight it, the right window will display which mod, if any, has edited this setting). The default value is 3 days. If none of the plugins in your load order has edited this value, then my first theory would be entirely off the mark, and we would have to look for another cause to this issue (although it's still possible that a script might alter the value of that setting dynamically, it's less likely).

Yeah the issue is gone, but this means you would have to start a new game to get rid of the problem :) We still don't know what is the cause though. It could be that in the new game, you have not triggered the problem mod's scripts, so it's not running and causing havoc in your game. It could just be that you were using too many 'script intensive' mods using continually updating scripts (you have...many). So there is no assurance the problem won't recur. If you are willing to start a brand new game, I'd recommend you 'scale back' on the number of 'script intensive' mods in your modded installation. This would be the perfect time to do it, since you would not need to worry about any mods leaving orphan data baked into your save games when uninstalling mid-playthrough. Cutting back on the number of these mods you use will alleviate the stress on the game engine as well as your system (keeping in mind that the former has a smaller threshold than the latter, considering this engine was designed to run on a last-gen console, not a powerful custom built PC). I'd keep Papyrus logging running for a few days so you can see if the stack thrashing occurs again. After that, if you haven't experienced the same game instability and do not see the same issue appearing in the log, you can turn off Papyrus logging (because it siphons resources that could otherwise be allocated to the game).

You are just testing right now, so just consider any save you may need to make during the testing period as throwaway saves that you will never continue with in a serious playthrough. This way, you don't really need to worry about the long term repercussions of uninstalling mods as a result of the testing. If you can't afford to turn some of the unrecognized plugins off because they are script intensive, you should at least clean them. Since the BOSS database has no information on those mods, it will not inform you if any of those plugins contain 'dirty edits.'

To help narrow down the possible causes of this issue, I advise you to uninstall the mods associated with the plugins not recognized by BOSS for now (unless you want to look through each of those plugins' records in TES5Edit), before doing further testing to try and identify the cause of this issue.

I did notice this: fMeshLODLevel2FadeDist=10000000.0000 fMeshLODLevel1FadeDist=10000000.0000Pretty sure this is not a default value even at ultra settings, and it's an 'absurdly high' number (by default, they should be in the 4 or 5 digits range on ultra settings). Try deleting your SkyrimPrefs.ini and let the game generate a new file on next launch, see if a more reasonable value appears in the new ini. Some users tweak these settings to address the 'distant LOD pop'in' glitch. I would suggest that it's not worth it. The default game ini settings values are already optimized for 'stability', if not performance or graphics. This puts an additional load on the engine and your system, and since your game has become unstable, it's time to reset everything back to within a 'safe parameter' until the game can be stabilized. It's not the cause of your stack buffers overflow, though. The Papyrus log from a new game will establish for certain whether or not it's caused by a mod.

1) Download TES5Edit from the link in the BOSS log, follow the instructions on the same page, and clean the plugins flagged by BOSS as containing 'dirty edits' (except where BOSS explicitly states they are 'intentional' and need not be cleaned), including the DLC and update esm's. You'll need to remove identical to master entries as well as undelete/disable deleted references. This probably doesn't have anything to do with your issue, but it should be done nontheless. 2) Since you are using the Hi-Res DLC, I recommend you download the Unofficial Patch for the Hi-Res DLC. Nothing to do with your dragon issues, but no reason not to do it. 3) Your dragon issue: if I understand you correctly, you are saying that you no longer see random dragon spawns, like the ones that attack cities, even though you have triggered the appropriate stage in the main quest (I am going to assume you didn't use console to advance quest stages, because that will often break things, but has played the game normally to reach that stage of the main quest). There might be a few different causes of this issue. There is a game setting that controls the timer between random dragon spawns. That value can be edited via the CK or TES5Edit to shorten, extend, or halt the timer for dragon spawns. It's possible that a mod you are using may have edited that value, either intentionally or unintentionally, to extend the timer beyond the time you've waited so far. So any and all dragon related mods in your load order could possibly be responsible for this problem. Try waiting for something like 30 days, and do some fast traveling (always a quick way to trigger random dragon spawns), and see if it helps. Incidentally, did BOSS output a list of plugins it did not recognized?

I think I know what's 'wrong' with your game, thought not necessarily what is 'causing' it. This repeating message in your Papyrus log Suspended stack count is over our warning threshold, dumping stacks: Dumping stack 737689:indicates stack buffer overflows. The CK documentation for that is here. Basically it means the game is trying to process too many script actions at one time. Have you experienced intermittent stuttering and freezes, in addition to the CTDs? One of the frequent causes of this is when some users tweak memory allocation to the Papyrus script engine to an absurdly high value (usually following one of the 'Skyrim ini tweak guides' floating around the interwebs). But you mentioned that you haven't tweaked the game ini settings....but ideally, I'd still like to see your ini settings, even if you've deleted the ini files and let the game generate new ones on launch, both 'Skyrim.ini' and 'SkyrimPrefs.ini', from '...My Documents/My Games/Skyrim/', just to be sure. Just copy/paste the contents of those ini files here, and enclose them in separate sets of spoiler tags. If it's not the ini tweaks, then it could be a really badly written script from one (or more) of the mods you are using. It might also be that you are using too many 'script intensive' mods that is stressing the engine and your system beyond its limitations. Try this: start a new game, and play for 15 minutes with Papyrus logging on. See if you are seeing the same 'stack dumping' messages in the Papyrus log for the new game. Incidentally, how many hours have you logged in your current save games?

I hope that's not the load order...and it looks like you are using an older version of 'Immersive Armor.' It also looks like you are not using the unofficial patches. Replace that mod list with a complete BOSS log (include the SKSE information and a list of plugins not recognized by BOSS if one is generated). Enclose the BOSS log in a set of spoiler tags so it won't clutter the screen.

Copy/paste your complete BOSS log here, and enclose it with a set of spoiler tags so it won't clutter the screen.

If it's too big to upload to PasteBin, then already it's a bad sign....but try splitting it into smaller parts. I...don't want to download anything from sources I can't verify, just a habit. Have you uninstalled mods then continued with save games made with those mods installed?

The Papyrus log is not a crash log, so it will not indicate why your game CTDed. It's a last resort for looking for possible script errors and debug messages that may provide some clues as to any issue your game might be experiencing. As I said before, you need to play for at least 10 - 15 minutes without CTD, and copy/paste the complete log here (or PasteBin, if it's too big to upload here). Snippets will not help.

The Papyrus log should appear under '.../My Documents/My Games/Skyrim/Logs/Script/'

I can't think of any off hand, because I haven't done any mesh editing since Oblivion, and even then, it was just armour mash-ups using NifSkope. If you want to do more complex mesh editing work, you're going to need something like Blender or 3DMax. Just typing those names into a search of these forums should yield a ton of information for you to get started.

CTD at the logo screen is a classic symptom of mod dependency. It doesn't have anything to do with NMM. It's usually caused by attempting to load a mod that is dependent on a (or more) master that is missing from your load order. So if you uninstalled Falskarr, then attempted to start the game and load a mod, for example, a compatibility patch, that is dependent on Falskarr's plugin as a master, that will cause the symptom you described. In short, the real cause of the issue you describe is neither NMM nor mods. It's...user error.

I use the BSA Browser. The Creation Kit comes with its own archiver that you can use to bundle your resources into a BSA. You just need to extract the textures for the armour pieces you want and edit them. But if you want to mess with meshes (like remove a base armour piece component, i.e. cape), you will at least need NifSkope (and you will need to edit the meshes in NifSkope to redirect the texture paths to your edited textures).

I recommend you start keeping a journal of your random CTDs, just so you have a history of reference. Keep track of the location where you experience them (worldspace or in interior cells, where in the world, etc.), and what was going on/what you were doing (in combat, with/out followers, against bandits, a particular outfit being worn by an NPC is present in all CTDs, etc.) This will greatly help to track down the culprit because in a heavily modded Skyrim installation, the cause of random CTDs could literally be....many things. The best way to fix it is to systematically eliminated all possible causes. CTD when reloading after character deaths can be ignored. That one is common and there isn't much you can do about it. In fact, even if your game does not CTD when reloading after character death, you might consider quitting to desktop and restarting the game, to avoid the possibility of corrupt saves made after continuing to play from that reload. I don't use SkyRe, but does it support BOSS v2.2 yet? It's my understanding that the masterlist for the previous version of BOSS will no longer be updated, and all the work for masterlist updating have migrated to v2.2. You can also post your Papyrus log. Play for at least 15 minutes without CTD to log enough information, then copy/paste it here, inside a set of spoiler tags like you did with your BOSS log. If it's too big to post here, you can upload it to PasteBin.