MAXsenna

No need for all these posts at the various forums. Can't have a look at the track right now. But I did have the same issue until I learned to do it the correct way. When I got my original TM Cougar, I was confused. I also thought pressing that button on the TQS would lock the target. As it turns out you have to press the TMS up button on the grip on the stick, (as long as its correctly bound), to lock the target. Not on the throttle. Have you actually tried that? Just mentioned it like four times now. 
Cheers! 

No, you just have reached your limit of uploads which is 200MB or something. You can delete old files, but that might ruin older posts, so I use Imgur, (there are other services), to post pictures. I upload to Imgur, then I copy the image link and post it here, so the picture is embedded in my posts.

Sent from my SM-A536B using Tapatalk

You're missing the texture for broken windows. Either perform a repair, or if you're using a cockpit mod. Reinstall it or notify the dev.
Cheers!

Sent from my SM-A536B using Tapatalk

Because it's not axis in the real aircraft. And it would probably work very badly. What to do when you've reached the end of your physical axis, but you still need to "scroll" further?

Cheers!

Sent from my SM-A536B using Tapatalk

Have you excluded the DCS core folders in your Anti-Virus solution?

Sent from my SM-A536B using Tapatalk

They changed the controls. So you might need to delete the controls folder for the Chinook and start over. Like Raven says, it's a conflict, and that might happen from time to time. Should be able to see the conflict if you hover over the exclamation mark.

Sent from my SM-A536B using Tapatalk

You're not using any curves or saturation in the Phantom by chance?

Sent from my SM-A536B using Tapatalk

Exclude the Steamapps folder under Program Files (x86)\Steam\ in your Anti-Virus solution (Ie. Defender), THEN perform a file verification of DCS in Steam. Hopefully that will solve it.

Sent from my SM-A536B using Tapatalk

Clear out any axis in any module for peripherals you don't use. You have axis conflicts for sure.

Sent from my SM-A536B using Tapatalk

Get a second screen and export all the displays. It will be the quickest and easiest solution!

Sent from my SM-A536B using Tapatalk

You missed the point. The Beta testers have access to a pre-release. I have no idea how often that's updated. The Modders would have access to the same build, and are able to test themselves, not relying on testers. If they discovers some issues, they can either fix that, with or without ED, and/or give the community a heads up. They could even tell the community they're going away. We sort of know the patch cycle now, so it wouldn't be too hard to anticipate when a "conflicting" patch drops. 🤷‍♂️

Same! Have a great weekend!

Sent from my SM-A536B using Tapatalk

I don't use VR so this might be a goose chase. Could you by chance have saved a Snapviews setting? At least in 2D with TrackIR, you must stop the tracking, or what you observe will happen.
You can see if this remedy fixes it. Open the Snapviews.lua in Notepad++ and delete the whole F/A-18C section. You will of course lose all Snapviews settings for the F/A-18C though, while I think you got nothing to lose besides wasting two minutes trying.

Cheers!

Sent from my SM-A536B using Tapatalk

Where is it stored? It needs to be in the mission\campaign folder for the A-4E-C.

Sent from my SM-A536B using Tapatalk

@Fireman1979
Hi Eric! You're Anti-Virus solution snagged important files and put them in quarantine. Add your Steamapps folder to your Anti-Virus solution, and perform a file verification in Steam of DCS. Then everything should be back to normal.
Cheers!

Sent from my SM-A536B using Tapatalk

First of all. This setting is not for FFB. It actually says "Without springs and FFB", which means without springs nor FFB. Use the first one, Default. That's for FFB. Even so, it only affects the trimming mode. It seems to me FFB is turned off altogether, as no one else have reported this, so it must be a local problem. Which helicopter module is this? 
Read again, you have working FFB effects when you turn on telemetry for the Moza. Pretty positive FFB is not turned on in the Misc settings.
Cheers! 

Apologies, but why did you start a new thread before you Googled it or search the forum? That goes for more than you.
Your Anti-Virus solution has snagged an quarantined an important file. Exclude the DCS installation folders and Saved Games in your Anti-Virus solution and perform a repair, or verify your files integrity if you're on Steam.
That's it!
Cheers!

Sent from my SM-A536B using Tapatalk

Spray the rain repellant and turn on the heat, or ask the ground crew. /s
Jokes aside, it's not possible. Should disappear when the rain stops I believe.
Cheers!

Sent from my SM-A536B using Tapatalk

You can run repair in a command line.
Double check if your Anti-Virus solution didn't snatch any files, maybe they're just quarantined.

Repair DCS World
In the command prompt type the following command: DCS_Updater.exe repair. Press Enter.

Sent from my SM-A536B using Tapatalk

@MrMigz Hi! You have tons of mods, in Saved Games Mods Tech. 
Do a full repair, and rename your DCS.openbeta to DCS.openbeta_old, and I'm sure DCS will start. 
If you want to use Skatezilla's app, you need to turn off Multithreading, as there are only one version now. 
Cheers! 

/topic/369577-official-news-updates/

Sent from my SM-A536B using Tapatalk

Cool! Hope you get there!

Sent from my SM-A536B using Tapatalk

Saved Games scripts? Don't remember if it has an entry in the export.lua, where you can just uncomment it by adding two dashes, -- , in front of the corresponding line.

Sent from my SM-A536B using Tapatalk

Had the same issue. Under the Special Settings you can fix it. I'm not at my computer so I can't remember the setting.

Sent from my SM-A536B using Tapatalk

@SuperTonique Wild guess. Have you enabled Easy Comms in the DCS general settings?