Devrim

Anyone tried this? I did but this time DCS won't see the monitor lua file, because (probably) something is wrong with bright command I guess.

Wow. You're lucky. Satellites must be just come from Mars mission.

Thanks a lot @Raptor9 @BIGNEWY I added a zip file that includes the mission and the track file. Thank you. No Green Numbers.zip

Hi. I created a simple mission in Syria map; Put a few enemy units there, put a blue Apache on a base (Hakkari) and start. That's it. The problem is that after engine start (please be sure - I do proper startup), I'm waiting too long to see green confidence but can't see the green numbers. They're always white! Normally I get greens (in other servers or missions - not made by me of course) in 2 or 3 minutes. In this example, purposely I waited approx. 10 minutes to be sure there's something wrong with me. But no luck, no green numbers. Is there anything to put on the base (maybe near my aircraft) to connect satellites? What do I do something wrong? Thx.

Thank you @Floyd1212 I use that software and I'll try what you told. Thanks a lot!

Please don't break the topic. Your one is another case and I suggest you to start a new topic. Thx m8.

The solution, I believe, is on your side. 1) The Apache is W.I.P (early access stage) and, in my opinion, there's nothing wrong with it for an early access module. 2) X56 is a nice HOTAS. It works good I'm sure. 3) The Apache's graphics are great. Also nothing wrong there. The problem starts on your side, as I said. Please check your selected options, axis controllers in Controllers tab. Don't use ED's default profiles for X56. There may be some doubled axis commands and that causes some ghost or wrong inputs for the aircraft. So, create your own profile: Clear all axis commands in Axis page and set your inputs and adjust them. Check YouTube videos. Everyone fly it very nice and interior and exterior graphics are great. See you.

I've used X52 for years and am still using X55. No problem at all. Your problem is probably doubled axis issue. Check your all axis controllers.

Thx mate.

Hi. Exported images look darker than the MPDs in the cockpit. Even if I roll the BRT knob all the way, I can't get enough brightness for exported displays. Everyone see that, or is it just me? Thx.

Hi. It's definitely better now. The aircraft is in more calm attitude. Last night I tested updated SCAS and it was the first time I've seen 3, 2 and also 1 knot while hovering. But yes, I've realized more the sense of that SCAS is fighting against you, but if you stop fighting SCAS, the aircraft immediately calms down and do what you want to do. Note: I'm still using curves. Love it!

Yes, he murdered me a few times with the same style.

THIS! Plus: If I want to record in-cockpit view, I always stay in cockpit during the playback. If I want to record F2 view, at the beginning of the playback I hit F2 and stay there until the end of the track.

This is my story: In a multiplayer mission, my aircraft was full of Hellfires. I killed some targets. Everything was going well. Then; a missile exploded next to me and I lost the half of my left wing. All hellfire missiles on the left gone! But after trimmed well, I was doing OK. I ordered George to fire. he said engaing.... but nothing... Left hellfire was flasing on the left MPD... but nothing... By my orders, George switched to GUN and took some shots, after that, by my command he switched to MSL. A hellfire missile on the right side was flashing. I ordered to fire, and George fired and killed the target. For the next target, left side was flashing (but no missile there), and George was stuck again. Obviously there's a bug here. George didn't aware of the situation. That's OK. I know there's no any command to say him "Skip the next missile!" What a CPG would do in that situation? Oh! RTB? NOTE: I have 6Mb multiplayer track or a few minutes long video that I can upload.

This is it! Thanks for the golden information. (I'm sorry I missed if this was written before.)

Yep! The same product.

Go to: "...\Users\{your-user-name}\Saved Games\DCS*\Config\Input\{aircraft}\" folder Delete joystick or keyboard folders. Doing this should get the defaults back. * DCS or DCS.OpenBeta - it doesn't matter.

Hi. Thank you Osram. Its name looks like Green Touch, but that may not a common brand. This is the link of the local store's. With a short search on Aliexpress, people can find similar products I believe. Actually, (honestly I've just learnt "touch-foil" things with this products) there're a few type of touch-foils. IR type: I guess there're IR sensors in the frame and they send the coordinates to PC via USB. Resistive type: They are used for industrial purposes and respond to hard contact (like ATM machines I guess), and Capacitive type: They are mostly used in multi applications screens, industrial areas and administrative data screens. So, I preferred IR type. No need any touch pressure. If you move enough slow, it senses your finger before the contact. After a few adjustment on Windows and Helios, it works perfectly. Button, knobs and toggling switches, all works great. I need to develop muscle memory for rotary knobs tho. The product I have hasn't got USB-C type. The cable directly connects the frame and other tip is standard PC USB type. Yes, it's actually "plug & play". I didn't install any driver but I downloaded a little software with the website's redirect. There're some calibration buttons and other nice options but I didn't even calibrate it. I tried something on Windows side to make it work properly. Example; At first run, I needed to double click to trigger a button on the second monitor or sometimes my touch triggered my main monitor. I did some mess with Touchpen or touchscreen settings of Windows and finally found how to do it. Now, it works completely how it should be. I can tell the details later if anyone needs

After the latest patch, you need to enable the radar altimeter. Go to FLIGHT page. It must be around R6 button. It was ON by default before the patch.

Hi. Thanks so much @osram for the idea. I have 2 x Trustmaster MFDs and I am using them for almost all aircrafts, and Helios app didn't take my attention until the Apache and this idea. You know, the Apache has 6-button MPDs and Trustmaster MFDs are kinda useless if you don't find a solution-ish things. So, instead buying an expensive touchscreen monitor, I've bought a china-made "touch screen" (not a monitor) from a local store (I guess you can find it in Aliexpress etc.). I attached it on my 18.5 standard monitor with double sided adhesive tape. I did struggle a little bit to make it work on my "second" screen, and DONE! Now, I can use the Helios for Ka-50 too. Thanks so much for the Helios profiles to Oze and Capt Zeen. I've edited a little bit. NOTE: It's not a glass. Just a plastic layer (mika? mica?). And, yes it looks like there's too much reflective but IRL you don't see the reflection. Eyes focus properly.

Maybe you can do something like this with different coordinates on the same monitor but I say that this is useless unless you have got 24" or bigger monitor. I tried this on my 18" monitor and it's not a good idea. Other than this, we're waiting for a solution from ED's side.

The code must be come from Mi-8's or Mi-24's file. H: Heading, K: Bank, T: Pitch, B: Altitude. Go to: "...\Mods\aircraft\AH-64D\Cockpit\Scripts\ControlsIndicator\" folder. Edit: ControlsIndicator_page.lua Find the line #715 and replace: local chan_names = {"H","K","T","B"} to: local chan_names = {"HDG","BNK","PTC","ALT"}

I have the same problem. My thread has been marked as solved; Raptor did a good explanation, but actually that's not a solution.

Actually and honesty I have no clue how to solve this issue for Steam version. But the only solution in my mind is that you download and install the DCS from ED's website and transfer all your Steam modules to non-Steam version in your Profile page (in digitalcombatsimulator.com)

It's opposite for me! At first, I thought it was distracting object that swinging there all the time, but after a while I've realized that I barely notice it.