Garfieldo

Its not context sensitive and does not appear in the menu. It's only what the your pilot says (He pronounces it Spee, as in "Speed") when you give the ... -> "Wingman" -> "Engage with..." -> "Armor (or Tanks?)" -> "Missiles" -> "North" ...-command. I wrote the command from memory, so it might be a little different in-game. I'm sure it works with any other target, weapon or direction.

I am positive that the "Engage tanks at my SPI with missiles from the North"-Command has worked for me in the Easy Instant Action Mission using Beta3 (at the "Tanks" Wpt). All I did was broadcast my SPI, give him the command and 30 seconds later he called in 3 tanks destroyed, all done with Mavs. I have not yet had time to reproduce this, will look into it soon.

Thanks man, very much appreciated! Rep inbound!

very noice! thanks!

F-ACK is TMS Left Short. When hooking a target (red triangle), you can delete it by hitting the OSB labeled CNC (Can Not Comply), also in red, on the right side of the MFCD.

I have not been able to use my own preset channels... What I do is this (for AM Radio): 1. Turn on Radio (TR) 2. Set Channel #1 3. Set mode to MAN 4. Enter freq (131 for a tanker I put into the mission) 5. Press LOAD (now 131 should be stored under #1?) 6. Change freq to something other than 131 (to prove comms go over the channel, not the freq) 7. Set mode to PRE (now channel #1 should be activated with 131 as freq, although something else shows under frequency?) 8. In the VHF AM comms menu the tanker is greyed out and can only be reached by setting the mode to MAN and the freq to 131. Is my procedure correct? Or do you have to be in PRE mode to LOAD a freq to a channel?

In the manual you can find it under the expand (EXP1 and EXP2) modes for the TAD. Manual page 304.

Thanks ED, great work! Can't wait to DL and install! So, I guess now there will be a closed Beta2 forum? Where can I get access? :idiot:

... when you purchase green lightbulbs for your computer room?

I tried taking off with NWS on, and the nose wheel retracted without problem. This might very well be the case, since it was a nighttime takeoff. Maybe I was a little too occupied fiddling with NVGs and did not pay too much attention on the runway... :juggle:

Thanks for sharing that info, Deus!

Thank you for your quick reply! With those two possibilities in mind, I wil try to reproduce this error later on.

Hi all, on my last testflight I encountered a very strange problem: After a ramp start and takeoff at Groom Lake my nose landing gear got stuck in the extended position and would not move. I followed the standard startup procedure very accurately and have no idea what might have caused this. I did not have the situational awareness to check the hydraulic pressures, so maybe there was a fault there. The preflight BIT did not produce any errors. The main landing gear retracted and extended repeatedly without a problem (the nose wheel position light stayed black the whole time while the other two worked accordingly). The whole time the audio warning for the LG kept beeping, even with all pos lights off. I tried to release some 82s and it said "Release Aborted" (or something similar) in the MFCDs. Neither the manual nor the forum produced any usable info on stuck gear in the DOWN postion, maybe you can help. I'm sorry that I cannot provide a track of the event. Thank you for your time!

And you didn't even jett your 82s? Nice landing!

In my opinion the flight plan method is there to organize your mark points and save them for a later time. If you encounter 2 groups of 3 T55s each that are 4 miles apart, you can save mark A-C under flightplan "T55A" and mark D-F under "T55B". Also you have the added benefit of not overwriting your mark points when you reach Y and keep on marking. But, when you are only attacking one group and there is little time between target acquisition and running in hot, then making the extra FP might take too much time and not be that beneficial. The "perfect" way to mark points is if you are directly above the target, i.e. looking straight down. The more you deviate from this angle- and rangewise, the bigger the designating error gets.

Next time it happens I will check CADC status on CDU and see if that is the problem. Thanks!

I just had my HUD quit on me for the second time in about 6 flight hours. The first time I had been hit once with a .50 from a tank, so I thought nothing of it. The second time I was not even hit once and the HUD died seemingly randomly. What I also experience is the KIAS in the HUD and airspeed indicator remaining constant from a certain point on, last time it stayed at 231 KIAS for the rest of the flight until the landing. When I stopped on the runway it read the usual 50. My card is a 9800 GTX with 512 memory.

thank you headspace for that great video! It worked perfectly for me, but 2 related questions arose: 1.: Say I entered 5 Mark Points into my "Target Flightplan" and only need 4 MPs, how do I erase a specific one? 2.: Can I somehow send flight plans to a human wingman, so he can use it as target guidance? Sort of like "Buddy Lasing 2.0" ;)

I cannot answer your question directly, I can only decribe an example that I set up intentionally: I put a LOT of unarmed units on a map and by killing around 50 HMMWVs I was awarded a medal for that piss-easy mission. So I guess if you can get medals, you can gain rank as well in user-made missions. I hope this helps you out to some degree.

Yeah I'm guessing laser slant range too. Will have to try those settings when I have the time. 800m Rad Alt is pretty high though... Do I hear a MANPAD launch already? :blink: I'm guessing the airspeed is needed to take the bombs' drag into account.

This is a pretty impressive (accuracy-wise) video on bombing: At the end of the video the maker of the video lists his bombing parameters for height, speed and range.

I completely agree, it would be really nice to rearm the three categories - Outer Pylons, Inner Pylons, Cannon - independently via the maintenance menu. If this is not going to happen, the loadout list should at least be updated to have most of the possible loadouts. For example, 12 x Vikhr + 40 x S-8 OFP would be nice to have, since the KOM variants only kill by momentum, i.e. by poking somebody's eye out. The TsM/OM variants are not listed as well.

I had the same problem after I patched 1.0.1 to 1.0.2 (I know, I know). After a clean install and patch from 1.0.0 to 1.0.2 everthing worked again.

I usually prefer a continuous program with only a single flare per burst, like X-1-1. Length is adjusted by the number of sequences. I always want to conserve flares, I just cannot help it :music_whistling: How big is the impact of dispensing multiple flares per burst, like X-2-Y, opposed to single flares? Especially with both sides selected, they will run out rather quickly.

This has helped some people before, I hope it helps you too: