Hog_No32

Why would you want a steeper approach when the sea is rough?

Talking about the lethality, I think those of us (myself included) who transition from the A-10C to the F/A-18C are just too spoiled by the massive 30mm gun which easily kills a T-72 when employed correctly. Don‘t expect anything close to that from a 20mm M61.;)

When IN RNG is coming up, the rounds still have to travel a long way. They are exposed to gravity like everything else so at one point their trajectory will become ballistic, especially when you ate at max range. The hornets targeting system takes this into account and therefore, you see you bullets initially flying above the reticle but they should ‚fall down‘ onto the target where the reticle was. So if you are seeing them flying high that is ok, but they should still impact the point on the ground where the reticle is (at least some bullets - at max range the dispersion is still rather big of course). I did a couple of gun runs on manpads and APCs and I am quite happy with the accuracy and lethality of the gun.

It‘s the same as in the A-10C. Just like DDSSTT, I alwas start my missions with throttles at idle, unpause, move them to cutoff and then I begin the cold start procedure with BAT ON.

No worries, I wasn‘t asking for it on August 1st. If you read my posts before you‘ll see that I DON‘T expect those things to be close to release (and I consider August 1st very close). I‘m sure we‘ll get teased appropriately and in advance through Wags‘ videos and mini updates before these systems are going to be released.:lol:

August 1st???

No way, integration of the AIM-120 is a biggie I think and requires further upgrades to the radar and possibly other systems. Nevertheless, Wags confirmed in a the last video that AIM-120 and AIM-9X implementations are high on the priority list. But I‘d be very surprised if we see either one in the next OB update already.

Totally agree. Not the first time BSS_Sniper exhibits this attitude. Good there are knowledgeable people around here who behave differently and who add value to this community and our discussions.

Nope, from what I read I believe it is like that: (applies to carrier ops only) Landing lights: always OFF Nav Lights and Strobes: ON during landing UNTIL just after trapping OFF during all taxi (except in the emergency case of a brake failure, substituting hook down in daytime ops) ON when hooked on the cat and ready for launch (substituting the salute during daytime ops)

The lights should come on when you follow the standard comm routine for requesting a landing. After a bolter or touch and go you always have to do the comm procedure again to have the lights on for your next attempt.

That describes very well the technique I am using too to land on the boat and it works for me. And weights are a big factor. Maximum unrestricted landing weight for a carrier landing is 33k lbs (with some restrictions it can be up to 34k lbs). I often come in close to the maximum weight and yeah, my throttle is at MIL during the pattern and groove a considerable amount of time when I feel the need to add some energy. I don‘t need burners though (I can tell because I have the TM Warthog AB detent installed and adjusted my throttle axis accordingly). As soon as you try and land at a significantly lower weight you will realize how much more margin MIL thrust gives you compared to landing close to maximum landing weight. For a landing at say 28k lbs I rarely have to use MIL thrust for corrections.

Honestly, I thougt I‘ve used it in A/A mode as well. I can‘t see it on your screenshot and I can‘t check on my own since I am away from my PC till Monday.

on the STORES page you can manually select the missile to be launched next by pressing the OSB next to the label STEP.

when the option to remove pylons was introduced revently, Wags reported that currently there is no effect on the FM. At the momemt it is a pure visual thing. That will change though, of course but I haven‘t seen a timeline.

Thanks for your replies. What a pitty the fix didn‘t made it into yesterday’s update. I can work around it for takeoff by starting on the catapult („start on runway“) instead of a deck („ramp“) start ... even though for the immersion I really prefer taxiing to the cat. But it is a real issue when I want to land and then refuel/rearm and launch again. Sometimes it takes me 3 attempts to bring the jet in the correct position for the cat shuttle to be connected, messing with other jets on the deck.

The bug is that the AUTOPILOT caution never disappears after it comes up.

Hi all, reading the release notes of todays update I am wondering if fix for the issue regarding ice skating on the deck is included or not. Previous posts from Wags indicated the issue has been resolved by devs. Hopefully it was just omitted from the changelog by accident. I can‘t try it out tonight myself, that is why I am asking. Thanks.

No, I don‘t. I thought that was actually more a bug than a feature. Anyway, the way hiw I understood the issue is that the graphic card has to render each pixel of the resolution that you tell it should - regardless whether there actually is something to render or not. So in my case, my 1 screen setup has a res of 1920x1080, so there are roughly 2 million pixels to render. The second screen has a res of 800x600, bringing the total to 2720x1080 (side-by-side setup). I always thought the video card has to render the full 800x600 pixels even though I only „use“ 560x560 pixels of it for the DDI display. If that is true, I don‘t think I will get a benefit from not displaying the DDI on my main monitor as well, will I?

Which map/theater are you talking about? Keep in mind TACAN is a military installation so don‘t expect it at civil airports.

That is interesting. Usually I don‘t watch the track playback, hence I didn‘t notice that issue yet. Indeed, editing the programs in the ME would be great!

Funny...I did stick to a 1 screen setup with the Hornet until just after the last update when Wags said exporting DDIs should work now. So I gave it a try after the update and simply switched from „1 screen“ to „Camera and RMFD“, adjusted the resolution to cater for my 2nd screen (800x600 8“ display) and adjusted the corresponding lua file in the monitor setup folder. And it works like a charm! No other tweaking required, no thin lines, no issues with any other indicator. It works and looks exactly as it did for me in the A-10C. (Unfortunately, the higher resolution that my graphic card needs to render now coupled with a complex mission and many objects and triggers and stuff brings my rig to its limitations. So I figured unless we have the ATFLIR I don‘t use the second screen as the impact on performance for me exceeds the benefits. That will definitely change when a targeting pod arrives since then I will be much more head down in the cockpit and then the ATFLIR image on a dedicated external screen will definitely become necessary. Maybe by then I have upgraded my rig too...:music_whistling:).

That I can‘t tell since I only fly SP. Would a „crash of the game“ (that is what was reported) be the expected outcome of a failed integrity check when trying to log in on a MP server?

No, no issues with the edited lua file. As always, I use Notepad++ and format is UTF-8 (without BOM).

You can, if you wish modify the default programs outside of the simulator by editing the respective .lua file. IIRC the file name is CMDS_ALE47_init.lua. I did so because I always use the same programs for my missions and now I don‘t have to edit them new on the each flight. Sure you‘d always need to check that lua file after an update to DCS.

Yes, I figured with my average return weights of 32-34k I usually trim to 9° first (checking in the CHKLST page) and then fine tune from there. Works pretty well as a workaround until we get the readout of the trimmed AoA on the HUD (if we will get it all provided it is part of the software suite our Lot 20 hornet is based on).