Jump to content

silverdevil

Members
  • Posts

    3927
  • Joined

  • Last visited

Everything posted by silverdevil

  1. the error in the .OLD file has a similar error to one solved in this thread. though the user is crashing and it is not screen anomalies. i am thinking there is some hope in "restore defaults" in nvidia panel tip.
  2. definitely not this or the forum would be blowing up. maybe something amiss with the mission. try a test by changing the frequencies in the ME. PS: i missed you said multiple missions. can you share missions? i have A-10CII and do not have "Shooting Range"
  3. what AV do you have? anything that does not have exclusions would be unusual.
  4. @lwalter hello again. i realized yesterday in the F-4 that when i pressed the M key, the F-4 manual appeared. i did not see any difference in performance. i did not check memory usage either though i have 128 GB on my system. The manual in the folder is 75 MB.
  5. the controls are in the save games folder. log book is also in the saved games folder \Saved Games\DCS.openbeta\MissionEditor you can also copy this folder over from the .BAK
  6. roger that though, normally because of how vector based threats work, smaller files one at a time are scanned. when dcs loads, it checks all of the files which is literally hundreds of thousands. depending on your hardware, this process can take time. one benefit i found was adding exclusions to AV shaved off 90 seconds from load time (down to 30 seconds).
  7. logbook and configurations for controls are in saved games\dcs. can you share your dcs.log? also a slow repair essentially performs the action of a fresh install. also another idea to test is rename the saved games\dcs folder to dcs.bak. run dcs, a new folder with fresh settings will be made. then copy the input folder \Saved Games\DCS.openbeta\config\Input over from the DCS.BAK.
  8. i have Nvidia but the premise is the same. some settings have to be controlled by DCS and sometimes the setting in the graphics driver are set wrong. here are my settings pages and maybe you can decipher which are relevant in the AMD drivers. null null
  9. agreed. i personally pre-purchased Phantom Dec 23, 2023 for $59. so everyone had at least 5 months to get $20 off.
  10. hello. usually AA settings can be the cause for jaggies. maybe that is set wrong in driver in game? another idea is what are your cockpit textures set at? mine are set to 1024.
  11. i think you should separate the kneeboards into smaller chunks. i personally only have a max of 10 or so. it forces me to get the basics, add a little muscle memory, and use the kneeboards for reminders. eventually i do not need the kneeboards. sorry but i think you have reached the limits of what you are trying to do.
  12. i find a little improvement when i reply the track with all my controllers disconnected.
  13. @lwalter i do not think a track is going to help since the kneeboard is located on your computer. have tried to load the same mission without the kneeboard and with the kneeboard to compare the memory usage. it might be just me but 240 pages for a kneeboard seems excessive.
  14. hello. i do not see the same artifacts in my system what is your video card? here are videos of my flight in your track. https://www.pcwiseman.com/downloads_files/DCS1.mp4 https://www.pcwiseman.com/downloads_files/DCS2.mp4
  15. many folks are seeing m2000 files being flagged. if you are comfortable with it, add exclusions for the folders in your AV program. this is what do in defender null
  16. have you deleted / emptied the shader folders found in saved games\dcs? first time compiling new shaders takes some time. can you share your DCS.LOG?
  17. hello. i see other posts about you error may have something to do with Openkneeboard (or some other mod). have you disabled mods? take a look at this post too.
  18. never knew this in my time in world of nvidia. either way. good luck figuring out your issue.
  19. where did you get that idea? i know for my case i have never used anything but the latest nvidia game driver. i do not have any issues.
  20. hello. it is impossible to see trouble via screen shot. best to share the mission and / or track so we can run it to see if it happens on our systems.
  21. hello. you should be using game ready driver i think.
  22. hello. can you share a track? that way i can see what happens on my pc.
  23. those people drive like maniacs. lol. seriously. can you share a track? that way i can see what happens on my pc.
×
×
  • Create New...