CHRISXTR3M3

Yes multiplayer tracks are in a folder in saved games

Don't set a value for mult. What that does is compute "x" number of times you want weapon program to repeat itself on each pylon upon single press of pickle. Qty1 mult 1 will release total of 2 bombs if you have two pylons with bombs

What I did is bind the right DDI OSB 11 and 12 on my throttle cuz I put radar on right screen

Almost done with the x55 controls profile guys. Tweaking it a bit here and there for ease of use as I test it

Make sure you're running profiler software and dcs as administrator

https://forums.eagle.ru/showpost.php...3&postcount=10

Can you list any background apps that you have running at the same time this occurs?

also...here's this link because you're having the same app crash Problem signature: P1: ATKEX_cmd.exe P2: 0.0.0.0 P3: 00000000 P4: KERNELBASE.dll P5: 10.0.16299.402 P6: 81d25214 P7: 0eedfade P8: 00103f12 P9: P10: https://answers.microsoft.com/en-us/windows/forum/games_windows_10/upgraded-from-windows-7-to-windows-10-now-world-of/e9bd0e88-9daf-412e-86cc-6d7d74ce82ff

Not sure why, but your steam streaming mic is showing up as a speaker "audio output". also you have x2 device recognitions for your throttle and stick.

threads must have been merged

Fixed your embed

https://forums.eagle.ru/showpost.php?p=3506783&postcount=10

I've gotten missile launch warnings from my buddy launching A2G rockets so I'm guessing there is rocket motor smoke detection somehow

Yes the stuttering can be due to background apps running and using up resources such as CPU load and RAM. Yes your hardware surrounding the GPU is pulling it through, making it seem like the GPU isn't as old as it is. Yes, even if you have a Nvidia TITANX GPU but you have slow mobo, slow ram, old HDD, and a sluggish CPU then the GPU no matter how good will be hindered in performance. This effect is known as "bottle-necking". Like the neck of a glass beer bottle, the speed and flow volume are reduced at the neck due to compressing the fluid into smaller room for travel.

I haven't had the opportunity to check myself...but make sure there aren't airfields on the western straits that also operate on the same TACAN freq you used

You don't assign an axis for the TDC in the SIM with this profile. This profile uses the default keyboard bindings for TDC slewing. If you check the assign controls page while the profile is active and move the nipple around you will see the controls being engaged. Have to be under the "all" subcategory, not axis assign

https://forums.eagle.ru/showpost.php?p=3508996&postcount=15 Let me know if this helps

I'll work on it tonight then! Keep in mind it will be a work in progress just like the module.

The attached image is the best I could come up with on the fly while at work. SHhhhhhh don't tell my boss! I hope this helps! If you need further clarification please let me know!

Ironically disengages NWS lol

I've successfully lased a buddy GBU-12 into target from 13 nearly 14nm away in the A-10C. Anything past 14nm in A-10C and the laser doesn't even like to fire. This is what the behavior I experienced was a couple months ago. Havend tried it again since.

This is correct. I should have been more clear in my reasons...I use BYPASS to allow me to release CHAFF or FLARE at my own discretion....in other words, I don't use a counter measures release program, I release them in my own way/count/frequency/type etc. which is what BYPASS is for

I can check it out later on when I get home from work if you'd like. Might need to do a Keyboard type of binding then software programming to act as keyboard input to get it to work. I know I have it set up that way for My A-10C where the mode dial was actually the "pinky switch" for external lights.

In my honest opinion...I just leave it set to BYPASS...I've made it part of my checklist prior to take off, or if you want to go as far, you can make it part of your IP checklist.

It is even more noticeable in the F-14 =D