KoleTang

The location saved relative to AI planes and ships is not accurate and seems to be miles from correct. Flying in close formation with AI ends up about a mile away. Carrier landing is not close. Without saving aircraft current config this is of little use. Not useful for creating new missions. Did anyone actually try this before release?

I agree the radio menus are way too long. If mapped to HOTAS, scrolling down 9-10 times is not effective and frustrating.

If I do anything like fly single-player and then go to multi-player my server list is empty. If I restart DCS and go to multi-player immediately it loads fine. When it's empty the drop-downs like map and region will not even populate.

Crash on exiting here as well. No mods. New with latest release.

@KP_Ghost thanks for the response. I do have my frequencies tuned. I was trying to point out that the comms menu is changing the frequency slightly. 251.000 to 251.001. Just as feedback to help the devs.

My "\" does bring up the comms menu but when I do an "F5 - Tanker" and then an "F1-Intent" to refuel I get a strange behavior. The tanker frequency should be 251.000 and the cockpit shows 251.000. But when the F1 key is pressed it changes the cockpit frequency to 251.001 and the tanker never responds. This worked before 2.9 and if I fly the same mission with the hornet or viper it works fine. I have attached the mission. F-15E_Tanker_KC-135.miz

Figured it out. I was not turning this off when flying the mission. Apparently, these things are maintained in the track file.

Does anyone know how to stop the George AI message texts from appearing in external views? I have unchecked subtitles and cockpit sounds in external views but they have no effect on George messages.

@Rudel_chw, Interestingly, the ATC Engage/Disengage button works similarly to the UFC A/P. It requires a press and un-press. However, it actually engages the ATC with the press action. But, the ATC indicator does not appear in the HUD until the un-press action. Just sharing. Thanks again.

Thanks again @Rudel_chw, I was using one trigger for all the actions. I never thought to use separate triggers for each action.

On mission start, I have an inflight hornet. I want to set the autopilot. I want to click the A/P button on the UFC and then UFC Option button 3 to set the barometric altitude hold. The first problem I run into is that X: COCKPIT PE1RFORM CLICKABLE ACTION Cockpit device 25, Command 3001, Value 1 presses the button but appears stuck. I am then not able to press UFC Option button 3 with Cockpit device 25, Command 3012, Value 1. Am I approaching this the wrong way?

Thanks @Rudel_chw, I tried that, but I was using a mission start event versus no event. It works with no event but not with a mission start event. Thanks for including an example. I am good to go now. Any idea why it does not work on mission start? Thanks again

I am trying to figure out how to set my cockpit up at mission start. So I picked the battery switch to try. I am trying to set the battery switch to on at the mission start with the X: COCKPIT PERFORM CLICKABLE ACTION trigger action. I have only been successful at setting it to ORIDE. With: COCKPIT DEVICE: 3 COMMAND: 3027 VALUE: 0 How can I set the switch to ON?

When the sim freezes try a mouse click to end the freeze. This has worked for me. And I would be interested if others can do the same. Hyperthreading is kind of a red herring. By reducing the number of virtual cores some of the threads are actually executing sequentially rather than simultaneously and thus hiding the underlying issue. In my prior life experience with scaling multi-threaded applications, I found that all IO activity must be handled in separate threads. The main threads write the log info to a FIFO queue and the logging thread does the actual logging from that queue. My fear is that multiple threads are trying to write to the log and or track file at the same time. Does anybody know how to temporarily disable logging and track file generation? I would like to test my theory.

I have also now seen this on other maps as well now. It is way worse on the Sinai map than the others. I am thinking it is a release-specific issue now.

The flickering in the video below shows up very frequently while flying. Many times in the same mission. It makes this map annoying and unplayable. I shortened the video to one such encounter to fit it here. But it will go and come many, many times while flying a mission. I have all the other maps and I have never encountered this problem before. SinaiFlicker.mp4 Cairo.miz dcs_sinai_flicker.log SinaiFlashing.trk

Also, note that the menu is shifting up slightly in your display from the correct position in the 1080 versions I posted above.

No, just running 1 display. Native resolution. No mods. Again, I can repeat this on multiple machines.

@BIGNEWY, Be sure that you are not testing with an upscaler (like DLSS) turned on. I am using native resolution. Attached below are screenshots the first two are at 4K and the second two are at 1080. You can see the 1080 screen shots have the AI menu in the correct location. This is a problem with 1440p as well. I also included mission, log, and track files. This is repeatable across multiple machines. Let me know if you need more. dcs.log GeorgeAILocation.trk AH-64D_Cold.miz

George Menu is now in the middle of the screen in 4K resolution. The location is not scaled properly for higher resolutions.

This has been fixed in the DCS 2.8.4.38947 release. Thank you.

As Heatblur is updating the F-14, binding "Ready pre-contact" like the FA-18 has would be very helpful for A/A refueling.

I found the problem. I was using a switch on my throttle as a modifier for my Radio PTT. When I use that modifier it kills all keyboard activity and other buttons until I click OK on the controls adjust screen. I removed it and no longer have an issue. This also exist in the ST version

This has gotten worse since the update on Friday. Often my non-axial and keyboard bindings just stop working in the middle of a mission. I work around it by going into Adjust Controls and just hitting OK. They will work again for a while. This last release has made MT unplayable. Updated info. This also exists in the ST version as well.

Yeah, this is ongoing. I keep another app open just so I can create a windows GUI event and unfreeze the mission loading.