Jump to content
  • 0
ATMPlays

C++ Coders needed to fix Mod Organizer to work with the new Windows 10 Version/Insider Builds

Question

On October 17th a the Fall Windows 10 Creator Update is coming out, with it comes a patch for the DX9 4 GB VRAM limit. But it breaks Mod Organizer (at least in insider builds). Tannin and others have layed out how to fix it in this GitHub Issue. All we need is some coders proficient in C++ to build and compile MO with these fixes. I'm sure everyone would appreciate if someone solved this problem.

Share this post


Link to post
Share on other sites

8 answers to this question

Recommended Posts

  • 0

I have also "put out feelers" for coders in as many places as I can think that coders/gamers would look.

Push comes to shove I may have to reinstall my development environment for MO/MO2. Not pleased about that as last time it was a hassle of different installs just to get the correct files to compile.

 

That and the fact that I'm not a very good coder. :cool:

Share this post


Link to post
Share on other sites
  • 0

I have also "put out feelers" for coders in as many places as I can think that coders/gamers would look.

Push comes to shove I may have to reinstall my development environment for MO/MO2. Not pleased about that as last time it was a hassle of different installs just to get the correct files to compile.

 

That and the fact that I'm not a very good coder. :cool:

I could probably try to fix it myself but I don't want to install the Insider version and I don't have any other Windows Keys to put it on other computers. If it is not fixed by the fall update I will update my PC and try to fix it myself

Share this post


Link to post
Share on other sites
  • 0

There are plenty of users here with the Windows update that can test for you if you want to do it.

Share this post


Link to post
Share on other sites
  • 0

@chrisbro-MSFT,  a Microsoft developer apparently, just posted on the GitHub that build 16289+ will have the fix for this so maybe there will be no need to make any changes.

Share this post


Link to post
Share on other sites
  • 0

@chrisbro-MSFT,  a Microsoft developer apparently, just posted on the GitHub that build 16289+ will have the fix for this so maybe there will be no need to make any changes.

Sweet, I just read that myself. I guess we will see when the build comes out if it works or not. If it doesn't I will take up your offer to fix it here without the update and then letting the users here on the STEP forum test it.

Share this post


Link to post
Share on other sites
  • 0

You know it's nice when the fix is mentioned in the official blog on the insider release.

16288

Gaming
  • We fixed an issue resulting in Mod Organizer no longer load mods into Skyrim in recent flights.

Share this post


Link to post
Share on other sites
  • 0

This is pretty awesome and my hat's off to the Microsoft developers that walked this up the chain to get it fixed so quickly. What I find really annoying though is that the original 4GB issue sat in Microsoft Connect since 2015 and is still active. I think Microsoft Connect was a good idea when it was created, but it's become a dumping ground for issues and is no longer useful.

 

https://connect.microsoft.com/VisualStudio/feedback/details/1263324/gpu-memory-allocation-limit-on-directx9-windows-8

Share this post


Link to post
Share on other sites
  • 0

I had seen that the 4GB dx9 issue was still listed on connect but I can verify that as of build 16278 it no longer exists. Confirmed by Boris's VRamSizeTest for DX9 running that build Win 10 64bit. Somone on the connect end really needs to reply to that thread and close it, unless they are waiting for the fall release to go public and not just insider.

Share this post


Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Similar Content

    • By irisquexo
      Hi guys I'm new here so hopefully this is the right place to post this.
       
      When I try launching Skyrim SE through Mod Organizer 2 I get the error "REL/Relocation.h(567): failed to open file"
       
      Before this error I was getting the error "REL/Relocation.h(548): failed to open file" but I uninstalled and reinstalled the engine fixes and SKSE libraries. After doing that and relaunching I get the error I mentioned above. Do you guys know what I could have done wrong? I'm really new to messing with mods so it's probably something I did wrong... I've made sure all plugins are enabled and all mods are installed with their masters except for the ones below because I can't find the appropriate mod that goes with it so maybe that could also be the issue. I'm pretty sure I have "Blues Skyrim" but the creator renamed it so that's why MO2 is detecting it as missing. Idk if that's the case with the other ones though.
       
      Missing masters:

      Master                                                                               Required By
       
      Blues Skyrim.esp                                                              Eli_Breezehome [PATCH - DOS (Director's Cut) SE VER1.4] (STD).esp
       
      Skyrim Better Roads - All In One - Merged.esp                Settlements Expanded SE - Skyrim Better Roads Patch.esp, Skyrim Better Roads - All In - One - Merged - PATCHED.esp
       
      Soljund's Sinkhole.esp                                                      Settlements Expanded SE - Soljunds Sinkhole Patch.esp
       
      Tes Arena - Skyrim Frontier Fortress.esp                         Settlements Expanded SE - Legendary Cities Patch - AIO.esp
       
      Whistling Mine.esp                                                           Settlements Expanded SE - Whistling Mine Patch.esp
       
       
       
      also another problem is when I run LOOT it gives me the error 
       
      Loot failed to run
      Errors:
      Cyclic interaction detected: ELE_SSE.esp --[Master]-> SoS_ELE_Patch.esp --[Group]-> Luminosity Lighting Overhaul.esp --[Master]-> SoS_Luminocity_Patch.esp --[Group]-> ELE_SSE.esp
       
       
       
      If anyone knows what I could do to fix this, that would be amazing. Thank you


    • By JackGee
      Hi there peoples,

      First time posting, so if this isn't allowed please just let me know. Looking for a bit of support, as been scratching my head for ages now and getting nowhere.

      I have used MO2 + xEdit in the past and never had any issues with it. However, decided to mod Fallout NV again. When trying to run FNVEdit through MO2, it doesn't seem to complete the action as LOOT tells me after cleaning that it still needs cleaned. I have made sure the installation directory for MO2 isn't in the Fallout folder. It's all on my C drive (SSD). Tried running as admin ect. Clearing read only. Just can't seem to get it working.

      Any advice or help is appreciated.

      Thanks 
    • By Kattmandu
      Since the release of Anniversary Edition, I renamed my Skyrim SE installation folder from 'Skyrim Special Edition' to 'Skyrim Special Edition Classic' before updating the game on Steam.  So now I have both folders in Steam\steamapps\common.
      I have setup MO2 to have two different instances of Skyrim SE (one being Anniversary Edition and the other being just before Anniversary Edition).  I'm using the same Base Folder (F:/Tools/MO2Base/Skyrim) for both instances so I don't have duplicate mods using up disk space.  However, I did create unique subfolders for 'Profiles' and 'Overwrite' (e.g. %BASE_DIR%/AE/profiles and %BASE_DIR%/SE/profiles).
      So, now I have FNIS installed and when I run it through the 'Skyrim Special Edition' instance, it runs as expected.  When I switch to the 'Skyrim Special Edition Classic' instance, FNIS gives me the following warning...
      FNIS Behavior V7.6   11/14/2021 2:35:15 PM
      Generator: F:\Games\Steam\steamapps\common\Skyrim Special Edition Classic\data\tools\GenerateFNIS_for_Users\GenerateFNISforUsers.exe
      Skyrim SE 64bit: ??.??.?? - F:\Games\Steam\steamapps\common\Skyrim Special Edition\ (Steam)
      >>Warning: Expected generator path: F:\Games\Steam\steamapps\common\Skyrim Special Edition\data\tools\GenerateFNIS_for_Users not found<<
      I'm also getting similar pathing error when trying to run DynDOLOD through MO2...
      Error: Can not find DynDOLOD Resources SE core files to create improved LOD.
      Current Data path F:\Games\Steam\steamapps\common\Skyrim Special Edition\Data\
      Is there a way to run these utilities through MO2 with Skyrim SE being in a folder other than 'Skyrim Special Edition'?
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.