m005106

That's the page I'm using. 1.21 for the handle and 1.40 for the throttle base. I also noticed the brightness of the 5 leds is a lot more higher than other backlights at max.

Distinguish or not, the led is still stuck at max brightness. Stays on even when computer is shut down

I do have simapppro running in the background. The thing won't sync anywhere; not in game, not in app. Once I plug in the USB, it's just MAX brightness for those 5 leds. period. I tried syncing manually, in DCS, and through an axis. My take off panel, combat panel, and every thing around the throttle base syncs wonderfully. But those five culprits just keep shining.

Hi folks, Just got the new throttle, but with a problem. As the subject says, the 5 LED backlights right under the throttle(MAX, MIL, FRICTION, IDLE, OFF) is always on its brightest setting. Cannot control brightness, or turn it off. It's even on when the computer is off. I tried to sync it to an axis through SIMAPPPRO to no avail(other panels are all synced. Takeoff panel, combat panel, and lightings around the throttle) No manual adjustment through test mode either. Just did a firmware update but still no improvement. Any thoughts?

Just installed a pair of lcd screens behind the Cougars. It looked okay, but the frame drop and stutter is unforgiving. I have a Ryzen 5600x, 6800xt, 32gb, 165hz monitor @ 3440x1440 rig which is quite smooth with all graphic options pushed to max except for AA and RT . (only play SP so far) But once I start pushing screens to the MFDs, it is choppy as @!￦#. (freesync is off) I am exporting via monitorsetup lua file adjustment(file attached). Freesync is off and total resolution on options is 4240x1440p (MFD LCDs are 800x600 each and are stacked on top of each other/ to the right of center screen) ANY Help would be greatly appreciated MFD export.lua

Thanks! This fixed it!! Who would have known right?

At the start of every mission, the joystick x, y axes are pushed like in the images. It returns to normal after I give a slight nudge to both x, y axes. It's okay when starting on the ground, but not starting in mid air It also returns after I unplug and plug it again, but the bug(?) returns after a while. I'm using a VKB gladiator nxt. Any thoughts?

Is there?

Would you be able to share with us what was wrong after you guys correct it? Just got super curious after this 40+ page discussion. In layman's terms of course.

Is it just me or is anyone crashing more with the F-14? It seems like crashes are more likely if I switch to or from the F-14. If I just stay with the Hornet, it loads just fine. At least it seems like it.

Flappie, My export.lua has nothing in it. 0KB. The file is there, but no content.

try inserting this line into your autoexec.cfg input = { threaded_ffb = false } I had the same problem and this fixed it. good luck

Tried creating a custom resolution in radeon software and it works perfectly. Should have searched more before posting.

I'm on a WQHD monitor(3440x1440). However, fps was a bit disappointing at this level of resolution, so I lowered the resolution at the DCS options to 2580x1080(preserving the 21:9 ratio). The game starts up fine at full screen, but the menu buttons correlate to the windowed(2580x1080) position. I can ALT-ENTER out of full screen and confirm this position, and when I ALT-ENTER back to full screen, the correlation is fixed, but ONLY for the menus. Once the game starts, non of the cockpit controls correlate to the fullscreen position(it does match the windowed position). ALT-ENTERing out and back does not work. Hoping there is a work around for this that anyone knows about? Thanks in advance

Thank you, I'll give it a try

My last crash was kind of weird. The game crashed during F-14 free flight loading screen, gave a "unfortunately DCS has crashed, allow dxdiag.exe blah blah" pop-up, but I could alt-tab back to the game and start playing, WITHOUT PLANE SOUNDS. could hear the slight low frequency sounds when pulling back on the stick, but else nothing. No engines or button clicking sounds. I did crash the plane and that's when sound came back to life. The crashing sound and F2 view and sounds of other planes. I then ESCed to end the flight and that's when DCS proceeded to crash for real. Had to alt-tab to the above "unfortunately blah blah pop-up" Crash logs attached. P.S. The first time stamped log file was broken(?), the extracting software repaired it(not sure what's going on, so I attached both of them). dcs.log dcs.log-20210512-053850.zip dcs.log-20210512-053850.repair.zip

Not sure if this crash is relevant to the second mission crash, but I never had any crashes except the second mission crash and then this started to happen so here goes; Started up DCS(steam version), went straight to Syria free flight on the Hornet, pressed ESC and started adjusting controls. Half way through, BAM. CTD. Was not flying, paused. Logs attached. EDIT : I am no longer getting second mission load crashes since I am crashing during the first mission loading or in flight. I'm assuming the last small update is the culprit? More crash logs attached. EDIT2 : Is it possible to uninstall just the latest patch? (I think it was 4.5mb or something) The game is now totally unplayable, crashing left and right. dcs.log-20210512-042807.zip dcs.log dcs.log-20210512-044902.zip

Didn't work for me. DCS froze during mission loading screen, didn't let me alt+shf+del nor alt+tab. hard reset.

Just DDUed the AMD graphics drivers and installed the newly released May-1 drivers. No crashes..yet.

For me, 2.7 was working fine.. until I installed some official mods(fc3 and syria; could be coincidence, not sure). bignewy advised on deleting all unofficial mods and doing an integrity check, which I did. Worked fine for a day, but started crashing again I did get the security center thing in the event viewer.. attached are log files. dcs.log dcs.log-20210506-021734.zip dcs.log-20210507-004400.zip

Thanks for the help! I know it's a weekend and I really appreciate it. Back to flying!

I'm not actually sure but ever since I installed Syria and FC3 during the last weekend steam sale, DCS crashes to desktop. This never happened before. I uninstalled FC3, checked file integrities, deleted fxo and metashaders folders but no joy. Crashes happen during loading screen and never during actual gaming. Any help would be greatly appreciated! dcs.log dcs.log-20210502-111509.zip

+1 on a Korea map. Having served in the ROK Navy for 20+ years, I can assure you that the Korea Theater of Operations can be one of the most dynamic there is. Numerous OPLANs for contingencies and all out war are in place, and although they are all secret, many of them are easy to deduce, and more than vaguely available to the public. Wartime US augmentation through time phased force deployment data, which is also confidential but more than vaguely available, will contribute greatly to the dynamic campaign's realism. The geographical position of the Korean peninsula is also an attractive one. Right smack in the middle of the US-ROK-JPN vs RUS-PRC-DPRK power struggle. Oh and don't forget. The Korean War is not over yet, it is on hold through the armistice agreement, hence our ROE name : armistice rules of engagement. Please make this happen

well, figured it out. the swap axis option under ff tune made it go away. it does pitch now, but manageable through trim.

same here. gun acquisition, wide acquisition, vertical scan mode does not work. only bore sight mode locks on. hope they fix this soon