FoxTrotAlpha691

Yes Deka, please don't forget about the J11-B if you release that one Deka will have to two most awesome planes in DCS! We will be patient because if the J-11B gets done we will all be too happy to remember how long it took!! Salute to you Deka and blessings during this time of emergency I pray that all is well soon.

I use VA to communicate with ATC, landing gear, AWACS bogey dope calls, to center my Track IR and a few other small tasks that really help out. Not sure how much you already know so don't want to insult you, if you want some examples or to see the profile reply here and we'll make it happen.

Is there a version of the J-11 IRL that is capable of firing the SD-10 or any of the other modern Chinese missiles and if so will Deka ever bring it to DCS? Also, I have seen posts that make mention of editing the J-11A's LUA file but I have yet to see anyone post exactly how to do this and actually I'd rather have an aircraft that is truly capable of firing the missile than to McGiver the LUA file and have it not work in MP.

@sylkhan, I would like to say that I really appreciate the way you resolved this by owning up to what happened and apologizing for the misunderstanding. This is exactly the way mature folks resolve an issue, salute!

The J-11A campaign in user files is called the Red Knight campaign.

@AeriaGloria, sir if you have a way to edit the J-11A LUA files please share it, when I looked at it it was scrambled and not like the LUA files of the other FC3 aircraft. So if you know how to do this please post the method or where I can get information on how to do it myself. I love the J-11A and more effective missiles would definitely be a bonus.

Greetings, has anyone experienced issues with VAICOM PRO not working with the JF-17? I am having similar problems with it that I had with the J-11A for some reason the VAICOM PRO software breaks comms with these two planes preventing communication with the AI ATC and AWACS. The command displays, the pilot voice plays but I get no response. So does VAICOM PRO only work with US based aircraft? There seems to be an issue with VAICOM PRO and Deka Ironwork aircraft, if anyone has any information on this I would appreciate it, at this time all I can do is disable VAICOM PRO profile and use Voice Attack with my own profile that I created.

I'm using a 2 way button on my T16000M throttle, I have a paddle axis available, I will try mapping to it and adjusting the Y saturation in axis tune as you have suggested. Appreciate the response, also what keys do you have your elevation mapped to? If the axis does not work out for me I can try the key mapping.

Not sure if this is the correct forum for this issue but I have been unable to adjust the slew rate on the Radar Antenna Elevation switch. It is very difficult to adjust the altitude range with the numbers moving so rapidly. Also, what is the purpose of the elevation being able to go to such extreme negative altitudes, i.e. -121000 ft?

@almullao, very well said and point taken, I like the JF-17 and I will take your advice and enjoy what I have. Salute to you sir!

SOLVED: The issue was the VAICOM profile for DCS, it was not allowing communication with the AI towers or AWACS. I disabled Plugin Support, created my own profile and now everything works fine. A user suggested this fix, I can see now why the Voice Attack devs nor VAICOM made this suggestion to me, it was purely a business decision. So VAICOM sucks and I will use Voice Attack without it from now on.

@L0op8ack, thank you for the response as I believe you are on the dev team correct? If ED did downgrade this module it would be the last one I purchased from them. I like competition, fair competition, not people who get whiny when they can't win all the time. Salute to Deka, the JF-17 is a great aircraft!!

Question in the title.

So what has everyone's experience been with the JF-17 in MP the last few days? It seems as if the aircraft's performance has been downgraded, can anyone else confirm a similar experience? For example, degraded turn rate and or weapon performance.

Thanks to everyone for their input, the JF-17 is an outstanding model and I'm sure Deka will address this issue, it causes undo stress during the mission when you know you are going to have trouble getting the elevation set properly so that you can locate and engage your targets.

Problem solved using these cockpit view commands.

@AeriaGloria, I changed every slew setting on the Special Options page and none of them had an effect on the antenna elevation slew rate. If you have had success with this please post the exact setting you changed that had an effect on the slew rate.

I use Track IR in game and am having a lot of trouble seeing the upper row of buttons on the center MFD, as this is where I normally have the radar it is problematic to say the least. The upper portion of the UFCP seems to stick out too far forward, partially obscuring the top row. Is there a fix for this that anyone knows of?

Thanks Ranma13, I tried that and just hoped there was a better solution! I guess I'll be leaning back from now on, salute.

I use Track IR in game and am having a lot of trouble seeing the upper row of buttons on the center MFD, as this is where I normally have the radar it is problematic to say the least. The upper portion of the UFCP seems to stick out too far forward, partially obscuring the top row. Is there a fix for this that anyone knows of?

Is there a flight manual specifically for the J-11A?

Thanks for the reply Greyman but none of the information in the thread applies to my situation. I have the most up to date VAICOM dll, the correct version level of VA and no Update folder or update.cmd file present on my machine.

For the last week each time I start Voice Attack I get a notification that VAICOM PRO wants to install an F-16 and a Chatter update. I have installed them and the version of VAICOM is up to date however it wants to install every time I start the program. Any advice on how to resolve this would be greatly appreciated.

I pursued this issue with the Voice Attack developers and here is their response: Originally Posted by Hollywood_315 Thanks for sharing the log. It states a script is missing a particular 'Callname 1' input parameter. This appears very specific to J-11 and not seen in other modules i.e. problem seems to originate in the module code. The plugin does not use this parameter but, since the script halts, the voice command cannot complete. Suggested to contact the module developers for a fix. What you can try as workaround in the plugin is switch off these prefs: Force NATO ATC names / callsigns. May have some effect so worth a try. Grtz So the root issue is with the code for the J-11A not containing the proper callsign programming to allow the aircraft to communicate with ATC. Please provide a fix for this coding error. All other FC3 aircraft are functional with Voice Attack/VAICOM and the J-11A should be functional also.

Just created a mission at Tibilisi for the J-11A after closing DCS, making the change on Preferences tab, closed VA and restarted, restarted DCS and created the mission, opened the mission and am getting the same results, no comms at all. Thanks for the suggestion but no joy in Mudville tonight.