SnapRoll

After losing lock in TWS when the radar gimbal is nearing its maximum travel limit, radar elevation is limited thereafter. In my track I switch between RWS and TWS after losing lock. In RWS I can still move the radar elevation to the very top, in TWS the upper quarter of the range is no more accessible. TWS_elevation_limited.trk

Have you tried what I described in the third post? After mission start --> no reflections from behind the seat (correct) Remove Pilot Seat --> no reflections from behind the seat (wrong) Change position to Gunner (while Pilot Seat is still removed) Change position back to Pilot --> reflections from behind the seat are visible (correct) Make Pilot Seat visible --> reflections from behind the seat are visible (wrong) It should add/remove those reflections as you make the Pilot Seat disappear and visible again, not after you changed to the gunner and back.

After restarting the mission these reflections were gone and I had troubles reproducing them. They appear when you remove the seat, change to the gunner seat and come back to the pilot. If you want to get rid of them, make the seat visible again, change to the gunner and back and all is fine. So basically, they are not changing while you are sitting in the cockpit and you make the seat disappear and visible again. But something is off with these reflections anyway, those panels should not be reflected on the map in any case.

Ok, I did not see it properly before, as I am just using a POV hat and no TrackIR. When moving the head position up and down and left and right it is all visible on the dials. It comes definitely from back there. The yellow pipe should for sure not be visible. There is definitely something odd with these background reflections, as there are as example these panels visible on the map that don’t even are in the line of sight of it.

There are some strange reflections on the dashboard. One is that yellow line and the other the moving blue part of the Doppler Indicator. A possible source for this might be in the back of the seat. I suppose the yellow line should not be visible, the blue part might be even possible. It still looks weird, because it is moving when you turn your head.

As in the title, I suppose this should be bound to the switches volume slider.

Hi Reflected Some issues in Mission 3. flown with current OB version 2.7.3.8494 (June 30). There is a View.lua included in the mission file which messed up my views. I was able to remove the config folder inside the mission file and all was good. When the bombers spawn, two of them crash into each other immediately (without units removed) --> 1.jpg There was real carnage when the bombers let loose their bombs. --> 2.jpg and 3.jpg. It seems two bombers always fly on top of each other. I also had troubles keeping up with the others during the initial climb to altitude during this and mission-2. With 3000rpm and almost always full power I was kind of keeping pace, but it is a very steep climb. I haven’t flown the P-51 for a while, so I am not sure if it used to climb faster. It seems other users have the same issue. Cheers, SnapRoll

Hi maks While I can’t give you definite a solution, at least I can give you some hope. I sat in the exact same boat like you when I attached my 3x 1024x768 MFD screens to my 4k system. At first there was the realization that full-screen mode will not work any longer and that performance was terrible. Through testing some different settings, I am now at a stage where I have better performance than ever before, even with my three additional screens. Also FPS difference between full-screen mode and full-screen borderless is marginal. The main thing for me was changing the vsync option from in-game to the NIVIA control panel one. But generally speaking, you have to tune your system and find the settings that work best for you. Unfortunately, every system is a bit different and while some settings work for one guy, the do not work for another. Here are my general recommendations that work for me: DCS Settings: Vsync: uncheck Terrain Object Shadows: Flat MSAA: Off SSAA: Off SSLR: Off SSAO: Off PC settings: Processor power management --> Minimum processor state: 100% Graphics settings --> Hardware-accelerated GPU scheduling: On Game Mode: Off Game Bar: Off Enable MSI interrupt mode for grafics card NVIDIA settings: Monitor Technology: G-SYNC Compatible (use this if your monitor is FreeSync or G-Sync compatible) If G-SYNC Compatible then --> Set up G-SYNC! Power management mode: Prefer maximum performance Texture filtering – Negative LOD bias: Clamp Texture filtering – Quality: Hight performance Vertiacl sync: On Antialiasing – FXAA: On (I use this option instead of any in-game AA, it is very efficient) You have to fiddle around with all these settings and maybe others to find what works for you. Cheers, SnapRoll

I was watching Blade refueling and then suddenly he went berserk, dove down into the see and started playing ping-pong ball. No more scripts triggered from then on, but I got 100% once landed on the boat. OpenBeta 2.7.0.5659

I always used LCTL PAUSE, but with today's change (2.7.0.5659) RCTL PAUSE was assigned and I had to reassign it to LCTL PAUSE.

Hi Mr_sukebe. I’ve been running Windows 10 for quite some time with memory compression as well as the page file disabled. I also had the same observation with my 64GB system and thought I might as well save those CPU cycles. Unfortunately, I’ve never really tested it, but my soon to be 5 years old system @4k runs mostly without stuttering. I suppose every little helps.

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. I also get problems with newer drivers. I am at Nvidia driver 451.67 with a 1080 card and it runs very smooth @4k. I did not have any luck with newer drivers. You probably have to find the right combination of all of the above that works for your setup. Cheers

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.

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

I hope you are aware that it is not Friday today They just released a few campaigns on Wednesday and hence this news...

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 yours and reach you much earlier. Only a tacview analysis will really tell what happened.

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.

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.

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.

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.

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.

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 an update. Do not use Notepad, use WordPad.

Play with these values and see what works for you:

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 export. These files get overwritten with every update or DCS-repair but they get copied to the _backup.00X folder in the DCS root.

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 works best for you. I am at 451.67. I also sometimes need to Alt-Tab a few times until it catches FreeSync (with Nvidia). Not sure if this is relevant in VR.