Hog_No32

My sincere apologies, Nooch. I realize it indeed was poorly done. Can I compensate you by buying you one of the other Raven One books as a Kindle edition? I‘m serious since I fully understand what it means. Please let me know via PM.

Thank you. Never heard of this before, so unfortunately I cannot help.:cry: e

Excuse me if this is a stupid question, but what does SRS mean in this context?

Isn’t the next OB update today - and per the schedule that will be the last OB update this month. So I‘d think there still is some hope we‘ll get JSOW, BRU-55A and MSI tonight. Don‘t be too worried if there aren‘t any explanatory videos yet - those might come later (actually only needed for MSI since I would assume dropping the JSOW will initially be very similar (if not the exactly the same) to how we currently drop JDAMs.

Absolutely. It‘s also one of my favorite episodes (actually it‘s two). Listened to that numerous times already, also because Farva comes across as a very nice and humble guy! I sometimes „use“ these episodes to fire me up - can‘t wait to jump into the Hornet after listening:)

You are right Yurgon, thanks for pointing that out!

I think in RL when you work with a JTAC who lases for you, you don‘t fire another Laser Maverick before the first one has hit. To assume the second one will catch the shifted laser illumination after the first target is destroyed is rather risky. That is why the JTAC dialog includes the „SPOT“ confirmation which ensures your second missile (while still on the rail) will indeed pick up the laser. Anything else bears the risk of the second missile going crazy when it doesn‘t pick up the shifted laser. Keep in mind that CAS and working with a JTAC means there are friendly units not too far from the target.

A couple things here: First, to be able to talk to a particular TWR at a particular airfield you need to tune the appropriate frequency and transmit your „Inbound“ call on that frequency. That is if you have the „Easy Communication“ option not enabled. One way to get that frequency (if it wasn‘t in the mission briefing already) is to go to the F10 map ingame and click on an airfield icon. Second, runway lights (including at the Carrier) will only light up after you call „Inbound“ AND it has to be dark enough (dusk, night or dawn). In daylight the runway lights are never on as far as I can tell. Maybe in daytime with a significantly impaired visibility but I am not sure on this one. Others certainly can chime in on that.

Actually, if the LSO‘s voice would have been the one from Jack „Farva“ Curtis that would also have been pretty cool - he is the guy who actually was an LSO (up to CAG Paddles IIRC) and explained Day Carrier Landings on the FPP. But Jell-O will be great as well for sure. I‘m just thinking when Baltic Dragons Raven-One campaign will come out where Jell-O will also do the voice overs for Cajun, it might become a bit awkward to hear the same voice for Cajun and the LSO upon landing. I think I just need to improve my CASE I even more so I‘ll don‘t get too many calls from Jell-O as my LSO then :smilewink:

I wish more people (including myself from time to time) would exhibit such a grown-up and self-reflecting attitude as you did here, BuzzU. Kudos to you.:thumbup:

Holy cow :surprise:

Sorry then, I wasn‘t aware you are a daily reader;) The fact that they talk about WHAT they WANT to do for the F-16C is no reason for concern in my opinion as it doesn‘t present any sort of impediment for the Hornet development. I would only have been concerned if they would have attached a „when“ to the „what“ or would have shown screenshots of the Sniper XR work in progress. Factually the only thing that has changed now is that the Viper is on pre-order. Nothing more. We knew there will be a DCS F-16C before and obviously it would come along with many nice and some new bells and whistles including some type of targeting pod.

Very valid point, I forgot about that one. I also use the center station for the usually only bag I carry in basically every mission. ATFLIR will definitely increase the flexibility in loadouts.

Just follow the weekend news and especially the Hornet Mini-Update posts that Wags provides. Whenever the team has confidence that an in-development feature is mature enough to be released within a month or two, that is usually announced in the Mini-Updates (see the words about JSOW and Litening TP in the last Mini-Update). Anything which isn‘t explicitly mentioned to be in development at the time of the Mini-Updates (such as the A/G radar currently) is unlikely to be released soon. Also, please let us refrain from again and again accusing ED of sacrificing Hornet Dev resources for the Viper. They explained to us more than once that this is not the case. Instead in the past year we mostly got smaller software updates with little fixes but very frequently (every 2 weeks, sometimes even faster). Now they are simply working on bigger items which take more time and which partly require fundamental parts of the core engine to be reworked (like the bespoke A/G radar and also IR render for ATFLIR and other IR sights). And talking about a targeting pod: ED thankfully agreed to give us the Litening so we can have a TGP sooner than originally foreseen. Once we have the Litening in our Hornet implemented (end of next month), I strongly doubt there will be any „operational needs“ for the ATFLIR at all. The Litening has served me so well in all the years in the A-10C that I cannot imagine the ATFLIR will bring significant operational benefits. Not saying that I don‘t want it, please don‘t get me wrong here. Just saying the Litening will already bring all the TGP functionality that I am personally missing currently. The „only“ reasons I still would want to have th ATFLIR after the Litening is a) it is the realistic pod for our Navy Hornet and b) because hey...it is a new gadget still! :)

I based my assumption on the fact that - quite some time before the DCS Hornet came out as EA - there was a huge forum thread with the title „F/A-18C Lot 20 OFP 13C“. https://forums.eagle.ru/showthread.php?t=168861 That (mis?)led me to believe this is the configuration which is being modelled. I could be wrong of course and it could also be that maybe this was what ED wanted to do initially but changed their mind during the development.

Isn‘t our Hornet intended to replicate OFP13?

If you leave out the part with GPS jamming or laser countermeasures which both are not modelled in DCS, yes the rest applies to DCS as well as RL. I would argue though that there are scenarios where actually it is the JDAM which is more versatile than an LGB. You cannot program any sort of terminal guidance parameters for an LGB. If there is a stationary target which you want the bomb to impact on a certain heading (which might be different than you delivery heading), in a defined angle and with a defined velocity, that is something only a JDAM can do. This however really applies to RL only (at the moment) since a) terminal guidance for JDAM is not implemented yet and b) even when it is, I hardly can think of a mission in DCS where you would absolutely need this feature.

ROFL, best intro to a post I‘ve seen for a long time :lol::thumbup:

Thats also how I understand PB to function. With one difference though. IIRC when the HARM‘s sensor doesn‘t detect the pre-briefed (i.e. pre-programmed) type of emitter when it opens its eyes, I think it will go after another emitter within its FOV instead of flying to the location of the PB target. If there are multiple other emitters it will prioritize the one which is deemed the highest threat.

Yeah, finished „Lions of the Sky“ by Paco Chierici just yesterday. You‘ll love it if you loved the Raven One Series! Next is Stephen Coonts for me. I watched the movie „Flight of the Intruder“ when I was still a kid. I think that was the first time that I ever saw an aircraft carrier. Hooked up to naval aviation since :)

Is that something which is only required in TOO mode? I have used PP exclusively so far and I never set EFUZ to INST more than once. Yet, 4 JDAMS on 4 targets all detonate as desired.

Agree 100%, thats how I do it too. Doing it before jumping into the cockpit is also what PP actually means, right?:smilewink:

Thanks, Matt. "Misleading" was a very friendly way of putting it... some people have either no clue how software development works or are just ignorant. Or both.:cry: Thanks for all the hard work of you and the team. Still having so much fun in the Hornet.

Matt mentioned one bug at least which will get fixed by tonight‘s update. That is the game crash when there is a mismatch between the station selected in QTY and the actually active JDAM station. We should keep in mind that Matt created the video to present just the JDAM updates (plus ME). There still is a likelihood we will get more little fixes for the Hornet which Matt just didn‘t mention because the video was all about JDAM employment. There‘s always hope...:smilewink:

I don‘t have them linked (as I never have when controlling a twin engine). I don‘t see it as something that increases my workload, I just move both simultaneously every time. Also, as I often start cold-and-dark I have to have them unlinked to put each one from OFF to IDLE individually as part of the normal startup procedure (same thing during shutdown). Sure, you can use the keyboard commands instead but for immersion I prefer to physically lift the throttle levers over the detent. Regarding walking the throttles, yes, that is something I do a lot when in the groove. Throttle levers never rest for more than half a second in any position. The same is true for aerial refuelling and any sort of close formation flying (even though to a lesser extent compared to behind the boat).