TechAngel85

The reason this caught my intention is because the parameter is still in the latest binary.

Oh, you'll still need to download the binary from ENB Dev and install the d3d9.dll and the enbhost.exe files if you didn't do that. Nothing else is needed from the default binary. The rest is provided by Vividian. For want reasons are you running the limiter? With Vsync enabled there's not much use for it. Inspector doesn't really bring much. I was only asking to see your settings to make sure you didn't have some set that would cause the limiter and/or vsync to stop working.

ASUS products will not lead you astray. They are about the only brand I use for motherboards. Future proofing doesn't necessarily mean having the best and most expensive components. Being smart about their interactions is better than having brute strength. I have the ASUS z87-Plus board and it has all the bells and whistles I need. I could have spent $100 more on the board but there was really no point. I also have the Core i5-4670K that is not overclocked. It handles any games that I play without even sweating. This combination will be good for 4-5 years because if I ever need extra juice, I can just overclock the CPU and call it a day. Seeing that this processor has never struggled with anything so far, I don't see any logical reason to have anything faster than it right now for just gaming purposes. The board is also rock solid. So I've spent approximately half of that you're planning on spending on your top choices for the motherboard and processor and I can guarantee that in gaming only scenarios with the same graphics card, you'd have no advantages over my hardware. Proof is in that video I posted. So, your reasoning isn't wrong but is it the most practical for the application? Probably not. A lot of the high-end products on the market are just for enthusiasts and simply add a lot of bells and whistles that most users will never take advantage of. The base features of the ASUS boards you mentioned are just as good as the Z87 boards I linked. You'll want to look for good quality RAM so don't go with some unknown off brand. I have these sticks in my system: https://www.newegg.com/Product/Product.aspx?Item=N82E16820148486 I went with this product for a couple of reason (the sport edition is black): They're low profile just in case I need to install an aftermarket heatsink one day (future proofed that)They're low voltage so they use less power to achieve the same performance.They are a lower CAS latency that normal DDR3 1600 sticks (8-8-8-24 compared to 9-9-9-24)Due to the lower voltage and lower CAS latency they have great overclocking potential according to reviews, if it is needed (mine aren't overclocked...yet).Hopefully that will give you some ideas to think about when looking for system RAM.

Assuming you have a legal copy of the game, let Steam be your ally here. Delete everything but the Data, DirectX10, DoNotFX, Skyrim, and VCRedist folders. If you've installed MO to the root Skyrim directory, be sure you don't delete that folder as well. Then open up Steam and go to your Library. Right click on Skyrim and choose Properties. Click on the Local Files tab and then click the Verify Integrity of Game Cache button. This will reinstall all the necessary files that you just deleted. Once that is done, launch the game from Steam to open up the Launcher. It will do it's initialization and then you can simply close it. That will reinstall the needed registry and ini files so third party apps (like TESVedit) will launch. You should now have a clean root directory. Now install the ENB as you described above. Just copy and paste the files into the root directory. With that VRAM and system RAM your enblocal [MEMORY] settings should be like: ExpandSystemMemoryX64=true ReduceSystemMemoryUsage=true DisableDriverMemoryManager=false DisablePreloadToVRAM=false EnableUnsafeMemoryHacks=false ReservedMemorySizeMb=512 VideoMemorySizeMb=10240 EnableCompression=true AutodetectVideoMemorySize=falseWith just STEP installed and 4GB of VRAM, ENBoost will only use ~1.5gb of system RAM. That is approximately how much my system uses with my 4GB card. With the settings above, you've told it that can use up to ~10GB of system RAM. It will never do this, but those are very stable settings on my system since we have about the same setup. Also be sure to remove EnableVsync from the [WINDOW] section because it's not suppose to be there and you should only have one instance of that parameter in your file. Do these things and let us know if you're issues have been fixed.

Those high-end processors are aimed more towards content creators and not gamers. Very few to no games are going to use 6 to 8 cores. Even modern games use no more than 3 or 4 and when most games "recommend" a quad-core or more CPU, they typically will not use more than 2 or 3 cores because the system itself will need some room to run as well. This video is a couple years old but it's still pretty relevant in terms of the message that 4 cores is enough for gaming and HT rarely matters for a straight up gaming rig. That stuff is really only useful for content creators. Don't let me bust your "enthusiast bubble" though! If you want a hardcore and probably overkill rig, then certainly build one. But I'm with these other guys. Buy a Core i5-4670K @ 3.4GHz and put that saved money towards a good motherboard, RAM or a bigger/better monitor if you're buying one. If you need more power from that CPU in the future, buy aftermarket cooling and overclock it. Personally, I've never overclocked mine and haven't seen any reason to yet.

I think you're going a little overboard there. :: The official recommended specs: A Core i5 like my Core i5-4670K is more than enough to run Far Cry 4 for the CPU.

I've noticed this too and it's rather annoying. It's not how anchors are suppose to work (tons of HTML/XHTML experience here) but you just never know with the wiki. It seems to follow its own set of rules that sometimes make no sense to me.

Before I cause an uproar on the ENB Dev forums, I'll ask for confirmation here... In the 0.198 release thread it states that EnableUnsafeMemoryHacks was removed. I never seen any reference where it was added back in. Can any confirm that is parameter no long works or serves a function?

XCE and Better Males is suppose to have covered that. No More Blocky Faces is suppose to be in included in the XCE package but the files are missing. You posting this just reminded me of that. You can install No More Blocky Faces after XCE.

Okay, guys. I've finished looking through most of the release threads on ENB Dev and have provided reference links to the information I could find. As you will be able to see, it's not very much. This is as expected because Boris is flat out terrible with documentation. He basically developments a feature, says "I've added these parameters", and that is it; leaving it up to everyone else to figure out what the heck all the parameters do. At this point, I'm going to refocus again and go back to taking some compare shots and making sure the values for the parameters are accurate. I'll be using JawZ's ELEP to do the compares.

Okay... First, you have a lot of stuff in your root folder. I'm going to assume that all that unknown stuff is from the ENB Manager. Do you switch between ENB Presets? If not, I'd drop the Manager and just do it manually. Second, your ReservedMemorySizeMb is far too high! Half of that at around 512 should be good. What are your system specs so I can figure the right values? (VRAM and RAM) EnableVSync should not be under [WINDOW]. It should only be under [ENGINE]. EnableSubPixelAA can be turned off if you're using SMAA. I only use EdgeAA and SMAA on a medium preset and never see any jaggies anywhere.I still need a pic of your Nvidia Inspector settings (asusming that you use that) and your SkyrimPrefs.ini file in spoiler tags. Also, is there an enblocal.ini or enbseries.ini file in your enbseries folder?

Can you shot some screen shots for us? One of your Inspector settings (this might take two)One of your Skyrim root directory.Copy and Paste your INIs hidden with spoiler tags (SkyrimPrefs.ini, enblocal.ini, enbseries.ini) [spoiler] text text text [/spoiler]

Nvidia will run exactly as it's been described in the post above. There really isn't any need for multiple people testing. It's graphic card specific. The only other things that might change it would be drivers and the monitors refresh rate. We all know that Boris caters to Nvidia and only fixes AMD bugs when necessary. From Z's link above...Boris's quote (users confirmed later in the thread that the issues which brought this up was a driver issue...which is again, why I say to never use Beta drivers!): If I'm reading that correctly, from the first sentence...if ENB vsync is turned off, then only the driver version of it will work. From the second sentence....if ENB vsync is enabled, then so must be iPresentInterval in the SkyrimPrefs.ini for it to actually work correctly. Currently I have two setups... STEP:Extended Profile // iPresentInterval =0, ENB vsync enabled, Drivers set to application controlled. Personal Profile // iPresentInterval =1, ENB vsync enabled, Drivers set to application controlled. My result here are the same as #4 and #5 above. It would seem that iPresentInterval doesn't need to be enabled in order for the ENB vsync to work. Boris might have changed something since v0.231. In any case, when it comes straight from Boris himself we should probably be listening and follow his advice to keep iPresentInterval enabled for both ENB and ENBoost users.

Looks like Hodilton has already made a video of your preset, Jafin:

Thanks for this! I also agree with you opinion I highlighted above. Many users report issues when iPresentInterval is turned off. The havok system (physics) will go haywire with this off usually due to really high FPS. With that turned off and no vysnc, one would have to enable a frame rate limiter to fix those issues. However, many report that certain aspects of the game also rely on iPresentInterval to always be enabled. Some of these reported aspect include time-of-days events, NPC paths and events, and certain quests. It doesn't hurt to leave it enable so I personally recommend it always be enabled just to thwart any potential issues, if nothing else.

STEP is 1k for exteriors and 2k for interiors. Unless you're playing on a really high res, that should be good. I wouldn't push it too far with just 2GB of VRAM. ENBoost will help and take on the extra load; however, it's still slower than VRAM and some stuttering is always possible.

Yeah, you guys just take it a section at a time. Don't think about doing the whole Guide at once! I have it sectioned off right now with the header tabs for that reason. It's easier to work with the header tabs to focus in on a specific section and then later I'll covert it to a TOC Guide since that is how the Admin would like it done. That is nothing you guys need to think or worry about. The Guide will be complete for that is done.

Thanks for the additions guys! @Aiyen, The only thing you need to do different from what you're doing is to add 4 tildes to the end of your edits ( ~~~~ ) instead of "by Aiyen". The tildes add in a system generated signature and time stamp like you see at the end of JawZ's edits. @All, If you need to add a link you can do so by using the following: Code: [URLhere LinkTextHere] Example: [http://wiki.step-project.com/Guide:ENBseries_INI#tab=Depth_of_Field DoF Section]Result: DoF Section Anytime you see this, just ignore it. I've been removing it as I find it. That text is left over from cutting and pasting from what we'd done on the ENB Guide (most of it was hidden on the ENB Guide so only editors would have known it was even there).

The chat was mainly created for the purpose of getting everyone together to talk about the shaders and .fx file to get a standardization down. Most things should be recorded here in this forum. I doubt at this point it's going to be used. @Confidence Anything is helpful! If something isn't exactly right then it can be corrected later. Multiple authors can add to the same comment. I'll simply combine all input later into a cohesive description. @All I've been adding to the descriptions off and on all day long. They've been randomly added here and there as I've come across them on the forums. Accompanying each is the reference link to the info on the ENB Dev forums. Most of this info has came straight from Boris himself so I'm fairly confident that it's accurate, but if anyone sees something that needs to be added to the parameter, just add in the addition as you normally would.

Your previous edits were saved okay, so not sure what you're trying to do that you're getting a blank screen now. Make sure you're still logged in. The wiki tends to log users out if you don't tell it to keep you logged in for the 180 days or whatever the limit is.

Congrats and job well done. The pictures look awesome! I'm sure you'll continue to work on your preset but I'm also glad you'll be putting some time in on this project as well. I've almost given up on it seeing that really nothing has been done to the Guide in while a while and some of the authors that committed to help have all but disappeared. @All authors and contributing members, I'll be removing anyone from the special credits and thank you section that I don't see any work from. I made that point early on and so far only 2 or 3 out of 8 have made any significant contribution to this project. I understand that everyone has other projects, mods, presets, and real life on the side. I'm one of those; however, even just a couple minutes every few days from everyone that committed would suffice to get this project rolling again! I have broken down to searching every page of the ENB release threads on the ENB Dev forums just to get something done and perhaps make it easier to review. I've added linked referenced where I find useful information. If this is how I have to finish this project, that is what I'll do. My resolve to having the most complete reference Guide for enbseries.ini has not wavered. If you feel you can no longer be a part of this project, please let me know. EDIT: Jafin, I've made you a Mod Author on the forums.

Vsync is more of a case by case scenario if you ask me. For instance, I have to be very careful about vsync and frame rate limiters with my monitor. It's an IPS panel and it does not agree with some of the settings. I mainly leave all that on default and I'm good to go. iPresentInterval should be left on though. Most tend to agree that the game engine and certain aspects of the game need it. We're currently telling users to turn it off and use vsync in ENBoost. Both can be enabled without issue and leaving iPresentInterval turned on could negate some future issues.

It really should be left on in the INI at all times.

Just wait. He'll stop in within a day or so.

That is why we're holding off on taking the mods out of STEP for now. Waiting to see how this plays out.