Jump to content

Recommended Posts

Posted (edited)

I'm starting a new topic since there was a bit of a discussion of how the PH ACT switch works in DCS currently in the latest feedback post. Currently PH ACT makes it go to a certain point (without any midcourse guidance or loft) and then go active at the target. IRL it would go active but would get guidance commands from the AWG-9 until it could pickup the target with its seeker. What we were discussing was the possibility of this switch or another switch in the RIOpit that allowed for manually sending an active signal to the 54 instead of waiting for the WCS to automatically send the signal at the distance set by the target size switch.

One of the points of discussion brought up by @Snappy was from what Ward "Mooch" Carroll said during an interview in June:

 

At this time stamp (1:29:52) he talks about how an enemy enters the beam and how you would make the missile go active to see if you could splash the bandit with the amount of energy it had left. This clip isn't 100% evidence of the existence of this possible feature but it's something.

Edited by DSplayer

Discord: @dsplayer

Setup: R7 7800X3D, 64GB 6000Mhz, Saitek/Logitech X56 HOTAS, TrackIR + TrackClipPro

Resources I've Made: F-4E RWR PRF Sound Player | DCS DTC Web Editor

Mods I've Made: F-14 Factory Clean Cockpit Mod | Modern F-14 Weapons Mod | Iranian F-14 Weapons Pack | F-14B Nozzle Percentage Mod + Label Fix | AIM-23 Hawk Mod for F-14 

Posted

This was brought up in the Air Combat Sim podcast with HB, but for whatever reason the topic died down.

BreaKKer

CAG and Commanding Officer of:

Carrier Air Wing Five //  VF-154 Black Knights

 

Posted

As it currently stand we have documentation saying explicitly that you couldn't do that, at least not in the early software tapes.

 

This might have changed but we've yet seen evidence certain enough that we're willing to change this.

 

And no, unfortunately that interview isn't enough. It's not that we don't trust him but having a singular SME we don't work with say something like this isn't enough for us to change something we have data on. If we had we would have had a lot more errors at ea launch that we'd then have to change.

 

People can forget stuff and confuse stuff with other aircraft and systems, we've seen this happen many times so if going by word of mouth from an SME only as evidence we either need it to be a trusted SME we work with or from multiple sources.

  • Like 5
Posted
2 hours ago, Naquaii said:

As it currently stand we have documentation saying explicitly that you couldn't do that, at least not in the early software tapes.

 

This might have changed but we've yet seen evidence certain enough that we're willing to change this.

 

And no, unfortunately that interview isn't enough. It's not that we don't trust him but having a singular SME we don't work with say something like this isn't enough for us to change something we have data on. If we had we would have had a lot more errors at ea launch that we'd then have to change.

 

People can forget stuff and confuse stuff with other aircraft and systems, we've seen this happen many times so if going by word of mouth from an SME only as evidence we either need it to be a trusted SME we work with or from multiple sources.

Fair enough. But just to understand this correctly, your own RIO SMEs are saying  this was straight out not possible?

Or you can’t verify it with them, because it encroaches on an area of sensitive information?

 

kind regards,

 

 Snappy 

Posted
1 minute ago, Snappy said:

Fair enough. But just to understand this correctly, your own RIO SMEs are saying  this was straight out not possible?

Or you can’t verify it with them, because it encroaches on an area of sensitive information?

 

kind regards,

 

 Snappy 

 

The latter. These are topics that they generally don't want to discuss and we have to respect that.

  • Like 1
  • Thanks 1
Posted (edited)
5 minutes ago, Naquaii said:

 

The latter. These are topics that they generally don't want to discuss and we have to respect that.

 Very understandable, thought it might be that. Thank you for answering .

 

Kind regards,

 Snappy 

 

 

 

Edited by Snappy
Posted

IRL, if the switch was on PD active and you fired on a PD-STT track, say 80 NM away, would the missile loft when it started receiving the fallback wcs guidance?

Posted

There is a problem with PH ACT and Pulse STT launches currently anyway. Currently in DCS its got a magical way of acquiring the target it was shot  at (Magic INS) when its within pitbull range if shot above the pitbull range. For example , you shoot at 25NM and it flies straight till 10NM then it will magically know where its target is and will start going after them immediately. I'm assuming the intention for it in reality is to turn on , scan and acquire a target within its FOV not have Magic INS outside its FOV. Although if it has passed the target it will not do 180 but it still will still start going after something outside its FOV.

The 120s and SD10s had the same logic for awhile when if you lost lock before Pitbull it didn't matter as when it got within right distance it would start magically tracking the target. just as the 54 does currently . This was corrected though so wondering when this is going to be corrected with the 54's active from launch modes.

Posted
9 minutes ago, DarksydeRob said:

There is a problem with PH ACT and Pulse STT launches currently anyway. Currently in DCS its got a magical way of acquiring the target it was shot  at (Magic INS) when its within pitbull range if shot above the pitbull range. For example , you shoot at 25NM and it flies straight till 10NM then it will magically know where its target is and will start going after them immediately. I'm assuming the intention for it in reality is to turn on , scan and acquire a target within its FOV not have Magic INS outside its FOV. Although if it has passed the target it will not do 180 but it still will still start going after something outside its FOV.

The 120s and SD10s had the same logic for awhile when if you lost lock before Pitbull it didn't matter as when it got within right distance it would start magically tracking the target. just as the 54 does currently . This was corrected though so wondering when this is going to be corrected with the 54's active from launch modes.

It has been like that for a very long time. It's actually better than TWS in many scenarios (old video from 16/05/21).

However, the devs have already discussed the problem. Hopefully, it'll get fixed when the new API is fully implemented (and the additional necessary functions are implemented).

full_tiny.pngfull_tiny.png
full_tiny.png

"Cogito, ergo RIO"
Virtual Backseaters Volume I: F-14 Radar Intercept Officer - Fifth Public Draft
Virtual Backseaters Volume II: F-4E Weapon Systems Officer - Scrapped

Phantom Articles: Air-to-Air and APQ-120 | F-4E Must-know manoevure: SYNC-Z-TURN

Posted
There is a problem with PH ACT and Pulse STT launches currently anyway. Currently in DCS its got a magical way of acquiring the target it was shot  at (Magic INS) when its within pitbull range if shot above the pitbull range. For example , you shoot at 25NM and it flies straight till 10NM then it will magically know where its target is and will start going after them immediately. I'm assuming the intention for it in reality is to turn on , scan and acquire a target within its FOV not have Magic INS outside its FOV. Although if it has passed the target it will not do 180 but it still will still start going after something outside its FOV.

The 120s and SD10s had the same logic for awhile when if you lost lock before Pitbull it didn't matter as when it got within right distance it would start magically tracking the target. just as the 54 does currently . This was corrected though so wondering when this is going to be corrected with the 54's active from launch modes.
I know it's broken in dcs but I wanted to know how the fallback SARH mode is supposed to work.
Posted
22 hours ago, Naquaii said:

 

The latter. These are topics that they generally don't want to discuss and we have to respect that.

bugger lol

 

7700k @5ghz, 32gb 3200mhz ram, 2080ti, nvme drives, valve index vr

  • Recently Browsing   0 members

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