FoxTwo

Has anyone noticed that switching between cat 1 and cat 3 interrupts your alignment? Also the aircraft pitches down after putting the gear up during takeoff in cat 3 I didn't notice that in cat 1.

Do communication events export? The tankers always call contact when there's a hookup.

https://forums.eagle.ru/showpost.php?p=4440440&postcount=43 This is all we know so far.

Yeah I've noticed the same thing.

You may be noticing OLED smear. Not a lot you're going to be able to do about that.

Is the A2A basket/boom connect event exported by DCS?

https://www.mudspike.com/wp-content/uploads/guides/DCS%20AV-8B%20Harrier%20Guide.pdf Page 38

Guess it's easier to combine threads than to make a statement as to whether or not this is intended...

Was on a server that uses the current date/time for a mission and it read MM/DD/YY 7/45/20 I created my own mission set to 8/8/2020 and this is what it displayed Then I hopped on growlingsidewinder's server and it showed 41st day of December? This a bug? Seems like a bug.

Try this https://forums.eagle.ru/showthread.php?t=281666 Currently the game renders like a very overexposed camera, this tones it down to something a bit more reasonable.

More data! https://forums.eagle.ru/showpost.php?p=4446178&postcount=22

It does, and it's better. But it's frustrating and it shouldn't be necessary. Even watching the latest video from Growling Sidewinder you can see how the world is just incredibly overexposed outside of the cockpit. The HUD disappears completely near the horizon.

There's a significant improvement here. There's still some difficulty seeing hud values around the horizon line but overall much more tolerable in VR at 2.0 gamma.

Game doesn't seem too bright, game is too bright. Particularly the sun flare effect, but in general daytime lighting is way blown out. At gamma of 2.2 the night looks great and you can see everything in the cockpit but the clouds and sky disappear into a whitewash of nothingness. On the flipside night looks great? I dunno but the whole thing is a bit of a mess. An example. Gamma set to 1 (lowest) world looks fantastic. Clouds are defined, terrain pops, shadows are shadowy, you can actually read the HUD against the sky, but the cockpit may in fact be painted in vantablack... With gamma set to 2.2, absolutely everything in the world is completely blown out, contrast goes right out the window and HUD is borderline unreadable, but all the instruments and even the dark corners of the cockpit are visible, instrument lighting actually works, MFDs are readable and their colors pop, etc... And just for good measure, the same cockpit in the same mission @ 2.2 gamma in 2.5.5 release (just before the lighting change) Just look at the histograms for the two images 2.5.5 @ 2.2 gamma vs 2.5.6 @ 2.2 gamma

At the expense of blowing out and over exposing the daytime sadly.

Since 2.5.6 bumped up the brightness/exposure of the outside world to improve night lighting and visibility (which is a definite plus for night operations) the daytime is completely blown out at the appropriate gamma value for normal cockpit brightness (~2.0-2.2). If you dial back the gamma to make the daytime outside world reasonable (~1.5-1.8), the cockpit becomes a black hole, details get lost and blacks are completely crushed. The whole thing is a mess frankly. For a gain of somewhat better night visibility (admittedly impressive tbh) we've lost cockpit interior backlighting, flood lighting, HUD lighting, DDI/MFDs, moving maps, warning lights, KC-135 pilot director lights, the list goes on... And it's not like 2.5.6 is openbeta anymore, this version of the lighting system is currently 'stable' so everyone gets to suffer equally I guess but it's incredibly disappointing. I know there have been some efforts in improving bits of lighting that has been broken in some of the modules, but overall it seems like one global lighting change has literally broken every single aircraft or AI unit in some way.

DCS has built in control maps for cougar MFDs 1 and 2 to left and right DDIs respectively. If you have a 3rd, you'll have to map that manually. You don't need target or any 3rd party software. The thrustmaster MFD drivers can be handy to set one to left or right and change the lights.

Thoughts? Comments? Uncommanded rolling without pylons (or with only some pylons) seems like it shouldn't be happening. The F-16 doesn't have this issue.

Looks like your nvidia dx10 driver is crashing. Try removing any overclocks and/or downgrading your driver to an earlier version.

This was reported earlier and moved to a general DCS bug, because it affects all modules with GI enabled.

F-18 rolls right without pylons Not sure if this is a bug but I'm putting it here as I did some testing based on another post in the general F-18 forum... The F-18 behaves differently based on how many pylons are on the aircraft. My limited testing has it doing this: No pylons - rolls right Center pylon only - rolls right Inner pylons only - rolls left Outer pylons only - rolls right Inner and outer pylons (no center) - small left roll All pylons - level flight There's a trackfile in the original post that shows the roll effect with no pylons. https://forums.eagle.ru/showpost.php?p=4436329&postcount=12

So I did some additional testing... this is most confusing. No pylons - roll right Center pylon only - roll right Inner pylons only - roll left (wtf?) Outer pylons only - roll right Inner and outer pylons (no center) - a very, very minute left roll All pylons - level flight Realistically I don't think anyone aside from a blue angels pilot is going to be able to tell you if the actual F-18 rolls when there are no pylons on the plane.

I took control of your track at two points and flew the mission. The first I took control at the beginning and did not contact the ground crew to remove the pylons from the aircraft. After takeoff and gaining some altitude, there is no noticeable right roll effect. The aircraft flies true. I then replayed your track and took control after you'd taken off, and you had contacted the ground crew to remove the pylons. Without pylons and a completely clean aircraft, there is a very slight right roll. You can counter it with a single left trim click but it's not entirely neutral as you then get a much more mild left roll. Conclusion: A clean F-18 (without pylons) has a slight right roll. An F-18 with pylons does not. I don't know if this is accurately modeled only ED can answer that.

I do something similar with mine starting simshaker, srs and loading a VR or pancake config profile. #popup $wshell = New-Object -ComObject Wscript.Shell $answer = $wshell.Popup("Yes = Enable VR, No = Disable VR, Cancel = Quit",0,"DCS Launch Script",32+3) #program paths $ssa_appref = "$env:userprofile\AppData\Roaming\Microsoft\Windows\Start Menu\Programs\Dream Sim Team\SimShaker\Simshaker for Aviators.appref-ms" $dcs_exe = "D:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin\DCS.exe" $srs_exe = "$env:ProgramFiles\DCS-SimpleRadio-Standalone\SR-ClientRadio.exe" #option paths $options = "$env:userprofile\Saved Games\DCS.openbeta\Config\options.lua" $vr_options = "$env:userprofile\Saved Games\DCS.openbeta\Config\vr-options.lua" $novr_options = "$env:userprofile\Saved Games\DCS.openbeta\Config\novr-options.lua" #processes $SimShaker = Get-Process "SimShaker for Aviators" -ErrorAction SilentlyContinue $srs = Get-Process "SR-ClientRadio" -ErrorAction SilentlyContinue #Cleanup multiplayer tracks older than 7 days Get-ChildItem "$env:userprofile\Saved Games\DCS.openbeta\Tracks\Multiplayer\" | Where-Object { $_.LastWriteTime -lt (Get-Date).AddDays(-7) } | Remove-Item #enable vr startup, menu choice Yes if($answer -eq 6){ if (Test-Path $vr_options){#verify that VR options file exists Copy-Item $vr_options -Destination $options #copy VR options to game options } if (!$SimShaker){#checks to see if simshaker is running, if it's not then start it Start-Process $ssa_appref } if (!$srs){#checks to see if SRS is running, if it's not then start it Start-Process $srs_exe -WorkingDirectory "C:\Program Files\DCS-SimpleRadio-Standalone\" } Start-Sleep -Seconds 2 #necessary for simshaker to settle down so the DCS hooks work Start-Process $dcs_exe -NoNewWindow -Wait #start DCS Wait-Process -name SimShakerSoundModule #wait for simshaker to close out gracefully Get-Process "SR-ClientRadio" -ErrorAction SilentlyContinue | % { $_.CloseMainWindow() | Out-Null } #close SRS Get-Process "SimShaker for Aviators" -ErrorAction SilentlyContinue | Stop-Process -PassThru #fully close simshaker resident loader Copy-Item $options -Destination $vr_options #save any changes to VR options } #disable vr startup, menu choice No elseif($answer -eq 7){ if (Test-Path $novr_options){#verify that no-VR options file exists Copy-Item $novr_options -Destination $options #copy no-VR options to game options } if (!$SimShaker){#checks to see if simshaker is running, if it's not then start it Start-Process $ssa_appref } if (!$srs){#checks to see if SRS is running, if it's not then start it Start-Process $srs_exe -WorkingDirectory "C:\Program Files\DCS-SimpleRadio-Standalone\" } Start-Sleep -Seconds 2 #necessary for simshaker to settle down so the DCS hooks work Start-Process $dcs_exe -NoNewWindow -Wait #start DCS Wait-Process -name SimShakerSoundModule #wait for DCS and simshaker to close out gracefully Get-Process "SR-ClientRadio" -ErrorAction SilentlyContinue | % { $_.CloseMainWindow() | Out-Null } #close SRS Get-Process "SimShaker for Aviators" -ErrorAction SilentlyContinue | Stop-Process -PassThru #fully close simshaker resident loader Copy-Item $options -Destination $novr_options #save any changes to no-VR options } #menu choice Cancel else{ exit }

https://www.amazon.com/80-20-Inc-Standard-Fastener/dp/B07VN6Q4HL/ These?