Jump to content

SnapRoll

Members
  • Content Count

    110
  • Joined

  • Last visited

About SnapRoll

  • Rank
    Member

Personal Information

  • Flight Simulators
    DCS

Recent Profile Visitors

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

  1. Hi there I only have a 60Hz main screen but running it with G-Sync on a non officially compatible Freesync screen, plus 3 additional MFD screens... so I am not sure if I am of any help, but... If I were you I would look on the Windows/driver side. Keep the in game vsync off and play with vsync and g-sync/freesync options in the display driver. Also, put alt-enter into consideration. There were some driver levels where I needed to alt-enter a few times until g-sync would catch. Hardware-accelerated GPU scheduling is another thing that could interfere.
  2. They mean F10 in the comms menu. Press the "COMM Push to talk" button, and then you get the comms menu in the top right of your screen.
  3. Hi, Your resolution seems low, my MFD cut out is 718x718, but I think you should be able to get it working. Play around with these settings, they also affect the MFDs. My MFDs were also blurry, including the HUD on the 4k monitor. Maybe you can find a setting that works for you in every aircraft. Here you can see how it looks in my setup: Cheers
  4. I hope you are aware that it is not Friday today They just released a few campaigns on Wednesday and hence this news...
  5. I think you got your answer here. While you are somewhat flying toward your opponents missile, he is more or less flying away. There is two things that make a 120 go active, either the distance to target reached a certain distance, or when the supporting aircraft looses lock on the target. It can happen that your opponent looses lock because he is defending. Also, when your opponent is defending and going to a lower altitude, your missile is also going lower and will be slowed down faster than his. If you stay at your 37'000, his missile will inevitably be faster that you
  6. I do not know what DCS BIOS can do and how easy it is to handle but I am not sure if this is a bit of an overkill for what you trying to achieve. If it is only about a simple button box and you have no programming experience, then you might be better off with MMJOY or FreeJoy. Check this out: MMJOY: https://github.com/MMjoy/mmjoy_en/wiki https://sites.google.com/site/mmjoyproject/fajly-dla-skacivania FreeJoy: https://github.com/FreeJoy-Team/FreeJoy The needed boards you can get very cheap from AliExpress.
  7. The most likely cause is switch bouncing, which is normal for mechanical switches. I do not know DCS BIOS but it is more then likely offering a delay function whereas it does not accept additional "button presses" for a certain amount of time. Set it to 50ms or something and you will be fine.
  8. I suppose you've already tried loading the default BIOS settings and saving it, right? Also, is the CMOS battery still ok? Does it show the right time when you go into the BIOS? They would be different symptoms when it was that of course, but still worth checking.
  9. Have you tried booting without any USB devices attached? I have a similar issue when my Warthog Throttle is attached while booting. It would freeze during the UEFI load 2 out of 5 times, even when it is connected to a external powered USB hub.
  10. From the newsletter: Our Winter Sale 2020 has started and will run until the 11th of January. On Steam, the sale will start on the 22nd of December and end on the 5th of January. We are pleased to announce an additional ‘Free to Play’ period starting on the 22nd of December, giving you access to all aircraft and terrains from our e-Shop and Steam for two weeks. The modules will just appear in the module manager for download when you start DCS sometime tomorrow. There is no need to do anything on the webpage.
  11. Press your windows key, write “wordpad”, right click on the appearing “WordPad” icon, select “Run as administrator”, answer the security question with “yes”, open/edit/save the file through this WordPad now. After saving, you have to restart DCS. Do not be afraid to make mistakes, you can always run a DCS repair to revert back to the original file version. Be aware that every update or DCS repair, will revert edited files to their original version. Also, new updates sometimes bring new versions of these files, so do not just blindly copy the old file back after a
  12. Play with these values and see what works for you:
  13. I've put these lines at the bottom of file: Mods\aircraft\F-16C\Cockpit\Scripts\EWS\RWR\indicator\RWR_ALR56_init.lua --at the bottom dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_RWR") For the DED: Mods\aircraft\F-16C\Cockpit\Scripts\Displays\DED\indicator\DED_init.lua --at the bottom dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") try_find_assigned_viewport("F16_DED") Then you can use those two view port names as all the others. The rings are not visible in this e
  14. I am running 4k, not VR, but you could try disabling Turbo Boost and see if that helps. I had similar problems when that was enabled. Disable it in the TurboBoost Application, which you can normally find in the Task Tray when it is running, not in the Bios. Also activate the “High performance” Power Plan. (Minimum processor state = 100%) Check if enable/disable Win10 Game Mode or enable/disable Hardware-accelerated GPU scheduling makes any difference. Trying different graphics drivers might also help. Start with the latest and then work your way back to older ones until you find one that
  15. Here my setup, built around a VPC Desk Mount. Will probably paint it at some point…
×
×
  • Create New...