AJaromir

Here I made small video tutorial. As I wrote, it will take time to fully shine. Aslo it will take time to fully exhaust. This is how fluorescent paint works. The UV light does not make gauges shining. It provides energy to fluorescent paint which then emits light. The start position is to warm up UV light electrodes. Same principle like fluorescent lamp starter. But here the start is made manually. Note: It still does not work as it should. It is not possible to blow out the UV lamps when the rheostat is in "start" position.

To turn on UV lights: set rheostat to "start" position for around 10 seconds, then move it back to "out" position. Do not leave it in start position or the UV lamps will blow out. It takes up to minute until the fluorescent paint will start shine on gauges. Edit 2: From my experience the UV lights are modeled properly only in Mig-15. In P-51D the UV lights are modelled wrong - there it works like common bulb on rheostat and not like UV lamp which must be held in "start" position for few seconds and then turned back to "out" position. In other modules I don't know because I don't own them.

I am not sure there is possible to fix this than using no curve. The thing is: For ffb sticks the "center of curve" does not shift. The best solution of this is using the joystick lenght extension tools for now. Also a note: In most WWII aircrafts you don't shift the stick neutral position. The neutral position is shifted by aerodynamic forces. When the aircraft is not moving, there should be no centering force.

Yesterday I did fly P-51D for hours, without issue. Only once when the oil was not warm enough for take-off. In debriefing was "engine jammed". But that was pilot's mistake. I also was able to run it on full WEP for 10 minutes. Until the engine is not too hot or too cold, it will run smoothly for a very long time.

Here is the video with take-off and landing which I've made today in 2.8.0 You can see in input graph (the red square in bottom left cornet) that my rudder input is very stable. P-51D gains rudder authority very fast. Also you can see the take off and landing is very stable.

From my experience the take-off with P-51D in DCS:World might be unstable at some conditions. First of them is overweight. Make sure your aircraft load is in weight limits. Second - make sure you have set rudder trim 5° right. Third - make sure you pull your stick a bit. There is mechanism which locks the tailwheel when the stick is pulled. When the stick is pushed, the tailwheel is unlocked to be able to do sharp turns. Remember, the best take off and landing is perfomed from/on 3-points. Taking off from two points need extra rudder pedal kick when lifting tail - to compensate gyroscopic precession which is created by change of attitude. Time 20:20 Edit: reminder - All of those factors (specially the slip-stream) are most strong when the engine power is at maximum and aircraft speed at minimum. One of those reasons is almost no rudder authority caused by no airflow. All flight control surfaces need airflow to be effective.

Oil dilution is used before engine shutdown. Not after engine startup.

Here is the video which I've made as reference. It is clearly visible how the pressure depends on altitude and instantly drops or raises.

Good day. Flight conditions: - Just when I enter the mission editor and create new mission Terrain: Caucasus Airfield: Kobuleti Take of from runway Payload: - 100% gun - 68% fuel - both droptanks ----------------------------------------------- When I did fly using drop tanks, I've noticed the instant drop of fuel pressure bellow redline. It was like: In altitude 13400 ft ASL the fuel pressure is on top of green strip - around 16 lbs sq. in In altitude 13600 ft ASL the fuel pressure is far bellow the redline - around 9 lbs sq. in The change of fuel pressure is instant. Is this behaviour correct? If yes, should I fly in altitude where the fuel pressure is in limits? By the way in DCS:P-51D manual is written that I should fly in normal altitude. But nowhere in manual is written what is normal altitude for P-51D.

A2A Simulations 3rd party developer?

@okopanja - Yes, because it is "ripped of" from the original Flamming Cliffs manual which contains both the SU-25A and SU-25T. In the time of release of SU-25T its manual was part of FC3 manual and not separate like today. I am working on next reviews.

The 14 day trial does not work in steam version of DCS:W which is where the most of new players come from. The mentioned videos are not official guides. If those are, it is good to post links right in the in-game main menu.

In the tutorial is literally written and told: "make sure that more than three minutes have elapsed in order to let the horisontal situation indicator gyro to align properly" Time 0:42 I know, the INS is usually being aligned. Well, IRL in SU-25 it takes up to 60 minutes. Only the devs know what they want to align. I followed the instructions like the new player would. Yes, probably the turorials were not supposed for new players because SU-25T came after the LoMAC and since that the tutorials had not changed a lot. But time has changed. Now it is the very first aircraft the new player will have the honor of flying this. So maybe it is time to change something. BTW after fast check of other tutorials my opinion is there should be something like official video guide for new players. It is very very much info which need to be explained to new player and now I see this training missions are not the best way how to do that.

I've made the DCS:SU-25T Tutorial #1 review. To show what should be improved. I hope this will help improve the tutorials and so the new player's experince. I will also review all SU-25T tutorials but it will take a time. - First of all, the tutorial should explain how to control camera on first place, how to zoom in, zoom out, recenter camera. IMO this is very important. - The "hear like in helmet" MUST be turned on in "factory default" setting or the player will hear nothing what instructor says. - The tutorial designer should turn off the wind in this mission or explain the source of beeping (AoA/Stall warning) which may confuse many new players. - The tutorial does not count with built-in ATC comms. The messages like "not authorised to take off" may confuse the new player. The tutorial should include the ATC comms or at least say the player to ignore the ATC messages for this tutorial. - In the briefing or right in tutorial should be mentioned the player should meet himself with manual first. The player must know the basic avionics and how to setup controls even before this tutorial. - 0:40 The tutorial says we should wait 3 minutes but the design of tutorial forces the player to skip the waiting. Also in the manual is nothing about 3 minutes. - 1:05 In my opinion the tutorial designer should add info for new players how to ensure the throttle is set to 0 - like: "Check the in-game throttle lever" or "press and hold the "-" few seconds to ensure the throttle is set to 0 power setting" or whatever. - 1:25 IMO the tutorial designer should highlight the gauge which instructor is talking about. Just like interactive tutorials for other addons. Same for 1:45 and on. - According to DCS:SU-25T manual the tutorial does not say the RPM should stabilize at 33% and the EGT should be around 440°C e.t.c.. (manual, page 46) - IMO the tutorial MUST follow the DCS:SU-25T manual to make things clear. - 1:48 The flaps setting is missing in SU-25T Take-off manual. IMO very important thing which should be there. - 1:54 According to instructions we are not ready to taxi yet because 3 minutes HSI align time is not over yet. 3:50 - end of waiting. - 4:39 In my opinion the information about taxi speed should be given before the start of taxiing to avoid problems with sharp turns e.t.c. Mind the many new players does not have rudder pedals or stick with twist. - 5:40 The information about turn IMO came bit late. The instructor should finish his speech before the player reaches the "fork" - 6:30 There is very big problem of the tutorial desing. I've tried it more times. If the player is not enough fast or not enough slow, then the player will strike himself with the helicopter on runway. Solution: remove the helicopter. Also there is no info that pilot should taxi to runway threshold first. - 7:10 again the tutorial does not follow the Take-off page in DCS:SU-25T manual. Very important. Press and hold wheel brakes, increase thrust to 70-75%, release brakes and full thrust, e.t.c... Also most things MUST BE EXPLAINED TO PLAYER BEFORE THE TAKE-OFF MANEUVER. The instructions about raising gear and flaps in tutorial are given to player TOO LATE. Also after take of the player may not know what to do next. The aircraft will change its pits uncontrolably and player might not now if it is right or not. There should be given some info like "hold pitch 10°-15° above the horizon bar by stick" or something like that. Those are IMO the most important things which should be improved in this tutorial which is usually the very first experience with DCS:World for new players. Thank you for understanding!

Is there possible that devs would make it more accurately?

In general the servo is set of actuator of any kind (hydraulic electric , pneumatic,...) which holds precise position given by command. There is not needed any regulator, feedback sensors e.t.c. because those are already built in servo. Simply you put in power and command and it will be executed. For example the electric servos are commanded by PWM signal. It is 20ms long period.

Nothing this year?

The box and the green symbol in it shows the same things like the servo visualisation in Hind autopilot panel or like in MI-8 - which is the deflection of servos. Once those are on the edge of the box, the servos can not do its job properly and so the SCAS. In MI-8 the flight egineer manually reset the servos by rotating knobs on central panel to get them into operating area. In MI-8 this system is independent on the stick position. That's why it must be manually adjusted. In other helicopters like KA-50 or AH-64 or whatever it is bounded with the stick neutral position (trimmed position) So, if the green symbol is on the edge of the box, you should reset trim to new position.

Red cross is neutral force position - the point where the controls are trimmed. The white is pilot input. The green is SCAS servo deflection. The box is SCAS limit.

To see the limits of the SCAS. When the SCAS is on the edge of its input authority, it will not be able to do its job properly.

Which track do you mean? Do I have to post video in youtube again? It is 12 hours of work to make it. Checking this issue internally will take less than 15 minutes.

I can comfirm. Turn on the wake turbulences. Then load E.G. the bomber intercept fast mission for FW-190A8. Fly into swarm of B-17s and stay there for a minute. The frame will drop to very low values. Probably caused by CPU bottleneck which has probably problem to calculate ineractions of turbulences for such big swarm of units. Now try the same thing with wake turbulences set to off. No FPS drop at all. My system: MB: MSI Z170A gaming M5, running in UEFI mode CPU: Core I7, 6700K RAM: Kingstom HyperX Fury DDR4 64GB (kit 4x16GB) 2400mhz CL15 with cooler GPU: MSI GTX1080 Gaming X 8G SSD: Samsung NVMe SM951 512GB HDD: Segate BarraCuda 3,5" 7200RPM, 2TB OS: Windows 10, version 20H2 (build 19042.685), installed to SSD. Game installed to SSD in directory "C:\DCS World\"

If the source is the manufacturer (the sukhoi site) Then probably the ED has the information directly from them. I hope.

This is the data source used by ED to get information about SU-33 https://www.sukhoi.org/products/samolety/military/su33/ http://www.airwar.ru/enc/fighter/su33.html

I don't think so. Why the ED will do the PFM and ASM for Mig-29 then? The SU-33 like other addons got the new PFM with all that gizmo around. ED never do something without relevant and legal data. Also the 3rd pardy developers must send the ED evidence of their flight and systems models and everything must be legal.