Japo32

@Hollywood_315 These are also discovered and some of them are very important. Had to add them to the first post: 1. The most important one: AG Attack Mode Pilot and AG Attack Mode Target doesn't work. These where working previous to this one. I thoght that this was because the lantirn new selection mode by Yester was overriding the logic of Vaicom, but not installing the Lantirn produces the same problem 2. Switch Lantirn changes the first time to the TCS (Television) if I was in Lantirn view, but quickly it changes back to Lantirn. Commanding again to switch Lantirn, don't do anything. It remembers me the first bugs that I posted, where something is overriding th logic. 3. Don't know if this one is in this update. Toggle PDSTT/PSTT do not change from PD STT to PSTT. I go back to the RIO cockpit and always is set PDSTT 4. Command MAP [1-10] to point 1-3, fix initial etc, works with only some points: (Defense, home base and danger zone). Don't work for points1-3, fix, IP, or surface target 5. Aceman Orbit destination doesn't work. I think this is normal, because we don't introduce the radious nor the direction of turn. Usually Aceman commands are not very important but the fly to destination (works) and this one are very important to play as human RIO in single player while don't want to jump into pilot seat continuously. Neither works the orbit map marker. 6. None of the RIO Grid options works. Only Radar Stabilize, and Map Mark [0-10] to Grid function. Appart from RIO module I have seen these problems also with normal Vaicom: 1. (undefined) repeat don't repeat anything of what the communications (AI or ATC) says. Don't know if this worked some day. 2. (Crew) Request NVG don't install the NVG or changes to HMD. It has to be done via Menus 3 (Crew) Stow Boarding Ladder don't do anything (this is a totally minor one) 4. (ATC) Approach Overhead, doesn't do anything. Don't know if this was always this behaviour as this overhead feature don't appear on menus. 5. (ATC) Approach Instrument don't seem to do anything. 6. (flight) Anchor at SPI / Point / Steerpoint don't do anything. Don't know if this is a bug or the way to make it work. Any suggestion? 7. (flight) Make Recon num Miles don't produce anything. It has to be made via menus. I think this is important with the new helicopters comming. 8. Appendix Directions Fron the (north, south , west, east) commands do show in the VoiceAttack msg but the units don't follow orders. They just attack directly to the target. Don't know if this was always like this. They seems to be a lot, but not at all!!! there are 1198 orders I give to the Vaicom and most of them are ok. But I think the most important one for me is the pilot/objetive RIO A/G mode. The A/G mode is stuck in pilot mode, so we cannot use Objetive mode in multiplayer without a human rio. Of course the issues with the lantirn are also important I think. Thanks!

Hi @Hollywood_315First say that thankyou for updating the Vaicom program Is well appreciated! Ok here we go. I am making the spanish conversion of the latest commands and I found this issues. Have to say that the language is not a problem here as it recogizes the instructions and command them. I have used spanish version for a long time. 1. This is not lantirn one, but If I command Jester to be silent, he won't. I think this is important for our peacefull flights!. He continue giving "nails" rwr callouts. 2. The Kneeboard Extension don't recognizes the Clear notes. Of course the end of dictation is commanded before trying to clean everything. 3. Lantirn Laser: Don't know if Latch is activate or deactivate Laser (languaje barrier) but it seems to activate it. When I want to toggle the laser with laser toggle command, Jester stops firing the laser, but in 2 seconds or so he arms the laser and starts again to fire it (the L appears blinking). Don't want to burn my laser! Please help! 4. Track QHUD and Snow plow don't work. If I select a steerpoint with QDES and the Lantirn goes to that point, then after I command Snow Plow or Boresight, it jumps to the bore or snow, but quickly returns to the last area that was selected in QDES. Undesignating the lantirn don't work for this. 5.selecting other point (home point, inicial point, fix point) the lantirn becomes crazy, jumps to the point and then returns to the QDES one and then try to return to the selected not steerpoint one. 6. Selecting any target (surface, tanks, ships, etc...) the lantirn don't turns into point track.. just area track, so if the target moves then the point will be in place not following the target. This are the first bugs/Issues I found. Of course they can be my fault, so for that reason it would be great if someone could test them. Thanks!

Añadido el JF17

Thanks for the clarification!

Like to here it! Thanks!

no, I was saying heatblur fix something from their F14, so they would break anything in Vaicom. Vaicom it is true it is the last in the line, as any change in DCS would break the F14, so would break Vaicom... so we would need first ED to fix the stuff, and then Heatblur fix their stuff to let Hollywood make Vaicom compatible again... But I would like hollywood to explain the stage of his product, also sometimes. I don't read him a lot latelly, even in support areas. And that worries me a little.

long time problem not fixed.

And also fix the broken radio or tacan commands that were working previously and now not. I don't know you, but I don't want to wait for Heatblur to fix things, because we even don't know if they are going to fix things or change them. Previously once we had a beta update we had our vaicom update the next day or so. Now for some time we do not, and I am starting to be worried about the continuity of Vaicom. Hope soon we have some good news.

I am in, if they release something great. Because the apache will be great, but very easy to fly. These type of small helicopters are great for fun and help the apache a lot. BUT they have to do things right, and for now they only have a Gazelle, that don't fill the bar to everyone. We will see.

I am not a fan of this P47D sound engine. After closing the canopy it doesn't sound as other propeller planes but anyway if it is as it was. What is strange to me is not hear anything of the landing gear motion up and down. Totally quiet. Is that normal also? What a cockpit sound attenuation it had!!! (also don't hear the low throttle landing gear warning sound. Don't know if this was in the real plane)

Hi! I started today with this campaign and the first mission was a blast see so much bombers in the air, plus not bad performance in VR (sometimes some lag fps suppose becasue spawn of other aircrafts) But when returning I was with my group and suddently they turned 180º and climbed. Leaving them I put channel D radio and said "inbound" but the field told me "go to alternative" hahaha Because I didn't know what was my alternative I landed there (there was not hole in the runway or anything) and I received a flare to allow me land... It was funny and just wanted to let you know. DCS things.... XD PD: ED has to fix the AI.. they are crazy turning, climbing, changing speeds... if at least they could communicate what they would do in future inmediate action.....

well... Stable is here.. so hope see the update of Vaicom soon. DCS 2.7.7.15038 (digitalcombatsimulator.com)

@Hollywood_315have a big bunch of changes to make in a future update. Previously he usually made the updates just not so many days after the beta updates (even, sometimes the same day of beta-release). Now we have to wait more, I think to the release of the stable version... but stable came with the Mosquito and still we do not have anything. I am starting to be worried about when DCS change all the ATC system what will happen with VAICOM.

Yes.. I could do it. I was watching a video I made on September, and I rotated it. Now I cannot. It don't show the icon to rotate it. @BIGNEWY

I think I could in the past.... Maybe I am wrong but I think I was able to rotate the wheel. Now there is not icon in the knob of the directional gyro.

I try to make a short takeoff so I go to vrest,/sto, then on ODU I press FDAT and activate GWND, typing in the UFD any value as for example 132/05 and it doesn't change.

found the problem. It was wrong in the first tutorial mission because the carrier was 44x. The same as Kobuleti. I downloaded a spanish translation of the tutorials.. which still had 44x. Now it is 46x and it is ok.

I made a search and didn't see anything. If you run the carrier landing tutorial, and you set the carrier tacan, you will see that the tacan symbol is is not in the right position of the carrier in the EHSD. You can see how the pointer is one direction and the RWR emitters comes from other directon. More visual once you have them on sight. Someone told me that is an old bug that has never been solved. I remember I had this issue some months ago (maybe February this year when I tried?) Just wanted to report in case noone did it.

Sorry to reply with a post more than a year behind, but I cannot make this work. Put the datalink switch to AUX don't show anything in the TID from my AI wingman. Also setting 300.0mhz don't do anything. I don't know if I have to set any parameter in ME to make it work. Edit: I see they are transmiting their position in 300.0mhz but I cannot see anything that they identify. So Datalink only show their actual positions.

Sorry for resurrect this post (well we are near halloween XD), but I was learning about the non done functions of the CAP and "landed" here. I have the viggen and I think is amazing the elint feature it has to recognize the battlefront. I know that is very limited in DCS right now, where all missions all the recognition intelligent has been done before, but I think this tasks will be more important in future, with the new upcomming dynamic campaign. So before attack, we have to know where are the enemy troups. Hope this TARPS pod is implemented in future.

No se si os pasa, pero tanto módulo produce una empanada mental brutal, por que en realidad todos utilizan más o menos las mismas soluciones pero por diferentes caminos, y cuando dejamos de volarlos, volver a ellos es una laguna de "como se hacía esto". Soy persona que aprende por videos y me apoyo en manuales, y para recordar me voy a Grim Reapers, Jabbers, Red Kite o quien sea, pero estaba un poco hasta las narices de tener que encontrar el minuto exacto que hablan sobre tal o cual sistema, así que me puse a hacer videos sobre como funcionan los módulos que conozco y más complicados, para revisitarlos más tarde y recordar. No están indicados para aprender de cero, pero sí que una vez conocido el sistema pueden hacer ver otro punto de vista para afianzar, y además están recien hechos así que los últimos cambios (no los futuros) se ven incluidos. Espero que los disfruten.

In the last update (don't know if was produced previously, the ADM 141 decoys don't extend their wings to glide. They do it right glidying but visually their wings are stowed. edit: oh.. didn't see this one. Sorry

Hi! I try to kick this failure in 1 minute 100% and it doesn't do it. Nor left or right engines. Other failures are produced normally. There is one that produces fire (Turbine failed) but I cannot stinguish the fire following the procedures after depressing the fire extinguisher bushbotton and climbing decelating.

Thanks!

I have an issue with the navgrid. I tell Jester to show it, and all is ok, then I center it to the aircraft and it removes the navgrid showing the normal non ground stabilized radar mode. If I go to the wheel navgrid options it says that the navgrid I can disable it, and when I press it, the navgrid appears again, but of course Jester disable it, so I have to press again "enable navgrid" to show it again. Sometimes it doesn't change, but modifying other parameters as number of sectors, coverage etc, may change to the normal view of the radar. A PITA.