Jump to content

Recommended Posts

Hi,

 

in a Case III recovery player's readback is totally off, dunno if it is Hornet bug or Supercarrier bug, sorry, if wrong place here.

 

Reporting in to Marshall, and giving my bearing, distance, (altitude?),and fuel state, Marshall gives me instructions:

"...expect final bearing 164, altimeter 29.88, Marshal on Mother's 344 radial, DME 23, Angels 8. Expected approach time is :41"

 

"My" auto-readback to Marshall: "Marshal, 403, DME, angels 24.5, expected approach time 0, approach button 15"  Marshall replies: "Redback correct", altough no DME number repeated, Angels 24.5 is my present altitude, and expected approach time is not 0.

 

Am I missing something, or carrier to F-18 comms still W.I.P.?

  • Like 1
Link to post
Share on other sites

Hi, I will move to the super carrier, but if you have a track replay please attach it and we can take a look, its important to get the radio calls right at each stage as per the manual.

 

thank you

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 10 Pro x64, NVIDIA MSI RTX 2080Ti VENTUS GP, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3000, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to post
Share on other sites

Dang, it was a 1.5 hours long mission from Raven One, not sure how long in size the track could be. How can I retrieve the track, if I didn't fly another one since?

 

Edit: found it, 69 MB... geee... I suppose I can not trim it down somehow? Or it would loose it's point then anyways?

 

EDIT: made a track by simply starting a SC Case III recovery, find attached. Totally the same things happened. But the track did not recorded any communications. I used Voice Attack and VAICOM, and went smoothly in game, dunno why not recording in the track.

 

However if you simply start the same SC CASE III recovery mission (Persian Gulf), all you need to do is calling Marshal, and you can see what happens. By the way altimeter callout is also off by 0.01, because I guess Marshal should say altimeter 29.92, but she said 29.93 instead. I reported it in the F-18 bug topic, together with a fuel state and altitude being also off. "Angels 16.5", when altimeter shows 16040, and "state 10.3", when fuel qty is in fact 10150.

readback.trk


Edited by Razor18
Link to post
Share on other sites

Thanks I will ask the team, if I find something I will let you know

  • Thanks 1

smallCATPILOT.PNG.04bbece1b27ff1b2c193b174ec410fc0.PNG

Forum rules - DCS Crashing? Try this first - Cleanup and Repair - Discord BIGNEWY#8703 - Youtube - Patch Status

Windows 10 Pro x64, NVIDIA MSI RTX 2080Ti VENTUS GP, Intel® i9-10900K 3.70GHz, 5.30GHz Turbo, Corsair Hydro Series H150i Pro, 32GB DDR @3000, ASUS ROG Strix Z490-F Gaming, HP Reverb G2

Link to post
Share on other sites

I got it messed up too, but different:

 

MP: Did a CASE 3 - Bolter -> Missed Approach Procedure -> Calling Inbound again 25nm out - Getting a Push-Time T+50 Minutes. WTF? I'm host with no clients...

 

Yesterday flight with three, same thing. First round went ok. For a second run we'd get just crazy late approach-times from ATC.

 

What I discovered sometimes wrong in ATC calls is the tail#.

[sIGPIC][/sIGPIC]

Asus ROG STRIX Z390-F Gaming, Intel Core i7 9700k , 32gb Corsair DDR4-3200

Asus RTX 2070 super, Samsung 970 EVO Plus M2, Win10 64bit, Acer XZ321QU (WQHD)

TM HOTAS Warthog, SAITEK Rudder Pedals, TIR 5

Link to post
Share on other sites
  • 3 weeks later...

Just found the thread now.

 

Yes all these things are correct and happen always.

 

Case III Approach Time: Always at around 20 to 30 minutes. Even when there is no other flight in the stack. If there are other (AI) flights, I always get a time at around 30 minutes even when I arrive as the last one. AI flights fly their marshal all night long (arrived way earlier on lower angels, so they should commence before me) and even after I landed they might try an approach 10 to 15 minutes after me. When I strictly fly my pattern and approach time, most times they don´t land at all and run out of fuel...

 

Radio calls: "Marshal, 403, DME, angels 24.5, expected approach time 0, approach button 15" <- exactly this. Always. The "players" readback isn´t correct, never. This also counts for fuel states on all calls on all cases. "Player" fuel state message is always 200 pounds more than actual state.

  • Like 1
Link to post
Share on other sites

I don't think guys this has anything to do with the original bug report. If you think your issue is a bug too, maybe it would worth it reporting it in a separate Bug topic, as probably the solution is also totally different, but definitely worth to take a look at too?

 

Regards

  • Like 1
Link to post
Share on other sites

Do you guys use Vaicom? I’ve seen this too (the original problem with read backs), but it only started when I installed Vaicom.

Ryzen 9 3900X / Asus Crosshair VI Hero X370 / Corsair H110i / Sapphire Nitro+ 6800XT / 32Gb G.Skill TridentZ 3200 / Samsung 960 Evo M.2 / Virpil Warbrd base + VFX and TM grips / Saitek X56 Throttle / Saitek Pro Combat pedals / Rift S

Link to post
Share on other sites
  • 4 months later...
Am 14.1.2021 um 15:51 schrieb Andartu:

 

Radio calls: "Marshal, 403, DME, angels 24.5, expected approach time 0, approach button 15" <- exactly this


I have the same issue in conjunction with the F-14B and SC in the Caucasus CATIII instant mission. Readback is always incorrect: approach time should be 38 instead of 0 and ICLS channel is 0 instead of 15. 

And yes, I am using Vaicom. 
 


Edited by Viking667
Link to post
Share on other sites
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...