Search the Community
Showing results for tags 'already reported'.
-
already reported Mosquito's artificial horizon fails on shutdown
ssn posted a topic in Bugs and Problems
Artifical horizon drifts on shutdown and newer corrects itself neither stationary on the ground with engine running nor in a level flight. mosquito-gyro-broken-on-shutdown.trk -
I went back to some carrier practice missions I use for random stuff yesterday and now when I spawn in position 1 I have this issue where the flight directors have position 2 move to Cat 2 first, which causes my wingman to run into me. This is with the F14, in the F18 he just sneaks by me without hitting me. In this mission previously I was directed to Cat 1 before my wingman was directed to taxi to cat 2. I did this 4 times with the same result each time, not sure why this has changed as it has worked with me taxing first since flight directors where introduced. I have other missions where I am in position 4 and 14 with a full deck of planes launching and those still worked for me. I understand this is a very complicated system and still under development, so I am just throwing this out there not really looking for any answer. It's been a great addition for immersion. Flight Diretor issues .trk
-
Radar mode standby is causing crash to desktop for me. dcs.log-20250116-192908.zip
-
Flying the KA-50 through the rain brought to mind a story a Russian friend of mine once told me. It took place back in the Soviet Union during the 1980s. He was standing on a balcony in Moscow when the weather turned, and raindrops began to fall. Whenever visitors from abroad witnessed what happened next, it always intrigued them: everyone would pull over, stop their cars, open their glove boxes, and take out their windshield wiper inserts. Right there in the pouring rain, they’d quickly attach the blades, jump back into the car, and continue on their way. Once they reached their destinations, they would remove the wipers and stow them away again. This strange ritual was all because hooligans would steal the wiper blades and then try to sell them. Anyway, is ED so committed to realism that the wiper blades on the KA-50 have been swiped by neighborhood kids, or have you simply forgotten to implement them? I’ve tried turning them on, but they seem about as effective as a condom salesman at a monastery. I’ve seen the capitalist pigs in their 64-Ds repel bad weather, with their wipers and this just doesn’t seem fair. With the recent weather patch, everyone seems to have fallen in love with rain, which makes flying the KA-50 quite challenging and unenjoyable Please, consider making these wipers actually wipe
- 1 reply
-
- 2
-
-
-
AI do not engage like they used to, Quick mission FW190A8 attack airfield , Normandy Map, the Spitfires now just fly in circles in a disorganized manner and do nothing, before they used to attack the 190s, not anymore. Quick mission P51 The Channel map FW190A8s furball, the A8s are not aggressive anymore, you can even fly straight and level, and not get attacked, or see as much action as before AI vs AI.
- 1 reply
-
- 1
-
-
Pressing the Emergency jettison button should jettison the TER (if carried of course). Seems that the SIM only ejects the bombs from the TER. Also as mentioned before the pylon of the Pylon tank is connected to the tank itself and should also 'leave' the aircraft when jettisoned.
-
Hi, Should it be possible to connect ground power at a friendly airfield and then shut the engines down whilst maintaining power and keeping the current alignment? When I try this, as soon as the throttle moves to OFF the alignment is reset back to 0.00/99. The aircraft then needs a full 8min alignment to be corrected. Cheers,
-
I place it on the bug list and not the wish list, because the F/A 18 isn't playable for me on vr at night. If you turn on the nvg you can see the terrain, but can't read any of the instruments. The brightness doesn't matter. Perhaps, instruments shouldn't be easily readable with the nvg's. But, not readable at all, might be wrong too.
-
Hi, not sure if this is a bug or the correct behaviour of the model. Whenever I lock up a moving vehicle with the TGP in Point Track the SPI is not following these track. It always stays at the location where the Point Track was initialized. This makes it really unhandy to handover to the MAV and lock up the target. It is also an issue when dropping LGB's as the CCRP is calculated based on the position where the track was initated and not the actual position of the target. I only could see this behaviour in the Viper. Other models I fly, like the A10 oder the Hornet have a different behaviour, there the SPI always follows the Point Track. Best, F16-C-TGP_Point_track_SPI_Bug.trk
- 1 reply
-
- 1
-
-
In the last update the Amraam lose easy the lock from target if the target NOTCH the Amraam. in low distance you have to release the Amraam below 5 miles with 1.5 mach in order to hit the target if the target notch aggressively. I think it is need some refinement the Amraam AIM 120C5 to be more aggressive and not lose lock or energy so easy.
-
Is there any new issues that have occurred with the collective being powered at start even with my throttle axis being fully in the rear? This only started happening to me in the last few days, anytime I am starting a mission with an up and running Hind she takes off immediately as if the collective was full even though I never touched my throttle axis I have assigned to collective. I have another track that proves it's the collective axis because I add collective input and kill it and the bird seems to respond as you'd expect. hindtrack1.trk hindtrack2.trk I have T16000m throttle and VKB gladiator stick. I also recently added logitech pro rudders. In the second track you can probably see me searching my saved controls to see if collective is assigned anywhere else by default or something.
-
already reported AAR TACAN not working
hrnet940 posted a topic in Aircraft AI Bugs (Non-Combined Arms)
I have been working on my AAR, 70 registered in my logbook so far, and using TACAN to find my Herc for refuel, but now after tuning the correct TACAN station my F/A-18C doesn't find the TACAN. I can have the aircraft 0.5 nm off my nose and still nothing. How do I get this fixed? It worked before the last update and now not working. Wayne -
Can ED please finally aknowledge and fix the issues with ship wakes in 2.7? Especially regarding the paid supercarrier module? It is all but realistic, looks weird and the turbulent white wake effect should also be more pronounced and visible from a distance, helping you with lineup.
-
Time to revisit the accuracy of AA/AAA. Here's some links to stats and info: https://www.quora.com/How-effective-were-anti-aircraft-guns-during-the-Second-World-War https://www.lonesentry.com/articles/ttt07/german-aaa.html The first study includes data from the US Navy and as an example shows that for say the 20mm AA, that it would normally take over 5000 rounds to kill an aircraft. The second talks about the use of larger AAA, like the FLAK38/41 including: The Germans had stats that it took roughly 16,000 rounds on average to bring down a single bomber. The FLAK guns had a minimum 20 second period for the fusing, and were typically employed against targets at over 20,000' To predict where to fire a large AA - "This method requires that the aircraft be flying reasonably straight and level for about 90 seconds before reaching the predicted point" To sanity check how the above stands up in DCS. I setup 3 airfields, one with a single 20mm AA. The other two with FLAK unit and the spotting kit, then flew a P51 straight and level over each. At 2000' the P51 was shot down on the 4th burst of fire by the 20mm At 5000' the P51 was happily engaged by the large FLAK At 10000' the P51 was happily engaged by the large FLAK The track file is here: https://drive.google.com/file/d/1IVThE92KoJQTkER03k7lcTQd6sIXFtO6/view?usp=sharing If the above links are anything like accurate that would imply: - The big FLAK shouldn't have been shooting at the P51 at 5000' and 10000' - Accuracy of the shooting against a target at 2000' is simply too good
- 6 replies
-
- 12
-
-
-
Combat Mix and AG belts do good damage on enemy aircraft. Stealth belts barely can put an aircraft down. They stream, smoke, loose parts, etc but they survive way to many hits. They catch almost never fire too. Can you guys just please give the No tracer belts the same ammo mix like in the tracer belts. No idea what ammo type is missing but it might be API.
-
AIM-120 midcource guidance is often not being synced between clients, reuslting in the missile position being quite different between the shooter and target. In this example, the AIM-120, shot by Sizzle, on my end as defender had no midcourse updates, lofted to 60kft and quite abruptly "snapped" active at around 10nm, appearing to pass quite far behind me (the RWR indicated this as well). This is also what was shown on the server track/tacview: Meanwhile, on the shooter (Sizzles) end, the AIM-120 appears to guide normally with midcourse, only lofting to around 53kft because of me diving, conserving energy, with no abrupt snap upon active. It passes in the end quite close to me (this is what is shown on sizzle and his wingman's track/tacview): tracks (from me, sizzle, his wingman, and server) and tacviews (just me and sizzle for illustrative purposes) attached server.acmi sizzle_shooter_client.acmi dundun_defender_client.acmi moldy_wingman_client.trk sizzle_shooter_client.trk server.trk dundun_defender_client.trk
-
already reported Spotlight TMS up issues / SAM Lock issues
Fulgrim posted a topic in Bugs and Problems
Since the last update, the radar is so broken that I'm not even in the mood to fly. Issues in RWS: When blocking a contact in SAM, the antenna altitude constantly oscillates, many times below or above the contact's current altitude. When launching a Fox3 in SAM, the radar loses the contact. IFF not working. Issues in TWS: When pressing TMS Up short to softblock a contact, it immediately goes into spotlight mode and STTs the contact instead. Track here. -
In the attached track, the helo is hot started. After achieving level flight, heading 090 at 115 knots,the helo will roll to the right when cyclic is pulled aft (only a little) Then (heading 109 at 105 knts) pushing cyclic forward causes a left roll so severe resulting in an inversion. Look at the controls box to see that only pitch was manipulated. This is what I would expect from gyroscopic precession. Doesnt the FADEC (or FCS) take gyroscopic precession into account and adjust the blades to prevent this (basically fly by wire)? ApacheRoll2.trk
-
Edit: looks like I'm duplicating my own report from 2020. Had trouble tracking down the initial post; delete or merge as needed. They used to on intial Supercarrier release, then they stopped and have been doing wings-spread initial for two years now, even showing up in official DCS video content. Wings should be swept to 68.