Zyll

Provide some screenshots of your registry for the two steps of finding the section and creating the entry, and a screenshot of File Explorer showing your pr0 file. We should be able to figure out what is wrong. Mine works fine fyi

Do you have a mouse wheel that has a mechanical toggle for going from smooth scrolling to normal? I have one like that, if so try using normal scrolling. Smooth scrolling is meant for scrolling really fast through many pages of a document, and would not work well in this use case.

In addition, if I use R/BL mode with a turn point, it doesn't fly to the WP, instead it heads straight to the target point. select a WP, press HPTP to make it a turn point, designate a different WP as a target, press Mode to go into R/BL mode. The HSI symbology indicates the path I expect. If I fire, the missile ignores the TP and instead heads directly to the target, as if it were a normal R/BL mode with no turn point. Additional track attached 20200321_harpoon_test2.trk

When I setup my harpoon in BOL mode, I have WP2 selected, select HPTP and I can see on my HSI that the line draws out towards WP2 as expected. I want the missile to turn 050 upon hitting WP2, arm at 10nm and destruct at 30nm. The symbology on the HSI and SA page looks correct, the missile is going to fly to WP2 and then turn right over the target. When I fire the missile, it immediately turns 050 from my jet, as if I did not press HPTP, and it keeps going until it destructs. I have made multiple attempts, it does not fly towards the WP, regardless of whether I still have the WP selected, or I switch over to a different WP (as in the attached track). 20200321_harpoon_test.trk

E2 Hawkeye and E3 Sentry are NATO AWACS aircraft. Provided the mission has these in the air, and they are setup with an AWACS mission as their role, then you can contact them and request 'bogey dope' and 'picture' which will give you the info you are looking for.

For example, TAW NA1 and NA2 would work. Tune into the AI frequency for the AWACS aircraft and check out the F10 menu items for Magic, or Darkstar, or whatever we named the E2 and E3 in those maps

And a bogey dope request will give you a BRAA to the closest bandit

Any mission with an E3 or E2 setup will give you bullseye posit when you request a picture

Bypass works, where it just sets you up to pop 2 chaff or 2 flare when you push forward or aft on the CMS switch

Try pressing alt tab to get to the desktop, and then alt tab again and see if that helps. I run my game in 1080 on my 1440 monitor, and I have seen what you are experiencing, but can get around it in this manner.

If your radar gets stuck in a mode you can't get out of, I find switching weps (like going from AMRAAMS to sidewinders and back to AMRAAMS) resets my radar nicely

Why exactly is using TDC depress on an L&S target incorrect? Honest question

You could also consider joining an online squadron to fly with other like minded enthusiasts like yourself.

These Eccles cakes sound awesome

just happened to me now too, never had this issue before 2.5.6. I have changed my password as a precaution

It was wrong previously? I always assumed the weight displayed there is accurate.

That should not be necessary. I just comment out the 5 lines as follows. Always works for me. opacity_sensitive_materials = { --MDG_font_name(MDG_SELF_IDS.HI), --MDG_material_name(MDG_SELF_IDS.HI), --"MPD_DMC_OUTLINE", --"font_MPD_DMC_outline", --"font_MPD_DMC_main", }

I saved this note on using ground power in the hornet. With external electrical power - 1. Battery - ON 2. EXT PWR switch - RESET - NORMAL (right click) 3. GND PWR switches 1, 2, and 4 - B ON (left click hold for 3 seconds) 4. L® DDI, HI/MPCD, and HUD - ON 5. COMM 1, 2, and ADF - AS DESIRED 6. Warning and caution lights - TEST 7. Inertial navigation system - ENTER WAYPOINTS DESIRED

Are you sure it wasn't a HARM?

It's the file Installer.exe in the zip

hi team, The attached screenshot shows in red, the missile range of 65nm for an S-300 launcher. The larger yellow rings show the detection range of the Big Bird search radar, and the Flap Lid tracking radar. The smaller yellow ring shows the detection range of the Clam Shell search radar. There is no terrain to affect the test. I expect that I should be engaged by the missiles right at the red ring, 65nm. In actuality, I'm getting engaged consistently at 35nm. Aircraft is at 25,000 feet. Is it possible that the range rings are incorrect across the board? I ask because Wikipedia tells me that the Big Bird should have a detection range of 190nm, but the game has range rings at 86nm. Clam Shell radar should have a detection range of 75nm, but the game shows 32nm. It seems as if everything is halved in the game, perhaps ranges are incorrectly being represented on the map with diameter instead of radius.

Keep in mind that being a semi active homing missile, the AIM-7 needs the hornet to maintain radar lock all the way to the bandit. You break lock early, the missile will miss.

Need to toggle on the laser, it's to the right of the toggle you used to turn the TGP on

attached please find a trk file with the issue. https://drive.google.com/open?id=1Tw4T2ypJaPTWgubL-ig5JIWCVukBETC2 I don't even hop in a jet. I just unpause the game and watch F10 view, you will see the warping within a minute.

and i believe the freezing occurs when these messages get so big and numerous. If you left the client logged onto the server and continued to get the errors, I feel like you would have eventually experienced a DCS freeze. ERROR EDTERRAINCORE: utm_private::fromLatLon Longitude