Sandman1330

I dropped textures down from high to medium, memory usage dropped by a couple gigs and seems smoother so far. The visual fidelity difference wasn’t really that noticeable, but it’s too bad with such a high end system I had to do that.

To simplify things, and because when I build missions I CAN control the weather, I set the carrier’s course to what it needs to be at 15kts, then put 15kts of wind into the mission at 18* from the ship’s port side and voila, resulting vector is 30kts of wind down the angle. But that’s gaming the system a bit. You can figure out the trig to use 10kts of wind and 20kts ship speed, or any combination, but I don’t math so well so I keep it simple. :)

I think AIRIO is due for an update. I’ve voiced the issue to the dev and I think he is going to take a look at it.

You are right. My VRAM usage is 10+GB, effectively my entire 11GB are in use. Then system memory goes all the way to 30 of 32, with DCS using 25+ of that. I’ve only experienced it since the last bug update though.

Yeah, in the wheel you can just tell jester to tune up the stennis, or an airfield, or a specific tanker, and he will tune the comm radio to the right frequency. A similar command exists for tacan. In vaicom, the comm radio is not implemented yet, but the tacan version is.

Thanks, I did get some help from the Viacom support team, and they indicated it’s not possible to even implement this due to DCS limitations. For others who may find this thread, resolutions / responses for each question: 1. They are looking at including this command now; 2. Coming in the next AIRIO update; 3. They will look into implementing a differentiation between 1-1 and 2-1 callsigns, but it may prove difficult. My workaround for now is to ensure they are on discreet frequencies, and with easy comms off, manually tune the frequencies (or command AIRIO to do it with the frequency rather than callsign) 4. Stated above. 5. Still an issue, I think AIRIO gets confused by the callsign issue in pt3. Workaround is to have jester manually tune by frequency. 6. Nothing to add. They recommend you disable player voice but I like to have it as confirmation the correct command was recognized and sent. 7. Vaicom detects if there are AI units on the same frequency. if there are none, the PTT works normally for SRS and doesn't pick up commands. If there are AI and human players on the same frequency, it listens for a command first. If you don't want to issue a command, you say switch, then it opens up SRS and stops listening for commands. 8. They are looking at my mission and doing some forensics as to what may cause this. 9. Related to a DCS ME issue where easy comms was being forced on despite not being selected to do so in the mission editor options. Maybe a DCS bug but I was able after some random saving and re-saving to clear the bug.

There may be a DCS bug at play here, I had the same issue with a server mission of my design. Even with easy comms set not to enforce in the ME mission options, the check mark for “value” was stuck on and it was still enforcing easy comms. I ended up saving and re-saving a few times, then it just magically started letting me have both enforce and value check marks off, and with easy comms turned off in my master DCS gameplay settings, it now works. TL;DR: It turned out to be mission editor weirdness causing this issue for me,

You may need to do the finish steps in the manual to import the new AIRIO commands into VA.

Truthfully I just keep my foot on the left pedal to keep the ball centered. You can trim it out with rudder trim too

Dedicated server. It's really weird. Sometimes I'm unable to uncheck the value when I uncheck enforce, so what I end up seeing is easy comms turned on, but not enforced. I'm unable to uncheck the value. When it's like this, it enforces easy comms on, even though enforce is unchecked. But after saving and exiting several times, it now shows both boxes unchecked - and now it works. Super weird. I'll have to do some more testing and see if it stays the way I want or reverts itself again

Strangest thing... I have a server mission where I have, in the options, not checked enforce for easy comms. Both check marks are not checked - enforce, and the value. I have easy comms turned off in my gameplay settings, with the check mark selected to apply these settings to all missions. Therefore, the behaviour I would expect is: With easy comms turned off in my master gameplay settings, and the option not enforced by the mission, I should have easy comms off when I join the mission. Another person joining who wishes to use easy comms (has it turned on in gameplay settings) should be able to use it. What I'm experiencing is that easy comms is enforced on, regardless of settings in gameplay. Therefore, when I join, easy comms is on - it is overriding my gameplay setting, without having selected "enforce" in the mission. It is reeking havoc with my voiceattack. I don't want to have to enforce easy comms off, as I want people to be able to have the option. Any idea why it would be enforcing on even though it's not selected to do so?

You can train windows speech recognition manually to recognize specific words or phrases. Open up the speech recognition bar, right click and open the dictionary. Follow the prompts and tell it you want to record new pronunciation and voila. I had to do this for a few of the more non-standard phrases.

Thanks for responding. I have no problem with Voiceattack understanding my commands (I manually added “TACAN Tune” to windows speech recognition). One of my problems is that Vaicom can’t tell the difference between Texaco 2-1 and Texaco 1-1, which are different tankers. My mission I use for testing has 5 tankers, so I have Shell 1-1, Arco 1-1, and Texaco 1-1, 2-1 and 3-1. Something in this breaks Jester’s ability to tune tacan, because he tunes the wrong frequency every time. I tell him to tune Arco, and he tunes Shell, etc. All of this worked fine with the jester wheel. This is just one of the many questions I had in my OP, but it seems to be the one you were looking to clarify? The biggest problem I have now is auto tune seems stuck on, I can’t get it to stop tuning my radios on me despite having those options turned off... more for the vaicom forum as it happens in the hornet too.

Has anyone noticed or had the issue where the recoverytanker callsign (set using the setcallsign command) doesn’t always work, or often will not work on tanker respawn?

Concur. I think not going into burner in the wires (as dictated by natops for F14B) leaves one open to EGIW as well.

The AMD FX professor was the precursor to Ryzen. It came after the Phenom II and unfortunately it was quite a flop, Intel’s then new Core architecture walked all over it. The 6 core FX 6300 I had to buy for Oculus support was slower than the 6 core Phenom II I had before it. I still run an old FX 8350 in my dedicated server. https://www.newegg.ca/amd-fx-series-fx-4300/p/N82E16819113392 https://www.cpu-monkey.com/en/cpu_family-amd_fx-9

Hey guys, I've posted this in the Viacom section and gotten no response. Before I submit an official support ticket, I'd like to ask the community if there are easy fixes / things I'm doing wrong here. Original post: https://forums.eagle.ru/showthread.php?t=275087 1. How do I get Jester to "tune tac" for a radio frequency? I can't find a command, and it would take longer to look up the frequency and read it out to him than it would just to use the wheel to "tune tac"; 2. How do I get Jester to "tune tac" for the new Supercarrier TACAN? It doesn't show up in the list. Same as above, manual tuning defeats the purpose; 3. What if I have more than three tankers in my mission, and therefore need to re-use Texaco (ie Texaco 1-1, Texaco 2-1, Texaco 3-1) because I've already used Arco and Shell; 4. Is there any way to get the Jester wheel back for times when my spoken message just isn't getting through? 5. I am getting no response oftentimes from valid commands. Jester responds affirmative when I tell him to tune the Stennis TACAN, but he doesn't actually do it - or worse, he puts in the wrong frequency! I notice this with tankers especially - I say "tacan tune arco" and he tunes up Shell! Or "tacan tune shell" and I get Arco! 6. Realistic ATC - Doing a Case III, the readback from the player of the marshall instructions is wrong, commence time comes up as 00 every time and I think the DME was wrong too. It seems the entire comms has been shortened, is there a way to disable this and stick with the default DCS calls? 7. SRS integration - I have set it up per the manual, but I am still not clear about what steps to take in cockpit. If I want to make an SRS call, what do I do differently than if I want to make a VAICOM command? 8. Calling for "Status" or "interrogate" activates triggers within my mission. Those triggers are usually done as additional items from the F10 menu (spawning AI fighters). The triggers are all vanilla editor, done by turning flags on/off via F10 menu. 9. Even when having Jester manually tune a tanker frequency, as soon as I request rejoin ("approaching for refuel"), the frequency changes automatically to the frequency of one of the OTHER tankers, not the one I want to use! "Select tunes radio" and "instant select" are unchecked in settings, easy comms in mission on or off makes no difference.

Anyone? Or do I have to submit an official support ticket for all these questions?

I've made a recent post, I'm new to VAICOM but I'm finding that Jester very frequently acknowledges my order, but doesn't do it. Tuning TACANs is the big one I've noticed - he'll roger the request, but not make any changes.

Good day, Just got VAICOM - struggling through the setup but making progress. I bought it mostly to control Jester in the F14. Question: If a mission has more than one Texaco (Say, Texaco 1-1, Texaco 2-1, etc), can I have Jester tune 2-1? It seems right now the commands only exist for Arco, Shell and Texaco, with no provision for additional flights. Thx Edit (many edits as I add questions along the way): Further questions: 1. How do I get Jester to "tune tac" for a radio frequency? I can't find a command, and it would take longer to look up the frequency and read it out to him than it would just to use the wheel to "tune tac"; 2. How do I get Jester to "tune tac" for the new Supercarrier TACAN? It doesn't show up in the list. Same as above, manual tuning defeats the purpose; 3. My question above, what about when there are more than one Texaco? 4. Is there any way to get the Jester wheel back for times when my spoken message just isn't getting through? 5. I am getting no response oftentimes from valid commands. Jester responds affirmative when I tell him to tune the Stennis TACAN, but he doesn't actually do it - or worse, he puts in the wrong frequency! I notice this with tankers especially - I say "tacan tune arco" and he tunes up Shell! Or "tacan tune shell" and I get Arco! 6. Realistic ATC - Doing a Case III, the readback from the player of the marshall instructions is wrong, commence time comes up as 00 every time and I think the DME was wrong too. It seems the entire comms has been shortened, is there a way to disable this and stick with the default DCS calls? 7. SRS integration - I have set it up per the manual, but I am still not clear about what steps to take in cockpit. If I want to make an SRS call, what do I do differently than if I want to make a VAICOM command? 8. Calling for "Status" or "interrogate" activates triggers within my mission. Those triggers are usually done as additional items from the F10 menu (spawning AI fighters). The triggers are all vanilla editor, done by turning flags on/off via F10 menu. 9. Even when having Jester manually tune a tanker frequency, as soon as I request rejoin ("approaching for refuel"), the frequency changes automatically to the frequency of one of the OTHER tankers, not the one I want to use! "Select tunes radio" and "instant select" are unchecked in settings, easy comms in mission on or off makes no difference.

I’ve had the blackout on launch issue occasionally as well. Though I haven’t extensively tested, my initial impression is it seems to happen more when the aircraft is heavy (6PH loadout or lots of bombs). I’ll see if I can do a track today if I can reproduce it, but I’ve had bad luck with tracks lately...

The F14 module already has this, it’s super cool!

Yeah, same. Probably because I find a tendency to float in close, so I have to reduce power a smidge just before the ramp, otherwise I go from centered ball to high ball / bolter. Alternately I’ve been able to hold 1-2 dots low on ball, then without touching throttle I’ve been able to get _OK_ 4 wires, though I don’t like this solution. In both cases I go full burner as soon as I hit the deck. In my mission I have 30kts down the angle (15kts ship speed, 15kts wind 18* left of BRC), so I don’t think island burble or anything like that are a factor. It almost feels like a ground effect...

I have been getting this in Rift S as well. I thought my HMD was dying!

In the latest open beta, I’m having a similar issue. I need to do some more testing, but after a couple hours of multiplayer, I start to get terrible stutters and high frametimes, even though the in game FPS counter remains around 40. I believe it may be related to the supercarrier, as it happens most around the new boat. Using afterburner to monitor the system, it seems my memory gets pegged at 28-30GB usage for DCS alone (I have 32GB). Further, eventually I start getting low disk space errors, which leads me to believe windows is increasing the page file size to compensate for the maxed out RAM. GPU is my limiting factor (it’s always maxed at 99-100), but when frame time spikes, there is a corresponding drop in GPU usage, indicating a bottleneck somewhere else - RAM, methinks. Perhaps the new SC has a memory leak issue? Graphics settings: