Take a look and get back into the capital wasteland.
Some geospatial data on this website is provided by geonames. All trademarks are property of their respective owners in the US and other countries. Note: This is ONLY to be used to report spam, advertising, and problematic harassment, fighting, or rude posts.Īll rights reserved. Then have you got copy either the wrapperversion or the injector version. It's just two unpack and copy operations, the only trick is to know that you put them in the main folder, not data.ĭo you download the. What that page suggests in a roundabout way. If you link the ENB you're using, I might further assist you. Afaik, the ENB presets mostly just come with the needed configuration files, most of the time you still have to manually download the required ENB files. I searched on Google, YT but still no solutions Can u help me? Showing 1 - 5 of 5 comments. So i just downloaded Oxide ENB and i dunno how to install it, or how to get it work. Maybe some others will report in with more conclusive results.Home Discussions Workshop Market Broadcasts. I am curious, where does the 1500MB get stored when EnableUnsafeMemoryHacks=true if not in enbhost.exe and why is it unsafe? Also, regardless of the USMH setting or ENB version, the VRAM usage for the save game I am testing with is always at 2400MB when the save game loads and doesn't change much while wandering the local area. When ReduceSystemMemoryUsage=false, loading the save game freezes when the game's exe is around 2200Mb with both versions. When USMH=false, enbhost.exe is using around 1500MB. Also with USMH=true the memory usage of the game is the same as when it's false around 750MB. When there is lag, after the freeze, the values are sometimes zero and sometimes low in the 100 Mbytes per second range.Įither way, USMH(UnsafeMemoryHacks) still works and seems to perform with +5 FPS on average. Sometimes the numbers jump and there is no lag. However, it doesn't always correspond with the lag. With the profiling, I can see the Deleted, Allocated, and Created Textures profiling numbers occasionally jump from zero to values in the 100s for Created Textures and up to 5000 Mbytes per sec for Deleted and Allocated.
With EnableUnsafeMemoryHacks=false the lag is present in both versions.
Could this be attributed to EnableCompression=false working as intended now? v0278 might feel slightly smoother or more consistent FPS. First, the FPS with EnableUnsafeMemoryHacks=true was about the same between v0267 and v0278. If I want to test correctly, I should really take my own advice and test on a totally vanilla install.īut for comparison sake with v0267.
0 kommentar(er)
