FoxTwo

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?

Mine arrived today. YMMV of course but for me this was exactly what I needed to get the throttle where I wanted it in relation to my chair position and my desk. The winwing mount wouldn't go forward OR high enough for me. The monstertech mount doesn't allow for a lot of horizontal adjustment but if all you need is up/down then it's probably going to work well for you. It's also has significantly less flex. I was able to get rid of the books I had stacked under the throttle for support. Not a cheap solution but for me it was worth it.

So I played around with this a bit. I started a mission and climbed to 50,000 feet with oxygen completely off and OBOGS disabled. Cockpit pressure gauge indicated approximately 18,000ft. This is equivalent to the extreme zone for mountain medicine. Not a great place to be and you're going to have a bad time but you don't start getting into the loss of vision and consciousness until the death zone at 26,000ft, which would probably be like around... 60-65,000ft? Above the Armstrong Limit anyway, at which you'd be required to wear a pressure suit. Just for giggles I popped the canopy and started getting tunnel vision as expected. Turning the oxygen and OBOGS system on had no effect which at that altitude probably makes sense. In short, you're probably not having a great time with the oxygen off at altitude but I don't know how you model a headache in DCS.

Really? That contradicts the reports of the failed OBOGS causing hypoxia and possibly contributing to pilot deaths. https://www.stripes.com/news/navy-4-f-a-18-pilot-deaths-could-be-tied-to-oxygen-system-failures-1.473811 At the very least, leaving the OBOGS disabled should cause hypoxia at altitude even if the cabin remains pressurized

No? Why would winwing advertise a monstertech product. I had this userid long before they setup their US marketing company.

Anyone received theirs yet? Just wondering how stable it is compared to the winwing mount.

It's not. That's windows scheduler doing its job.

Also experiencing this. Flashes of shadows and then not.

I've been having a problem in the spitfire where it's not loading my controller mapping if I start a mission without first going into control settings on the main menu. Doesn't happen every time but happens enough that it's a problem. So what ends up happening is it only loads the default mapping, which has axes bound to multiple input devices and tends to just make a mess of trying to control it.

Clara = report to LSO can't see the ball Flight kiss off = tell wingman GTFO I'm going in for a landing

People have been waiting 18+ months. That's more than a hiccup. It wasn't a kickstarter, it was a product that was being sold and it's great that it's being delivered now but they went for so long with no updates and no deliveries that any goodwill they had with the community has long since been exhausted.

Don't select trigger. The tpod will auto lase with the laser armed.

I can be noon on the server and I still can't see any of the switches. Cockpit shadows are ridiculous. I know the instrument lighting is bugged but it's more than that, ambient light is nonexistent. It's like someone painted the inside of the cockpit with vantablack, there is zero reflected or global illumination.

Make sure that no other device is bound to thrust

I find giving your throttle a curve on the bottom end helps significantly. Giving yourself more throw range in the 0-30% throttle area allows you to make minor adjustments with more precision.

If you get it repaired and it's functional you could sell it with the slew upgrade for like $300 right now. It's probably worth taking the chance, but it's your money.

There's a guy on ebay who repairs the logic boards too for like $40

If you haven't been able to notice the mura, then good but don't go looking for it. Because it's there. And once you notice it, you won't be able to un-notice it.

So I think I've resolved the issue on my end. After several hours of playing with settings, different AA modes, in both SteamVR and DCS, I've found that the SteamVR Advanced Supersample Filtering was the cause. Or at the very least I've not been able to recreate the issue since disabling it. Edited: This didn't entirely fix it but it did lessen the effect significantly in most cases. On the supercarrier it's still an issue, and gives you a twitchy, blinking feeling as if your eyes were closing on their own. It's very, very, very disorienting. And ED will likely never acknowledge or fix it.

If you alt tab while DCS is starting up or loading into a mission, the game will freeze on the DCS logo screen and stop refreshing entirely. The game is still running, sounds are working, I can flip switches in the cockpit but the screen never refreshes. Alt tabbing out of the game while it's running is fine, it's JUST if you do it while loading. All you get is a black screen. What's even goofier is that taking a screenshot shows the game rendering just fine. It's just not making it to the screen.

Need a track to verify.

https://imgur.com/a/HjhuHTu The exact same issue in the channel map. With the Spitfire. Nowhere near a supercarrier. Or a taxi light. It's an MSAA dynamic cast light bug.

It wasn't on the carrier, it was Kobuleti. I'm saying the bug isn't localized to the supercarrier. It's a dynamic light/shadow bug interacting with MSAA. IT'S THE SAME BUG.