Leaderboard

Ребята, вот решили показать модель над которой сейчас трудится наша команда.

Some superb photos of a Typhoon sub, both inside and out http://community.livejournal.com/ru_submarine/17486.html

New 3D model C-17 Globemaster III by precise3dmodeling.com

I beg to differ. In game, it works very similarly to targeting points. The closest explanation to it is on page 7-9 of the manual. (Assuming Targeting mode has been reset) 1. Select the Datalinked target of choice (it will flash on ABRIS) 2. Select the "DL/Ingress Button" (next to Send/Mem). Once selected, your target of choice will be marked in a cross on the ABRIS. 3. Uncage the Shkval. At this point, the Shkval should attempt to "snap" to the datalinked target location if it is within the Shkval field of view. Fine tuning may be required. Also, notice that the targeting gate on the ABRIS should be over the datalinked target icon. Keep in mind, as long as your AP functions are engaged, your aircraft will also attempt to orient itself on the targeted axis when approaching to attack. Have to test later, but you may also be required to turn your Automatic Turn on Target button to maintain the targeted axis while attacking. Love to use it for high altitude rocket suppression at long distance. It also saves a lot of time when needing to identify the exact target that has been handed off.

I'd first check the stick and throttle with the SAITEK Control Panel. See if the throttle has the same behavior there. If not, go to the options-screen ingame and make sure you don't have 2 axes set to throttle. If you have rudders connected as well, it might be that one of the toebrakes is mapped to the throtte, too. Since always the latest input will be used, the toebrake-input might simply override the throttle input.

The collective brake works exactly like the trimmer on the cyclic, but where the trimmer on the cyclic is for the PITCH, ROLL, and HEADING channels of the autopilot, the collective brake is for the ALTITUDE channel. And just like the other channels, the autopilot only has 20% authority over the controls. An example of using altitude hold in normal flight would go like this: 1. Flying along straight and level, you decide you want to change your altitude. 2. Press the collective brake button (F) and hold it. 3. Adjust your collective to begin a climb or a descent (still holding the collective brake button). 4. Arrive at your desired altitude and adjust the collective to halt your climb or descent (STILL holding that button!) 5. Let go of the button for the collective brake (after you've stabilized at the new desired altitude). At this point, the altitude channel will do its best to keep you at that altitude (either barometric or radar altitude). Remember that your autopilot can only do so much (20%), so drastic changes in the cyclic (or drastic changes in altitude if using radar altitude hold) will cause the altitude hold channel to work improperly.

In this mission you will need 2 or more players to compleat the mission in time. mission start 5:10AM Dustoff by 5:20 TOT 5:40 RTB by 6:00 to make the 6:20 deadline for landing. their are many threats to contend with. You will need a good plan of attack on target site. STP 3 is the raily point/attack start point. their is a NAV TGT point for the target site. If you want to play the mission in singel player go to the ME and change the SLOT 1 to player insted of client. Enjoy this mission and leve feed back here after flying it thanks. updated mission 5 1.2 is now loaded Strike 5 added

http://forums.eagle.ru/showthread.php?t=41170 Petite traduction express : Eagle Dynamics Update – 03 Mai 2009 Il y a plusieurs projets en cours chez Eagle et j'ai pensé qu'un bref point d'avancement pourrait répondre à beaucoup de questions : 1- Patch pour DCS: Black Shark. Le patch est en travaux et nous espérons toujours le mettre en ligne d'ici un mois ou deux. A force de corriger des bugs et d'ajouter de nouvelles fonctionnalités, nous avons dû revenir en arrière et refaire une partie du code multijoueurs. Cela a conduit à un temps de développement plus long que prévu. 2- Traduction de DCS: Black Shark. Mise à part la version espagnole, toutes les versions sont terminées. Cependant, l'équipe se concentre sur la correction des erreurs introduites lorsque la version française a été dupliquée. La traduction de la version espagnole est en cours de bouclage et nous espérons la rendre disponible d'ici un mois ou deux. 3- DCS: A-10C Warthog. Certaines parties de l'équipe se concentrent déjà sur ce projet et d'autres les rejoindront une fois terminées les tâches concernant Black Shark. Les progrès sont bons et nous prévoyons de publier bien plus d'informations sur ce sujet dans le courant de l'été. 4- Lock On: Flaming Cliffs. Cette franchise connaîtra de nouveaux développements en 2009 maintenant que Black Shark est en cours de bouclage. Une fois les détails finalisés, nous pourrons fournir plus d'informations. Fil de discussion ici : http://forums.eagle.ru/showthread.php?t=41172

As you have mentioned, it would be a great task to individually map each button in the Lock On controller menu. Also, if you re-install you would have to do this all over! The best thing to do would be to search for a pre-made profile for your gear, then customize it to your own taste. I am sure there are Lock On profiles over at lockonfiles.com and other places.

Hi Kung Fu! I'm a Staff Sergeant stationed at Nellis. I work on the flightline as a 2W1 weapons troop, and I've been working several flightlines for 8 years on both the F-16 and F-15E aircraft. I currently load and maintain weapon systems for the F15E Strike Eagle. I am on the flight line everyday and could very much help with the layout of the flight line and common things you would see there to include common support vehicles that are never included into flight sims. Which buildings do you need information on? Perhaps a more detailed layout with building numbers would help as a reference. Let me know. Certain pictures from certain angles or locations will need special permission. I can facilitate this, and that's why I need to know building numbers and angles. If you don't have such a diagram with building numers let me know. It is also possible for you to be escorted around areas of the flightline if you'd like for some of your programmers to see for themselves what it looks like during daily operations. By the way...you have created the best helicopter/combat flight sim I've ever seen or played (Been playing flight sims since my 486 computer). You're attention to detail and quality of programming has raised the bar of excellence. Your willingness to go beyond an already fantastic project makes me eager to help you out. SSgt. J. Williams "Scrape"

Hello - I don't know really much about Flaming Cliffs-LockOn I will fly it more often when my KA-50 has to visit the maintenance ;) But one thing I know for sure : It would be one of the worst decisions a software company could do if they would release the source code of a) a product that sells up to now (doesn't mater how old). b) parts of the code and the engine are still in use. If they would - it would be against all economical rules. And I can't see how they should benefit from it.

:beer:

Give me some shaders 3.0 and... voilà! ;) Regards!!

This model for DCS only.

Спасибо. Это не только моя заслуга, но и всей команды. И до него руки дойдут. Вопрос времени.

Il peut s’agir d’un problème de routine C++ qui interfère avec un des éléments du logiciel. Commence par désinstaller BS suivant la procédure normale (ajout/suppression de programme). Ensuite téléchargez sur le site de Microsoft les dernières versions du pack Visual C++ et .Net Framework. tu trouveras ces éléments sur la page du centre de téléchargement de Microsoft. Après l’installation de ces deux composants, redémarre ton ordinateur et installe à nouveau selon aussi la bonne procédure ici http://forums.eagle.ru/showthread.php?t=40895

Yes superb pictures, thanks for the link.

Hi Guys, Nice work on the suit, but for anyone who still likes the olive (default) version I have had ago at adding a map to his knee pad slot. If any one would like. Timm

The 'Typhoon' is NATO code designation for Russian 941 project sub or… 'Akula' (Shark). So, here Tu-16 over Akula.

Wow, those are some nice pictures. Breaks my heart to see that beast so worn though - it's been a favourite sub of mine ever since I was a small kid.

Very nice pics of this monster, Mustang. Just by looking at them you get the feeling its pretty huge and dredful.

Hello- Something similar happened also to me few times in my beginning - I have a Hotas Cougar and I discovered that it was caused by a faulty calibration of my throttle axis. That means that when I pushed it full forward it showed up as jumping back to the beginning of the axis in the windows properties. A new calibration solved it . And it only happened at the last tiny 1% of the axis. At a point I was sick of doing the recalibration each time and I set a small dead zone to the ends of the throttle band - and I had the problem never again. Maybe you have the same with your X52 (probably inaccurate measurement in the end of the axis in the potentiometer) Check your controller properties in windows - and try a recalibration. Also try to set a very smal deadzone in BlackShark. Maybe that helps.

[i suggest, you know about "real" and "game" modes in CONTROLS] 1. Do you use Saitek profiler? If yes - please, unload it and try once again. 2. "and saved the profile" - how do you saved profile? Please, step by step. 3. Set your Saitek Throttle in the middle position, start simulation. Move throttle at approx. 1/5 of full scale forward and back (i.e. not to full forward or full back position) - will the collective axis invert? Check also collective moving using RCtrl+ENTER.

This msg :thumbup: Like some radar avoinics fixes Avionics request: Elevation and Azimuth setting follows target (In all planes, _all modes_, ) Fix TWS memory in eagle so it does not report ghost contacts at time of detection, but expected new position Fix so that elevation and azimuth adjusts Instantly when bugging, so its possible to bug memorized tws tracks outside elevation/azimuth Implement target step functionality TWS (both step and cycle pdt) Implement Long range boresight F15 (and possibly 8 bar scan) Fix F-15 radar angle elevation indicator (the *<* should not move like it does right now) Have Automatic HOJ engage when target starts jamming, regardless of previous lock method if outside 25 km Make HOJ go back to TWS bug after HOJ target goes ECM off (if previous tracking mode was TWS) Make ECM contacts buggable TWS after burnthrough achieved (currently they go auto STT) Make it possible to go scan->bug->stt->bug->scan and NOT scan->bug->stt->scan Disable LA override for weapons were it produces unrealistic results. Make RWRs give not so 100% perfect range reading on warnings/missiles Make so that you have to hold down the fire button 1-2 seconds to fire a radar missile, for all planes Make eagle radar capable of detecting cold aspect targets further out than 21 nm. Missile TimeToImpact/toPitbull disappears when out of missiles but still have a missile in flight Missile electronic systems For missiles in scan mode/relock mode, reduce scanning sweep angles, so a broken missile doesnt relock 90 deg off bore Reduce/break chaff efficiency, also make zero unless close to beam (since they can easily be separated with doppler shift if head on) Greatly increase prox fuse (and explosion strength) for R77, R73, Aim120, aim9, to compensate for these missiles problems catching barrell roll targets After missiles lose lock, have them start look at expected target new position, not just exactly where it was lost Have missiles stick on flares a bit longer after going for it, dont switch back to AC so fast Completely remodel numbers for radar floor/ground clutter Physics Fix f-15 engines high (right now cannot fly mil power above 30k with combat load, and the flanker has 3 times the engine power) Add drag to missiles going up, reduce drag on missiles going down Increase maximum speed of R77 and AIm120 Increase burn time Aim7 (15 sec) and R-27E (not certain), increase drag slightly Fix Aim9 burn time (it's not supposed to be 3 sec :)) and top speed For all a2a missiles : add a part of plane launch speed to missile max speed, alternatively, remove missiles speed cap entirely (or add 50% to it), and cut missile accelleration by 70% (going from approx 30g+ -> 10g acc) Lua interface bugs Make Lua radar export work in tws mode (eagle) When using lua mode switch (example: bvr->CAC) also switch keyboard (example : bvr->CAC) The analog command for azimuth angle does not work (it switches setting instead of moves radar),fix The discrete command for azimuth angle movement only works in eagle, fix for flanker/mig .

Is this the line you are looking for? I've attached my (AFAIK) normal file if you want the whole thing. TrimmerTauInverse = 7.0 --lower value - decrease trim speed after trim button release. For personal tuning on flying style. (Has an influence on tracks) FMOptions.rar

http://research.microsoft.com/research/vibe/pubs/CGA2005-LargeDisplayUX.pdf А что такое «баны…»?

Трава нужна лишь в считанных процентах времени в полете, но всё равно красиво. Да, нужна. Количество объектов - вот камень преткновенья. Детализация рельефа дает вирпилу вдохновенье, его правдоподобность отраженья - изгибы рек, дорог, строенья, овражки, холмики, леса, их измененье с высотой полета... там открывается исконная поверхности краса.

Oh yeah..! I almost forgot... About the video of the Cyclic Stick..? Well....? I have to get some help with it..! I've tried a couple of times making one, but they all stink so bad I did'nt dear put it out there on the net.. These video editing programs are seriously complicated to work out.? .. Glowing Amraam..?! How the H*LL do you manage to make your videos so perfect? I say your multitasking skills must be WAY above average..! I had maybe 20 clips, and completly lost track of where I wanted them to go after 3 seconds. And you moviemaker guys work with maybe..? 100 clips..!? And then you add effects and music..? Respect to you all. I'll never say anything bad about anyones video again (not that I ever have..)! I'll try find someone who has a clue, and post the video ASAP..!

Hey all, My name is Evontroy. I live in Sunrise, FL USA. I love all things aviation and programming. See you all in the air.

Through epic forum-searching, I located the above post. I'm going to give this a shot!

What Esac_mirmidon said :)

Про это, что ли: «…есть надежда, что выйдет в течение ближайшего месяца (или двух ближайших месяцев)»? Переписывают что-то в коде, отвечающем за мультиплейер, что потребовало дополнительных/незапланированных затрат времени. Довольны? P.S. Судя по «красной карточке», нет. P.P.S. No good deed goes unpunished.

Assasin подключил 4-х портовый хаб Toshiba, в качестве внешнего питания использовал адаптер от Nokia N73 (вольтамперные характеристики соответствовали требованиям хаба) - картина та же, дрожат резюки и все тут :( Можно вообще от этих шумов избавиться? Повторюсь, сервис в Москве, а я в Баку, никак не хлямба... У меня на РУДе ,на маленькой крутилке,установлен ЗУМ,думаю так у многих,но очень обламывает дрожание,просто накаляет... Хаб с внешним питанием проблему не решает,хотя,здесь кто то советовал....Я проблему решил,теперь,ЗУМ вообще не дёргается,в каком бы положении его не оставить....Проблему решает прога NewView http://www.newview.hruks.com/about.php Поставите галочку,"Аналоговый зум" в NewView и обязательно,удалите назначенную на ЗУМ ось в LO,если этого не сделать,то LO будет считывать данные прямо с РУДа ,минуя NewView и по прежнему,будет всё дрожать... В NewView ,есть пошаговая инструкция по её установке,внимательно читайте и всё получится,если что ,спрашивайте....

This is an effect of blade 'flapping' ... because on that side the blade travels faster through the air, it lifts up higher the faster you go. If you go too fast, bang ;)

Yes I agree Poko. It is not only war, war and war ;]

:)

well the albino is going, since i cannot figure how to get the sdk working right. i assume that nellis got stuck on my side do to the fact, that simmod went down and the sdk files must be damaged in some way. so i got back to the eagle. right now i am unwrapping and thinking about the damagemodel and the textures. only one thing is not clear to me, how such nomera files work and what i have to do in max to get that set up right. so far the eagle grows and grows in detail again :-) do to the skinning

I posted this elsewhere, but it kinda fits here, too, so... Sorry in advance for what must seem like a dissertation, but this is what I've learned about coaxial rotor flight dynamics. It may help to have a picture or model of the Ka50 in front of you while you read this. In a hover, the two rotor disks of the Ka-50 contra-rotating coaxial rotor helicopter are designed so that they produce the same amount of torque (due to drag) in opposite directions. The lower rotor actually produces less lift/drag than the upper rotor for the same relative airspeed, but since it is working in the higher airspeed downwash of the upper rotor, they match torque production at a hover setting (at sea level on a standard day, <yawn>). This designed so that minimal (ideally NO) yaw input is needed at a hover. During forward flight, this difference in lift production capability results in the upper rotor generating more lift than the lower rotor. The upper rotor rotates clockwise, so you get a net counter-clockwise torque from drag, thus the left yawing tendency at airspeed. This yawing tendency, left uncorrected, will result in uncoordinated flight which is messy and unprofessional. So, in a Kamov contra-rotating coaxial rotor helicopter, like the Ka-50, a Good Pilot, interested in maintaining steady-state coordinated level forward flight, will apply right rudder to counter the left-turning tendency of the upper rotor disk. In a conventional helicopter, applying pressure to a rudder pedal increases (or decreases) the pitch on the blades of the tail rotor, increasing (or decreasing) the lift they generate. The mounting of the tail rotor is such that lift from the blades directly translates to turning moment. So, pressing a pedal directly affects turning moment (aka torque) on the chopper. Unlike conventional helicopters, however, there is no tail rotor on the Ka-50. While removing moving parts from a design is usually a good thing, the function those parts served must be replaced by other parts, or else thrown out of the design. Yaw control is most certainly not an optional "feature" of a combat helicopter and the solution implemented in the Ka-50, while complicated, is quite elegant. In the Ka-50, yaw torque is controlled by varying the pitch of the blades of the two rotor disks. To yaw to the right, the pitch of the blades in the upper rotor disk is decreased which decreases lift which decreases drag which decreases the counter-clockwise (i.e., left-turning) torque it produces. If nothing else was done, the helicopter would yaw to the right due to the excess torque generated by the lower rotor disk, but it would also start sinking due to the loss in total lift. To counteract this, the pitch of the lower rotor blades is increased at the same time, increasing lift which increases drag which increases the clockwise (i.e., right-turning) torque it produces. The total change in lift is zero while the total change in torque is to the right. The process happens in the opposite for yawing to the left. This is all accomplished automatically by the helicopter control systems when the pilot stomps on a rudder pedal. This technique was apparently pioneered by Mr. Kamov, by the way. Unfortunately, that's not the end of the story. Due to a number of factors, including the fact that rotor blades are not infinitely stiff and thus flex a little, rotor blades slope upwards away from the rotor mast when the produce lift. This causes the rotor disk, which is essentially flat while making no lift, to form a cone shape, or rotor cone. In forward flight these cones are asymmetrical, even in single rotor disk helicopters, because of a phenomenon called "dissymmetry of lift". Dissymmetry of lift is caused by the fact that, on a helicopter that is moving, the rotor blades on the side of the disk that is moving in the same direction as the helicopter are moving faster through the air and thus generate more lift than the blades on the other side of the cone. More lift means more force pulling up on the blade, which means a steeper cone angle. Less lift means less force pulling up, which means a shallower cone angle. From the outside it looks like the cone is leaning away from the side of the rotor disk that is headed in the helicopter's direction. This side of the cone is generating more lift than the other (hence the handy-dandy "dissymmetry of lift" moniker) which creates a banking torque on the helicopter. In the Ka-50 contra-rotating coaxial rotor, the upper rotor is producing more lift overall, so although the lower rotor is producing a banking moment in the opposite direction, there is net banking moment to the right. So, in addition to the right rudder needed due to the differing torque production of the two rotor disks at airspeed, left cyclic is also needed to counter the dissymmetry of lift effect. Hence the left stick and right rudder we keep finding ourselves using to maintain straight and level coordinated forward flight. It's natural. And it's right. Now for the Dark Side: One of the cons of this design is that the cones of the two rotor disk system lean in opposite directions. This is because the two rotor disks spin in opposite directions. Although the upper rotor is a bit higher than the lower rotor, at a high enough airspeed, the two cones can cross, which, if you remember from Ghostbusters, is a bad thing: Dr. Egon Spengler: There's something very important I forgot to tell you. Dr. Peter Venkman: What? Dr. Egon Spengler: Don't cross the streams. Or rotor cones. Dr. Peter Venkman: Why? Dr. Egon Spengler: It would be bad. Dr. Peter Venkman: I'm a little fuzzy on the whole "good/bad" thing here. What do you mean, "bad"? Dr. Egon Spengler: Try to imagine all life as you know it stopping instantaneously and every molecule in your body exploding at the speed of light. Or your rotor blades clashing at high speed and breaking off your helicopter, sending you spiraling to the ground! Dr. Ray Stantz: Total protonic reversal! Or rotor clashing! Dr. Peter Venkman: That's bad. Okay. All right, important safety tip. Thanks, Egon. To make things worse, since the lower rotor disk is working in the downwash of the upper rotor disk, its coning angle is more severe than the angle of the upper disk's. In forward flight the top rotor cones a little to the right, and the lower rotor cones severely to the left, bringing the tips of the lower rotor closer and closer to the blades of the upper disk. This is not an unanticipated aspect of the design. Mr. Kamov didn't have a maximum indicated airspeed warning system put in his attack helicopter to keep pilots from getting speeding tickets - he put it there to prevent the pilot from reaching airspeeds that cause intersecting cones. The system doesn't, however, take into account rapid increase of the collective at high airspeed (increased pitch = increased lift = increased coning = see Egon's saftey warning above). Stomping on the right rudder makes the upper rotor disk cone less, but the lower disk cones way more, further reducing the distance between the two cones. Throw in some cyclic controls in just the right direction and voila, rotor blade salad and lots of paperwork! The solution is simple: avoid high airspeeds! If you have to move fast, limit climbing to very gentle rates and avoid strong cyclic or rudder inputs in any direction. If you have a need to climb, pull back on the cyclic first while holding the collective steady. The helicopter will pitch up and start climbing without significantly increasing the rotor coning angles. As airspeed bleeds off slowly introduce collective to maintain your climb rate, but keep the total collective input low until the airspeed bleeds down. There's probably a table somewhere to help real pilots figure out what sort of climb rates they can get at high airspeeds before the rotors clash, but experimentation in DCS: Black Shark suggests you can comfortably climb/maneuver at speeds up to 225 km/hr without coning problems. At 225 km/hr and above, more and more caution is needed with the cyclic, collective, and rudder inputs!

С удовольствием, вот только времени нет :(

Согласен, просто модель эта делалась из другой модели и у и дабы съэкономить время решил использовать пакет текстур от родственной модели. Ктому же эта модель не для игры и никто бы не рассмотривал ее так тчательно чтобы заметить зеркальность.

Спасибо! будем стараться :)

My comment was not meant for you SNAFU, as I appriciate your remarks to make my checklist better. Thanks !!! The last three comments before my reply were referring to the other checklist. I don't have any problems if people are making checklists of their own, ofcourse not. But I do find it a bit rude to use someone elses thread to give support to your own checklist, while I have put so much effort in mine.

Stop using antivirus software. I've been using PCs since 1994, building PCs since 1998, never used antivirus software, never had a virus. My main problem in my work PC is the centrally managed antivirus, it's intrusive and blocks completely random stuff left and right...

What's funny here is that I had written "(at least in the game)" to my post in reference to the brake not doing anything, but I deleted it before submitting, thinking nobody would bring up the real thing. Silly me! :P