Jump to content

Recommended Posts

Posted

So I was surprised to have the cache run for over an hr. before the first crash, at 671,xxx entries.

the second crash however occurred at 674,495.  And the third at 676,995.  After that it ran to completion.  Folder is 1.57GB.  <--Does that seem small? 

I noticed that whatever 3D object that was displayed would keep changing, shiny then dull, part shiny part not.  (Hope that's not indicative of a problem) And the audio kept flipping through various small sound files. Total time hmmm not sure, around 1.5 hrs.  (I miss my desktop)

Anyway, just some feedback.

  • Like 1
Posted
12 hours ago, Silverpanther34 said:

So I was surprised to have the cache run for over an hr. before the first crash, at 671,xxx entries.

the second crash however occurred at 674,495.  And the third at 676,995.  After that it ran to completion.  Folder is 1.57GB.  <--Does that seem small? 

I noticed that whatever 3D object that was displayed would keep changing, shiny then dull, part shiny part not.  (Hope that's not indicative of a problem) And the audio kept flipping through various small sound files. Total time hmmm not sure, around 1.5 hrs.  (I miss my desktop)

Anyway, just some feedback.

The display and sound issues during cache generation is normal. Crashing during the process isn't `normal` but it is common. I assume you pasted the line to ignore worldspaces (single line with quotes). Graphics drivers and processes can also inflate the time it takes to create the cache, particularly if using AMD. Before generating the cache, you can use Taskmanager to "end task" for any processes related to your video driver software (processes beginning with `AMD` or `NVIDIA`. This doesn't affect your video drivers, and those processes will come back after a reboot. Also disable ENB while generating the grass cache by moving or renaming `d3d11.dll` and `d3dcompiler_46e.dll` in the game directory to speed up generation.

Posted (edited)

I think the speed was more dependent on my laptop specs than anything else.  Also, the next time I have to do this it will be on my desktop which is leaps and bound more powerful.

I don't have the headroom for ENB.  I just did grass, Terrain, Occlusion, and Tree.  My average FPS during benchmark was 117.  80 in the rift. Good enough for me.  My monitor is 120. On the laptop.  I did have to go with BethiniPie Medium preset, and Upscale 0.75, and grass density 65 to get there.

EDIT: Embarrassing but a suggestion... Just above Texgen guide maybe place another reminder to Disable Temp file and reenable World map.  I did do the disable but forgot to reenable the map, Only realized after LOD gen.   Had to redo them over.   Might be helpful for people who were dropped on their heads as a baby, a lot.

Edited by Silverpanther34
  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Guidelines, Privacy Policy, and Terms of Use.