Leaderboard

So I was reading a post here somewhere, and someone complained about getting eaten alive by Hinds in Air to Air on a mission, so I decided to run a little test. I set up several engagments with various weapons loadouts for both friend and foe. From an even position with 10k of distance I was able to come out on top with a 4 to 1 disadvantage using guns only. From a position where the enemy had the advantage and a distance of 3k or greater it was about 2 to 1 with guns only. Closer than that and it was a 1 to 1 knife fight. If I could swing around and lock him up with the Shkval quickly I could win, if I had trouble locking him up, toast. Adding missles to the mix gave me an even greater advantage if I had at least 7k of distance. I went head to head with a flight of 5 Hinds and came out on top. The Vikhr works fairly nicely in A to A. I even managed to dodge an AT-6 spiral. Here is what I found. First, set the laser to standby and the engagement mode to AA. Believe it or not it makes it much easier to lock up an airborne target. The HMS is your friend, especially if you have Trackir or something similar. Bring up the HMS, and all you have to do is look where the target is coming from. Keep your zoom out a bit so you can see the Shkval screen and make adjustments on the fly. I actually had better effects with the tracking gates a little bigger than with ground targets. Ussually for ground I keep them small, but here I found it easier to get a lock if they were a little bigger. Make sure your laser is lasing before you fire. You should see TA and the range should be changing, unles of course your not closing with your target. But normally the number will change. Just tapping the lock button quickly well reset the laser, but not cause you to lose your lock, unless there is a ton of movement relative to the target or he goes outside the Shkval FOV. Your gun is bigger and badder, use it. Ever wonder why some guns have long barrels and some don't? The longer the barrel, the more muzzle velocity for a weapon of similar caliber, what this means to you is your rounds will travel farther, and hit harder at a longer range so use that advantage. I found a Hind wouldn't open up on me until he was within 1.5k to 1k. While I could score hits from 2.5k to 3k depending on the deflection. I scored a kill on a hind from 2k with both helicopters moving like bats out of hell from 90 degrees off his wing. Only took 2 bursts. Which leads me to the next point. Remember your gun hits harder. The Hind is known as a flying tank. But your gun is meant to kill actual tanks. Ok well APCs and light armor. But those don't fly, and have more armor. The times I was killed it took 4 to 6 bursts connecting from the Hinds gun to kill me. Ussually 2 or 3 solid bursts did him in. Lastly if you see a burst connecting, and your target starts to fall like a stone, don't fall for it. He's probably just manuevering, he isn't dead. This one caught me a couple time before I figured it out. How do you know he's a lawn dart? Flames, or a big explosion. Otherwise keep him in the Shkval FOV so you don't lose your lock and keep on him. Ok so this isn't a very technical entry, not a whole lot on tactics. But it was much easier than I expected. Sometimes I have a hard time getting the Shkval to lock up a truck, so I expected to have a heck of a time with a fast moving airborne target. But the KA-50 computed distance and lead on airborne targets. The Vikhr worked like a charm I couldn't get it to miss. The only thing I didn't try with it was a firing 90 off a targets wing, but even if the target was jinking I got hits. Next up, Black Shark vs Fast Movers.

I can assure you, at TFC/ED, we do not think that you are second class customers. You are one side of a two headed coin, and a coin that must have two heads.

I haven't actually used Cachya, but I have tried 2 FreeTrack setups (one 30 fps webcam, one 100 fps Wiimote) and one HAT-Track setup (worst ever, do not buy under any circumstance). Plus, I have two TrackIR 4s. I’ll try to shed some light on what I understand and believe the differences to be… both technically and experientially. While the respective software--be it TrackIR, FreeTrack, or Cachya--can be important, the bulk of the performance comes with the camera. Good interfaces optimize your tweaking process, process the 6 DOF algorithms with more/less success, manage profiles, and regulate CPU footprint a bit (plus potentially lots more). All good, important stuff to consider. But, in the end, they're just the go-between. The camera determines the quality of data the software can work with. There are at least four (probably more) main aspects you should consider when evaluating the camera: resolution, frame rate, field of view, and processing. The resolution is probably tied for most important on that list. The more resolution you have, the more stable and responsive tracking will be. If you have very few pixels tracking your head movement, small head movements will either not be picked up at all or will be significantly exaggerated. The more resolution the camera has, the more granularity of the motion tracking. This is a good thing. More granularity = more stability = more native smoothness. Native smoothness means that artificial smoothing is less necessary. Since artificial smoothing is essentially an averager, it introduces latency. (It can't predict your future head position, so it makes you wait X frames before it can average their results and give you a nice, smooth motion... that waiting = latency.) So, if you need more smoothing (because your resolution is lower), you will have a longer delay in your head tracking and a much harder time "stopping" quickly. Many low-res/high smoothing head tracking demo videos on YouTube show this. The motion will often kind of crawl to a stop when directions change. Resolution is also important when tracking at further distances. The further away you are, the more physical space each pixel of resolution represents. Low res cameras assign large chunks of physical space to each pixel. This results in the unstable tracking described above (unless severely smoothed, which introduces problems already outlined). Frame Rate is basically just as important as resolution. The faster the camera updates, the more likely that when it reports your head position to the game, it will be correct. If a game updates at 60 fps and your head tracker updates at 60 fps, for your head position to be correctly represented, they need to be refreshing exactly in sync. This is essentially impossible. Their inconsistency is called phase drift, and you basically can't avoid it. So, the best solution is to pump as many frames to the game as possible. The more times the camera tells it where your head is, the higher the likelihood that it will be correct. So, a 30 fps camera will never give you an accurate reading of your head movement, because it just doesn't keep pace with a decent game refresh rate. An additional problem with low refresh rates involves the smoothing addressed above. Because smoothing requires a delay of several frames to take its average from, a slower refresh rate makes you wait potentially 3-4X as long to get your movement to register. A 30 fps camera will take 4X as long as a 120 fps camera if they have the same amount of smoothing. Field of view is important for obvious reasons. The higher the FOV, the more physical space you have. The only downside is that at really high FOV (maybe 60+), you start to get distortions at the edge of the viewing area. So, the marginal return after 60 degrees or so is likely pretty small. Processing can be hugely important... both type and location. If the processing is done on the camera, it lessens the footprint on your PC. If you have a monster of a machine, this probably doesn't matter. If it's older, this could certainly matter a lot. Processing type is also important, but kind of hard to explain. Basically the camera can see light in different ways. TrackIR 4 uses segment tracking, which is OK, but does cause some inherent jitter if completely unsmoothed. There is talk of a certain TrackIR 5 releasing soon, and I understand it will have grayscale tracking. This would be huge, because it allows the camera to see much more subtlety in light. This means way less jitter and a lot of stability. The problem with grayscale is that it gobbles up bandwidth. I think most smaller cameras couldn't handle it on-board. So, to summarize... A camera with high resolution and low frame rate (high-end webcam) will give you smoother tracking, but more lag. A camera with low resolution and high frame rate (Wiimote) will initially give you less lag, but will be more jittery. The jitter will require more smoothing to be steady, which wil reintroduce lag into the tracking. A camera with low resolution and low frame rate (low-end webcam) will be laggy and jittery, and if smoothed to reduce jitter, really laggy and mushy. Really, the most disastrous confluence of conditions when it comes to motion tracking of any kind. A camera with high resolution and high frame rate (TrackIR, others??) gives you the best of both worlds. It should accurately and quickly track your head movement, but also should have good native stability. Whether you really need stable, smooth, and fast tracking is a bit subjective, I guess. If you only doddle around cockpits, it’s not hugely important. :) If you race or play tactical shooters, a laggy or imprecise camera is worth little.

i know its too much to ask but i would love to see ground crew working on BS or up coming A-10 when we give them orders to refuel or reload weapons based on realistic timing... since you guys have given us such a great, detailed simulation one would like it to be more realistic... i know it would deviate from the main purpose of the game but one can always enable/disable that feature if it is provided... like turning on the tip lights should mean something to me that i have to look around if the area is cleared before i turn off the rotor brakes... its a little far fetched but can be possible... "click YES if you think it would make a difference" would like some feedback on this as well...

As you know TrackIR5 is on its but yesterday NaturalPoint released new software update: http://www.naturalpoint.com/trackir/06-support/support-download-software-and-manuals.html

Indian Su-30MKI crash near Jaisalmer in Rajasthan, killing one of the two pilots. The incident occurred at around 1020 hours near Rajmathai village, about 70 kms from here, when the plane, the squadron of which is based in Pune, was on a routine exercise, Defence PRO Lt. Col N N Joshi said. According to district officials, one of the two pilots, who were both holding the rank of wing commander, was killed. The other pilot managed to eject safely from the aircraft, they said. A court of inquiry has been ordered into the incident, IAF sources said.

РЛЭ на миги валом валено, например: http://civilavia.info/documents/home.html

Hi. I’ve done a review on the Black Shark and it will be published in Aerospace International Professional. They will launch a PDF onto the net for those that don’t subscribe. It explains how an Apache should take on the Ka-50 too and what type of fight to draw it into! I have designed 'Advanced Weapon Lessons' and 'Afghanistan' programs for the Boeing Apache Simulator before running the crews through the sorties. You should have seen the sore thumbs on the crews after two hours of ‘weapons hell’! With that in mind the ED DCS Ka-50 was great. The graphics and user interaction were awesome. I really liked the way the cockpit replicates the real thing, even down to the scuffed floor under the pedals. I have spoken to the Russian contingent on this forum in my pigeon-Russian. It’s quite difficult but some of it is translatable! A friend of mine tested the Apache at altitudes that I thought helicopters designed for sea level could never attain - seriously high. The oxygen mask fitted fine with the monocle, it worked a treat as did the British Apache with its Rolls Royce engines. I don’t get much time for reading through forums at the moment but will reply from time to time whenever I can. Best Ed PS HarperCollins released the paperback version of Apache today. The paperback version is interactive and a website accompanies it. We have MoD declassified video on the sight and its well worth a look (last video). It’s at http://www.harperplus.com/apache Ed Macy www.edmacy.com www.harperplus.com/apache www.twitter.com/edmacy

:D:doh:...И снова кто то считает коммерческий успех,выгоду и еще много чего о чем команда ИД не спрашивала. Вот скажите - те, кто так отвечает? Вы что читать не умеете? или не понимаете о чем прочитали? Опрос вроде понятен и не сложен, и не надо сильно напрягаться для того, что бы просто ответить без измышлений в сторону. Андрей(Stalker)- молодец!

Сэры, а вам не пришло в голову(ы), что он переводчиком пользуется? И с каких пор в Испании английский стал родным?

:thumbup: I am so glad to see that most of us are on the same frequency... and i hope that up coming patches for black shark and maybe in A-10 DCS has this feature, i totally agree to what Poko is saying... its all about how much one is serious about this simulation, one should actually get the realistic factor in dealing with the ground crew may they be the refueling crew or the marshals... that brings out the seriousness... like its no joke... this maybe not that appealing for the pilots who play in Game Mode... but it matters to me... Alot

Я бы не был столь категоричен.

-fixed nose shape -added some details on landing gear almost finshed texturing and here are some new screenshots.:)

Там обычная модель МиГ-29, только и всего, она без гака, и садится на авианосец не может. Полноценно полетать на МиГ-29К мы сможем только если Alfa найдет возможность сделать корабелку с рабочим тормозным гаком, либо в будущих модулях DCS. А чтобы были будущие модули для DCS нужно покупать лицензионные диски с симуляторами от ED, тогда у них будет хорошая прибыль, они смогут нанимать больше программистов, которые будут штамповать новые летабельные самолеты :)

Use of "Swallow airbrake" is disabled with a lowered landing gear on 9-12 and 9-13 airframes. It's because the AoA during landing might damage the airbrake feathers so it could scratch the tarmac before wheels touch it and cause some damage. However, newer MiG-29 airframes (M, K, MiG-35, OVT) have a redesigned airbrake, so called "Beaver tail" that can be used with gear in green!

People would complain about the Brick's turn radius, and the fact it's undermodelled. Evidence would be provided, including theoretical papers from MIT proving that bricks have a superior climb rate to the KA50, especially at low altitude. ED would inevitably be forced to produce a brick modelled on popular American types. GGTharos will write 5000 words on why it is too fast.

Cool Su-33 movie: http://video.aviacia.ru/478 Photos from Aviacia.ru!

The only other thing that isn't lining up for me is the start/pause, but that doesn't bother me at all. My control input window seems to be doing fine, as far as I can tell, but I'm going to do some more testing on this. As for the three green lights, I'm not sure what you are talking about here. I guess mine isn't being affected or I would probably notice it. Most of the minor bugs we are having are just that, minor. :smilewink: But it would be nice to get it perfect. :thumbup: I'll play around with settings more today and if I find something I'll let you all know. Also, just wanted to let you know that I can't take screenshots either. I get the array error as well. I just found this out because I was going to post a shot of my UI, but I guess I'll have to figure out a work around for this first.

In context of the Ka-50 the A-10 have some speed.

Here are my settings: Options: 2 monitors abris + shkval on left monitor 1360*768 16:9 aspect main monitor 1680*1050 16:10 aspect ["multiMonitorSetup"] = "2mon camera+shkval+abris1024", ["color"] = "32", ["heatBlr"] = 1, ["scenes"] = "high", ["water"] = 2, ["fullScreen"] = false, ["visibRange"] = "High", ["aspect"] = 2.895238095, ["textures"] = 2, ["shadows"] = 3, ["display_mode"] = { ["avi"] = { ["bpp"] = 32, ["resolution"] = "640x480", ["full_screen"] = false, ["aspect"] = 1.333333333, ["height"] = 480, ["width"] = 640, }, -- end of ["avi"] }, -- end of ["display_mode"] ["effects"] = 3, ["lights"] = 2, ["haze"] = 1, ["terrPrld"] = "20", ["height"] = 1050, ["resolution"] = "3040x1050", ["civTraffic"] = 1, ["width"] = 3040, }, -- end of ["graphics"] } -- end of options Description = 'Shkval+Abris on the left monitor, camera on the right' Viewports = { Center = { x = 1024; y = 0; width = 1680; height = 1050; viewDx = 0; viewDy = 0; aspect = 1.6; } } Shkval = { x = 1360/2; y = 0; width = 1360/2; height = 768/2; } ABRIS = { x = 0; y = 0; width = 1360/2; height = 768; } Please help

В войне с Чечнёй чечены тоже читерили :megalol:

Ящик водки и всех обратно! :D

Hi all, Legolasindar and PB0/KGM_Foxy, thanks for the images and the Link, the first Link already knew but the second and is not very good, thank you very much again.:smilewink: I believe that the French image of HAD is a version of one of the last prototypes of the Tiger before entering the line of production:smilewink:. The difference between the HAD(Helicóptero de Ataque y Destrucción), Spanish version, the HAP and the ARH, is that version HAD and the ARH have engines with greater power than version ARH and the systems of allocation and location of targets, that vary depends on the type:smilewink:. I put to you a series of Render of the model:smilewink:, so that you see the evolution of the work realized on the Tiger in these days:smilewink:. As they can see almost is finished the model in 3D, only need to finish I the main rotor and to make artilleryman and the flight cockpits and to make animations and textures by all means. I process from the last remittance of Render that I put.:smilewink: The present state of the project.:smilewink: Since they can see this one it already has the first painting hand before applying the mimetic definitive one to him:smartass::smartass::smilewink:. I hope that you should like the aspect of the model and if you have some comment that to say to me, you do not hesitate to say it:smilewink:. A greeting and good hunting.

Sorry my bad im not using the the modman version. But still its the same mod

Model looks grate, much appreciated for the hard work everyone did on this model. This was about time Su-27 did get a face lift:) Thank you!!!! Now when Su-27 is ready would it be as hard to model su-33?

FaceAPI to PPJoy 1.5 Обновленная версия FaceAPI to PPJoy. Сглажены все оси, немного изменена логика работы фильтра. Стало значительно стабильнее, картинка не дрожит. Выкладываю только exe файл, который нужно подменить в старой версии. Вот новые настройки осей в ЧА Ось Горизонталь Абсолют: Ось Вертикаль Абсолют: Если ничего не перепутал, то все, успешных полетов! :pilotfly: П.С. Добавляю трек с демонстрационным полетом. П.С.2. Ассиметричное освещение стало значительно меньше влиять! TestAppConsole.rar FaceAPI_Test4.trk