Japo32

I will reply in this email making changes to it, as I re-test with new indications. I will do the reset VoiceAttack and DCS switching between modules: 4. AJS37 Viggen - Still the same problem. Voice commands to move between menus are seen, but not command anything. Only keypress or mouse selection. Tested to be in the right frequency with overlay of SRS to see if was tunned correctly. Also tested without SRS to see any difference (not at all). Also checked that only menus are shown and can be selected (but not commanded with voice as said) if VOIP Control is set to "dynamic switching". "TX Link" the menu don't show once called. no beep heared from vaicom, and even deselecting "disable menus" becasue it shows an ·listening suspended, and "Broadcast Parallel" shows the menus but any voice command to select any option is not allowed because an "listening suspended" problem. 11. F86F - Same problem. Because there is a difference here between me and you, will post the options that I have set in Vaicom: I made a reset of LUA code in reset options to see if there is any difference but nothing. Again, I made a mission with the plane ready for takeoff in kobuleti with channel 1 set to 262mhz, but the takeoff quick mission also will set the right frequency on the radio. in "DxLink" or "Broadcasts Parallel" still the same problem as I have the problem of "listening suspended" with those options. The "disable menus" options will make appear the menus, but in the press of the PTT, but won't be allowed to choose any option by voice as it disappears once PTT is again pressed, or with "dynamic Switching" it just makes also the menus disappear without any option choosen 22. Mi24 - Same problem. Just made a mission with the mi24 on air with the right radios already set, and the menus don't appear. The "disable menus" makes the same behaviour as with the Sabre. It will appear with ptt push, but will disappear once the command is given, so if there are nest commands, there will be a problem as I cannot choose it. At least in can be selected with mouse... but why we should have vaicom on, in this cases? not going to test more modules as it is time consumming and I have seen with those 3 that still I have the same problem as previously. If there is a difference between me and you, then there has to be a configuration option different. for that reason I put my config selections to try to find the culprit of those issues. Thanks!

Hello! Because I am tired of waiting for a fix from @Hollywood_315on the multiple issues that Vaicom has, I have decided to share a list of the aircrafts that works for me Vaicom or not. And that way it can help others to try to find solutions and new people to share if it is working for his module propertly or not. For testing I just call the "show options" and "menu item #" to see if the manus appear or not, because that maybe is the most important command to work in Vaicom (all can be processed through menus with voice at least. For testing I am loading two quick Caucacus missions. One on ground with engines running and other free flight. I have seen that there is a problem on some aircrafts when flying. All are with complex communications, but if one of them doesn't work also will put if it works with simple communications. 1. A10c I&II - No problem 2. A4E-C - Works on Ground but not on Air (menus don't show up). With Simple Comms, no problem. (I just put this one that is a free one and it is known Vaicom don't support mods) 3. AH64 Apache - On Ground (OK - QMission=HotStart) - On Air (sometimes when takeoff from quick mission on ground. On Mission editor airborned start NO WORK (menu don't show up) with Easy Comms = All works ok. 4. AJS37 Viggen - No problem With Menus, but they don't do anything. They have to be selected with mouse to interact. This problem even with Easy Comms on. 5. AV8BNA Harrier - No Problem With Menus 6. BF 109 K4 - No Problem with Menus 7. C101 - No Problem with Menus 8. F14 - No Problem with Menus (have several problems with AIRIO module). Here the list of all the problems with Airio: 9. F16 - No Problem with menus 10. F5-E - No problem with menus 11. F86F - On Ground Don't work (The menu appears but disappears inmediatelly) - On Air, the menu appears, but once selected an option that has other options nested, it disappears as on ground, so no possible selection. Works on ground and air with Simple Coms on. 12. F18 - No problem with menus 13. FC3 planes - No problem with menus 14. Fw190A8 - No Problem with Menus, but they don't do anything. They have to be selected with mouse to interact. This problem even with Easy Comms on. With easy Comms it can accept orders as "anapa, inbound" with realistic comms those type of orders won't be "heared" 15. Fw190D9 - No problem with Menus they appear, but they don't do anything. They have to be selected with mouse to interact. This problem even with Easy Comms on. With easy Comms it can accept orders as "anapa, inbound" with realistic comms those type of orders won't be "heared" 16. i16 - Works on Ground,but on air the menu don't show. With Easy Comms on, the menu appears on air, but after first second selection on nest options it dissapear 17. JF17 - No Problem with Menus 18. K50 - On Ground the menu disappears as soon as it it called - On Air, the menu appears, but after first selection in options, the second selection the menu disappears. With easy coms on it is worst, as in air, the menu just disappears once called. 19. L39 - No problem with menus 20. M2000 - No problem with menus. 21. Mig21 - No problem with menus 22. Mi24 - On ground no problem - On air the menu don't appears when called with Vaicom - With Easy Comms on, no problem. 23. mi8 - On ground the menus disappear just when called - On Air they are ok - With easy Comms on the menus on air also disappears as the ones on ground. 24. Mig15 - On Ground the menus disappears just when called - On air, the menu appears, but after first selection it disappears. Have to be operated with mouse or keys - With Easy Comms on, no problem with menus. 25. Mig19P - No problem with menus 26. Mosquito - No problem with Menus 27. P47D - No problem with menus 28. P51D - On Ground the menu disappear just when called - On air it appears once but if I choose anything it disappears - With Easy Comms no problem 29. SA342 - No problem with menus 30. Spitfire - On Ground the menu disappear just when called - On air it appears once but if I choose anything it disappears - With Easy Comms no problem 31. UH1H - On Ground the menu disappear just when called - On air it appears and I can make the first selection but the second one disappears the menu - With Easy Comms on, it is even worst as the menus just disappears when called on ground and on air. 32. Yak52 - No problem with menus.

Thanks for the assist. In Norm or in Multi don't make any difference. It seems that is ok when I takeoff when engines running, so I can call the menus by voice on land or after takeoff, but if I make in the mission editor a single Apache just flying, then I try to call the menu options with Vaicom and it won't appear. As said, if I start from gound yes... and even after takeoff it appears. There is a quick mission in Marianas called Battle for Saipan: highway, that starts on ship and all menus appear right, Just when airborned we have the problem. Don't know why in one of the missions appears right and others not Here is the track of my built mission to try. ApacheNoRadioAirborned.trk

Don't know what it is mean to set all the radios to 4 way switch. I already had it this way, and never worked. Only with simple communications..... and still no patch.

I have this issue also. Both com knobs are up... but when contact with ATC, there is a reply but not audio. In backup radio the same, and the volume of backup radio is also maximun volume.

What worries me is the long time to reply. That, with the lack of communication here and time to have real updates, seems that Vaicom is dying. Hope I am wrong.

Still this problem persists as I see.. Rain3 not show raindrops.

Hello! I wanted to add this video I have made of how to export your model with animation from Blender to DCS. Of course still lots of things are needed to learn to continue tutorial series about physics applied into animations, etc... but it is s first step that hope helps people around with all these tutorials put in here this forum.

Thanks a lot! I was able to see the texture in DCS. It was a typo problem and very easy to do it! Now it is time to start understanding how to apply the physics into the model. But first I wanted to show my "how to" to the people. As said, I was not only going to ask, but also offer to do things. This is a video I have been making for everyone and also me in future (as Blender is not intuitive with it's shorcut hotkeys), of how export your model (not have to be a plane) from Blender, to DCS World. Hope it helps people as there is not so much information of how to do things. It is in English and Spanish to spread more the knowledge. Thanks.

For me the problem still with the Yak is the engine management. It just goes to more than 150º oil temperature, and that should break the engine, because it remains all the time there even the cowl flaps or refigerators are all open. Would like to see at same level as the wardbirds.

and @Hollywood_315missing. There was a time I recomended to all my viewers, buy Vaicom.. but now is the opposite.

I think even the AI were good, they shouldn't use it for the Dynamic Campaign. I think is not necesary, and the only things they have to simulate is the virtual movements of those units WHEN the AI is not in the bubble of the player flying or viewing. In fact, there are already custom dynamic campaigns done with scripting. If they have to put CPU ussage computing the real behaviour of AI units fighting between them of the whole map, the campaign would be less than "dynamic". This "bubble" was the solution for other simulator. Other thing is the absolutelly need of fixing the horrendous way of AI do things. UFO flying, crashes with terrain, and the examples here put already. Just working in that willl be a major enjoy experience with DCS even non dynamic campaigns developed.

still is forever visible: Also would be nice to see the bombs delay menus in rearm that was annunciated time ago and seen in a video... My Mosquito is waiting for that.

Did someone checkout if the cursor not hidding is still there? There is nothing in todays patch related: DCS 2.7.11.22211 Open Beta (digitalcombatsimulator.com)

at the end was a campaign problem. Default with A10c alone no problem.

I think I tried that, but I will try again. Thanks!

yes... it was supposed... but..... I suppose the testing was not made deep.

I am learning everything from here: and here: For Blender support, here: But I had to find this links myself. There have to be lots of artists that desists of making any work. In my case, I have been playing with DCS a long time, so I know more or less the way things are done.. but never touched professionally until today. For sure, I wish there where more free and easy official documents of how to do the things. Those documents are from 2015 written by users. If I learn enough I will make videos of how to do the things. I always teach my "tricks" because the problem is not really to know how to do something "that in this case is..." The real problem is join all the energy and effort to be more than 1 year making a product and end it.

Hello! I come from another simulator, and there, a programmer and I joined to make this little aircraft, the Siai Marchetti SF260D, that after release, we developed a military version that today is flying in their sims, the belgian airforce. Have been playing DCS for long time (since lockon) and I decided to jump in it, and see if I could have an third party agreement. but seems complicated as there is not so much documented information. I start to work with this SF260 trying to understand how things works in DCS. For that reason I open this post to concentrate the development of it asking questions "how to" and later showing people those learnings to everyone that want to enter this sim, as I did in my previous working sims. Right now I have a problem. The model exports correctly the textures in model viewer, but not in the sim. Does anyone knows why? I set the path of textures in the lua file, but in the model viewer is different. Should I put the edm textures folder in the same folder of the 3d model as I did for the model viewer? Lot to learn, which is not a problem if there is a clear path to walk.

with easycoms. They do not work. At least in my case.

No, and it is is a shame. This program was good in the past.. but little by little is becoming something near "abandonware" with sometimes very minor updates that even don't work (for example last one of the Apache). I would recomend it to all my friends in the past. Now I don't do it. As said.. a shame.

These are great textures, but I cannot use them anymore when I have to use flir. The terrain has too much "hot" spots when setting the A10c flir to G6, L8. In the default ones almost the terrain is "cold" and the units shines a lot. With Barthek textures are really difficult to find targets. Of course will use it when not FLIR mission.... or if there is any kind of fix in future for the new FLIR.

a10cII problems asking for taxi in 133 no reply.

Today I tried to communicate with kobuleti with the A10cII in 133.00 and nothing. Other things yes are fixed.

Yes... the same....... as always.