Lymark

As long as you rotate at 120kts and hold 10degree, the plane would go airborne itself at around 180kts without blowing tires, no flaps needed regardless of your loadout. I think the tires only get blown out if you're still rolling at 200kts. IIRC, you can even take off without using AB, given there's a long enough runway.

I only play in PVP where the frontline is usually 60~100nm away and I have never run into fuel problems as long as I don't use AB until I have to. A typical A2A loadout would be; 4x SD10, 2x 1100L tanks(9500lbs total) and a SPJ pod. I have a total flight time of one hour flying at 2000ft(covering 550nm) in this config without AB. It burns 1000lbs of fuel every ~6mins. The plane without bags can fly for 30mins w/o AB, or 6mins with AB(everything was done at 2000 feet). Fuel burn rate between normal(99.2%power) and combat(100%) engine mode is very negligible, you're only saving ~20sec worth of fuel in normal mode. So, I tend to go for CMT mode and leave it there.

Both F-16/18 are also having an issue with projecting the correct contact altitude info in the HMD this update. Whatever this bug is doesn't seem to affect the JF-17 only.

My bad, your post didn't cross my mind when I posted this report, cause the tendency of losing lock after high angle of bank seems to occur in STT only, so I thought it was due to something else. I'd like to point out that testing in SP and PVP is different tho, besides the not seeing things at the 80nm scale, I'm able to track contacts at 40nm scale pretty accurately in SP, not in PVP tho. I will try out the AA/AG swap trick later. Anyway, you happened to record a new bug that keeps freaking me out this patch at 12:13. Notice how the contact appears behind you on the D/L after you've locked him? At first, I thought it was some sort of INS drift, but it wasn't the case because the 'drift' could still happen with INS+GPS and locking up my 1st contact 10mins after take off. However, I'm unable to reproduce it in SP environment.

Just managed to get in PVP server with the bug recorded as well as getting both logs and trk file. Note that three contacts on the left side of the D/L page disappeared whenever they're picked up by my radar. You can also notice my struggle of getting the bugged antenna elevation into the 'correct' angle. I purposely put the lowest elevation to be at or above my contacts in order to have a better chance of picking them up, it wasn't like that pre-patch. The trk file alone is 140mb, so I've uploaded both to my google drive. https://drive.google.com/open?id=1I4vRM89mlqfdN4yWqm2V3UHtc5JE5Hy8

Just a quick update guys: I believe that this issue is related to this reported antenna elevation bug. https://forums.eagle.ru/showthread.php?t=260890 I've a bit more success in seeing them by rising the antenna until the lowest elevation is higher than the target. There's some 'luck' involved, but it's better than not seeing them at all.

Here's another example with incorrect altitude info. Contact was at 5.500 feet, I was at 10,000 feet, though the HMD indicated that he was higher than me.

If you'd please see the screenshots attached, you'd see that a radar locked contact at 36,000 feet(1a) doesn't have its position projected on the HMD correctly(1b). This bug occurs in either RWS or TWS. All you need is to turn on the HMD, lock somebody up and look at him outside. I was playing on the Growling Sidewinder server(PVP).

I'm not sure if it's related to the reported antenna elevation issue, but there's a high chance that a contact(friend or foe) will disappear from the D/L whenever I find them on my radar. This makes losing a lock in BVR very dangerous now, cause I'd pretty much be in a blind If I lose the lock and forget that there's actually a target over there, or unable to get the buggy antenna into the right elevation in time.

Out of interest, can we get a status update on this bug? Been getting into close range a lot and have just realized how important having a proper VT scan is. :lol:

The workaround at the moment is to go back to TWS via INTC switch on the throttle, it will bring it back to 25 degree.

This probably explains my radar not picking up contacts issue. But does it only occur in 80nm range scale?

Radar not picking up contacts I don't have much detail to provide yet, but there seems to be a tendency that RWS/TWS/VS won't pick up contacts(including friendly) further than 40nm(in PVP). Some players on discord are also experiencing the same issue. I pretty much haven't seen contacts at 80nm range scale, and there're times where they won't show up until ~20nm, or just won't show up at all(rare). And I'm pretty sure the contacts were within my radar perimeter with a high closure rate.

Noticed that too, I remember TWS pre-patch had 25 degree by default that was also not changeable with S2 right.

It means that you're being scanned by something, be it friendly or hostile. And yeah, I find it annoying too :lol:

Are you guys able to use RP as a turning point for both DIR and COO? I read that RP can be used as such for both modes before turning to their final target point, but so far AKG just flies straight into SPI/PP respectively.

FYI: Last year's 1st new year update was on the 16th.

My friend and I have had such issue(ever since the RWR broke) against the phoenix too, sometimes all we hear is one quick missile warning then we exploded in like 1 sec later. We just assumed it's due to the bugged RWR tho.

Ahh! I really should consider getting a 2nd monitor :lol:

I'm using TrackIR and I do lean in toward the displays too. Guess I'm just too used to having a fixed view where I can keep an eye on all MFDs, as well as look ahead to not lose my outside SA. Not really a big deal tho, just thought I'd ask on here anyway.

Not the entire MFD font, but that particular part where it shows the contacts altitude in both the radar and D/L page(Picture attached). I can't be the only one who has had to zoom in very closely in order to read it ,right? I feel like it's one of those looking through a computer monitor vs eyeball things. Would be nice If we could adjust it somehow in order to compensate for the fact that we can't be sitting in the cockpit IRL. IIRC, there used to be a similar DCS1.5 mod for the old A-10C a few years back.

Not really, as it also provides accurate range information of RWR sources. It's pretty much a must have pod to carry for air to air loadout.

Your assumption is correct. I've mistakenly reported it as a bug a few weeks back, Deka then confirmed that the power system on board only has about 100 seconds of life time. https://forums.eagle.ru/showpost.php?p=4142982&postcount=5

https://forums.eagle.ru/showthread.php?t=256827 I just noticed the issue has been bought up from a few days after release. The devs have comfirmed it. Just gotta wait for the fix i guess.

If we really need to wait til the 15th, I hope that Deka would nail the D/L problem by then for one good MP patch! :lol: