Quetzalkoatl

There's another bug which coexists with one described in this forum section. Not modelled parts of the map appear black in spring and autumn months, but they look fine during summer/winter England, western map border May 31st And the same location but 1st day of June Here are screenshots from the same mission. Possibly those two bugs have common reason, or one is linked to another.

As F-4E is planned to be released in late 2022, I was wondering if it's still possible that two remaining variants of Tomcat (F-14A-135-GR (Early) & F-14A-95-GR (IRIAF)) would come before Phantom or I should expect them after F-4E release

I noticed this as well, and not only in F-14A but also in B variant.

I'm wondering if it's the same F-4E that Belsimtek worked on before merge with ED Because that would explain partnership with ED in making F-4 and why it's announced to release this year.

Back in May 2021 I bought The Channel. After checking out all airfields I noticed that there's something wrong with Dunkirk-Mardyck grass strip. Grass part of the runway seems to be extremely bumpy - it acts pretty much like casual ground which is not prepared for aircraft usage. It is possible to taxi on it, but as soon as you reach ~120 km/h, problems with stability start to be noticeable. ~140 km/h is the moment where large jumps to the side start happening - that in the end leads to a crash. Landing looks very similar but because it happens at higher speeds the results are a bit more drastic. I chose Fw 190D-9 for this bug report because in my opinion it's one of the most stable on the ground out of all WWII modules. There are two track files - one from take off attempt and second shows landing. TheChannel_Dunkirk-Mardyck_GrassStripBug_TakeOff.trk TheChannel_Dunkirk-Mardyck_GrassStripBug_Landing.trk

I have this bug too, not seeing any reference points in ME is problematic for someone trying to decorate the carrier I guess it would be good if this post got moved to Super Carrier Bugs and Problems section, so ED has easier time finding and fixing it.

Yeah, it would be great if it this option was added... possibly in a hotfix? It is possible to trick the system with AI menu where camera transpose mode is present there, then change seat to weapon operator and go back to pilot to make petrovich cursor disappear - unfortunately it works only in single player as in multi changing seats is impossible.

Hey everyone, I had this idea in my head for some time and decided to write it here with hope that one day ED is willing to implement it. As you could have guessed after reading the title, I'd want it to be possible to set custom bort number to static aircraft as well as give them specific payload. It definitely would be important improvement for mission makers who'd want surrounding scenery to be as close to real life as possible. Things with bort number i managed to achieve by spawning AI aircraft on the parking spots, because those have them editable. Then I set fuel to 0% so they wouldn't try to take off. Basic cons of this solution is that pilots are inside of these aircraft and I am limited to use only parking spots instead of whole airfield ramp. And here's the part of this effect that I'd love to achieve with static planes too: All of these AI controlled planes are with their real numbers - in a way that they match real counter part that is visible on archive photos. Sadly it is currently impossible to set it like that when using static aircraft because it gives random number to each static plane. Thank you for reading.

Would be good if 6 pylons on BS3 were optional. For those who feel the need to have proper Ka-50 without any fictional stuff - 4 pylon wings should be there too... And please don't tell me to fly BS2 if I want only 4 pylons - because afaik it's not getting new 3D external model which is one of the most important stuff of this whole upgrade. When we look at previous BS3 pictures we can see that 4 pylon wings were already done, hopefully they did not end in a bin and still can be implemented. Pylon number could be changed via ground crew commands (e.g. like in JF-17 refueling probe) and mission editor.

Hey, generally I have to say that this is one of the best top quality mods ever made for DCS. I absolutely love how it looks, and how it files... oh well - I actually found something that seems to be an issue: It looks like engine performance related to altitude isn't modelled correctly and it does not lose thrust while gaining altitude. Which results it going extremely fast. If not hypoxia then I guess it could reach even Mach 3. Here is another image - dive after passing out from hypoxia: Hope you'll find a solution for this... and again thank you VNAO team for this piece of art!

F-16 external fuel tanks textures are not showing up on a plane. It's the most visible in case of tiger meet camouflage that should have tiger stripe pattern on the center fuel tank. Both skins have default american textures on their external fuel tanks which are a bit darker than they would be in case of working polish textures. Tiger meet camouflage with fuel tanks textures in red frame: Standard camouflage: Tiger meet with fuel tanks textures in current DCS open beta (central fuel tank missing tiger pattern) Standard Also worth mentioning that both skins have no consitency in exhaust nozzle colour: Standard shares nozzle colour with US agressor skin, Tiger meet has its own darker. Here's .trk file that lasts 1 minute where those planes loaded with fuel tanks are "posing" to my screenshots: F-16C_PolishAirForce_Livery_Bug.trk

It doesn't look like system wants to recover from it - in 2nd track i took control at 13:36 of the mission, left engine idle. Plane didn't recover from the stall and crashed. Tried the metod with MPO switch in another trial, also took control at 13:36 and managed to recover... at least that works. I have no info how it should work in real plane - it just looked strange in something as advanced as F-16C block 50. In best case scenario this thread will have [NOT A BUG] next to the title.

Hello Today I encountered a bug that looks like this: Under certain conditions like slow speed, high angle, thrust above idle and higher altitude F-16 tends to have FBW freezes that causes it to have elevator in constant down position, controlling via stick is impossible. Plane basically falls from the sky and nothing can be done about it. Increasing throttle to afterburner prevents it from crashing, but it remains in high alpha (still without ability to control it) When it's low enough somehow it manages to turn itself level enough to gain speed and wake up FBW system. Here are 2 track files. 1st is achieving that state by accident. Please keep in mind that I was afk for around 20 mins and didn't pause the game, so you may want to rewind it farther in time. F-16_FBW_freeze_bug_1.trk 2nd is trying to reproduce it on purpose (which is difficult and took several trials during this flight) F-16_FBW_freeze_bug_2.trk

I spotted that when nothing is assigned to "camera transponse mode" then mouse button 3 is still performing as it was assigned to it. I had it assigned to mouse button 2 and it doesn't work after most recent patch, all other mouse buttons work when assigned. Could ED bring back mouse button 2 for this function? Thanks

Here is the video Slowed down in-game time so it's easier to spot the issue.

I'll put it this way: this bug is present in that video from that bug report https://forums.eagle.ru/showthread.php?t=252409&highlight=exhaust It can be seen around 31st second of the video. Slowing down the video to x0.25 may help spotting it. Everything else from that bug repot has been fixed. Torching is gone, and nozzle is fully open for the whole time of RPM increase in engine startup process. I think that making bug report about it is necessary because it's still there, 8 months since EA release, and it seems like it's difficult to spot. Also, right now I am absolutely sure it happens in the moment of moving throttle to idle position (RShift+Home by default).

During engine startup exhaust nozzle blinks in the moment of moving throttle from 0 to idle position. F-16_nozzle_blink.trk Here is a track file, described event happens really fast, somewhere between 37-38 second of track.

Yep, there were few planes with just eyes... so it would be nice to still keep it and add clean Polish Air Force skin as it used to be. That way we'd have 3 polish skins. Adding emblems to it like in 8705 would be nice.

Hey, I have found a bug in F-16. While being low on fuel <2000lbs, and relatively low alt <3000 ft, and flying above Mach 1 speed plane starts to wobble. It's impossible to counter it. To be honest, moving any surface during this event or when it is about to start wobbling will cause much stronger wobble later. I've tried it only with no pylons loadout. Problem doesn't happen when plane has more than 2000lbs fuel. There are 2 short tracks, in 2nd one I have turned autopilot on (alt and course hold). F-16C_low_alt_FBW_bug .trk F-16C_low_alt_autopiloton_FBW_bug .trk

Hey, Yesterday I was flying F-16 in AO server. I took 3 fuel tanks and didn't clean rest pylons. Took off from Tibilisi and was heading Anapa - all time with afterburner at altitude 30K+ ft for most of the time. Jettisoned all fuel tanks when they got empty - 1st central one then 2 wing ones. Shortly after reached bingo 1000lbs, I switched afterburner off and was continuing flying straight. Suddenly plane system started doing weird things with control surfaces - i couldn't do anything despite moving a stick. After falling down below 10K ft managed to gain control back. I couldn't send a track file of that event because .trk file of server with over 200 vehicles and 50 players flying at the same time was way too big. Luckily managed to do that again in single player - and got track from there. F-16C_FBW_bug .trk Important events happen in the end of that track (after 7:24 PM of a mission time) so you may want to speed it up for saving some time. I also caught probe heat bug that was already reported here https://forums.eagle.ru/showthread.php?t=263739 but was missing a track. In my track you can clearly see that Mach on HUD is almost 2.0 while plane is doing 1300 km/h TAS at like 40K ft.

I spotted that F-16's exhaust nozzle changes position way too fast during engine startup. 10 seconds after ignition it goes from 100% to 0% in like 1/4 of a second. 23 seconds after ignition it blinks one time even faster. After that engine starts torching afterburner - but i've seen that this has been reported already... so just mentioning it here. Here I post a video with that bug: And track file:F-16 Nozzle Startup bug .trk

F-16 Trailing Edge Vapor bug .trk Here's a track I made where bug happend Action starts at 8th minute of a track

And here is a video:

F-16 is lacking left over-trailing edge vapor. Here's a screenshot

Would be nice if ED added Polish AF livery - even though DCS F-16C is block 50 and Poland uses block 52+.