First of all, I apologize for starting a new topic for this when one already exists:

 

http://forum.avsim.net/topic/345611-emb-hdr-mod-and-antilag-external-fps-limiter/

 

But since it's and "aged" topic, it won't let me continue the discussion there.

 

I had previously thought that I needed to chose either antilag or ENB, so I was excited today when I found this thread describing how to use both together. However, I have a question about these instructions:

 

Just rename the antilag's d3d9.dll to something else before putting it in the fsx folder. Then add this to your enbseries.ini where antilag.dll is what you renamed the dll file to:

 

[PROXY]EnableProxyLibrary=1

InitProxyFunctions=1

ProxyLibrary=antilag.dll

 

After ENB has loaded via its d3d.dll file, it will look for the other dll file specified in the ini.

 

Just for my own understanding, why does it work this way? I would have thought that you'd have to rename the ENB version of the d3d.dll and tell ENB where to find it. Why am I renaming the antilag version of the file and then telling ENB where it is? Am I allowing ENB to run and then telling ENB to run antilag as well?

 

Again, this is just for my own understanding. Hopefully this thread can be beneficial in some other way as well...

Am I allowing ENB to run and then telling ENB to run antilag as well?

 

Yep!

 

Remember that enbseries.ini isn't the first thing "loaded"... to FSX it's just a pointless file. Only the file called d3d9.dll is loaded automatically, in this case the enbseries version, which then looks for enbseries.ini for its startup settings. Thankfully enbseries allows you to then load another dll, the renamed antilag dll in our case. So it has to be like this. The antilag dll doesn't support loading another dll.

Thanks! I would have thought it worked the other way, but it makes sense now!