Sharpe_95

Hi everyone, After hearing recently that SRS was no longer being maintained (rumour, not confirmed) I looked at setting up the DCS VOIP. I have it doing almost everything I need from it, except one thing: How to I set it to move each radio so that it is either coming in from my left ear or my right ear (like we can do via SRS)? Example: I would like Radio 1 to only come through my left ear and radio 2 to only come through my right ear. Is it possible to do this with DCS VOIP or is it something that is going to be added later (or is it not even going to be added?). Thanks for the help.

Hi, First Razbam, thanks for the excellent F15E module - a great release, supported very well by Baltic Dragons manual and Notso's tutorial videos. I have found a minor bug/error in the listing labels given to the 'call backs' (if that is the term) in the F15E front seat menu for the following: - UFC PB 10 - Which actually calls back UFC PB 06 (not 10 as labelled). - UFC PB 09 - Which actually calls back UFC PB 07 (not 09 as labelled). - UFC PB 07 - Which actually calls back UFC PB 09 (not 07 as labelled). - UFC PB 06 - Which actually calls back UFC PB 10 (not 06 as labelled). UFC PB 01-05 and 08 functioning as expected, I have not checked the back seat. Thanks again - S

And so long as we have the auto saved file from both pilots that is was ED needs? -S

[REPORTED]Vaziani no longer has runway markings? Hi guys, We have been using Vaziani as an airbase to operate from. Since the latest patch all runway markings have gone. There is no centre line, no touchdown point, no piano keys, no runway numbers. Is this deliberate or an error? -S

^ I'll work on getting one but may be a week or two. @Newy - when you say a client track and not a server track - how do I save a MP file as a client track? -S

Friendly bump. Please could ED identify if this is correct as is or a bug? -S

Frankenstein was the creator, not the monster. :doh: Sorry just while we are needling people about being accurate......:smilewink: -S

Whoop :thumbup:

Naturally I cant be 100% sure but having just flown a low alt mission since today's v2.5.6.49718 update I cant help but think this issue has got worse? -S

Hi guys, I noticed today that the TACAN 'Yardstick' (mirroring TACAN channels to get distance data between aircraft) has developed a bug since 2.5.6.49718 (today's patch), after working reliably and well beforehand. I am describing this as a bug as I can't see that this is 'correct as is' as the functionality does not seem logical and also no changes were announced in the change log related to the F16s TACAN (that I can see). This issue is as follows: When a pair of (human) pilots set up the Yardstick, everything seems to work fine. However, when one of them either changes band (X/Y) or the mode (TR/AATR etc) then one of the aircraft (the one that 'stayed' on the original TACAN freqs) has an 'inverted' (black writting on green background, rather than normal green writing on a black background) range measurement in the DED. A further problem exists that when rejoining back to the original TACAN freq, the player that 'left' will show correct range data in the but not the pilot that stayed has (with the inverted DED/CNI range readout) has a 'frozen' range read out that never moves. The 'inverted' TACAN range readout in the CNI page only shows the range at which the other pilot was at the point they moved frequency. The only way to fix this issue is for both pilots to leave the freq (for example, by changing bands, although I assume it works by changing freq or changing mode). When swapping bands (Y to X) we then had 'normal' function of the TACAN in the DED/CNI and the same when moving back to band Y. In summary: Both pilots tune to a yardstick (EG 11/74y AA-TR). Pilot #1 moves to band X. Pilot #1 shows - - - - - in the DED/CNI as normal, but pilot #2 (who stayed on band Y) now has 'inverted' TACAN range info in the DED/CNI. Pilot #1 moves back to band Y. Pilot #1 has correct DED/CNI as normal, but pilot #2 still has 'inverted' TACAN range info in the DED/CNI. When the aircraft move around, only pilot #1 has range info in the DED/CNI. The only way to fix is for both Pilots #1 and #2 to move to band X then back to band Y. I have not tested this with more than two people sharing the channel and if this makes the matter worse? Nor have I tested what happens when another flight is using a different channel that you (accidentally or by purpose) 'drop' into - but I assume it then creates a wave of issues for the other flight that now also has 'broken' TACAN info? Anyway, I have provided a track of myself and a Sqn buddy demonstrating this issue. As I say, it looks like a bug as logic dictates its going to cause issues inter flight as well as the stated intra flight issues. Also ED have made no announcement of any change to TACAN/DED functionality and there is no evidence of this operation in any F16 reference material that I have? Can it please be confirmed if this is a bug? -S server-20200526-210834.trk

Is this what you are referring to? https://forums.eagle.ru/showthread.php?t=269358 -S

Yes but I think this has already been reported? -S

Quite right and almost fully agree. However, while I would normally be the first to jump up and down and complain about the state of the F16 and the lack of love it is getting ATM, in my mind I have rationalised it thus (maybe it is helpful for you)?: I am the first person in the queue when it comes to 'give me my module now I dont care what state it is in', I therefore cant and wont complain when what they give is a little (or a lot) rough around the edges. I am 100% behind EDs EA business model and fully accept the fact that we will have a 'busted/not ready' aircraft for a year or two while we all (hopefully) help ED with open beta testing, in my mind this helps ED and speeds the process up and I get a fun aircarft to fly a couple of years early :thumbup: Do I wish ED would give more love to F16? Yes. But then the Hornet was where the F16 is now some years ago and they are committing to getting it out of EA, hopefully we will see this same level of love some time next year. But also, remember that the skills the Devs are learning getting Hornet out of EA are if not directly relevant to F16 then very closely linked - so I see that as helpful too. ^Hope that's helpful to you? Although as they say 'rationalisation is the first refuge of an unsound mind' ;) Regarding the payment model - well now, there's an interesting and probably horrifying discussion for another day and another post. Back to your OP: Naturally (and with equal validity) not eveyone thinks this way. Some people will just apply a black and white picture saying 'it's not on the exact F16 model we fly therefore it's not realistic therefore no' - but forget that actually when you look around at how we all fly (even those of us that do fly in more realistic VFWS) and how the sim works, they forget we are breaking realism rules left right and centre by design, by choice and by accident. I think this therefore undermines any 'realism only' argument. As you said it's a matter of choice. I dont think the option for choice should be removed for weapons integration just because 'the weapon in question is not 'realistic' because it is not on our exact model of the F16'. Its is available on some F16s, give people the choice, let them decide to use it or not. -S

+1 However the OPs post is clearly not a bug but a wishlist issue surely? Recon a mod will be moving this post shortly. -S

Lol - very kind of you to 'take one for the team': you will forever be held in high honour among the fledgling DCS Typhoon community and your sacrifice never forgotten. NOW STOP TALKING HERE AND GET BACK IN YOUR WORKSHOP!!!!! -S