Jump to content

Recommended Posts

Posted

Having issues when trying to transmit VAICOM commands to the Tarawa in my Harrier. Whenever I transmit to it, I get the following error

 

3:27:55.996 Joystick : 'Transmit TX1 release'

3:27:55.452 Selected recipient is not a Supercarrier unit.

3:27:55.452 Recipient for ATC set by call contents.

3:27:55.451 Identified unit: Oliver Hazzard Perry class with id 16777728

3:27:55.451 Getting selected unit for category ATC

3:27:55.451 Have result, identified as command: See You At Ten

3:27:55.450 Captured sentence: see you at ten

3:27:55.432 Recognized : 'see you at ten'

3:27:52.990 TX1 | COMM1 AM 141.000 MHz tuned for ATC unit Beslan [AI]

3:27:52.989 TX1 | COMM1 AM 141.000 MHz tuned for ATC unit Tarawa [AI]

3:27:52.792 Listening resumed

3:27:52.767 Joystick : 'Transmit TX1 press'

 

Now the Tarawa is on 141.000 MHz, but the escorting Oliver Hazzard Perry class is not, I've changed that to another frequency.

 

Whilst the Tarawa is indeed not a Supercarrier, for the purposes of VAICOM, it should be treat as one. I'm not sure if this error is being thrown because of the OHP in the Tarawa group, if it's because the Tarawa's frequency clashes with Beslan Tower, or if it is simply not eligible for the command as it's not seen as a Carrier by VAICOM, but the in-game comms treat the unit as a Super Carrier.

Intel i9-9900KF @5.2GHz

MSI Z390 Gaming Pro Carbon

32GB G.Skill Trident Z DDR3200 RAM

MSI RTX 2080 Ti Gaming X Trio

40" Panasonic TH-40DX600U @ 4K

Pimax Vision 8K Plus / Oculus Rift CV1 / HTC Vive

Gametrix JetSeat with SimShaker

Windows 10 64 Bit Home Edition

 

[sIGPIC][/sIGPIC]

Posted

The answer is in the log - realistic ATC is only available on the ships that are part of the Supercarrier module. Tarrawa is not one of those and therefore runs on the classic ATC model.

 

this is a game limitation and not a Vaicom one

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted

Actually, I didn't test it thoroughly, but comms for Tarawa do seem to have been changed. I don't even own Supercarrier, but last time I flew I could tell it doesn't use the old protocol.

Posted
Actually, I didn't test it thoroughly, but comms for Tarawa do seem to have been changed. I don't even own Supercarrier, but last time I flew I could tell it doesn't use the old protocol.
Thinking about it, my knowledge might be not up to date looking at the Razbam forums (I don't use Tarawa at the moment) - what happens if you try using the options command to select the option?

 

The thread in the Razbam forum implies it might be that the Harrier is not supported by the Supercarrier module and that this might be why SC ATC does not work. Another thread from August says that all non-SC landing ships have been affected with messed up comms. Realistic comms were pushed as being for SC modules only so I am sure the issue is in DCS and not with Vaicom.

 

Away from PC - sent using Tapatalk

 

 

 

 

 

Windows 11 Home ¦ Z790 AORUS Elite AX motherboard ¦ i7-13700K ¦ 64GB Corsair Vengeance DDR5 memory @ 5600MHz ¦ Samsung 990 Pro 1TB SSD for OS, Samsung 980 Pro 2TB SSD for DCS ¦ MSI GeForce RTX 4090 Gaming X Trio 24GB ¦ Virpil WarBRD base with VFX grip, Thrustmaster A10c and F/A-18 grips ¦ VKB Gunfighter Mk4 and MCG Pro ¦ Thrustmaster Warthog Throttle ¦ VKB STECS Throttle ¦ Virpil TCS rotor base with Shark and AH-64D  grips ¦ MFG Crosswinds ¦ Total Controls Multi-Function Button Box ¦ Pimax Crystal

Posted

I'll look into it when I get back into the Harrier. Whether it's a bug or an undocumented (and perhaps unintended :) ) feature remains to be seen. I need to fly a proper mission and see if it actually works.

 

The Tarawa should be able to use SC comms. It'd be fine if it required ownership of SC itself, but if that's not an option for technical reasons, IMO they should leave it in for all Harrier pilots. Given the state in which the Harrier had been for a long time (and it's the main, if not the only, aircraft that would benefit from it), it would surely be a nice gesture...

Posted

As far as the radio menus and built in DCS comms go, it's Super carrier all the way, BUT it may only be that way if you own and/or have the Super Carrier installed...

 

Here is what VAICOM is capturing from DCS when I use the in-game radio menus to communicate with the Tarawa

 

12:49:29.984 [AUTO:] Player: 100

12:49:22.466 100, Tower, Roger. BRC is 209, signal is Charlie

12:49:13.973 Player: Tower, 100, overhead, angels 4, state 4.0

12:49:08.114 Player: 100 state 4.0

12:48:30.227 update state, switch tower

12:43:32.604 [AUTO:] Player: 100

12:43:14.182 100, mother's weather is visibility ten plus miles, clear, altimeter is 29.93, CASE I recovery, expected BRC 209, report see me at 10.

12:43:00.813 [AUTO:] Player: Marshal, 100, Marking mom's 070 for 45, angels 15.5, state 4.7

 

Interestingly, the only message VAICOM doesn't see is the player calling "see you at 10"

Intel i9-9900KF @5.2GHz

MSI Z390 Gaming Pro Carbon

32GB G.Skill Trident Z DDR3200 RAM

MSI RTX 2080 Ti Gaming X Trio

40" Panasonic TH-40DX600U @ 4K

Pimax Vision 8K Plus / Oculus Rift CV1 / HTC Vive

Gametrix JetSeat with SimShaker

Windows 10 64 Bit Home Edition

 

[sIGPIC][/sIGPIC]

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...