Search the Community
Showing results for tags 'reported'.
-
Long standing bug, (already reported with track, but missing link due to new forum). I thought it was going to get fixed with the wind bug, but it's still here. Very easy to reproduce and check. Going from IDLE to e.g. 90% RPM, the values for fuel flow, EGT and nozzle position are completely different than if you go MIL and then back to 90%. In other words, if you throttle BACK from MIL to xxRPM, you get higher thrust (and higher EGT, Fuel flow etc), than if you were IDLE and throttle UP to xxRPM This is consistent at any altitude/speed/tempera
-
TGP image in F-16 is much worse than in other aircraft. It has low dynamic range (whites are gray, not white) and the contrast adjustment does not really adjust contrast. Same mission, same distance, same targeting pod in the Hog, Hornet and Viper. In the Viper even the target cross and north arrow are dark gray while they are white in the other aircraft. You can try to manually play with gain control, but it will only make parts of the image even darker. Though it will help somewhat with making the tanks stand out against the background. Another possible issue is that the contrast
-
Bomb delay for the 500lbs bomb is no longer working and hasn't since two updates ago. Not sure about the 250lbs bombs though. Also the refueling bug is still happening on the Syria map,not sure about the other maps though.
-
I can't bring to work the dust smoke in the nevada map, no matter with wich setting. In the Caucasus map works perfectly.
-
I'm preparing for mission 9 and noticed a small error in the mission description pdf: In the FRAGO page 6 the primary objective stated is "Destroy SAM and AAA in Anvil, engage targets of opportunity", I'm pretty sure that is the objective from mission 8, so probably a copy&paste error? It is almost not worth mentioning, but because mistakes are far and few between I thought I would mention it anyway. P.S.: Loving the campaign so far!
-
CCIP and CCRP alignment after taking off from a carrier/supercarrier seems to be wrong for me. The HUD in the CCIP mode shows the aiming bar almost 90 deg slides to one side and in the CCRP mode the bar guides me about 10+ mills into different locations. I tested it after taking off from a ground airport and it seems to be ok, but for a carrier and SC it just don't work. There is no bug report about that, so probably the mistake is on my side, What Am I doing wrong? version 2.5.6.59625 -) Tested with GBU-12. -) Yes, I am using the "CV" position on the alignment knob and wait alm
-
The HMCS symbology on status page for mark/steerpoint labels incorrectly turns airspeed on/off, which is the item under it. Status for other labels higher up on the list are correctly aligned, but at some point it shifts to the next item on the list.
-
The Dora still has this weird engine blow bug when cruising at lower RPMs like 2600 / 2700. The Dora is known for random engine failures for two or more years now. This is confirmed by other users, for example Storm of War players and the workarround is to just keep the RPMs at 3000 or higher which then seems to prevent the motor from blowing up. I tried to attach a track file but the forum says it´s too big, was just a 6 minute flight or so. No idea how to prove it as others have problems to repeat this in SP tests. Attached are two pictures which are 5 seconds appart. The engine was f
-
Mission 14 "Depot Strike" has the wrong kneeboard map: it shows the one from mission 15 (see screenshot below, maps differ between the briefing and the kneeboard). It's a bit embarrassing because the player has to find an area called "29-70 section 6" which is not displayed in the kneeboard. Thankfully, I was able to use the briefing map, which is correct.
-
After a gun fight, and return to like Aim-120, the radar of F/A-18C inverted the horizontal and vertical axis. So what you will see is the now the arrow for radar elevation is moving up and down, and it's range can be control by the the degree setting on DDI like 40°, 60°... And the vertical line moves now as how the radar elevation arrow usually did, If the setting is 1B1, then it is stable and if the setting is 2B1 and 2B2, it will jump between 2 position. I have attached a video for that, this happens at any map, and always after a gun fight kill, and switch back to BVR.
-
Current Behavior. TWS scan centering currently remembers the last scan centering mode (AUTO or MAN) when switching through modes (e.g. STT or RWS). The one exception where it is correct right now if both a) STT has been entered from RWS and b) TWS is entered via the TWS pushbutton (PB10), AUTO will be selected. Intended Behavior. Instead, it should behave as such: When entering TWS from STT, either via pressing Undesignate, selecting the RTS option (PB5), or the TWS option (PB10), the scan centering mode is automatically set to AUTO. When entering TWS from
-
When entering the ACM radar modes from TWS whilst having a pre-existing L&S, the L&S will be maintained as a 'ghost track' that appears at a fixed location from aircraft. This Ghost Track will prevent the ACM modes from creating another proper L&S, essentially bricking the radar. Track attached with neutral aircraft located off the nose with an aspect of about 150, crossing right to left, range 30NM. NB, this bug is also exhibited with an L&S generated from RWS, track attached. TWSbug.trk RWSbug.trk
-
Hello, it looks like the AIM-120C is in a pretty sorry state right now regarding maintaining tracking of a target, missiles fired from ranges of 10-13 miles lose the track of the target at ranges closer than 2 miles from impact, even half a mile in cases. All you have to do is use chaff, not much, one puff is enough to trick any AMRAAM, even at half a mile distance from impact. I am attaching trackfiles, tacviews, and links of short videos below. You can see the issue is replicable with your own plane, or with AI. I hope this will get fixed soon, as the missile has reached impossible levels of
-
As the title says. I use the NTTR with my group extensively-and while I love the map, the lack of long range city lights in Vegas are disturbing. You practically have to be on top of it to see that is even there. When the PG and Caucasus maps were updated, I was under the impression that this was a first step in a total night-lighting revamp. Is that the case? A response from a member of ED would be highly appreciated.
-
Currently you are able to enter two different codes for Mode3 and ModeC IFF, this should be the same code carried between the two settings. Mode3bug.trk
-
HI. They does not illuminate over water, land only. Also HOT is set at 3,000 feet and it fires at 7,000. Do I something wrong or is that another issue? I attach track. Thank you. Antonio. Illum rockets A10.trk
-
Saw this issue messing around with the F-14, but it may affect other modules as well. The problem: ripple dropping the Mk-82 Snakeye in level flight has a pretty high chance of one or more bombs exploding in midair, possibly caused by collision with another bomb. Test parameters: Speed: ~400 knots Altitude: ~600ft MSL Standard temp/pressure, no wind 14 bomb ripple, 50ms interval snakeye_ripple.trk
-
In the Early Access Guide, in page 363 it states, "use the WPDSG pushbutton on the HSD to designate a target waypoint". "HSD" should be HSI.
-
Played through this a few times, and there's a lot going on here. It's pretty heavily scripted, and I'm missing something because the campaign won't advance. What specific actions must the player accomplish/complete in this mission to advance to mission 11? Thanks.
-
reported F-117A get locked and fired by Tor, SA-6 and other SAMs!
Raviar posted a topic in General Bugs
As the title says it, I believe that shouldn't happen! -
Aircraft had amraams and aim9x loaded. Master arm set to MASTER ARM. Air-to-Air master mode selected. Amraam selected. Dogfight override mode entered and I always seem to get aim9x selected with warm seeker head. It was only after I exited from dogfight mode back into AAM with those aim9x selected, and then back again into dogfight mode again, that the cool seeker arrived with aim9x cool seeker selected. Master arm was on constantly. My control setup was warthog throttle and I used boat switch as the DGFT and MSL OVR switch in controls. Clearly my controls work, otherw
-
Currently it seems that SA-2 can shoot down F-117 from huge distances, even with low skill value. But with the F16/ F18 I can scan the Night Hawk only at realy close range. Might be a bug.
-
See pictures below.