FoxTwo

I don't think the gear up noise should be going to my headphones. :)

The light itself looks fine, but the falloff doesn't appear to be coded properly.

For the F/A-18C, the throttle seems to be dead on with no additional calibration in DCS. I'm using the default AB position in the winwing software. For other aircraft, I've needed to adjust with custom axis curves. So far I have these done: F-14B 0, 4, 10, 21, 33, 45, 57, 68, 79, 90, 100 F-15 0, 5, 12, 22, 33, 45, 57, 69, 80, 90, 100 F-5E 0, 3, 9, 19, 30, 43, 56, 68, 80, 90, 100 Anyone care to share any others?

Can you not just make the unit invulnerable/have unlimited fuel?

No... no. That's... no. Entirely intentional and accurate. There's an option to enable it in both eyes, but no, it's supposed to be right eye only. World objects rendering in one eye or different LODs in each eye are another issue entirely and completely broken. Has been since the beginning of time, gets worse every patch, and doesn't seem to be high on the ED priority list for a resolution.

Sorry, Thursday. Not tomorrow.

https://forums.eagle.ru/showthread.php?t=244117 This post specifically: https://forums.eagle.ru/showpost.php?p=4047346&postcount=3

Their store page has a valid certificate, facebook probably sent you to https://wwsimstore.com/STORE. https://winwing.cn is the one with the expired certificate. Again it's... an annoyance, nothing more, they'll update the cert I'm sure.

I don't think it's just lights. I came up on a KC-135 and pre 6/10 could see them as a pixel dot at 26-28 miles out. Can't see a damn thing until like... maybe 5 miles now. In broad daylight.

Their certificate expired yesterday. It's fine they just need to update it. You're safe to click through.

Details? Video of the operation? Did you run separate power? How long did it take you to assemble it?

That is not normal, are you overclocked at all? It sounds like your system is unstable or you have a GPU driver problem of some sort.

https://www.monstertech.de/en/product/joystick-throttle-mounting-plate/ No photo yet but you can select it.

They screwed up the VR gamma somehow in the latest patch. I had to dial mine back to 1.5 to make things look normalish on my Reverb. It was at 1.8 pre Wednesday's patch and looked fine.

Had to dial back to 1.5 to get things looking reasonable, 1.8 (which is where I was previously) is now a whitewash and entirely blown out. I mean I guess that's fine but changing the global gamma value should be in the patch notes somewhere?

There's this: https://forums.eagle.ru/showthread.php?t=160053 But I just use a powershell script with independent options files. #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 $dcs_exe = "$env:ProgramFiles\Eagle Dynamics\DCS World OpenBeta\bin\DCS_updater.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" #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 } Start-Process $dcs_exe -NoNewWindow -Wait #start DCS 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 } Start-Process $dcs_exe -NoNewWindow -Wait #start DCS Copy-Item $options -Destination $novr_options #save any changes to no-VR options } #menu choice Cancel else{ exit }

It was rare before because most lights were baked. This seems to be a result of cast light cones interacting with MSAA somehow. Disable MSAA and it goes away. It's worse in 2.5.6 because of all the extra dynamic lighting but this problem has existed since 2.5 at least.

I've been able to see a pixel sized dot of a KC-135 at around 26-28 miles recently while rejoining. Ground targets though, they only seem to render at 20 miles or less.

smokeTrail.lua maybe? contrail = { --инверсионный след { Type = "smokeTrail", [b]LODdistance = 20000, -- m[/b] ScaleBase = 3, Lighting = 0.5, DetailFactorMax = 4.0, Nozzle = true, NozzleSpeedMin = 200, NozzleSpeedMax = 400, FadeInRange = 350, FadeOutHeight = 12000, Length = 12000, -- m SegmentLength = 100, -- m FadeIn = 30, -- m } },

Is the software required, or can I use the throttle without and still maintain complete functionality? I'm OK with the idea of something you run once for initial setup just not pumped about software that's on all the time if it's not necessary. I see a lot of software hacks mentioned in posts to get switches to behave a certain way but is this optional? I'm currently using a warthog without target and it's fine. I don't need a bunch of macros, a 1:1 mapping of switch functionality is all I'm really interested in. I'd much rather edit LUA input scripts than run an executable.

I'm expecting $250-300 tbh but regardless... I think one of the panels really needs flaps selection. The throttle panel doesn't have it, and it's an essential function.

Light bloom, particularly at distance, was changed for the entire engine and it's super goofy. You'll see a ball of aircraft lights but no aircraft in the middle of the day depending on the distance. It's an engine problem that they just introduced hopefully they fix it.

That's not true it'll happen anywhere a cast light source intersects the camera at an angle with MSAA enabled. Try taxiing past some F/A-18Cs with their taxi lights on. You'll have the same effect. It's an 18 month old bug. https://forums.eagle.ru/showthread.php?t=227646 Disable MSAA and it'll stop.

It's MSAA. It's not just the supercarrier, and it's a bug that's about 18 months old. Disable MSAA and increase your PD or target render resolution in steam.