Jump to content

erezt

Members
  • Posts

    6
  • Joined

  • Last visited

  1. Thanks Firebird1955 for sharing this. I had the same problem and what solved it was turning the INS Mode Knob all the way clockwise to Gyro, then optionally settings it to any other mode
  2. I play mostly WW2 and it increase the visibility, great! thanks!
  3. Looks good skliff13! Will definitely give it a try
  4. What I've noticed is that these freeze problems are ultimately concern with how much you stress your GPU, I started working in that direction as I noticed that in Medium graphic settings I experience no freeze. Even after upgrading my 970 GTX to 1080Ti (3 monitor setup) I still had lot's of freeze in 2.5 (and Normandy 2.2 beforehand) with High graphic settings. But luckily I got to somehow minimize these freeze significantly this way: * FPS limit: Limit to 45 FPS (Config/graphics.lua maxfps setting), though I might get up to 180fps without this setting in different scenarios, limiting it probably makes the GPU handle pick loads better * Max FOV: Decreased max CameraViewAngleLimits for the relevant module to 140 (Config/View/Server.lua), greater FOV means the GPU has to render more of the surrounding virtual world * NVidia Control Panel: as attached, note the bold ones * DCS graphic settings: as attached, specifically higher values of Preload Radius and Clutter are very encouraging freeze, and I used NVisia's FXAA instead of in-game MSAA and another one that doesn't hurt: after changing graphic settings - delete fxo and metashaders folders (under Saved Games)
  5. I got freeze/crash with Normandy too using 3 monitors and GTX-970, after a long trail-and-error the following graphics setting seems to solve the problem and yet look kind of OK visually (see attachment), what I've noticed is that larger values of the "Clutter/Grass" setting was the most related to Normandy being freeze.
×
×
  • Create New...