HiAlgo Forums
Sign up Calendar Latest Topics
 
 
 


Reply
  Author   Comment  
defear

Junior Member
Registered:
Posts: 3
Reply with quote  #1 
After trying to figure out massive drops in FPS(<1) with both ENB and HiAlgo active and moving my mouse or pressing the downrez buttons, which turned out to be an issue with a too recent ENB binary(v243 instead of v236), I finally got it working, but now I notice that I seem to get absolutely no benefit at all from using it.

I've recently been using ENB with RCRN and I figured I'd give HiAlgo a try when I found out it can support both at the same time. In my testing whenever HiAlgo is toggled on, I get a decrease in static frames, and moving frames have lower fps than with it toggled off. There's also extremely little to no appreciable difference in smootheness. This holds true when ENB and RCRN is on, when either is on and the other is off, and when both are off.

My computer is as follows:
  • CPU: i7 2600k Quad 
  • RAM: 16GB DDR3
  • Card: GTX 580 1.5GB
  • SSD HDD
Textures are mostly 2k but 1k for smaller objects. No other graphical mods besides ENB and RCRN. I'm also using Mod Organizer to sort my mods. SKSE is also present.

HiAlgoboost.log doesn't show anything meaningful to me, I used to get ref errors 160 and 161, but I've since disabled them in HiAlgoRegister. All other hialgo logfiles show their respective parts working perfectly.

This is the output of my latest run of the game, during which I alternated between various states of ENB/RCRN/HiAlgo like I describe at the top:

12/31/13  02:32:24 Attaching to process...
12/31/13  02:32:46 ======== GRAPHIC ADAPTER ============================
12/31/13  02:32:46 Device Descr     : NVIDIA GeForce GTX 580
12/31/13  02:32:46 Vendor Id        : 0x10DE
12/31/13  02:32:46 Device Id        : 0x1080
12/31/13  02:32:46 Device SubSysId  : 0x83851043
12/31/13  02:32:46 Device Revision  : 0xA1
12/31/13  02:32:46 Device GUID      : {D7B71E3E-53C0-11CF-F373-85A30EC2CD35}
12/31/13  02:32:46 -------- DRIVER -------------------------------------
12/31/13  02:32:46 User-friendly name  : nvd3dum.dll
12/31/13  02:32:46 Driver version      : 0x0
12/31/13  02:32:46 =====================================================
12/31/13  02:32:46 ======== GRAPHIC ADAPTER ============================
12/31/13  02:32:46 Device Descr     : NVIDIA GeForce GTX 580
12/31/13  02:32:46 Vendor Id        : 0x10DE
12/31/13  02:32:46 Device Id        : 0x1080
12/31/13  02:32:46 Device SubSysId  : 0x83851043
12/31/13  02:32:46 Device Revision  : 0xA1
12/31/13  02:32:46 Device GUID      : {D7B71E3E-53C0-11CF-F373-85A30EC2CD35}
12/31/13  02:32:46 -------- DRIVER -------------------------------------
12/31/13  02:32:46 User-friendly name  : nvd3dum.dll
12/31/13  02:32:46 Driver version      : 0x0
12/31/13  02:32:46 =====================================================
12/31/13  02:32:46 ======== GRAPHIC ADAPTER ============================
12/31/13  02:32:46 Device Descr     : NVIDIA GeForce GTX 580
12/31/13  02:32:46 Vendor Id        : 0x10DE
12/31/13  02:32:46 Device Id        : 0x1080
12/31/13  02:32:47 Device SubSysId  : 0x83851043
12/31/13  02:32:47 Device Revision  : 0xA1
12/31/13  02:32:47 Device GUID      : {D7B71E3E-53C0-11CF-F373-85A30EC2CD35}
12/31/13  02:32:47 -------- DRIVER -------------------------------------
12/31/13  02:32:47 User-friendly name  : nvd3dum.dll
12/31/13  02:32:47 Driver version      : 0x0
12/31/13  02:32:47 =====================================================
12/31/13  02:32:48 ======== GRAPHIC ADAPTER ============================
12/31/13  02:32:48 Device Descr     : NVIDIA GeForce GTX 580
12/31/13  02:32:48 Vendor Id        : 0x10DE
12/31/13  02:32:48 Device Id        : 0x1080
12/31/13  02:32:48 Device SubSysId  : 0x83851043
12/31/13  02:32:48 Device Revision  : 0xA1
12/31/13  02:32:48 Device GUID      : {D7B71E3E-53C0-11CF-F373-85A30EC2CD35}
12/31/13  02:32:48 -------- DRIVER -------------------------------------
12/31/13  02:32:48 User-friendly name  : nvd3dum.dll
12/31/13  02:32:48 Driver version      : 0x0
12/31/13  02:32:48 =====================================================
12/31/13  02:33:26 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  02:33:26 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  02:33:26 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  02:33:28 Error in file ShaderPatcher_DX9.cpp, line 1680.
12/31/13  02:33:28 Error in file ShaderPatcher_DX9.cpp, line 255.
12/31/13  02:33:28 Error in file ShaderPatcher_DX9.cpp, line 256.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 1680.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 255.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 256.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 1680.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 255.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 256.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 1680.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 255.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 256.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 1680.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 255.
12/31/13  02:33:29 Error in file ShaderPatcher_DX9.cpp, line 256.
12/31/13  02:33:29 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  02:33:29 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  02:36:15
12/31/13  03:06:15 Error in file IDirect3DDevice9_wrapper.cpp1680.
12/31/13  03:06:15 Error in file IDirect3DDevice9_wrapper.cpp1680.
12/31/13  03:06:15 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  03:06:15 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  03:06:15 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.
12/31/13  03:06:19
12/31/13  03:06:19 Error in file IDirect3DDevice9_wrapper.cpp, line 4107.



Should anyone think it relevant I can provide all my .ini files ENB files and dxdiag.
QuiteReluctant

Moderator
Registered:
Posts: 927
Reply with quote  #2 
Hey defear,

very comprehensive post, thanks!

You say "
 I finally got it working". Do I understand you correctly: you got it working by replacing v243 with v236? And now HiAlgo does no harm but no good either?

If so - hm, interesting. This is the first report like this. So, when you are "
pressing the downrez buttons", you do not see any change in the framerate? Do you see at least the change in the resolution? 

I think I was testing v221 with HiAlgo, and it looked normal (but actually, I was on lookout for failures, so I might have overlooked what you describe). Do you want to try v221? It is still available.

What I do know is that HiAlgo works well with RCRN, and it used to work well with ENB, but something went wrong, starting with version v0.240

I will wait for your clarification, and then will try to look into this again.
defear

Junior Member
Registered:
Posts: 3
Reply with quote  #3 
I did indeed use ENB v243 prior to installing HiAlgo, and I had to revert to v236 for the game to be playable at all with either of the two toggled on. I should also mention, that simply turning on "Use Effect" for ENB caused the massive frame drops, even though I tried toggling every single checkbox off or turned quality to as low as it goes in all the enb .ini and .fx files.

With ENB v236 there were no major issues of conflict between ENB and HiAlgo, but whenever HiAlgo is enabled and I look/move around I see my fps universally drop from an average of 40 by 5 or more and there is little to no appreciable change in smoothness or stutter-decrease compared to HiAlgo toggled off. If I watch carefully when moving I DO see the downsized resolution, I just get an FPS decrease instead of increase regardless of ENB/RCRN on-off states. Using the manual downrez buttons will also universally decrease my FPS for static frames. I can see the decreased resolution, and 33% seems to provide marginally worse FPS than 50% test mode.

I have now also experimented with turning Vsync off (disabled in drivers and vanilla game, only using the ENB Vsync) as I recall actually getting benefit with it off during my earlier testing, but i could see none now, and the 300+ fps in menus caused far too many visual and mouse bugs. And I feel it is too vital to keep FPS under 60 to avoid Havok physics glitches.

I have now also done an attempt with ENB v221 binaries instead. This time around I could in some cases notice HiAlgo doing its thing properly and giving me some FPS boosts when moving/turning, though it was spotty at best, moving in some places gave me only decreased FPS, and in some places the effect was unnoticeable in either direction. Same held for the manual test buttons, some static scenes gave me an increase, majority a decrease.

The log for the v221 test was pretty much the same as the one I posted before, though only the following two lines appeared a couple of times:

12/31/13  18:22:25vs_2_0
12/31/13  18:22:59Error in file IDirect3DDevice9_wrapper.cpp, line 4107.



I don't know if it might be a case of certain ENB settings that can't handle the downrezzed frames, some of which would be less or non-functional with the earlier verisons. Though I was using the same enb .ini and .fx files for all tests, as I have heavily customized them to an optimal performance/visual compromise for my system.

In short the downsized resolution works, but it almost universally decreases my FPS more compared to HiAlgo off even when moving/looking. Also the "combat" preset for HiAlgo that sets max rez to 50% appears to be non-functional for me. 
Bystander

Avatar / Picture

Junior Member
Registered:
Posts: 16
Reply with quote  #4 
Again, very good post. Thanks! 

It seems, you did a very thorough research. Here are just a few points:

1. "Error in file IDirect3DDevice9_wrapper.cpp, line 4107" is actually not an error [smile]; and "vs_2_0" also OK. So, your log file is fine.
2. About VSYNC - HiAlgoBoost also controls it (there is a flag in HiAlgoBoost.ini). So, it is possible that it affected the results of your VSYNC tests.
3. I have just noticed that both your CPU and GPU are very powerful. It is possible, that your GPU is more powerful than CPU in the sense that it is the CPU that is a bottleneck during the game. In such case HiAlgoBoost would not increase the framerate (because it eases GPU load, while consuming a little bit extra of CPU). In our FAQ, we do mention it.

Sorry that HiAlgoBoost is not helpful for you.
Happy New Year!


defear

Junior Member
Registered:
Posts: 3
Reply with quote  #5 
Thanks for the reply, I did know about the flag in HiAlgoBoost.ini and toggled it appropriately, but now that you mention the part about how HiAlgo works I recall reading it, and it would explain the results I'm seeing.

I might continue to try using it for a while in more normal gameplay, as during my testing I mostly ran around Riverwood so it might just not have been noticeable there.


And Happy New Year to you too!
Previous Topic | Next Topic
Print
Reply

Quick Navigation:

Easily create a Forum Website with Website Toolbox.