Any Heads Up About Win10 & Skyrim I Should KNow?

[Sarge Misfit]

Having issues related to my 3Tb HDD and Win7. Win7 was problems with any HDD over 2Tb. I've given Win10 a try a half a dozen times, had some problems and keep going back to Win7. Its now come time that I really need to get this drive working properly.

 

I'm already familiar enough with the OS to deal with things like privacy and security. But, I would like to try to prevent any issues with running Skyrim on Win10.

 

What should I be aware of?

[Guest]

I do use Skyrim (normal and SSE) on Win10. Zero problems.

[TanookiTamaTachi]

There was an issue with VRAM and DX9, but it seems to have been fixed: http://www.loverslab.com/topic/78934-microsoft-is-fixing-skyrims-memory-problem-with-windows10-and-dx9/

 

Additionally, MO's virtuallization didn't work with Win10, but that got fixed too (not sure if that update is public yet): https://www.reddit.com/r/skyrimmods/comments/6yxweh/c_coders_needed_to_fix_mod_organizer_to_work_with/dmr6bws/

 

Those are all I'm aware of.

[Guest]

33 minutes ago, tanookitamatachi said:

There was an issue with VRAM and DX9, but it seems to have been fixed: http://www.loverslab.com/topic/78934-microsoft-is-fixing-skyrims-memory-problem-with-windows10-and-dx9/

 

Additionally, MO's virtuallization didn't work with Win10, but that got fixed too (not sure if that update is public yet): https://www.reddit.com/r/skyrimmods/comments/6yxweh/c_coders_needed_to_fix_mod_organizer_to_work_with/dmr6bws/

 

Those are all I'm aware of.

The VRAM limit was removed with the latest version of Win10.

I do use MO and it works just fine with the version that is still on Nexus.

[Sarge Misfit]

Thanks, guys. Not worried about MO as I use it only to check for missing masters and to unpack FOMOD archives. I guess I like the "hands on" feel of a manual installation

[RW311]

I would reply but windows10 is updating....

 

Seriously stay away from win10 home version, pro is ok because you can setup update to install when you want. I had to wipe two pcs of win10 home and just use linux because they were always updating and shutting down and they were actively being used way too often when it happened.

[Dinosaurus]

8 hours ago, tanookitamatachi said:

Additionally, MO's virtuallization didn't work with Win10, but that got fixed too (not sure if that update is public yet): https://www.reddit.com/r/skyrimmods/comments/6yxweh/c_coders_needed_to_fix_mod_organizer_to_work_with/dmr6bws/

 

Those are all I'm aware of.

 

Like CPU, i have no problem using Mod Organizer (the version on Nexus) on my Window 10 system.

[Sarge Misfit]

I finished installing Win10 Pro (I never go Home, RW311 ) last night, got the basics configured. Took about 3 hours.

Anti-V, utilities, etc, all installed.

Then on to Steam, Skyrim and my mods. Since I'm now using different HDDs, I was able to copy my previous Data folder over to this 'new' setup.

Did the Vanilla activation of the mods, they sure look purty lined up in alphabetic order.

Time to LOOT and run.

 

Thanks again, folks.

 

[Sarge Misfit]

And that worked remarkably well.

 

Usually, when I start a game for the very first time using ASLAL, I will CTD jsut before RaceMenu appears, restart and then CTD just at the AutoSave that ASLAL does, restart and everything is hunky-dory after that. No CTDs this time.

[macnchz]

On 11/14/2017 at 3:03 PM, CPU said:

The VRAM limit was removed with the latest version of Win10.

I do use MO and it works just fine with the version that is still on Nexus.

Hello TO anyone with experience/knowledge here... 

 

I downloaded win10 creator v1079 (latest as I did this last week) and the memory bug was indeed fixed!  I do use MO.  Problem I ran into with the upgrade skyrim "flashes" through the entire load screen and ingame.  Reading forums on Nvidia there seems to be some kind of problem with win10 and them.   Anyone have any thoughts?  I rolled back to the win10 verison 1073.  

[Sarge Misfit]

I've got nothing happening that resembles any sort of "flash". I'm running an nVidia GeForce 720GT 1Gb VRAM and 8Gb onboard RAM. I was getting lockups and CTDs that CrashFixes kept identifying as issues with different memory blocks. Since then, I tweaked my system's settings to set Windows paging system to a max of 4Gb and ran Ordenador to optimize my textures. Everything works a bit better than they did under Win7. Not a huge improvement, but some improvement nonetheless.

 

Caveat: I'm not sure if my Win10 is fully updated as I haven't checked in a couple-three weeks. I'll check and will edit this once I find out.

 

~~~~~~~~

Just got updated automatically last night , Mon the 11th.

Haven't played yet.

Tweaking Crash Fixes settings after a full reinstall of my mods

[macnchz]

On 12/6/2017 at 1:13 PM, macnchz said:

Hello TO anyone with experience/knowledge here... 

 

I downloaded win10 creator v1079 (latest as I did this last week) and the memory bug was indeed fixed!  I do use MO.  Problem I ran into with the upgrade skyrim "flashes" through the entire load screen and ingame.  Reading forums on Nvidia there seems to be some kind of problem with win10 and them.   Anyone have any thoughts?  I rolled back to the win10 verison 1073.  

Anyone having flickering screen issues should follow this:  I know it says SSE version but it works... -   https://www.reddit.com/r/skyrimmods/comments/5a20vn/sse_performance_guide_stutter_microstutter_fps/

 

Additionally, it was an ENB error with nvidia geforce experience.  I had to tweak with inspector and clear out enblocal.ini edits.  Finally all good.