Jump to content
  • 0

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


ATMPlays

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.

Link to comment
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:

Link to comment
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

Link to comment
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.

Link to comment
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

Link to comment
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.

Link to comment
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
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.