Jump to content

Sherlockzor

Members
  • Posts

    7
  • Joined

  • Last visited

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I do not use mods, most I did was update the missionscripting.lua to enable persistence when using foothold. this has been reset during the repair anyway. just to recap: - I removed the config.lua - I ran the slow repair The result is the same. I included the newly generated log file. Maybe important to add, the external module is rendered completely and immediatly. it's only in the f1 view where the issue occurs and the fact I can not use any aircraft inputs. imgur album for screenshots: https://imgur.com/a/Ml4SUho dcs.log
  2. I have waited up to 5 minutes to be sure. The pagefile is automatically managed atm.
  3. Hey, I attached the logs as for specs i7 8600k (not overclocked) GTX 1070 32 GB of ddr4 RAM DCS is installed on a 500GB NVME (Samsung 970 EVO Plus) dcs.log
  4. sorry for the double post but, full repair also did not help
  5. Hey guys, Removing FXO and metashaders did not resolve the issue sadly.
  6. When trying to use the Apache module today I noticed the cockpit was not rendering and none of my stick or keyboard inputs were working. The only thing working were my headtracker inputs. what I tried so far: - reinstalling module - dcs repair - unplugging the headtracker - try different missions in both sp and mp Any more tips are welcome
×
×
  • Create New...