phazer11

Have you tried pressing ~ then entering pcb then enter again to purge your buffers once you enter an interior when you notice this happening?

Ok so anyone able to shed light on this issue? I know it's because of the new version but anyone have any ideas why? Setting the FOMOD installer flag Prefer or both the Prefer and Enabled flags to false causes this. Just for clarity these are the settings I'm talking about. Although for whatever reason it may not be just in those cases since when I tried re-installing A Quality World Map it gave the SNAFU as well. I tried using the separate NCC plugin from the optionals section like you would for previous client versions but no luck.

Do they act like cover i.e. prevent rain from hitting you?

Or might just refund the extra amount you paid.

I talked to him and I don't think he can. Mich you can look at the MT forum thread I made. @OP I'm still looking for a way to do what you asked, so till then I don't think it's possible.

Yeah I made mention of it somewhere in one of the mod suggestion threads a couple weeks ago and zed (or one of the other admins) didn't know about it.

That is one of the things I said setting the FOMOD installer flag Prefer or both the Prefer and Enabled flags to false causes this. Just for clarity these are the settings I'm talking about.

No I just don't want to make another custom archive it's annoying. I'm talking with Will to see if I can't fix the FOMOD. Though the latest version of MO may just be going bye bye the FOMOD plugins are pissing me off since I can't seem to disable the internal installer.

Well I'm looking at it from the point of view that the wiki guide for it is incomplete and the point of view that I'm trying to get it installed for my testing profiles and need more information and workaround since the installer is broken.

Well I would imagine Hunterborn is the problem as it's the only one I don't use for my own install. I really can't stress how useful Mod Organizer is especially when you have WB as an executable to run so you have the bashed patches. But no I do not know the intricacies of Papyrus and am too busy with HW, Classwork, setuping my Mod Testing Profiles and yard work to look through the documentation from Bethesda.

I know it's there but the options aren't working as I'd expect I tried disabling the internal FOMOD installer completely and just having the prefer option set to false and just having the NCC one enabled and it gives me an error as if it's missing something. Also are we recommending one version over the other or what and install notes? Should I make a custom archive or what (for STEP testing)?

So what version are we recommending for the wiki (and which should I use for testing)? Also we should add a note or instructions since the FOMOD does weird things in MO and with the latest version of MO it's a bit difficult to disable or enable the integrated FOMOD installer. Anyone else using the latest MO version?

Or you could look at the STEP wiki... and/or use Mod Organizer.

Legendary Edition is $35 through Steam and since the DVD version doesn't have the DLC's on the DVD you might as well get the Steam one if you already have a Skyrim disc. I was disappointed when I bought the DVD version only to find out it only had an activation code for the DLC's and a Skyrim DVD that the only difference from the one I got at launch was the image on the disc (it may have had the latest update I can't remember)

You shouldn't need to do much only add the new mods you want from the STEP guide if that's what you're using and add the DLC compatible ones of the ones you're using. If you're using Skyrim Revisited you'll need to add some more compatibility patches but that's about it

Yeah I realize. It's just I can see the difference and it bugs me. That's why I posted the archive. I'm going to try finding an alternative way of uploading the images so they can be viewed online.

What zed said plus the other thing to take into account is that the monitors and task manager are only showing us the working set of RAM and I would assume it (windows) holds some in reserve for the process. Also thanks for correcting me roland my posts are sounding a bit erratic even to myself as I've gone over them. I've been having migraines and haven't gotten a lot of sleep due to stuff...

I sent him a plea for help as I believe with the legendary edition's release we'll be seeing a lot more scripted mods in the near future that'll need testing (gut feeling).

Do I need to post those .bmp to the wiki? It's easier to look through the actual files through my archive. IMO and a better indicator as they're uncompressed bitmaps the .jpegs are smoothing too much out the EDT effects are subtler but they're being turned to mush in the .jpegs... then again I'm a bit anal with this kind of thing as I edit pictures and video and need the "trained" eye for my classes.

I guess I'll have to write some guides for the wiki before I start doing more testing.

Yeah I downloaded it the other night but haven't gotten around to trying it I'm mainly working on getting my STEP installs completed and separated for testing atm.

Yup makes them look nice. Gopher's using the mod in his let's play if you want to get some nice views. I don't think he's using the sword yet but he did a episode so people would stop bugging him about his uber skyforge steel sword in which he shows the 3D model with this mod applied. I'm using it as well in my SkyRe-ified Skyrim Revisited+ setup.

Doesn't Conskrybe do something like that? Idk I'll try to look into it between test runs and my screenplay and see if maybe STATUS has it. I'll also message MannyGT on nexus and here to see if he could incorporate something into STATUS.

What I think he's saying is that Skyrim CTD's whenever it tries to make a call to address RAM outside of the 4GB it's allowed which causes it to crash or returns an error after which point it crashes. I'm a bit rusty on programming and never dealt much with memory allocation but I think that's what he's meaning.

Well put couldn't have said it better roland. As it's been said the problem seems to be that 32-bit executables (in this case Skyrim) can only use 4GB of RAM. Skyrim's RAM usage is a combination of mirrored VRAM, RAM used by the main engine to run the game, and then RAM used for any scripts you have running. Therefore this is likely a combined issue of a 32-bit program limitation hitting the design flaws of DirectX9.