Inbound to Carrier Vocalization #21
Comments
|
Are you speaking of the pilot voice when it makes the call? Have you tested this without vaicom to see if the behavior is different? I just tested this with VAICOM and it reads the whole message. |
|
So when you are flying to a carrier and you use either "inbound" or "carrier inbound" you hear the pilot's voice read the whole message? I don't. It's a different sounding message and he just reads the numerical values. All other communications are fine and it has a different pilot voice. I made a video and will get it uploaded to YouTube to show what I hear. |
Yes I use "inbound for carrier" and it reads the whole text script. I tested it a few times to be sure in different aircraft I never had an instance where it only read off numbers. It sounds like its possibly your settings or configuration as I still am unable to reproduce. |
|
I recorded a video of what I experience. Please review the following. I have heard it like this for others as well. I am using a full repair of DCS plus the latest community Vaicom. I did copy my profile over.. Notice that the pilot voice sounds different from when I say See You At 10. |
|
I still cannot reproduce this. Can you share your vaicom configuration and vaicom and dcs logs when you try? |
I have this same behavior. Secondary issue: If ATC says: "305, rough rider marshal, CASE II recovery, CV-1 approach, expected BRC 308, altimeter is 29.93, 305, Marshal mothers's 128 radial, 23 DME, angles 8, expected approach time is 26" The pilot readback is (always, regardless of specifics in ATC instructions): "305, DME, angels 10, expected approach time is 0, approach buttion is 15" I have a second system without Vaicom installed and the pilot readback is correct and matches the specifics of the ATC instructions. Happy to provide logs and config if you let me know which specific files you need. |
|
Yes logs both dcs and vaicom would be useful, as well as steps to reproduce (mission/aircraft etc) |
|
Let me know if you need any other logs. These were taking in the PG CASE II recovery mission in the F/A-18C, however the behavior is consistent regardless of map or mission (the only carrier capable a/c I have is the 18). I made one call using the menu, cancelled the inbound, then made another call using VA. On a side note, I reset all of the viacom settings, profile and lua options, removed all my mods, did a full repair on DCS. I loaded into DCS (without launching voiceattack) and the pilot readback response was normal. I shut down, started voiceattack, and then launched DCS. The issues reappeared. |
You should have extended command at least enabled for instance, but I would also like to see your other tabs as well for settings. |
|
Here's my current settings. Mostly default except extended commands, the open beta flag and the auto import settings. I have tried with every combination I can think of, including a fresh install of vaicom on another machine with all settings default and see the same behavior. This is by no means a blocking issue. Just a bit immersion breaking.
|
First thing, check your DCS hook. Also you do not have the AIRIO DLL in the proper place. You need all the dlls for the community version |
|
I'll throw the AIRIO and chatter DLL's back in their folder. I had pulled them out when I was doing this last reinstall attempt since I don't fly the F14 (I though AIRIO only applied to that module), and I don't intend to use chatter. Being relatively new to vaicom, how would I check the DCS hook outside of resetting the lua (which I've done).? |
Just do a full rehook of DCS. Click fix reg, adjust sliders, and hit set and find your DCS path and if its not the default path you need to check the set custom path box. Then do a lua reset. Remember DCS must be closed when doing this. For further troubleshooting, please pop into the discord so we dont turn this into a support thread :P |
|
Sorry, I was away for two weeks..
So, I am still having this issue but I haven’t taken any additional steps yet. How do I go about a full fresh reset of Viacom Pro? I have logs and screenshots which I can send you but I don’t know if it’s worth while. I am happy to just blast everything away. I already did a full repair of DCS previously but I can do this again if needed.
… On Nov 14, 2022, at 9:50 AM, Ryan Callaway ***@***.***> wrote:
I'll throw the AIRIO and chatter DLL's back in their folder. I had pulled them out when I was doing this last reinstall attempt since I don't fly the F14 (I though AIRIO only applied to that module), and I don't intend to use chatter.
Being relatively new to vaicom, how would I check the DCS hook outside of resetting the lua (which I've done).?
Just do a full rehook of DCS. Click fix reg, adjust sliders, and hit set and find your DCS path and if its not the default path you need to check the set custom path box.
—
Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKRBEDIEHJZODYERV7ORV3TWIJGT7ANCNFSM6AAAAAARWJT5YQ>.
You are receiving this because you authored the thread.
|
|
Did you resolve this issue? I can't reproduce. It does sound like a hooking/configuration issue. |
|
This has not been resolved. I have performed an uninstall of VaicomPro (a few times) and also a full cleanup of DCS. I still hear the same numerical readout when calling inbound to the carrier. All other communications with the carrier are fine. |
|
Can you see if this is still an issue on the latest release? |
|
Hi! Unfortunately this is still an issue.
… On Jul 9, 2023, at 11:25 AM, Ryan Callaway ***@***.***> wrote:
Can you see if this is still an issue on the latest release?
—
Reply to this email directly, view it on GitHub <#21 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKRBEDIDPZA5NPESY7AP323XPLEQJANCNFSM6AAAAAARWJT5YQ>.
You are receiving this because you authored the thread.
|
|
I still cannot reproduce it on the latest version. You have the latest VAICOM installed? |
|
Yes. I actually did a full system rebuild with a fresh Windows 11 install (was Windows 10 before). Fresh install of DCS, voice attack and Vaicom (several months ago) and this issue persisted (so a full new install of everything on new hardware). I upgraded Vaicom today and did a quick mission for the f-18 CASE I landing and it happened. No clue why yours works and mine (and other players) doesn’t. On Jul 10, 2023, at 19:09, Ryan Callaway ***@***.***> wrote:
I still cannot reproduce it on the latest version. You have the latest VAICOM installed?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>
|
|
Also just tested it in the F18 with no issues, it sounds like a hooking issue somewhere. |
|
I have thrown this to the team to test on the latest beta we will see if anyone can reproduce the issue |
|
I finally got it to do what you say, only reading back the numbers in voice |
rcflyinghokie
added
Confirmed Bug
and removed
Unable to Reproduce
bug
|
I still can't reproduce this. Is it a DCS setting issue? |
|
I had this issue too. Just in case someone stumbles on this thread, resetting the Lua code from the last tab (Reset) in the VAICOMPRO control panel fixed it for me. I now get full readback (Marshall, marking mom's etc), not only numbers. Oh, and don't forget to use "Carrier inbound" or "Marking Mom's". Just saying "Inbound" will lead to readback of just the numbers. |
When calling inbound to a carrier, the voice only reads off the numeric values for vector, distance, altitude and fuel. It does not use the full text which is displayed when the inbound is called (or when using the comms menu to announce inbound).
This issue was around in previous builds.
The text was updated successfully, but these errors were encountered: