Jump to content


Photo

ENBOOST/Vram text dx9/11 - strange numbers?


  • Please log in to reply
9 replies to this topic

#1 m3dicat3d

m3dicat3d

    Prisoner

  • Members
  • 25 posts

Posted 14 May 2017 - 10:36 AM

So I have seen this asked when I searched under the sticky posts, but I couldn't find the answer I was specifically looking for. So hopefully this is okay to ask (and I do apologize if the answer is somewhere I didn't check).

 

My system has a GTX1080 and 16Gb of DDR4 3000 RAM. When I run memory tool i get the reported 4096/11860 (can't recall the DX 11 number exactly). There was an older manual way I read about some time ago about adding card ram and system ram, then subtracting something like 2k to get a value for the enblocal.ini file. If I do that, I'd be somewhere in the low 20,000 - 22,000. So when I see lower numbers, I wonder why the difference?

 

My question is specifically: Do I just use the reported number, or is something *amiss* for lack of a better word?

 

Thanks!


  • 0

#2 m3dicat3d

m3dicat3d

    Prisoner

  • Members
  • 25 posts

Posted 14 May 2017 - 11:00 AM

Okay, after I posted I kept doing some more reading, and I did come across something. Evidently, with Win 10, there is the 4Gb vram limit. I just built a new rig, and put win 10 on for the first time, was using 7 on the old rig, and from what I've read in the past, this could be the issue. I am still reading, and also DL'ing the Creator's Update (not sure is gaming mode is live yet or not, or even if it addresses the vram limit issue, but I'm going to give it a try.

 

Sorry for the extra post, couldn't find the edit button :(


  • 0

#3 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 12,051 posts

Posted 14 May 2017 - 11:10 AM

DirectX for classic Skyrim is limited to 4096. This is a bug with Microsoft that has never been fixed (and probably will not be).



#4 m3dicat3d

m3dicat3d

    Prisoner

  • Members
  • 25 posts

Posted 14 May 2017 - 11:14 AM

Thanks, I'm starting to get that same impression myself as I do more digging, and Game mode in the Fall CU doenst seem to be much at initial glance. Guess I will try it at the 4Gb limit and simply hope for the best.

 

Now I'm wondering if I should install a drive with win 7 on it for oldrim specifically.

 

Anyhow, thanks again!


  • 0

#5 Greg

Greg

    High King

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,485 posts

Posted 14 May 2017 - 11:30 AM

This bug was originally reported after Windows 8 was released and hasn't been fixed in Windows 8.1 or Windows 10, so I doubt it will ever be fixed. Some folks here report that Skyrim works fine on Windows 10 provided you stay below the 4GB VRAM limit although you may expect some stuttering and odd issues if you go over the 4GB VRAM limit. If I were in your shoes, I would try it first with the mods you want to see it in action before deciding to dual boot Windows 7.



#6 m3dicat3d

m3dicat3d

    Prisoner

  • Members
  • 25 posts

Posted 14 May 2017 - 11:41 AM

Good point, thanks!


  • 0

#7 bitdman

bitdman

    Thane

  • Members
  • PipPipPipPipPipPip
  • 351 posts

Posted 14 May 2017 - 02:59 PM

DirectX for classic Skyrim is limited to 4096. This is a bug with Microsoft that has never been fixed (and probably will not be).

 

This bug was originally reported after Windows 8 was released and hasn't been fixed in Windows 8.1 or Windows 10, so I doubt it will ever be fixed. Some folks here report that Skyrim works fine on Windows 10 provided you stay below the 4GB VRAM limit although you may expect some stuttering and odd issues if you go over the 4GB VRAM limit. If I were in your shoes, I would try it first with the mods you want to see it in action before deciding to dual boot Windows 7.

I don't understand the "VRAM limit". For years I've seen this topic discussed and the bottom line is always a"Windows issue", or a "game engine" limitation. This sounds a lot like the situation with the Script extender 64. in that it's a problem  that very few understand and are able to fix. To think that something can't or will not be be fixed is like building a ship when all you can get is trolling motor to propel it. Why are these limitations so hard to understand or fix?

 

Or is it being dealt with in baby STEPs  :) to keep upgrades and money flowing in?

Is it being deliberately and methodically dealt with? I'm not suggesting a conspiracy......It's just that?????? 


  • 0

#8 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 12,051 posts

Posted 14 May 2017 - 03:33 PM

It's been officially reported on Microsoft and confirmed as an issue with DirectX 9's implementation in Win 8/10. My assumption has been that it's because they used some 32bit implementation of DirectX 9 for compatibility reasons. This is the only reason I can think of it being limited to 4GBs.

#9 Nebulous112

Nebulous112

    High King

  • Super Moderators
  • PipPipPipPipPipPipPipPipPipPipPipPip
  • 1,414 posts

Posted 14 May 2017 - 06:21 PM

It affects all DX9 games.

I think Microsoft just doesn't care, because in their opinion too few people still play DX9 games for it to matter. And most / all DX9 vanilla games don't require more than 4GB of VRAM.

It really only is a problem with heavily modded games, and that userbase is faaaaar too small for Micro$oft to spend resources on fixing the issue.

#10 TechAngel85

TechAngel85

    Akatosh

  • Administrators
  • PipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPipPip
  • 12,051 posts

Posted 14 May 2017 - 07:03 PM

It affects all DX9 games.

I think Microsoft just doesn't care, because in their opinion too few people still play DX9 games for it to matter. And most / all DX9 vanilla games don't require more than 4GB of VRAM.

It really only is a problem with heavily modded games, and that userbase is faaaaar too small for Micro$oft to spend resources on fixing the issue.

Exactly!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users