BarTzi

Haven't you heard? They plan to overhaul IR texture for it. If it's still planned, that's a lot more than just "copy pasting". Besides, so many features of basic systems are still missing.. why rush?

I apologize if this is how it works IRL (doesn't seem likely) Here is my problem: While entering the coordinates for a waypoint using the HSI and UFC, if I ever want to change just the second line of the coordinates (suppose you made a mistake entering E or W digits) I can't. I have to go to through N first and type it all over again. Steps to reproduce: 1. Add one waypoint to the flight plan via ME. 2. Display WP data on the UFC. 3. Try to change just the E or W coordinates. (It's not possible, the UFC will only register N, and not E or W)

Well... In real life, if you cycle the battery it resets the system, which lets you run the second test without waiting. This is how the plane works, and this was also demonstrated by Wags in his start-up video. Also mentioned in NATOPS. If Wags mentioned it (and did cycle the battery) in his start-up video it means it should work in game.

IIRC after the first fire test is complete, cycling the battery (off, on) should reset the fire test and let you skip the 7 seconds delay. At the moment I can't get this to work properly. I can see the caution lights but hear no audio when I start the second test (the one after the battery reset). Track included. fire_test.trk

It can't take more than 6 digits at the moment. Wait until precise mode will be implemented.

You are not doing anything wrong. At the moment we can only type 6 digit coordinates. In the real plane you can also enter grid coordinates, change formats, and add more digits to get more accurate results. It's not implemented at the moment as far as I can tell.

Still an issue after today's patch.

Try this also

Also from NATOPS : Lighter hornets (no stores) with 2000 pounds of fuel will usually land at 125 knots (that's the ON SPEED value). For each 1000 pounds addition in weight, add 2.5 knots to the landing speed.

From my experience it's not how you set up the radios, but how long you hit the enter key after selecting freq. Try to click and hold it for a short period of time.

1. LTOD won't display on the hud 2. DATE won't display (either on the hud or the AMPCD) 3. (not sure if it's a bug) When CD is removed from the HUD, the HSI still keeps track of the countdown, but there is no way to bring it back to the HUD, only to start a new one

Hi guys, I have a couple of questions about this panel (shown in page 152 in ED's manual): 1. What does RCDR ON mean, and how can I get this light to show? 2. Page 152 in the manual states this panel will display the following: "GO and NO. BIT test result from when the Dispense switch is set to ON or BYPASS. BIT will take five seconds." I can't get this one to show either, even after the 5 second bit of the ALE-47. Should a light come on after this bit or am I wrong here?

IIRC NATOPS states you have to get special permission to use this on the carrier.

Doesn't it just convert? For example: 21/60 = 0.35 so : 24 13 21 = 24 13 35

Missed that comment, sorry. Anyways- I hope this gets more attention by players and ED. I'm not sure if they go through all those reports.

Thanks for commenting. I just want to point out two things: 1. I start in the air with INS aligned. This isn't an issue with the INS. 2. The WP's info (bearing, and distance) is indeed accurate. So I can hit targets all day long, and get to the waypoints just fine. The issues start when I want to make sure the WP is displayed in the correct location on the moving map itself. I do this all the time for the A10C, just to make sure Im heading in the right direction after making my own flight plans (for example: when you want to attack a base in BLUE FLAG). Right now, it just makes it really hard to understand your flight plan and use it for navigation with the map. If I could disable the map until this is sorted, I would.

Apologies if it has already been reported (I didn't find any similar threads), or if it's the way it's supposed to work in real life. This is the problem I'm having: I spawn in the air south of Batumi (my INS is aligned). I have 1 WP on the runway of Batumi, placed in the editor. When the WP's info is displayed on the moving map, the Icon's location is off (it's actually in the sea, and isn't near the runway icon on the map). In addition to that, the icon drifts forward as I fly towards Batumi. The only time the icon is displayed where it should is when I fly above the WP's location. This is obviously worse when you have more than one waypoint or want to make sure you entered the correct coordinates. Steps to recreate: 1. Use the attached miz mission file. 2. Start the mission, and display the first WP's (WP1) info on the HSI. 3. Observe the WP's icon location as you fly towards Batumi. When you reach it, keep flying and see what happens. 4. Go through steps 2-4, but this time use Batumi's tacan (16X), and observe the same behaviour for the tacan station icon. Just showing that it's not map related: (Video showing the problem, same methods used. Watch how the icon drifts as I move) Note: distance and bearing info is accurate, so I can get to that WP. The only problem seems to be with the icons. FA18_moving_map_acting_up.miz

Thanks for your tips guys!. Started working on the 2004 Dambusters cag (its an A afaik, but the camo is too good to be ignored)

Where do you guys find high-quality ref material for decals and paint schemes? How do you make the squad logo symbols and tail/wing art?

Thanks!

Hi guys, According to NATOPS, there is an analog clock in the cockpit (checklists also mention it). It should be located where the square black panel is in this picture (https://forums.eagle.ru/showpost.php?p=3350852&postcount=26). ED didn't miss it since they did include it in some older screenshots. Can anyone explain why/when was the clock removed (in real life) from the jets?

Thank you for your hard work!, do you have any updates on some of the missing cockpit functionality (HUD brightness for example)?

I agree! it would be cool if they add that.

There are some sections that lack a proper explanation of a switch /instrument functionality. I hope those can be fixed as well. Thank you for your work !

What are you guys bashing RAZBAM for? I mean- sure the manual isn't complete and the plane is missing features, but I am sure they will get to it (I am just as sad as you are about it). It's clear that they are not prioritizing the M2k at the moment, but they will get back to it and fix all the issues 100%. Why am I so sure? because if they don't, it will seriously hurt their credibility, to the point some people will reconsider buying their next module. No company wants that. Ralfi clearly stated that he is still learning the plane (and yes- at the moment, it is a hard thing to do - but it is very possible). The last video he posted flying the Mirage, he didn't even flip the cat switch. So every rookie mistake he made in that video is his fault. We all made those stupid mistakes, we all got frustrated and we all have our funny stories. This is how you learn things.