-Rudel-

Stop going to 5200-RPM. 2700 should be Max. Yes it's a bug as I've already told you in another thread. The engine took damage from that and most likely caused the engine driven fuel pump to fail. You're auxiliary fuel pump is off. With a damaged pump, you had no fuel going to the engine which would have caused it too stop. As for the shaking, it's most likely the cause of going to 5200-RPM and drastically dropping the engine speed to 2550.

Hi, Please provide a track file, dcs.log.

I understand how trim works and the effects of the pressures around aircraft control surfaces. For the F4U, I simply stated and correcting how the trim tabs operate in relation to the control surfaces. With no lift, adjusting trim will not mechanically cause the control surfaces/flight stick to adjust also. This aircraft just isn't designed that way. As pointed out by @Vladinsky, in the game they are moving. I replied that it's a bug by the programmers, and it'll be rectified. Example of the elevator trim tab linkage below. The screw and sprocket is the trim control. The screw itself is fed inside through the torque tube to the bell-crank with no contact except for some ball bearing ring at the sprocket plate. A chain/cable system is attached to the sprocket threaded to the trim control knob. This keeps the elevator neutral regardless of the trim setting. Now if there is pressure on the control surfaces while the trim is adjusted, yes the control surfaces will deflect along with the flight stick. If this isn't happening in-game, we'll fix it.

Right now the programmers are focused on the water injection and engine damage model. They'll look into it afterwards

There is a connector at the center of every lift. It will lower as long as the player and/or AI is placed correctly over it.

The tail wheel fork on the actual model itself is animated correctly. ED requires 180 degrees both directions. The programming of differential breaking is correctly programmed. The game uses a simple "stick" that acts as the tail gear/wheel. It doesn't rotate or move when extended. The issue is the 3d visual of the fork doesn't rotate 360 degrees properly in game. We are aware of the issue for many years, and can't seem to rectify it.

In this mission.... During take-off the master switch is off. Even though you're at full throttle and above 54-in/Hg.....this is good. At 1890 you turn n the master switch, but WEP did not enable because your MAP has not reached 54-in/Hg yet.....this is good At 2030~, you go full throttle, but WEP did not immediately turn on, because MAP didn't hit 54-in/Hg yet, once it did, WEP enabled. ...this is good So now you're hovering around 55-in/Hg..... At 2147~, you drop throttle for a bit causing MAP to dip below 52-in/Hg momentarily, causing WEP to disable And turn back on, when you went full throttle causing the MAP to increase above 54-in/Hg Everything is working as intended for this update, however the programmers are still working on the switch logic for a future update.

So in this case, when you finally went full throttle, WEP enabled. Roughly ~58-in/Hg Now...when you retarded the throttle, WEP stayed enabled, until the pressure dropped below 52.5-in/Hg......this is a correct operation of the pressure actuated switch.

They are concave mirrors, but to which degree, I don't know. The programmers adjusted the values to give the best rear viewing possible. As seen in my screenshots

I personally don't know how to add static objects to the hangar deck, but it is there.

I'm referring to the outside environment & quality along with auto pilot animation. In any case, seen in the last 3 screenshots I posted, is the code that should have been uploaded to ED servers. And if it was, it was most likely overwritten by accident.

The EA manual is being updated and will be available when fully finshed

We are trying something new with bug listing...because honestly, the Mantis Bug Tracker isn't great for us. For your viewing, we are sharing a google document with a list of bugs that we acknowledged on this forum as being looked at in some form. Our goal is to simply show in Orange highlight, that the bug and/or request has be fixed and/or implemented on our personal test build. And then highlighted green when our testers have confirmed it, to which then we will upload the fixes/requests to Eagle Dynamic's servers for further testing. This document, may evolve into a spreadsheet, but as requested by the Devs, it's in a doc for now. Some bugs may have been fixed already, but we'll be double checking. https://docs.google.com/document/d/1aOrQR8opRdUnNfK9aAFfXnRZUB6IGGDSYP5xXOkk9Jw ____________________________________________________________________________________________________________________________ Мы пробуем что-то новое в области отображения ошибок... потому что, честно говоря, Mantis Error Tracker нам не очень подходит. Для вашего ознакомления мы делимся документом Google со списком ошибок, которые, как мы отметили на этом форуме, в той или иной форме рассматриваются. Наша цель — просто выделить оранжевым цветом, что ошибка и/или запрос исправлены и/или реализованы в нашей тестовой сборке. А затем, когда наши тестировщики это подтвердят, они будут подсвечены зелёным цветом. После этого мы загрузим исправления/запросы на серверы Eagle Dynamics для дальнейшего тестирования. Этот документ может превратиться в электронную таблицу, но, по просьбе разработчиков, пока он представлен в виде документа. Некоторые ошибки, возможно, уже исправлены, но мы будем их перепроверять.

The 3d file is animated correctly. The programmers will need to remove that visual bug via code. They'll look into it

We are trying something new with bug listing...because honestly, the Mantis Bug Tracker isn't great for us. For your viewing, we are sharing a google document with a list of bugs that we acknowledged on this forum as being looked at in some form. Our goal is to simply show in Orange highlight, that the bug and/or request has be fixed and/or implemented on our personal test build. And then highlighted green when our testers have confirmed it, to which then we will upload the fixes/requests to Eagle Dynamic's servers for further testing. This document, may evolve into a spreadsheet, but as requested by the Devs, it's in a doc for now. Some bugs may have been fixed already, but we'll be double checking. https://docs.google.com/document/d/1aOrQR8opRdUnNfK9aAFfXnRZUB6IGGDSYP5xXOkk9Jw

hmm, we'll check this out, thx

Just a note: The trim tabs on the F4U do not adjust the control surfaces. They are mechanically separated by design. The flight stick will never adjust too.

Ok, added to our list now https://docs.google.com/document/d/1aOrQR8opRdUnNfK9aAFfXnRZUB6IGGDSYP5xXOkk9Jw

Hi, we'll see what we can do

Lights use to automatically scale in size as the distance moves out. Not sure why it's broken in DCS. I'll see what I can do

Same is with MiG-21, we'll check this out

Hi, we'll look into adjusting the speed.

Hi, we'll look into this 🛠