Se1ko

Nice tool. It would be even better if it had a "speed" function in it that allows you to set a desired speed to fly on a particular leg and calculates/populates the TOT for you.

I have just wiped and started a fresh install of Windows and DCS and note that none of my landings are being logged in in my log book.

I have a similar problem, once I join a coalition the slot screen appears but locks up, cant scroll down, selections seem to take forever. If I struggle long enough to eventually get a slot and get into the pit everything goes well from there. It doesn't happen when I join a server that has very few players on the server. Also noting that when a message is sent by a player the screen briefly becomes usable but within seconds locks up again. I had a similar problem about 2 updates ago.

Hi, the flare would look like a big heat heat ring to a thermal sensor as they burn at a temperature that is measured in thousands of degrees, which is what you want when you fire them in order to distract a missile sensor.

I don't know that it does or doesn't affect voice chat, I would hope not, however as there are a lot of problems with voice chat in its early stages I think its something that needs to be looked into. Making the assumption that because its different key binds it won't affect voice chat is something I personally wouldnt hang my hat on at this time. Whats to say that while the transmitter is keyed you can't hear whats being sent to you due to some problem with the comms logic? What it does bring to light is that there is no commonality between modules as to how the radio communications menu works and ED and its partners perhaps need to come to an agreed standard of how it works in the future. To my mind I would of thought the functionality for such a baseline feature of DCS World should of been standardised across all modules and module makers before the changes occurred in 2.9. Going forward I would love to see the implementation of the short press/long press of the radio button on a controller (like a stick abstraction) to be able to either bring up a comms menu or transmit over VOIP, rather than have all these key binds to deal with.

I think you're missing the point. I am not talking about the VOIP or the Radio PTT button. When I bring up the communication menu in the F-15 using the appropriate button for the radio I want to use, the radio itself is keyed into transmit and stays that way. It is not until i select a command from the menu and the call is made that it unkeys itself. So the radio is keyed the entire time from start to finish. What should be happening (and happens on the F-16C) is that I press the Radio call menu for the radio I want, select the call I want to make from the communication menu, the radio then keys into transmit and makes the call, then the radio unkeys and no longer transmits. The radio only keys itself when making the transmission of the selected menu option, which is what I would reasonably expect, not continuously transmit from just selecting the communication menu.

The beep you heard on Apollo and early shuttle missions was called a Quindar Tone You heard it at the start and end of a transmission from Mission Control. The tone was used as an analog method to key the transmitter that was sending the signal to the spacecraft into transmit, with a tone after the transmission to reset the transmitter back into receive mode. You wouldn't hear any tones when the astronauts transmitted from their spacecraft. The tone wasn't used as a way of making clear that a transmission had ended like people like to use on ham radio these days, it was just a way of keying a remote transmitter.

I agree, the F-15E MFDs are brilliant in terms of clarity both in-game and when you export them to another screen. I have found the AV-8B displays have been nothing but a blurry mess since they made an update some time ago, particularly when you export them. It would be awesome if Razbam applied the same technique they used in the F-15 MFDs to the Harrier.

The old "Command menu" using "\" doesnt appear to work as it once did. In the past you could do all your radio calls to AI, ATC, air-refueling, JTAC using the command menu as long as you had your radio tuned. Now it appears that commands have to be done using the the radio 1/2 call menu function, which is a PITA. Also the radio call menus will work differently depending on the flavour of the aircraft. In the F-15, once you select a radio menu, it will key the radio in transmit and wont stop until you have selected a call command from the menu and it has transmitted it. In the F-16 you can select the a radio menu, choose you command, then it will key the radio and send the message, then un-key. It looks like the old command menu using "\" (which was perfect for using the radio with AI stuff) is either bugged or its functionality has been removed. I really do hope its just bugged.

I have only had limited success with VOIP, as it would seem common with many others. I am sure in time it will be sorted. What I find is that the change to the Call Radio Menu function which is used for AI comms, air refueling, ATC, etc is now made more difficult than it should be. In the past it was just a matter of selecting the communication menu (which by default was "\" ) then selecting the command you wanted to use and, as long as you where on frequency, it would transmit. This was good as it didn't require extra key binds to controllers and got what you need to have done, done. Now the communication menu (for me anyway) doesn't work as it once did and am trying to find ways of using the "Call Radio Menu" (MIC Switch FWD/AFT) command with controllers that are already at the limits of what can be bound to them. It would seem that the current thinking is that you can either have VOIP or comms menu, but you cant have both. At least not easily. I use Helios, so I tried creating touch screen push buttons to bring up the menus for each comm. This works but I have found with different aircraft you get different behaviours. The F-15E will key the mic immediately upon selecting a radio using the MIC Switch FWD/AFT and wont unkey it until you have selected a command from the radio and it has broadcast it. In the F-16 you can select the radio menu, choose your command and only then will the radio key and transmit the call, then unkey itself. This is more of what I would expect. There seems to be no common logic to the core feature. I have also found that sometimes the old "command menu" will work if you have first used the new radio call menu. The old command menu worked just fine and was not complicated to use. This new feature, while I can see the benefits, seems not have been thought out too well and makes doing simple radio tasks somewhat overcomplicated for people that use AI aircraft, or do a lot of work with AI assets in the game. As I see it the radio command menu was always an abstraction feature that sensibly fulfilled a requirement of the game, but the change in functionality now pushes the users that want realistic-as-possible controllers into something that isn't very realistic.

In the F-15E I am finding that when you use the radio call menu (1 or 2) radio command to bring up the appropriate menu the radio selected keys itself until you select a radio call. For example, I select Call Radio 1 Menu (Mic Switch FWD) to make a call to the tower from the menu. When I do that, the UFC shows Radio 1 is keyed and stays on with the "T" displaying even before I have selected a call using the function keys. It is not until I have selected an F-key function and the transmission is made that the radio will un-key itself and the "T" disappears. This is in contrast to the F-16, where if I select radio call menu (1 or 2) to bring up the call menu, the radio will not key its self until the radio call has been selected from the menu, where it then keys the radio, makes the transmission, then un-keys itself, which is what I would expect from the radio call menu function. In short, it seems that the F-15 radio logic is keying the microphone the moment you select the radio call menu and does not un-key until you have selected a radio call and transmitted it. Would this not be a problem when using voice chat and you are holding the radio in transmit?

Hi @BIGNEWY, Here's a short track file from the Instant action Free Flight game over the Caucasus. Most aircraft are flying at around 7000ft however I can still lock targets up with lower antenna elevation well above that. In the track file you see I was able to repeatedly lock up targets at 7000ft with lower antenna cone elevation of height of 33000ft. I've included a second track focusing on the MFD and tried to let the contacts age with datalink off. From my understanding if the elevation is well above (or below) that of the contact and the contact is outside the scan volume you shouldn't be able to lock it. Happy to be wrong. Hope this helps. Mark cac a2a scan volume track bug.trk cac a2a scan volume track bug2 close in.trk

Can confirm. In A2A mode radar seems to be picking up ground unit returns. I have been able to lock up the return and confirm it with TGP on the F-16.

I'm noticing it too. In A2A the radar seems to be picking up ground unit returns. I have been able to lock them up and confirm this on TGP for the F-16.

Hi @Scofflaw, thank you, I think I have it set up correctly, my main issue is that I dont have the device recognised in the Dynamic Vibration Motor screen, is this related? (I have an Orion 2 base with an F-16EX throttle grip. I use a TM Cougar Control stick) See below: I was also curious to know if having selected the non-multithread DCS game Icon has an impact? (I run multithread but clicked the wrong button on setup, now I cant change that. When I un-install simapp pro and reinstall it returns with the same configuration). Is there a way to change your game and hardwear setup, like a file directory I can clear to have a fresh restart?

Hi @zeufman, I just received my F-16EX throttle and cant get the vibration working. Is there any chance your can explain you fix a bit more please? I think I might be having a similar problem. The instructions aren't all that clear how to set it up and would appreciate any help I can get.

Not a bug as such, but it would be nice if the F10 map coordinates picker window could be dragged around like the warehouse window. When using multiscreen or ultrawide setups the picker window is way off to the left so you have to turn away from looking forward. See photo. (Note: I really really like this new feature though! )

View exports in general need to be fixed, especially since the introduction of the pure scripts function of IC checks which stops people from being able to export views beyond the two MFD displays ED allows.

Hi @BIGNEWY, Thanks for the response, sometimes it can feel like you're talking in an empty room. Without wanting to pressure about a timeline of when things are going to happen, could you perhaps let us know if there is indeed work going on concerning the issue of pure scripts and IC and what that might look like?

As I've said earlier, the squeaky wheel gets the grease. In the real world of synthetic training devices for pilot training, where there's a lot more at stake, it is hard to get momentum going with OEMs to implement fixes or changes. You have to keep at them and eventually they look at it (this is from personal experience). ED is no different. There are people making noise about the effect of pure scripts on their DCS experience and its not an insignificant amount. I am optimistic things will happen if going forward people offer reasonable solutions to perhaps guide ED's thinking.

Back to the matter of IC and export viewports breaking pure scripts.... When multi-threading was released in a recent patch it initially broke cockpit display exports. MFDs were a mess everywhere. To my surprise (after being told off like a naughty schoolboy by someone representing ED saying that very few people use cockpit exports so it isnt worth the effort) the display extraction problem was fixed in a matter of days. I was amazed (pleasantly). The squeaky wheel gets the grease, so cockpit extraction must be a bigger deal and perhaps a lot more people use it than I was was admonished for. I am also heartened that @c0ff did say they are looking at IC. I was wondering this: If ED aren't able to readily change the IC easily for whatever reason, can they modify the script for the aircraft to allow for export of particular instruments? Case in point; currently in the F-16 it is possible to export the left and right MFDs only which does not break scripts (as far as I am aware). Many sim pit creators also break out instruments such as the DED, RWR, and HSI as well, which is where you run into the "Pure Scripts" issue. Considering that ED must spend a spend a small fortune and a lot of effort on developing 3D models of pilots to satisfy those that use VR headsets (of which I dont use myself but dont begrudge those that do, each to their own), why not add the few lines of extra code to the cockpit scripts of each aircraft that allow users to extract the most needed instrument displays, as mentioned above? Over time, ED could review each aircraft and its displays and add the extraction code to the cockpit scripts for instruments that would be the most needed to extract by sim pit owners, or even those with an extra screen that would appreciate being able to break out that screen or display if they so wanted (not all of us have the eye sight of a hawk). Surely it can't be that expensive or time consuming to do, especially when stacked against something like the rendering of a 3D pilot. Add lines of code to cockpit scripts for the few extra instruments (in the case of the F-16) such as DED, RWR and HSI (throw in the CM panel counters too for good measure) **on top** of the existing capability to export MFDs that you have as standard (which was fine back when DCS was first released, but time, technology and price point of equipment such as monitors has change a lot since then). Its easy low hanging fruit that could be introduced across the whole lineup of EDs aircraft over time. Hell, it can be a selling point (just like your expensive 3D pilot). That way you can keep your IC and at the same time make a lot of users (more than just a small handful) very happy. (P.S- the new F-15E has 7 MFD type displays. Do you think that hard-core simmers aren't eventually going to want to break out some simpit extraction for those?)

@c0ff Hello, is there any further progress on this?

It surprises me too. I have been told in the past by an ED partner and developer that apparently people using extraction and viewports are very much in the minority. Based on the amount of users posting here with this problem so far I tend to think that extracting viewports is more common than they realise and is only going to become a more popular thing to do and be far more mainstream, especially when there are companies making products like MFD bezels and such that require viewport extraction. Hard to picture someone like Wags having a simple single screen vanilla setup :).

An ED Partner too I see. Interesting....

Agreed. Nearly every post I have read about this is either about people having an issue that they cant change their countermeasure parameters (to which I say, so what, deal with it) or, and most frequently, that they have a cockpit scripts IC issue where they are simply extracting a display to another screen. I am sure ED would satisfy nearly everyone if they added a "pure cockpit script {yes/no}" option to their IC check that allowed display extraction while not allowing other script changes.