d3d9.dll proxy help!

[brothertodd7]

Here is the issue... I have optimus laptop so I have to use the optimus fix for any d3d9.dll-type mods out there. I prefer around 50-60 fps so a straight up enb is out of the question, I want to use the enboost memory management feature though, so I downloaded the enblocal.ini file to overwrite the default one from the newest enbseries. To compensate for not using enbseries, I decided to use Ultimate Lighting Overhaul (sweetfx version) to get bloom and the other effects i want. So in case you don't see my issue yet, it's this: I have "3" d3d9.dll's and I have no idea how to make them work together...

I understand that there is a way to chain two d3d9.dll's together by using the proxy settings in the enblocal.ini but I wouldnt know how to chain these three together properly...

 

To make it easier to answer I currently have in my TESV.exe folder:

 

d3d9.dll --------------- (with the all the appropriate enb series files)

sweetfx_d3d9.dll ------ (from ultimate lighting overhaul)

optimus_d3d9.dll -------(from the optimus fix)

 

 

and these are my current proxy settings in enblocal.ini (this is the enboost ini file) :

 

[PROXY]

EnableProxyLibrary=true

InitProxyFunctions=true

ProxyLibrary=sweetfx_d3d9.dll

I realize that I may overlooking something obvious, but for the life of me I can't figure out what!!

-Todd

and if you're interested in my specs for whatever reason: i7 2670qm (2.2GHz quad ) 8 gigs of ram and a dedicated 580m (1024 vram) with an integrated intel hd graphics (optimus derp) -nothing overclocked- cant really oc this processor and 580m's still throttle a little early (though not as much as they used to)

Edited September 27, 2013 by brothertodd7

[vlaka]

check this: http://enbseries.enbdev.com/forum/viewtopic.php?f=21&t=310

Just a heads up, Sweetfx can cause fps loss.

 

So you're using the injector version of the ENB?

[brothertodd7]

No I'm using the wrapper version of enb so that enboost can work- the nexus description isnt clear on whether or not you can use enboost with the injector version, if it is, then it must be lost in translation as I can hear his accent through his typing somehow, lol

[brothertodd7]

Also that link, I may be misunderstanding but it seems that he is using the proxy library to refer to the optimus version d3d9.dll. I know how to reference another library, I just don't know how to reference 2 libraries in the same ini file. or if there is a way to use the optimus dll for all three ( though I dont see that working).

 

Sweetfx causes less fps loss than an enb series though- or at least that's what it is claiming. I have a few frames to spare, I just prefer higher than lower if I can help it. I will use enb if I have to because it comes with the memory management, but I would like to find a compromise if possible

[vlaka]

As far as I know you can't use more than 2 dll's.

there's the enb d3d9.dll and then the other proxy one.

You're going to have to choose between sweetfx.ddl (which can cause fps loss) or the optimusfix.dll UNLESS there's a seperate config/ini file for the optimus fix where you can add an additional proxy.

Edited September 27, 2013 by vlaka

[brothertodd7]

 

you only need it to point to 2, d3d9.dll is used automatically.

 

I'm not well versed in ini editing, do I put a comma between them? for example:

 

[PROXY]

EnableProxyLibrary=true

InitProxyFunctions=true

ProxyLibrary=sweetfx_d3d9.dll, enboost_d3d9.dll

^is assuming that I use the optimus dll as the primary one of course

[vlaka]

i edited my previous post :D

 

Anyhows this is taken from the hialgo FAQ and an example of what I mentioned in my previous post ;)

WHAT TO DO WHEN ENB d3d9.dll-based MODS ARE ALSO USED

Note: ENB mods often come in to variants: as injector and as wrapper. Only wrapper version is based on d3d9.dll and requires changes described here.

1. Rename our d3d9.dll to, say, d3d9_hialgo.dll

2. Edit enblocal.ini, so that its [PROXY] section looks as following:

[PROXY]
EnableProxyLibrary=true
InitProxyFunctions=true
ProxyLibrary=d3d9_hialgo.dll

3. That's it!

WHAT TO DO WHEN non-ENB d3d9.dll-based MODS ARE ALSO USED

Note: this works no matter ENB mods are also present or not.
Examples of non-ENB d3d9.dll-based mods: Standalone SMAA, FXAA Post Process Injector.

1. Rename other d3d9.dll to, say, d3d9_other.dll

2. Edit HiAlgoBoost.ini so that the part of [PROXY] section looks as following:

[PROXY]
EnableProxy_d3d9 = true ; Can be used to load Standalone SMAA,...
ProxyLibrary_d3d9 = d3d9_other.dll

3. That's it!

[brothertodd7]

Ah gotcha...

 

what about another idea I had:

 

HiAlgoboost d3d9.dll is compatible with optimus, and it has an ini file that uses proxy-library in the same way as enb does... could i chain them together and have the correct effect I'm looking for? for example using enboost dll to refence optimus' dll - and hialgoboost dll to refence enboost's dll somehow?

[vlaka]

yeah that would be the only way to chain them together :)

you'll also have hialgo running too mind you.

[brothertodd7]

I see we had the same idea lol