Whistler_RIO

confirmed this actually did relate to an issue i posted in another thread about MP problems!

@MAXsenna Oh i see what you mean. thanks for the correction. ya i thought all four of the extension-pack commands (radio tune, map marker, link tune, tacan tune, etc) were somehow just simple constructers that didnt run inside vaicom, but now i see how thats AIRIO . I guess i didnt ever need (or try) to use that command outside of Jester lol. (i use the Logitech radio panel now. it works really well through DCS-BIOS! highly recommend)

youre absolutely right, to explain, its actually that the carriers are not always the same. See, the 'supercarrier' requres totally different radio calls than the normal carrier, and it gets confusing because a map-editor can name the carrier whatever they want, so you dont really truly know if a carrier is the classic one (requiring simply "Inbound" and just "request landing" afterward) or the new supercarrier ("Inbound for carrier" or "Marking Moms", followed by "See you at ten" and then "Hornet ball" etc. ) until you try it. Actually, im not entirely sure how a supercarrier responds to you if you dont own the module, does it maybe not respond ? possibly

this is interesting! could mods/modules , especially community made ones, create a conflict? yeah maybe! definitely not the popular ones like A4-Skyhawk, but like i have some that are total hacks off of Forums lol. im going to pull all of them down now and test this. easy to try! There are some things in DCS, especially in the exporting part of the engine, that use ID numbers to identify aircraft types with the data they share. (and theyre not complex. like A10=8, F18=9, etc. easily conflicted with) DCS-BIOS is essentially observing that data at all times and filtering based on the ID. (example: Oh this speed number has ID of 6, thats a russian plane, i need to convert that from kilometers and divide it by whatever and now i can display it human-readable as a circular-gauge, etc.). Sometimes these aircraft-mods piggyback on these by spoofing IDs to read and display data, so its feasible that this could cause an issue

The radio button that you use will define which radio gets tuned, and first you should just try using the actual name of things like "Nellis, request landing" and vaicom will actually sort that out for you most of the time and tune that radio and then send that message. You can even just try "Tower, request landing" and it goes based on distance and chooses the closest! Most of us just use the provided commands and you would say "Radio tune, one two seven decimal five" . Important to note here is that your Hornet's radios are not both the same. UHF (COM1) can only tune station numbers above 200.00 while VHF (COM2) can tune the lower numbers than that. if you are outside that range, vaicom will just fail. There is no effective way to ask for specific channel numbers (if you have noticed, most modern aviation radios can either use a preset channel number "2" as well as a specific channel "127.50"), in case youre trying to do that.

Good question. the PTT page , which behaves normally and always has, does NOT show the selected aircraft, and only during MP sessions. When not in MP everything works perfectly. Maybe this is an SRS conflict somehow? ill have to see if a recent update to SRS is somehow conflicting. (note: i run SRS whether im playing MP or SP having it booted before starting the game always) I am also a developer and agree that source code would really help debugging this, but at least we have the LUA code which shows whats going on. Its very elegant and reliable, but it also juggles a few third-party elements that really need hands-on tweeking sometimes (like that 'fix registry' checkbox in options. ugh...). The value returned for the cost of Vaicom is so good that i just dont complain but i really wish this werent all so locked-up. hey thanks for your insights and ideas. ill report back to this thread if i find the issue (and i always do i guess). The nuclear option of cleaning out DCS to reset the exports stack always works as a last resort. hmm...there was a large update for Windows 11 about 3 or 4 days ago. good suggestion that i take a look at any changes to firewall and etc. maybe whitelist the internal non-routable IPs used for the scripts. thanks!

That is why i mentioned it (perhaps unclearly). this issue showed up a few days before the patch. And its just so strange that only MP have a complete disabling of all vaicom extensions, while everything works perfectly in SP! (tbh i dont even need vaicom for MP often except with F14 Tomcat solo flights which rely on AIRIO and have no wheel-menu graceful fallback when failing, so lately im just flying Viper online). i have never understood the whole 'did you shut down VA for the patch' thing actually. who is running all their scripts during updates? you guys dont shut all this down to sleep your computer each night? anyways, my update routine is 1) OVGME and disable all 2) shut down Vaicom (i run the executable version which manages VA on its own), JetSeat simshaker, SRS, and DCSFlightPanels . 3) apply update 4) start once without anything turned on and no mods to confirm no issues. reboot the computer. 5) enable OVGME mods, then start in order (which is how i start every new session really) with SRS, Vaicom, SimShaker, DCSFlightPanels, then boot the game.

I have been running Vaicom and AIRIO/Kneeboard/Chatter for years, and its worked really solid until 3 days ago (curiously, before this last patch yesterday!), when all multiplayer fails. Everything working perfectly in all forms of SinglePlayer gameplay, but all , even my own squadron's server, all of which worked before, i get working recognition in VoiceAttack but no send to DCS, a "AIRIO not available" message if applicable, and also no kneeboard. I can jump out of MP into any SP and all instantly functions. Have tried toggling 'Use with multiplayer" and restarting a few times. (this was never disabled before. always worked. btw i use DXLink in parallel broadcast mode) Through the years, i have debugged Vaicom through many installs and i even help my squadron-mates and have just never seen it behave like this. usually it fails or it doesnt, but why only on MP servers, every single one of them? its just so odd! Thanks for any help you guys can provide o7 Export.lua below: local vaicomlfs = require('lfs'); dofile(vaicomlfs.writedir()..[[Scripts\VAICOMPRO\VAICOMPRO.export.lua]]) local SimShakerlfs=require('lfs'); dofile(SimShakerlfs.writedir()..'Scripts/SimShaker.lua') dofile(lfs.writedir()..[[Scripts\SimShaker-export-core\ExportCore.lua]]) dofile(lfs.writedir()..[[Scripts\DCS-BIOS\BIOS.lua]]) dofile(lfs.writedir()..[[Scripts\DCS-ExportScript\ExportScript.lua]]) pcall(function() local dcsSr=require('lfs');dofile(dcsSr.writedir()..[[Mods\Services\DCS-SRS\Scripts\DCS-SimpleRadioStandalone.lua]]); end,nil);

thanks for reporting back. its helpful when folks do that. maybe even edit title with SOLVED if you like

I think you make an insightful point. There is also (and neither of these are something easy to do or fix or get perfect) a bit too thick of a fog-of-war in DCS, especially single-player. IRL there is alot more communication happening. An entire previous day/night cycle's worth of reporting and battlefield chatter , plus the fact that a 4-ship of jets is actually four seperate, engaged and intelligent, brains all focused on maintaining the element of suprise, the safety of the entire element, and the larger mission being solved.

when you change the frequencies in the ME, you are reassigning the presets. so if i enter 205.00 in the first channel slot, that will show/be the channel #1. One thing to be mindful of with F14 is that the two radios are different. the front radio can only tune UHF (200 and up) while the rear can do VHF (120 and up). if you enter a VHF number in the first radio from ME (and that seems to be a default thing sometimes, annoyingly), it might not function correctly

tomcat is weird in that its not supposed to be flaired at all (must be a navy carrier thing?) and youre supposed to land it straight and level, so the DLC becomes kind of neccesary to do that right

This is really cool. thanks for sharing!

There is though a new bug created with the recent Iceman features. 1) jump in backseat and tell Iceman to fly to destination. 2) jump in frontseat and turn to a new heading. 3) jump backinto backseat and you will see Iceman still trying to take you to destination. The fix would be that when we take over front seat that iceman command queue is cleared. Thanks

I see it now in the comms sheet. Sorry about that.

The campaign is really well done too! its a kind of 'multiple aircraft perspectives from the same mission' approach thats really kind of new and fun. its a nice bonus!

That font looks like FUTURA to me. About motion-sickness with TrackIR, firstly know that we all get a bit of that in the beginning. however, usually the fix is actually a lack of sensitivity. The default profile that NaturalPoint provides is totally unusable and will give you neck-pain and nausea because youre having to move your head so much more for it to do what you intuitively want. Your body feels like there is something wrong as it wants to use its instinctual look-at-danger response and its finding that its retarded , and so it assumes you maybe ate something that is causing it and wants to expel it from your stomach. (this can also be caused by too low a framerate. you need at least 45fps or else it gets pretty bad) Try making much deeper V-shaped profiles with no deadzone for your horizontal and vertical head movement. (keep rotation and Z to have a good sized deadzone) and give yourself the week or so to get used to it. its like when you get that first 1000mhz gaming mouse, its painful to aim at first, but after a few days you are just as accurate but now faster and more responsive. be patient with yourself. good luck

that was temporary. i had the same issue. try it again and it should be up again.

With TM, you start all support with an email. it takes a few days to respond, but then they will provide you either replacement parts shipped , or else provide you with a shipping address for them to do the fix. (most repairs are easy to do yourself really)

Hey i just confirmed this is fixed now. thanks so much for the quick support! looking forward to your next campaign

yeah i had the exact same issue. probably its a new patch AI change that makes this fail now. Im messing around in ME to fix it and i think it might be how the scripting is written to support four different aircraft you get to choose in its multiplayer-server-intended design. Im going to try updating it for single-player F14 use and also ensure all the tacans/ILS commands are implimented, new weather, etc. (i do this for alot of older campaigns as a habit now, heh). This campaign seems worth the effort! its highly regarded. at least we have the skip-mission feature as of this year to push past broken missions

Great. thanks for analyzing that issue. im sorry i couldnt be of help. i look forward to running through it again after next patch if possible. Its been a real fun experience so far. keep up the great work!

This is reproduceable. I have sit in the orbit on WP2 waiting for that menu item to show up. this has happened twice and i think i count 7 seperate flights rallying with me for at least 30min. We need a persistant menu command to force push the strike package. this is frustrating. thanks for the support

Theres a mission for night qualification that fails to write the ICLS channel for the carrier in the briefing. kind of important

I would save that profile as your "DXLink" variant, and then if you need to roll back, just re-import the profile provided by Vaicom into a new one. (when you import, voiceattack is smart, and gives you a dialogue that allows you to select the commands you want to import/override with checkboxes. very straightforward)