Goliathus

Hey, I´m running the latest DCS OB version and am running it with the multithread option. I´m seeing impresive improvement, except some random stuttering when my FPS drops from 50 to single digit numbers in a split of a second and then back. Anyway, this is not what I wanted to report. I came across a possible bug flying the F/A18C with the datalink pod and SLAM-ERs. Since the last update if I link the SLAM-ER with datalink pod, I get a picture instantly on my AMPCD after I turn on the datalink pod. This is something that shouldn´t be happening, because the SLAM-ER is still onboard and should turn on the video only few NM before reaching the target. The fun fact - the picture on the AMPCD stays on even after the SLAM-ER is destroyed and there shouldn´t be anythink sending any signal to the datalink pod. This bug happens 100% of times I tried this and is simple to reproduce - just take a SLAM-ER and a datalink pod onboard, turn them on. You get the picture as if the SLAM-ER was already fired. Maybe this is something realted with the bug when GMT radar gets mixed with the map radar - it is possible that the bug I´m experiencing is in fact a datalink pod picture mixed with ATFLIR picture. I will enclose only a screenshot at this time and a track replay, but it is from a complex mission that I flew recently and is 1 hour long :/. On the screenshot you can see there is a picture on my AMPCD when datalink pod page is selected and that all SLAM-ERs are still onboard. Thx, Goliathus Btw. I run DCS on my DELL G7 laptop (NVIDIA 2070 RTX Super and i7-10750H CPU 2.6 GHz, 32GB RAM) Slam er bug.trk

Thank you for your response. The issue I´m experiencing is that I get no response from the ACLS at all. Not even the "landing check" light. It behaves like if my plane isn´t communicating with the carrier at all. TBH I was able to connect recently once and use the ACLS and I did only one thing differently than any other time - I switched to the RIO seat and set everything manually instead of using the Vaicom Pro plugin (to connect to the link of the mothership). I´m pretty sure I did everything correctly even when using he Vaicom Pro plugin and it does work in my test mission with this plugin. Unfortunatelly I didn´t have enough time recently to test this more, it is possible, that the Vaicom Pro stopped working after some update and is not able to set the link despite the fact I get the correct response from the AI RIO (we have this very same issue with removing the wheelchocks etc.). So I will test this more once I´ll have more time and check if the AI RIO is able set the link correctly when I give him the order via Vaicom Pro and if I don´t get any proper response from the carrier, I´ll switch to the RIO seat and check it manually. If there is enything wrong, I´ll set the link manually and see if it makes the ACLS to work properly. If yes, then it is clearly not DCS related.

It seems like there is just an Vaicom issue with the wheel chocks at the moment. Probably something got messed up after a certain update and it should be repaired by the new Vaicom team. If it works with the F10 menu (it works that way for me, and I'm experiencing the same issue using the Vaicom as you described) it's probably not DCS related.

Hey guys, this is meant to be a general question, this is why I don´t attach any files. If it will be necessary, I´ll add them later. I play solely SP and I like to play the Liberation dynamic campaign. I have everything up to date (DCS Open beta, latest DCS Liberation release). I fly mostly the F/A-18C and am fully aware, that the ACLS is not functioning at all it there are more aircraft in the mission involved and is pretty useless until this will get fixed. But is this the very same with the F-14B if you use the DCS Liberation? I tripple checked missions in mission editor and there is everything setted up correctly, so there are only two possible conclusions. First is, that the problem rests somewhere between my monitor and my seat (me) or it is messed up in DCS. To make myself clear, I know how to use ACLS in the F-14B and am able to land with it in the missions that I created for this purpose (yes all the settings are very same as in DCS Liberation created missions, so they should be "ACLS" identical). But obviously, if I fly a DCS Liberation created mission, I get only the VOICE message and never anything other (LANDING CHCK etc.) and am forced to land by myself. So I´ll try to ask a simple question - is there anyone who plays the DCS with DCS Liberation, is using the Supercarrier, fly the F-14B (singleplayer) and is able to land the CASE III landing via ACLS? If yes, then I can try to post my trackfile, mission file etc. to see if it´s me, but I´m strongly convinced that this is ACLS not working properly not even it F-14B at the moment. I´m relativly new to the F-14B and I was learning to fly it manually, so I didn´t try the ACLS in the past until now, so I can´t say if this was happening from the very beginning. But as I said, in a sterile enviroment created in my own mission I am able to use the ACLS and it is working there - if I´m the only aircraft in the mission. Thx and Happy New Year to everyone. Goliathus

Actually, the ACLS isn't working properly even in single player. From the very beginning, I didn't see the tadpole and getting the P/R ACLS message at all, not even once, if there where any other planes present in the mission. I'm able to manage the ACLS to work only in a very sterile environment - if I'm the only plane in the mission. And that is not what I consider being fun. So until they'll fix it so you could use the ACLS in a causal mission with some AI present, it's useless and not worth of trying.

If you want to scroll to another page you should use voice command "x page" where x should be the name of the page you want to open. For example "awacs page", "ATC page" "JTAC page" etc. You can use callsigns instead of x: Awacs = Overlord ('overlord page' command opens the awacs page same as the 'awacs page' command) etc.

It happens to me all the time when flying the F-14, and it is obviously connected somehow to the Supercarrier bubble because it always happen near the carrier. In the last few days this issue occurred even when I flew in the F/A 18, but it was a mission where were plenty F-14 in the air too. It never happened before to me in the F/A 18. Maybe there is something interfering between the SC module and F-14.

Please repair the "Request NVG" command, because the crew responds "copy" and then report "rearming complete". To be clear, no rearming is completed and no NVG is installed. This issue lasts for at least few month since I bought the Vaicom Pro licence, it´s not community patch related; if possible - make the AIRIO capable of storing spoken waypoint coordinates and set them as steerpoint (at least I didn´t find any Vaicom Pro command for this function);

I can´t stop laughing after reading this thread. Don´t take this PC game too seriously guys. You ain´t no real pilots, you´re just gamers having fun operating good looking pixels on your monitor screen So enjoy the game we all love with everything it brings and stay passionate about flying. DCS is a great game and a great simulator even with zombies onboard for few days with extra fun

Look here please: Goliathus

This is why I regret being a lawyer instead of IT programmer While I was thinking about the intellectual property of Hollywood, someone actually found the solution. Well, as one use to say - lawyers can find a problem on any solution Great thanks to you guys for making the fix and bringing Vaicom Pro back to life for now. I'll test it today. Goliathus

Well yeah, some arguments are just pure verbalized frustration. You can´t buy something that is not for sale, or when its owner isn´t here anymore or is not available... You can´t just steal the mod with whole know-how and continue its development just because someone dropped its support. At the moment there is no future for Vaicom Pro until there is an official update, which probably won´t happen. In this forum it is obvious, that there were a lot of Vaicom Pro users and that it was important part of DCS experience for many of us. Now we can call it a gap on the market, which can be filled by anyone else, who is able to do so. Maybe Eagle Dynamics will fill this gap someday, but I´m not sure if this will happen at all as we can see they´re busy with modules they already sold, and that it takes years to finish modules that were in early access. They have limited resources, so they must use it wisely. We´re still lacking other important stuff as well, such as (official) dynamic campaign... But aircraft simulators aren´t the main focus of the gaming market, we are not that big community, and there is no way that any company could keep itself alive just from us buying a single modul years ago. This can´t finance the support for this very single product in the next few years, so they must divide their resources between old modules and new ones (new market opportunities) and can´t focus on big new tasks and try to finish them in just couple of months. So I´m not being very optimistic and won´t expect the ED to do about Vaicom Pro issue anything, it´s not their business and building a new similar mod would cost resources. But - it is a new business opportunity, I´d definitely buy it

Very same here. After the update it takes second for all textures to load. I can look around though while textures are loading and thus I know, that it isn't caused by the lag. Another thing is, that this happens also in the mission editor, where it takes seconds for the map to render details. This never happened to me in the 2.7 version and seems like bad optimization to me. But that's why it's called open beta. Please ED, if you need any additional information about from us to solve the problem, let us know. Goliathus

TBH I don't think Hollywood's disappearing was voluntary. Anything happened to him happened too fast for him to arrange things otherwise. It doesn't make sense after all his previous support to just leave the project without any brief explanation, if he knew this in advance. So we can only conspire or to cope with new reality. It is not ED's responsibility to manage their updates in a way that no other third parties mods will be affected. At the moment they should try to implement something similar to the Vaicom Pro, even if it was a paid module. I don't know how to fly the F-14B without the Vaicom Pro and trying to force the Jester to operate the radar using the wheel commands while in combat. It can be done, but it's a immersion killer and too slow to work.

For the guys searching how to do cleanup and DCS repair - follow this link, it's easy to do: https://www.digitalcombatsimulator.com/en/support/faq/repair/

Actually, it is not that hard to make the regular comms work again. I did this yesterday. I'm not sure which steps were necessary, but I did this: closed DCS World Opened the Vaicom Pro settings reset its preferences (only preferences) in the settings menu quit the Vaicom Pro I did (both) the cleanup and quick repair of DCS as in this link https://www.digitalcombatsimulator.com/en/support/faq/repair/ restart PC that's it Just to make it clear, I didn't open the Voice attack after running the cleanup and DCS repair to be sure nothing gets reverted back. Does this solve the problem for you too?

At the moment there is an intense communication on the Discord about this issue and someone said there are plenty of third party modules affected by the 2.8 update. He said also that maybe they found a solution for the Vaicom Pro to make it work again. If this will be true, I´ll post the solution here. But it´s just a dream at the moment. I find this frustrating, because to me the Vaicom Pro plugin was the main reason why I started to fly the F-14 and found out later, that it adds so much immersion to the game, that I don´t want to leave this behind. I can only hope, that someone will take over this gap on the market after the Vaicom Pro was abandoned due to any reason. Maybe this could be a good idea for the ED team to start working on something similar, at least they´ve got the codes they need

There is nothing you can do about it at the moment. This is discussed in the forum already, no modules are recognized by the Vaicom Pro plug-in anymore after the update. At the moment you should consider Vaicom Pro as a dead project, it doesn't seem like you should expect any update of the Vaicom Pro. Noone knows what happened to Hollywood who made it, he kind of disappeared in April this year and we only hope he's well. Since April there is no connection with him, no updates come out, no support nor response from him. So it the 2.8 version broke the way Vaicom Pro works, it's done At least for now.

Yup, looks like this is it for the Vaicom Pro. This is a HUGE loss

I run the 517.48 GeForce drivers and I´m s till experiencing this issue in October 2022. I fly the F-14B solely in singleplayer and using the Liberation campaign mission generator. I´m able to finish maybe only like 40 % missions without DCS freezing, it´s so frustrating Approximately 95% of the game freezes happen when I´m on my way to RTB (that´s at least 45 min or later after running the mission), not too far away from the airfield or carrier. Everytime the freeze occurs while sitting in the cockpit and looking elsewhere than straight ahead. The DCS is only SW that freezes, the opentrack keeps running, the DCS Liberation campaign keeps running and the Voiceattack with Vaicom Pro plugin keeps running as well. I can´t think about anything I do to trigger the game freeze,. Theonly connection I can think of is, that it happens usually after I look behind my back or to the sides of my cockpit. But I can´t be sure about that, because you have to look around you all the time in this game... And maybe that I already called the inbound while ago. Is there anything we can help to identify this problem? Here is my log from the last game crash. Thx, Goliathus dcs.log

I was experiencing the very same thing when I was new to the F14-B, regardless if I was on a carrier deck or on the ground. I had to reverse the brakes axis setting, it seemed like my brakes were "pressed" all the time and reversing made them work properly (so brakes went on only when I pressed pedals, instead of releasing them only when applying pressure on pedals). Goliathus

As Foka said, you did correctly store all coordinates to all stations and for all TOOs (1/2), but you forgot to change the TOO1 to TOO2 on some stations before releasing the second half of your bombs. Your bombs always follow the coordinates preloaded on the very exact TOO (1 or 2) that was selected at the time of release. It doesn´t matter that you dropped first bomb from that station to the TOO1 coodrdinates, it won´t automatically switch to the TOO2 for the second bomb on that very same station. You must do this manually for each station if you don´t want to hit the same target with two different bombs. In the Hornet it takes few clicks to drop 8 bombs on 8 different targets on a single run. You can ripple 4 bombs at once easily with holding the pickle button, but then you quickly have to manually change all TOO1 to TOO2 (for each station!) before releasing another 4 bombs.

Hi guys, can you help me please what is the proper command in the F14 for the Jester to enter new waypoint coordinates into the computer via Vaicom Pro? Model situation - I fly DCS Liberation campaing and my mission requires more than 3 steerpoints navigation. I´ve got more steerpoints coordinates in my kneeboard, but I´m unable to tell the Jester to change the preplanned steerpoint 3 coordinates to new ones (so now the steerpoint 3 will be changed to coordinates of a "steerpoint 4"). I don´t use the Jester wheel when using the Vaicom Pro. I found a kneeboard with some of the Jester Vaicom Pro commands, but there is nothing such as changing coordinates manually (only restoring waypoints). But I know this kneeboard isn´t a full list of commands, because there is no command to change the frequency either and it is possible via Vaicom Pro plugin. Thx, Goliathus

Hi Str][ker, are you trying to hit tanks or a building? It you´re targeting tanks, it is pretty common that after the first bomb imapcts, other targets start moving and thus they won´t be hit (directly or at all). This is just a simple guess, what can be your issue. Another possibility is that you don´t use TDC depress after you find your target with ATFLIR, so the new coordinates won´t get to the next JDAM station. This could lead to hitting the same spot twice instead of hitting two different targets. Goliathus

You ask how you can acquire and maintain lock no matter what even on enemy using jammer. You can't, this is the whole point of jamming. If there was anything you could do about it, the jamming would become pointless. To be honest, jamming in DCS is probably not a simulation, it's just modeled 'somehow'. I'm pretty sure this can't be simulated because documentation about jammers is probably classified. This why it seems like jammers in DCS make it impossible to maintain lock until certain distance and 'simulates' what would jammer do, if used properly. So no, you can't maintain the lock, just try to maintain your SA.