WizzRD

Photo credit: https://www.targeta.co.uk/lakenheath_48fw.htm Agreed. Tho there are some with fins around as well, thus it´s not totally unrealistic to have them on.

Please post your mission so we can see what´s going on.

When or where was this ever stated? The current dimensions do match pretty well with current SAT imagery, it´s just that the hangars are the wrong size and/ or are placed incorrectly. Spots 120-137 are all drive through and large enough for both, the F-15 & the F-16 (IRL that is).

There is nothing RAZBAM can do about that. You need to direct your request to ED as this is a core "feature".

Well, it´s working "properly" for me as I´m dropping bombs left and right with no problems. Thus it´s certainly nothing that´s as easy to fix as a bug that everyone sees/ has and, most importantly, can be reproduced.

NVGs are set in the mission editor and the default is without them. So at one point whoever made the mission did enable it. With the NVGs you also get filters over certain light sources to not (totally) blind you

It´s a known thing and I´m sure it´ll get fixed eventually. Until then try re-designating the target (maybe more than once) until you get an ASL line that makes sense - works for me.

What Airfield are you on? Sitting at Wadi al Jandali (right next to Cairo) I get 2 hrs difference. I have 10.00hrs analog time and 08.00hrs UFC time. And here is what I thnk happens: - Analog clock shows local time - UFC clock shows GMT, and currently GMT is the same as BST - BST is 1 hrs ahead of UTC <- what we expect it to be In that case 10/ 08 would be correct. The 5 mins you get are because the UFC clock only starts ticking once the right engine is up and running, so whatever minutes difference you have is the time you needed to start your engine.

It´s a weapon/ TPOD thing that should be relevant to all modules. Basicly, Target Coords generated by the TPOD are not accurate enough to hit a small target at max. possible distance. By lasing the target shortly before dropping you do increase accuracy but it may well be that ED has it overcorrected now (have not run any tests yet). In general you should not drop a JDAM on anything smaller than a house. For Movers use LGBs. If you want to read up on this, search for: "AN ANALYSIS OF TARGET LOCATION ERROR GENERATED BY THE LITENING POD AS INTEGRATED ON THE AV-8B HARRIER II"

Once implemented you´ll see a large X (called "Break X"in the HUD upon reaching whatever altitude you have selected.

Nope, you did it right. It´s just that he F-16 is overly picky on where your steering line is. You have to have it dead center in the middle of the FPM or it will not release.

Strike Eagle Pilots do not call ATC before startup.

Did you assign No.3 as No.3 using TM´s software?

The 0° and 45° tic marks are single lenght, but double width (that looks amiss). 30° & 60° are double lenght, single width.

I think these are the terrain following bank limit carets, thus this may be an indication of what soon to come

Changing the LOALT warning worked from day one. Never tried to turn it off tho. I also seem to remember some of the SME´s saying that what we see is what is correct.

After you enter your channel click on it and remove the asterisk from T/R. That´s a current bug that will get fixed soon(ish).

They work as good (or bad) as any other. If your ASL is off just re-designate, maybe more than once, until it´s in the right spot.

Either way works, flying level the TPOD won´t get masked until after your bomb hits it´s target.

I usually drop at 480kt TAS, but up to 500kt TAS works nicely as well. Doing a 60° designator turn after release will support your bomb until impact just fine.

https://support.thrustmaster.com/de/product/mfdcougar-de/ Called "Unified Drivers Package 2018" and it worked fine for me on WIN 10.

You can download a little util program from the TM site that let´s you rearrange and rename your MFD´s.