LorenLuke

Laser point. Didn't realise I mistyped it. And yes it does, because reading is hard for me (i.e. I genuinely missed that point). So, if you capture the laser point, you could potentially use it as an acquisition source, as said, and then fire it from a masked location. But if you are trying to hit a target you don't have LOS on (which I'm an idiot and missed that part), you can attempt to enter a target point via the Keyboard Unit, OR, if you have a decently accurate idea of where it is on the map, you can use the CAQ as your acquisition source, and drop it as a point on the map, and launch it there. The biggest thing to do is have a decent idea of where the target is, and where it's being lased from, well enough that you can see the laser point (obviously you can't se the laser point if the target itself is blocking it, and be in range so that the missile can hit the target. Other than that, you're basically sending it and praying.

If you're in range (<10km), you can set your acquisition source to SKR on the 114Ks, and it should put the dotted cross over where the hellfire sees the ladder point as a sort of 'bootleg LST', no George or sparkle needed, if they're using the LD.

I believe it's ASE page -> Utility subpage (top row) -> RLWR (right side) Also be sure to turn up the audio warning volume knob on your radio (second from the left, aft row)

I think it's like 15 and 20.

Do you have proof that the helicopter wasn't designed this way?

Given that most scripts for IADS only function by using some form of the 'invisible' status for a target, and whole sites turn on/off with condition red/green, some additional commands for ground SAM (radars and launchers both), such as engaging a specific object, or group, as well as hold fire/free fire RoE would greatly improve how these systems work, and distribution of responsibilites and fires across multiple units to better model real behavior, and give scenario creators more granularity in what they make.

'Yes' to these questions. This will likely even go so far as being able to shoot a Lima Hellfire at a target from a buddy AH64 Radar, which was sent over Datalink.

Except they also said that AGM-130 would come after JDAM, so chances are that won't be 100% chronological.

https://twitter.com/RAZBAM/status/1707579227477004513

1) Did you have command of the sensor 2) Were you set to TGT on PB7? 3) Is the correct full action bound?

It would be nice if when pressing George action up to generate the target list, if targets were sorted by how close they were angularly from when you pressed the button, allowing you to have the target closest to that line of sight be the top of the list, and widen out from there as the list continues.

I believe RB have said that they will include the HMCS and 9X at a later date.

If you've used the F14 module, this targeting pod is literally meant to be the same one as that, which also has some relatively crap resolution.

When your bomb impact point is below the HUD in several aircraft, from the F-16 to the Su-25T, the pipper for the bomb is still shown at the bottom. Pressing and holding the pickle button in those jets designates the point as your intended impact point in a CCRP-type mode, with appropriate symbology to aid release. I'd wager that's what is meant, where the pipper is at the bottom of the guy's, but doesn't actually correspond to where bomb impact point would be (and would be such a case where the 'pipper' and 'sight reticle' may not be the same thing, or at least pointing to the same place).

The flir seems to have some sort of 'visible' component. Anyone know of any way to access this via command or button press, instead of just the thermals alone? visible = { fov = {math.rad(2.7), math.rad(28)}, -- min, max, in rad color = true, resolution = {625, 480}, -- w, h, in pixels digital_zoom = 12, -- max }

On the UFC, you can type in M1 (or M and whatever the number is), and then you can press Pushbutton 17 on the TGP screen to slave it to that point, I believe.

The entire gazelle flight model, and some of the weapons implementation.

Personally, I await the GBU-15 and the AGM-130 to sling from miles away. If they have buddy guide, would be cool to see the FA18 get code to guide ally's weapons.

That IS the official release.

But... you literally just... commented...

Include the overexposure effect that you see on old slow footage for the LANTIRN Pod, like how the F14 HeatBlur pod has. HB pod: Real life:

Not sure how it works in the real jet, but he didn't have his Master Arm on when he tried to jettison.

This was a consequence of their own doing. They had an announcement trailer for the blasted preorder (which they then delayed), for crying out loud. You don't see multiple threads in the Kiowa or Phantom sections stuffed to the gills with people lamenting the lack of communication or lack of a release date, and yet there's pages of the stuff here. It's all self-inflicted, at this point and for anyone who says to me 'people are just impatient', by all means, answer me why those other two yet-to-be-released modules don't suffer the same fate? Could it be that RB started this whole hype train with 'The year of the Strike Eagle!' for the past four months? A train we're being told that 'we're almost there!' at every turn, and yet all the track seems to extend out to the horizon. Ultimately, that's the crux of this whole mess, because this is the only place I've seen people this vitriolic about timelines and patience.

Just because I've not been around StarCitizen very long doesn't mean that their preorder practices aren't horrific. You can 'know what you're getting into' and still demand better, especially if you were to say that this sort of stuff would be unacceptable basically anywhere but here.