Zohardv

IMHO the icons and fonts should be at least 120% bigger, for the sake of usability, even if it's not 100% realistic or accurate. Would be much appreciated.

Thanks

Am I missing something? I didn't get any patch or notification. I'm using Stable version. Any Ideas?

I also think that touching the controls while performing the BIT might result in BIT failure. Also, I remember that in cold weather, the pilots used to "stir" the controls. Just give the stick a little wiggle around the center in order to "heat up" the hydraulics. Otherwise the BIT would fail. Don't know if it's an urban legend, bad habit or a substantiated process.

Without going into too many details. This launch was part of a drill, simulating an emergency scramble where everything that has two wings and an engine must takeoff immediately. The aircraft was just finishing maintenance and that's why the switch was in MAINT position. Due to the urgency, the cockpit was not prepared - by the book - and that is why the switch was overlooked by the ground crew. Furthermore, and this is me speculating, due to the urgency of the drill, the pilot did not perform BATT-TEST, but hit the Start-2 once jumping into the cockpit. This is actually the usual procedure for scrambles when the JFS is started while the crew are sitting in and fastening their harnesses.

Not sure about the technicalities, but I can clearly remember once that a pilot started a jet while this switch was in MAINT. He got a Christmas tree of warning lights and FLCS faults. Couldn't proceed with launching. Edit: or maybe it happened because the bird was starting up while using external power? :huh:

You are absolutely right. The question is, CAN you run a BIT in DCS while this switch is in MAINT? Or will it fit in a BIT failure?

Also FLCS - MAINT (shout disable control surfaces movement altogether)

First of all. I use a VR headset. I can easily read most pages of the MFD. In my opinion, there is a problem with the radar icon's scale. See attached screenshot. Second, I have many hours in the viper's cockpit (not as pilot, unfortunately) and I can surely say that most comfortable and well designed. The MFDs are quite close and readable very easily.

My two cents: after testing several setups and runs, it seems that there is a problem with CCRP altogether. The delay function does not apply and, once you pickle, the bombs are released (usually way ahead of time). Sometimes it works OK. I've narrowed it down to the direction of flight, but it seems like I'm missing something as it sound very unrelated. See this thread: https://forums.eagle.ru/showthread.php?t=271428

Hi All. My radar screen shows very small icons for aircraft blips. Much smaller than the bullseye and waypoint symbols, for example. Also the font for target data is very tiny and unreadable. Is this a known issue? How can I address that? Thanks

I remember emailing them about it back in 2002. Just out of curiosity. Still waiting for an answer.

Actually, pinky switch only changes the FOV from WIDE to NARROW. The correct implementation of zoom is done with the ANT ELEV wheel (rotate it CW/CCW to zoom in/out), which I don't believe is modeled in DCS yet. Haven't tried it though, maybe try to bind keys to RADAR ANTENNA ELEVATION and use it to zoom in and out.

You're right. I had TD/BP mixed up with SPOT/SCAN I'm not familiar with the option of manually slewing the AIM-9 seeker. I don't know of any controls or inputs for it in the cockpit. From my (very little) experience in real life F-16s, that not an option

AFAIK, you cannot slew the AIM-9 seeker. It's either SLAV or BORE and can be set to SCAN or BP. Closest thing you can do is set it to BORE and SCAN. That way the seeker scans it's entire aperture, but you can't control the scan pattern. Slew ACM mode is quite like BORE, but instead of being centered on the the A/C nose, you can change the azimuth or elevation of the radar scan zone.

Thanks Deano87 for the thorough explanation. My version of DCS is 2.5.5.41371 which I take is the stable one. I guess I can either switch to the open beta, or wait for those bug fixes to become an official update. I think I'll go with the latter. Anyways, if you happen to have the time, and you are using the open beta version of DCS, Try to fly this mission and see if the bug can be reproduced under the same conditions. I'm very curious. Thanks anyway. Zohardv

I'm sorry, but I'm new to DCS. I just downloaded the F-16 through the built-in MODs manager. How can I tell if its a release or an open beta?

I might be insane, but.... Finally, I think it has to do with the direction of flight:doh: I know, I know... I also didn't even considered this as a variable, BUT... In this mission there is a row of vehicles stretching from north to south. The mission spawns you SE of the target, so in all of my attempts I followed the closest path and tried to run the column from south to north heading 355. As mentioned, a press on the pickle releases the bombs immediately and regardless of the required delay and the bombs fall short. Now I tried the same profile, but running from north to south (heading 175) and the CCIP worked like a charm! 6x mk82s, 200ft apart, using TGP following the pipper, and delivering with delayed CCIP. The cuing works perfectly and the delay is kept while depressing the pickle. Bombs on target. Am I going crazy here? :joystick:

Bingo! I think Thanks for the feedback. I tried to remap the pickle as suggested, but it didn't work. After several tries, I managed to find a different root cause of this issue. It's not the TGP, but setting an interval distance between release pulses. In my first trials, I thought the TGP was to blame, but since I tried bombing using the initial settings and without changing anything in the bombing profile, but with the help of the TGP and it worked fine, I started to look for another culprit Here's a conclusion of my trials: [TABLE]Release pulses (#) Interval distance (ft.) Outcome Default (1) Default (10) Works fine 6 200 Doesn't work 3 200 Doesn't work 1 10 (changed back from 200) Doesn't work 2 Default (10) Works fine[/TABLE] Some other settings remain the same in all trials. It seems that changing the interval distance causes some sort of an error. Can I submit this as a bug to anywhere or anyone??

+1 on that one

Hi all. I've been fiddling around with unguided bombs and TGP. I've loaded the instant action mission called mk82/84 unguided bombs in Nevada. First bug, totally unrelated to the subject, but still bugging, is the bombs quantity in the SMS page. It shows I have 6 mk82 and 6 mk84 while I only have two 84's. Moving on, I like to find my target using the targeting pod and set a CCRP cue in order to bomb it. I line up the TGP and lock on the target (IR point). I follow the CCRP cue. When close to the target (delay cue is still visible) I press and hold the pickle, instead of delaying the release, the bombs fall right when I pickle, thus falling way short of the target. This doesn't happen when I designate CCRP visually through the HUD and without using the TGP. Second thing that happens is when using CCIP and having TGP displaying on one MFD. When set up - HUD as SOI, CCIP mode, the TGP is supposed to follow the pipper, providing a zoomed in view of the pipper's designation. The TGP does function as described, but the problem as described above occurs the same. I have a delay cue, press and hold the pickle, but the bomb is immediately released and fall short of the target. Is this a known issue, or am I doing something wrong?