escaner

Look for a shop in the USA that sends by USPS First-Class Mail International or ask them to do so. It takes 2-3 weeks, but it is way cheaper than any other method. I have purchased there several times with that one, including charts years ago.

This has happened to me a lot of times in Caucasus too, and a friend just suffered it last Tuesday. I started a thread about it and someone pointed to this bug report: https://forums.eagle.ru/showthread.php?t=154630 I don't think ED has acknowledged it though... In my case, I cannot relate it to flying under structures. Under other aircraft, who knows...

I just flew this mission and can confirm a few problems: SPOILERS AHEAD! 1. I am not sure now whether I told my flight to anchor but lost my #3 and #4 without a warning. Perhaps the load is too heavy for the AI at such altitudes. 2. When I was leaving IP ALPHA for the run on the first target, I was notified that I had hit it, before releasing the bomb. From the log, it looked like an artillery or mortar unit hit herself and killed all. This didn't happen in the second target, which was fine. Well, with the clouds I expected the JTAC to lase my GBU-12 so I didn't and missed. But hit it with a GBU-38, so the coordinates were fine in my case. For the guy with problems with the CBU, I recommend lowering the Height of Function (HOF). It is by default at 1,900 ft, which is too disperse anyway and inaccurate with wind. It worked fine for me at 700 ft.

Mission 10.

I taxied before communicating with Defender-9, but took off after receiving the SAM footprint clearance. After the mission I noticed in the log several SA-18 launches but didn't see them, my MWLS didn't alert me and neither my flight nor Defender-9 said anything about them.

Nice, the JTRS trick did it for me twice in a row, and my flight took off, thank's. :) I was getting used to do the missions solo haha.

BTW, I don't consider these problems game breaking. The missions can be done perfectly solo and the campaign is awesome so far ☺ Sent from my Redmi Note 4 using Tapatalk

Similarly for mission 6. Wingmen with lights on, but won't taxi. ATC allows me to taxi then cancels authorization. I takeoff anyway. Coming back, ATC wanted me to divert to alternate. The runway was clear, I landed anyway. This time my wingmen did not move at all. Sent from my Redmi Note 4 using Tapatalk

I have just done mission 4. My flight turned their lights on but would not taxi for takeoff, so I had to do the mission by myself. Then arriving back to Kutaisi I thought "Cool, now I won't need to wait for all those stupid AI to land after me". So I checked the the SAM threats through F10 and immediately those bastards started coming alive, so I had to wait for them to takeoff and then land, including three go arounds by #4. :-( PS: I am on the latest patch 1.5.5 Update 5

I agree with Redglyph here. The documentation is very thorough and immersive, but difficult to read. The aura in the font makes it harder to read, same as the background images in mission 2 orders.

That means that the aircraft is statically unstable. Much has been written about the Spitfire stability, but I haven't followed it, so can't say whether it is correct or not.

It is spring loaded and unbreakable. :lol:

Turn on that switch (CAP SEC or something similar) next to the ANÉMO in the right console first. Sent from my HM 1S using Tapatalk

Thank's Imp, that certainly could be the problem. Is there any trick to help with the lock, then? Maybe move the antenna up and down while in acquisition phase?

Well, then it is the module manual in this case what is wrong.

Nope, the manual says it is referenced to the ARL. See attachment.

When I cannot lock my leader that is flying 3-4 miles ahead of me, and then switch to dogfight boresight and immediately locks, its is not problem with range of ground clutter.

Maybe one that locks the target when you command a lock with the cursor on a contact? TBH it has been a long time since that last worked for me.

Unfortunately we are still missing procedures for GBU-12, Snakeyes and CBU in the manual. Greater variety in dive angles and release altitudes would also be nice for the slick GP bombs.

From the text in the image you posted, it looks the prop lever still sets rpm (it says it can be used as previously), but the throttle will override it when that setting is too low for the boost. So it is not an ON/OFF, but an axis.

That is what I said. This bomb is simulated as live, so it should have yellow stripe.

The CBU-52B bomb appears with two blue stripes, which means that it is an inert / training bomb. Live ordnance should have yellow stripe(s).

Or air density or airspeed... I have checked it in the sim. The rpm lever selects speed between 1600 and 3000 rpm. Below 110 MPH IAS the rpm will be lower than those 1600 and the rpm lever becomes useless. So it should be useful to retard it above 110 MPH, but the lower the airspeed, the less difference it will make.

Not with the engine stopped, as was the case. With the rpm lever, you set a desired rpm to maintain. The propeller governor uses oil pressure to maintain those rpm. If rpm increases, so does oil pressure and the governor moves the blades to a coarser position to slow the prop and keep the selected rpm. With lower pressure, it does the contrary and the prop goes finer to increase rpm (oil pressure). Engine stopped implies very low rpm and oil pressure. Even with the rpm lever at min (full backwards), the engine is rotating slower than selected, which drives the propeller to full fine pitch (and max drag). Similarly, when the engine is running and loses its oil (e.g. due to battle damage), the pressure goes down and the governor will move the propeller blades to full fine, which can overspeed the engine.

Try Operation Save Badger and The Jackal. Both are free short campaigns, with time to look for the targets and think. Enviado desde mi MI PAD 2 mediante Tapatalk