theChris

Wing lift, nullified in the vertical. While pulling up you will stall a wing DUE to engine torque at low speed (which is what i thought you were getting at with your previous comment) You guys are right about the torque rolling thing, more rpm = more power more torque - more power given the other is constant. If power is increased at a constant torque the plane will still have a higher "torque" acting on it from the engine. :) editL btw im just a student i don't claim to be a no it all. This is just what i understand

Yes more power more torque, which also means faster roll rate at low speeds too (while rolling with the torque). In general planes turn better in the direction of their torque. What i mean is you won't be fighting in the vertical at near stall speeds. That being said the 300-400hp difference (or whatever it is exactly, it changes depending on alt) shouldn't make too much difference anyway, and a good pilot will naturally counter the torque with ailerons at constantly changing speeds.

Excuse me for buting in, but i think Hummingbird is talking sustained turn at lower speeds then optimal (i.e. pushing your plane to the limit in a turn like almost everyone will do in a turn fight to avoid being sliced within the few seconds of an engagement). In a prolonged fight you are better off having more thrust as you can maintain a higher aoa then the slower accelerating enemy who has to decrease aoa to decrease induced drag so that he does not stall.

Also based on the manual the fw-190 we are getting has the semi retractable tail wheel. Adds a significant amount of speed.

Low speed turn: Dora, try maneuvering a plane with engine off, while drastic this wil show you the importance of horse power while turning edit: Dive: debateable, can be split into different categories like low initial speed dive:Dora, high initial speed dive:p-51, Dive recovery: Dora. High speed turn: pilot (opinion)

Hello, so bf-109k4 is a late 1944 German aircraft. Main opposition consisting of p-51/47 d American aircraft and Spitfire mk9 and mk14 British aircraft. I read that fuels are limited to B4 for Axis and 100 octane for Allies. So k4 top speed at 1.5-2.25km ranged from 630-640km/h, with a maximum speed of 712km/h at 7.1km Altitude. A safe landing speed of 150km/h thanks to leading edge slats and high chamber wings, combined with an all moving tail plane (flying tail like) controlled by a trim wheel make it an innovative aircraft imo. Just a bit of useless information to spark conversation about the 109 k4 and its competition to come in DCS World.

Any info on the k4 1g stall speed, virage time e.t.c?

would an enemy going 80 degrees off have a chance to go off radar as well? If so what would you estimate the top speed of this plane before it is recognized by radar.

I can speak for the su-25a but not the a-10a yet (due to recent experiences). The su-25a flight model is amazing, combined with the challenge of no tv this plane is great fun. Just the other day before i realized it has an afm i flew over to engage an enemy tank column but got hit by a couple stingers. 4km down the road with no engine power i was able to make a crash landing on the grass at about 300km/h. This truely impressed me, if i was in a flanker/mig29 or f-15c i would haveprobably flown underground upon landing :thumbup:

so the 70km range is without loft?

is it safe to say at a 65km shot the r-27er would reach the target first compared to the aim-120c5? Because of lofting. Note: this is a non maneuvering target

http://www.youtube.com/watch?v=iZk1yCYIdXQ&feature=youtu.be after repairing damaged landing gear from a submarine landing this happens. i think it also happens to other fc3 aircraft. edit: sorry forgot to disable record sound, may be a lot of swearing and offensive language.

http://s1.postimg.org/802b7pq9r/Untitled.jpg' alt='Untitled.jpg'> image hosting sites[/img] blew up around 60 seconds later lol.

Hi do you think you could include the normal r-27 missile in furthur tests (to compare with aim7m). Anyway here is a little info about the missiles to help estimate where they should be kinematically. --------------diameter(mm)--------------length(mm)-------launch weight(kg)-----source aim-120c-----177.78---------------------3660----------------150.75-----------------fas.org r-77 ----------200------------------------3600-----------------175--------------------enemyforces.net r-27er--------260-------------------------4780----------------350--------------------enemyforces.net r-27r----------230------------------------4080-----------------253--------------------enemyforces.net aim-7m-------200------------------------3640-----------------225--------------------fas.org

my plane rolls to the left to, but i do use a ps3 controller...

NICE! i might have to back track ir though =[

I am pretty sure the first two lose guidance because of the hill infront of me, the last aim120 is stil burning and it is seen that it tried to get me but i went into a big maneuver. p.s all missiles are aim-120c's except the first which is an aim7m

How to be the best of the best while flying a su-27. http://www.youtube.com/watch?v=VA-RItY1umM&feature=youtu.be

Hi i had similiar isues but in one instance was able to complete the mission! Kill al the f-16s before telling the frogfoots to attack. However i played this mision multiple times and it could just be an ai bug, all other times they would destroy the buk radar then head home with ful payload minus 1 kh58. One way to complete would be cheating and turning immortal and unlimited ammo on and strafing with your mg. This is what i did on the mig29s mission similiar.

Thanks for the clarification. But do you think in future it will be taken out of bvr controls? Only to avoid confusion.

Okay, but why is it under censors and why does it change scan zone range.

hey, this is where i found it. dcs world singleplayer --> options --> controls --> mig-29s --> censors--> scroll down to "target specified size increase/decrease (r alt - or =) Based on the english above(the command above specify size) "target lock" (which allows you to lock onto your target), the target specify size implies that i am able to specify my "targets"(blip on radar) "size". The entire point on this thread (before anyone posted) was to find out why this command would not work and only changes the "Radar scan zone" but in a different way (instead of 2-5 increments the increments increase as command is held down). However, now i am unsure if this command is meant to be there or not. If it is as you said Tharos, should the command be reworded to "radar scan zone increase/decrease" as well? Or is my english failing me (i took english throughout highschool just to chill and watch films etc).

you wont be laughing when i can spot invisible aliens heat signatures. btw this is a joke, i am not some radical anchient aliens guy.

Hi, thanks for all the information... But either i am not understanding the concept properly (which i thought i have been since i posed this thread) or i have poorly worded my thread. I understand that the manual distance input scan zone range, r cntrl - or =(stated previously as + in my thread, this could be everyones misunderstanding else people may just be skim reading my post) is a variable put into the electronics of the radar. This variable then would go into an equation with the height variable, and the radar will specify its search +height(in km) over the specified distance.. What i mean is you put the estimated range to target at a certain height, and the radar adjusts the height of its waves (for example if i did not input manual distance and enemy was 1km above me it would search 10km infront and 1km up. So if the enemy was far ahead my radar would be searching way above him.). note: you only put in manual distance to target if you are slewing the height (i.e. target is higher or lower then your radar).So correct me if i am wrong from this paragraph. Anyway this post is not about how to use this feature but why do the controls state different meanings for the same thing, with two different key bindings? "In the controls of the russian radars there is the option to select target size (r alt and + or -) and change scan zone range (r cntrl + or -) but these both change the exact same thing." Clearly r alt and - or = does not change the estimated target size. For example if i was told by awacs "boogies coming hot bearing bla (my 12) 7km altitude (while i am 6km altitude) 60km and closing". I would then set my radar scan range to 50-60km and height to +1, This is fine. What if these boogies were remote control planes? I know i will set my estimated target size 10x smaller. With the push of the old r alt - i am now at ... wait what 30km estimated distance to target? This can't be right. All it did was change my range to a closer target, now my radar assumes the target is 1km higher at 30km so it will search higher then the real threat at 50km (+1 km altitude). Do you see what i mean. I was hoping this spicify target size function would help me spot predator drones and f-16a's more easily. However it does not. In conclusion i am either horribly wrong, this is a bug, or there is more too it then i understand and somehow decreasing the range of the target somehow increases the chance of picking up a smaller target at the same range of the estimated boogie. I think it is a bug.

i would be keen, but annoyed when the awacs dies. It would be nice to have a well defended awacs for both sides.