Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 04/03/10 in all areas

  1. I am not the right person to say anything helpful about the integrity checking but I can give some charts instead. :) To show the fidelity, I'd like to present some figures about planes fine tuning. Some notes: I must recall that excessive power is the time derivative (Vy or dHe/dt) of energy altitude or full energy divided to mg. LEVEL flight acceleration in g's N_y = Vy/TAS. So you can see how the differences in itegral acceleration curve (TAS vs time) depends on flight model Vy deviation from the real values. Please keep in mind that Vy curves for F-15 was obtained from its acceleration charts and can not be presumed very accurate. That's why the ultimate reference is acceleration chart. And finally: after I made these charts CLT for F-15 drag is slightly reduced so the curves will match better.
    2 points
  2. One isn't a tank though, but I'll take a kill on a SAM vehicle any day... Out of missiles and with too many low and high threats to effectively use any of my gravity weapons, I head back to base and pull up on the ramp long enough to grab some weapons. In my utter stupidity though I am distracted as I leave the ramp and I run my wing into a refueler! Fortunately, I just catch on fire and rip the wing off. After a few minutes of repair, I'm amazed that the sim lets me taxi the rest of the way THROUGH the refueler and once I'm free I'm good to go! Up at the target area I find one more tank, but it takes me 10 minutes of looking while dodging AAA fire. After I launch my first Maverick I lock back on it with my second so that I can watch the explosion on my monitor. With two tanks burning it is a struggle to find the third tank. I refuse to resort to labels, but I do use the zoom and pan liberally to find the last tank. He's right there next to the power transmission tower. Once I get an idea of where a target is, I don't have much problem re-finding it. But finding them is darn difficult! I get the message that I've cleared the north target area and I head for home. Now - you all are going to think I'm lying, but this is the God's honest truth and how it actually happened. I made a beeline for homebase, which is only about 2 minutes flying time back to the west. A few miles from the base I see my caution light is on, but I didn't get an audible warning, so I can't figure out if I got hit by AAA or something. I glance down at my caution panel and the L/R Fuel Low warning lights are illuminated and the fuel gauge is reading zero. I had just put the speedbrakes out to slow for the landing, so I quickly retracted them, then added throttle to keep the speed up and I realized the engines weren't responding. I really had run out of fuel! Where is the low fuel warning? Do those lights just come on when you are totally OUT of fuel? I had just enough energy left to make the runway, but I elected to land on the taxiway instead because I suspect (but am not sure) that if you exit a mission while on the runway you might not get credit for the mission (?). I clear the tail of the C-17 parked in a revetment at the end of the taxiway and plunk it down right on the taxiway. Now, according to the after action report, I flew for about 45 minutes, so unless I didn't have full tanks at the beginning of the mission I have only one explanation for why I ran out of fuel. I didn't refuel during either of my 2 rearming stops, but I did receive that damage and was streaming fuel when I was hit between target areas. Perhaps I lost that much fuel in the short time I was flying back to base and then, not having refueled, the level was very low? No matter what, I can't believe the fuel ran out literally at the last second. Another 30 seconds of flying around away from the airfield and I wouldn't have had enough speed to make it home. One of the coolest things I've ever done in a sim (I once lost both engines in EECH though and managed to autorotate to an airfield where I got repaired, that was pretty cool too..) And verification that it was the ZSU that hit me.. Looking forward to the next mission! BeachAV8R
    2 points
  3. This is the best thing that could happen for FC.. In your server.lua try this. Original: --local old_aircrafts_6DOF = {x = {-2,2},y = {-2,2},z = {-2,2},roll = 90.0} -- {x = {0,0},y = {0,0},z = {0,0},roll = 0} local old_aircrafts_6DOF = {x = {-0.02,0.05},y = {-0.03,0.03},z = {-0.03,0.03},roll = 90.0} limits_6DOF = {} limits_6DOF[PlaneIndex.iSu_27] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iSu_33] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iSu_25] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iSu_39] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iMiG_29] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iMiG_29K] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iA_10] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iF_15] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iKA_50] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} -- After a quick "test" with the KA 50 parameters as bellow.. --local old_aircrafts_6DOF = {x = {-2,2},y = {-2,2},z = {-2,2},roll = 90.0} -- {x = {0,0},y = {0,0},z = {0,0},roll = 0} local old_aircrafts_6DOF = {x = {-0.02,0.05},y = {-0.03,0.03},z = {-0.03,0.03},roll = 90.0} limits_6DOF = {} limits_6DOF[PlaneIndex.iSu_27] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.20,0.20},roll = 90.0} limits_6DOF[PlaneIndex.iSu_33] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iSu_25] = {x = {-0.02,0.15},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iSu_39] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iMiG_29] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iMiG_29K] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iA_10] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iF_15] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} limits_6DOF[PlaneIndex.iKA_50] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} All this is just a start the parameters need to be adjusted to each aircraft to ovoid too much travel of the axis . But just if you test this you will see how GREAT this is and a new life for the SIM.. Thanks ED. Now back to work on the tuning! The Su25 sample: ============== ============== Edited :added below ============== ============== This is for each aircraft. Here test this.. remember keep a back up of those files first to be safe. Find those in your files and change the blocks to mine. This is just a first test.. more tuning will be made.. ( my own in sim settings for now ) Eagle Dynamics\LockOn Flaming Cliffs 2\Config\View\ server.lua --local old_aircrafts_6DOF = {x = {-2,2},y = {-2,2},z = {-2,2},roll = 90.0} -- {x = {0,0},y = {0,0},z = {0,0},roll = 0} local old_aircrafts_6DOF = {x = {-0.02,0.1},y = {-0.1,0.1},z = {-0.1,0.1},roll = 90.0} -- limited 6DOF / test 1 parameters by GOZR' limits_6DOF = {} limits_6DOF[PlaneIndex.iSu_27] = {x = {-0.02,0.15},y = {-0.1,0.2},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iSu_33] = {x = {-0.02,0.12},y = {-0.1,0.2},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iSu_25] = {x = {-0.02,0.1},y = {-0.1,0.1},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iSu_39] = {x = {-0.02,0.12},y = {-0.1,0.1},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iMiG_29] = {x = {-0.02,0.12},y = {-0.1,0.2},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iMiG_29K] = {x = {-0.02,0.12},y = {-0.1,0.2},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iA_10] = {x = {-0.02,0.15},y = {-0.1,0.2},z = {-0.15,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iF_15] = {x = {-0.02,0.12},y = {-0.1,0.2},z = {-0.1,0.1},roll = 90.0} limits_6DOF[PlaneIndex.iKA_50] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} -- Camera angle limits {horizontal angle max, vertical angle min, vertical angle max} CameraAngleLimits = {} CameraAngleLimits[PlaneIndex.iSu_27] = {155.0, -75.0, 90.0} CameraAngleLimits[PlaneIndex.iSu_33] = {155.0, -75.0, 90.0} CameraAngleLimits[PlaneIndex.iSu_25] = {118.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iSu_39] = {120.0, -80.0, 90.0} CameraAngleLimits[PlaneIndex.iMiG_29] = {155.0, -75.0, 90.0} CameraAngleLimits[PlaneIndex.iMiG_29K] = {155.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iA_10] = {150.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iF_15] = {155.0, -80.0, 90.0} CameraAngleLimits[PlaneIndex.iKA_50] ={140.0, -65.0, 90.0} == view.lua -- Camera view angle limits {view angle min, view angle max}. CameraViewAngleLimits = {} CameraViewAngleLimits[PlaneIndex.iSu_27] = {30.0, 115.0} CameraViewAngleLimits[PlaneIndex.iSu_33] = {30.0, 117.0} CameraViewAngleLimits[PlaneIndex.iSu_25] = {30.0, 117.0} CameraViewAngleLimits[PlaneIndex.iSu_39] = {30.0, 121.0} CameraViewAngleLimits[PlaneIndex.iMiG_29] = {30.0, 112.0} CameraViewAngleLimits[PlaneIndex.iMiG_29K] = {30.0, 112.0} CameraViewAngleLimits[PlaneIndex.iA_10] = {30.0, 97.0} CameraViewAngleLimits[PlaneIndex.iF_15] = {30.0, 110.0} CameraViewAngleLimits[PlaneIndex.iKA_50] = {30.0, 115.0} == Change the stock values to this. SnapViews.lua line 103: Snap[1][13]["viewAngle"] = 120.0 - line 208: Snap[2][13]["viewAngle"] = 120.0 - line 310: Snap[3][13]["viewAngle"] = 120.0 - line 418: Snap[4][13]["viewAngle"] = 120.0 - line 523: Snap[5][13]["viewAngle"] = 120.0 - line 628: Snap[6][13]["viewAngle"] = 120.0 - line 733: Snap[7][13]["viewAngle"] = 120.0 - line 838: Snap[8][13]["viewAngle"] = 120.0 - line 940: Snap[9][13]["viewAngle"] = 120.0 ...And i zoom out.. Here the mod to get this good 6DOF V1.1 DOWNLOAD 6DOF v1.1 0.05MB === ( Edited ) On this mods EACH aircraft has a precise parameters to respect all 3D cockpits and a good flight feeling and limitations === 6DOF-v1.1 + A10 fix 0.05MB
    1 point
  4. Flaming Cliffs 2 edition For us to be able to help you with your problem, there's a few things that is incredibly helpful. A post descripting: - What were you doing - or trying to do? - What did you expect to happen? - Relevant info regarding your issue - SP, MP, Mods, custom built gear - anything relevant. - Screenshots when possible. We may not understand what you are talking about until you illustrate it properly. So when you post a TECHNICAL/GAME problem please attach the following: DxDiag report: Use Start->Run: DXDIAG and "Save All Information, to a TXT file" for the report. In the forum post - upload it using "Go Advanced", then press the "Manage Attachments" in the section below the post. Upload the TXT file. [*]Any *.CRASH files in your ".\Eagle Dynamics\LockOn Flaming Cliffs 2\Temp" folder. [*]Any ERROR* files you find in the ".\Eagle Dynamics\LockOn Flaming Cliffs 2\Temp" folder. [*]Screenshots to clarify the problem. GAMING ISSUES - additional info required: To illustrate a "gaming issue", post a *.TRK file. (Check the same \Temp folders as above to find your last flights) SP last track: "LastMissionTrack.trk" MP tracks: "client-nnnnnnnn-nnnnnn.miz.trk" Locations of the \Temp folder may vary: * All platforms - custom install location: <YourDrive>:\<your custom location>\LockOn Flaming Cliffs 2\Temp * XP/2003: C:\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\Temp * Vista / Win 7 with "default permissions" on the system / UAC on: 32 bit editions: C:\Users\<users>\AppData\Local\VirtualStore\Program Files\Eagle Dynamics\LockOn Flaming Cliffs 2\Temp 64 bit editions: C:\Users\<users>\AppData\Local\VirtualStore\Program Files (x86)\Eagle Dynamics\LockOn Flaming Cliffs 2\Temp SP track recordings location: .\Temp\LastMissionTrack.trk MP Track recordings location: - MP Client: .\Temp\client-<latest-datetime>.miz.trk - MP Server: .\<your mission folder>\<yourmission>.trk
    1 point
  5. Had a visit today from the An-225, and I got to snap a few pics:
    1 point
  6. Frederf, I think it's easy to point out holes of a simulation. They all have them. DCS nevertheless allows you to simulate quite realistically the operations of a Ka-50 pilot in a contemporary conflict scenario. Perhaps the true weakness of DCS is that recreating this environment takes well crafted missions created by an individual as opposed to being generated automatically by the simulation, but it can be done and done quite well. This is also one of the DCS strengths.
    1 point
  7. Postal. I will try this out myself and make a seperate mod for so people can have a choice! Ok with you? Try this one guys: http://www.mediafire.com/file/nyji2qmtndj/FC 2 6DOF and Simmod A10 Fix.rar
    1 point
  8. Мда и главное как под кальку написано ... Уже даже не смешно ...
    1 point
  9. Я что-то не понял Warhammera этого. Он чего хотел? Пришел натоптал и забанился? Я вот АСУТП сейчас занимаюсь, и программирую слегонца для контроллеров пром оборудования, дык пока одну програмку отладиш времени и сил уходит вагон. Люди которые никогда ничего не делали руками, и зарплату наверное тоже не получали. Единственное, пожелание на после релиза, что бы в следующих продуктах ED восстановили работу с диском, у нас в глубинке народ не любит резких телодвижений...
    1 point
  10. О! мЕланетС :) Давненько тебя не было...
    1 point
  11. Что-то, до боли знакомое, проскакивало в постах Вархаммера... Потом вспомнил: http://rutube.ru/tracks/709969.html?confirm=3136b9ee4c732a6b49e1ed8966429820&v=1fc26a9ba9cb36133d1d4edea3c5fb8b И в догонку: http://dondrakon.j-net.ru/video/view/?id=47616 Простите за оффтоп.
    1 point
  12. 3 BMD-2 vehicles were dropped with the crews inside.
    1 point
  13. So I'm not the only one experiencing that! On a squad night I had an AMRAAM making a barrel roll around me once, then it passed, turned around and it hit me!
    1 point
  14. 1 point
  15. Ну вообще там все 3 танка вполне видно. Вот мои тесты. 4км: видны пиксели. 2км: отчетливо видно, что "там что-то есть" 1км: видно вполне отчетливо все 6 танков. Вообще конечно с 4 км можно разглядеть только точно зная, что они там есть(на скрине в статике наверное даже их не видно), поэтому эффективная дальность обнаружения 1-2км.
    1 point
  16. For me beavouse it's easy. What for turning oon TS, Ventrillos ect if I could have same in game? Look at Steam, there is nice Voice Chat and conferences. It works.
    1 point
  17. Yep thanks AS, noted the explanation of flaps reduced AoA. However, this doesn't really explain anything to do with the form of the results of my test. Even if you exclude the data point I collected at 170KIAS with flaps down, the rest of the data which is flaps up still appears as the inverse of the 'actual' data charts you've provided in your posts. I'm in the process of collecting the data from all of the aircraft in the game. At this stage, it is only the F-15 which seems to be way off the mark.
    1 point
  18. Почему естественно ? разработчики могли бы уже прекратить деньги втягивать не справедливо, сначала просто Lock on Современная авиация, потом Горячие скалы,теперь вот Горячие скалы 2, могли бы уже и подарок сделать а то давай деньги да давай,если не можете сделать сразу и хорошо, так хоть порадуйте бесплатным контентом блин, а если нет денег что теперь ? потом Черная акула 2 и опять плати.... блин. Спасибо конечно, что хоть доводите до идеальности игрушку. Можно было сделать, что вводишь ключ от Черной акулы и Горячие скалы и доступ обеспечен, нет блин хренушки иди и плати.
    1 point
  19. SOLUTION to crash cycle weapons SOLUTION: Stablish the FPS limit at "90 fps", in graphics.cfg You don´t will see the ctd anymore Regards ! FC
    1 point
  20. @Kuky: That is how it should look like, even though those are just few examples (can not post all) under specific configurations and grossweights: PW-100 engines (lockon 2.0 uses PW-220 supposidly)
    1 point
  21. Just to jump on the band wagon... I miss everything about the mission editor in 1.12, except the GUI. I still can't believe the sub-par distance tool, Lat/Long discrepancy, heading misalignment etc. As much as I want to like FC2, all the short comings of the ME are very annoying. I've said my peace. Hoping it gets fixed/enhanced soon!!!
    1 point
  22. As I don't have it(switching to med prf) mapped on my control setup, i prefer in such cases to use EOS, which of course gives you other advantages and disadvantages :)
    1 point
  23. Spade, no offense, but you should consider restraining some of the emotion in your posts. Set a Time Hold value to the group (for example 23 hours). And read the GUI manual.
    1 point
  24. Имею проблему с использованием очков Nvidia 3D Vision. Проблема в том что настроив все параметры 3D, сбивается прицел. Он не двоится, с этим всё нормально, но при стрельбе из пушки (НАР и т.д. ) устанавливая ПМ на цель очередь уходит влево. Из-за ниже следующего предположения хочу задать два вопроса. 1) Есть ли в планах на ближайшее будущее поддержать 3D изображение в виде правильного коллиматорного прицела? 2) Может быть есть сейчас какой-то файл.луа где можно в ЛА сместить ПМ и тем самым пристрелять самолёт к 3D? Спасибо! :)
    1 point
  25. Кампания "Воин Холодной Войны" у всех на Английском размовляет? Есть Русская версия?? Спасибо.
    1 point
  26. Here the mod to get this good 6DOF DOWNLOAD HERE To install with ModMan Try this one.
    1 point
  27. I started LockOn on a 19" CRT at 1024X768, moved to a 22" LCD at 1680X1050, and now run 3 monitors at 3840x768. The larger monitors or triple monitor set up did not improve my gameplay at all. It takes the same things and makes them larger. In the case of the triple monitors, I actually LOST vertical view distance until FC 2.0. Now, lemme have a 26" LCD in the center, and extracted MFD views on 17" monitors on each side - then that's a definitive hardware advantage. The trick is that it takes software to extrapolate that data to the side screens. In the end, the hardware would not be of much advatage unless there was software giving it additional data. As far as realism vs game - I'm all for the realism myself. In several cases LEAVU is not always "more realistic" than the vanilla game either. Case in point, here is a screenshot from a LEAVU sample vid: The model of the F-15 ingame has only a single MFD. In this screenshot, the user is able to extrapolate TWO of the MFD's functions and view them simulataneously. Not possible in reality and, therefore, makes this a compeltely unrealistic function of LEAVU and, imho, accounts as an exploit by being able to view more than one function at a time. I say again, I really like the features of LEAVU (bolded so not ignored), but there are things it makes possible (this being one fo them) that should be restricted. This is not realistic and should not be touted as "more realistic than the vanilla game" because while the datalink may be realistic, being able to view that much information at once in an aircraft that has only one MFD is not realistic ;)
    1 point
  28. You have to make sure that you either have .tgas or .bmps and that they are set to 24bit. You cannot mix and match in the same .cdds file. It must be either or. Works on Win 7 x64 no problems.
    1 point
  29. Small world. As far as the ping Bucic covered that one pretty well.
    1 point
  30. Now there's some nice suggestion - straigh for the wishlist. :)
    1 point
  31. Thanks Panzer! We will run it on our server! A things that would be cool if they could get implemented: For each player message, provide his coalition and aircraft (also of players he killed) Add the coalition of the airbase when a player takes of or lands Add an option to start the server when X number of people have joined (handy for multiplayer coops)
    1 point
  32. Will do!!! I graduated with my BA in Business Administration from UTA. (I'm back in school for a Computer Engineering degree) I now live in Kerrville, Tx. Now here is for my dumb question... If I play with people in the UK am I going to experience horrible lag like I do on consoles? (We don't really have "servers" in console games) Or will it all be dependent on my ping to the server? Do a lot of you guys play with people overseas with few issues?
    1 point
  33. I've been discussing tactics with a few of my squad members about the Su27 vs F15. One vs. One. My squad mate Fudd, he likes to go high with his eagle and I'm talking about 50,000ft +. The Su27 can do the same in FC2, because of the engine tweak! But that's not what you want to do! Because the F15C has a few massive advantages you need to be aware off: It can launch silently with TWS mode. The defense against this is to turn on your ECM. But the F15c will HOJ shot you, and those launches are silent as well. And once the F15 has burn through it can use TWS again (Is that a bug BTW, or is that realistic??). So in a 1 vs. 1 engagement no matter what you do you will always have a silent AMRAAM heading your way without a launch warning. Yes, it might seems a bit unfair, but just live with it! So if you are flying at high altitude it is more or less suicide. Because the closing speed is very high (otherwise you will drop out of the sky at high alt) and because the AIM120 hardly looses any energy at high altitude. So I decided to fight at low altitude. Fudd (F15) was cruising at 14000 meter, and I (Su27) was down below at 5000 meters. I can launch override my R27ER's from a very long distance (70-80km). The ER will start climbing to thin air, and if the F15 does not change it's course it will suffer the consequences. As a result he needs to start descending, that's exactly what you want! You want him down at low altitude! Meanwhile you start descending slowly at low airspeed. Remember that I said you almost certainly have a silent AIM120 heading you way. So if you reduce the closure speed, by flying very slow, descending to thicker air and by constantly jinking you can evade long range AMRAAM's while keeping head on and a lock on your target! The F15 on the other had has to got defensive, because the range of the R27ER is much longer. There will be a time where you do have an AMRAAM your way which has been launched from much closer distance, you can still evade that one using your RWR and buckets of chaff! The trick is to fly very slow, to keep the F15 at long distance and to keep him defensive at all times. If the F15 makes a mistake you will kill him! Try to get closer and closer, keeping him defensive and finish him of with a single R27ET. Also the F15 will use a lot of missiles, and he might even run out! And if you stay far away from him you can easily disengage and escape if you feel uncomfortable about the situation. So that's what you want to do. Keep him at bay and at low altitude, after all you have the advantage in missile range! Oh and don't forget your G-warm up!! :smilewink:
    1 point
  34. Hi All I am new to Helo sims and the depth of this one is daunting but i keep plugging away when I have time. I have not attempted online due to the noob factor ie not conversant with all the KA50 systems and online protocols. My point is I have always shied away from online flying for fear of arseing up someone elses Mission/campaign and then getting booted out. I am getting on 54 so the grey matter has to have time to take things in. Cheers all
    1 point
  35. ...Подумывал топать в банк заказывать платежную карточку, но почитал и вспомнил о киви, посмотрел на ее проценты и сбегал в магазин за углом. Мне понравилось, как всё прошло. Может, кому пригодится:
    1 point
  36. I have changed the code a bit to make it more clear which is which. I used the values from TheGozr's post, and combined them with the information Lawndart gave about the x-y-z axis. The result is the code below: local aft = { Su27 = -0.02, Su33 = -0.02, Su25 = -0.02, Su39 = -0.02, MiG29 = -0.02, MiG29K = -0.02, A10 = -0.02, F15 = -0.02, Ka50 = -0.02 } local fore = { Su27 = 0.15, Su33 = 0.12, Su25 = 0.1, Su39 = 0.12, MiG29 = 0.12, MiG29K = 0.12, A10 = 0.15, F15 = 0.12, Ka50 = 0.35 } local down = { Su27 = -0.1, Su33 = -0.1, Su25 = -0.1, Su39 = -0.1, MiG29 = -0.1, MiG29K = -0.1, A10 = -0.1, F15 = -0.1, Ka50 = -0.15 } local up = { Su27 = 0.2, Su33 = 0.2, Su25 = 0.1, Su39 = 0.1, MiG29 = 0.2, MiG29K = 0.2, A10 = 0.2, F15 = 0.2, Ka50 = 0.21 } local left = { Su27 = -0.1, Su33 = -0.1, Su25 = -0.1, Su39 = -0.1, MiG29 = -0.1, MiG29K = -0.1, A10 = -0.15, F15 = -0.1, Ka50 = -0.26 } local right = { Su27 = 0.1, Su33 = 0.1, Su25 = 0.1, Su39 = 0.1, MiG29 = 0.1, MiG29K = 0.1, A10 = 0.15, F15 = 0.1, Ka50 = 0.26 } local roll = { Su27 = 90.0, Su33 = 90.0, Su25 = 90.0, Su39 = 90.0, MiG29 = 90.0, MiG29K = 90.0, A10 = 90.0, F15 = 90.0, Ka50 = 90.0 } limits_6DOF = {} limits_6DOF[PlaneIndex.iSu_27] = { x = { aft.Su27, fore.Su27 }, y = { down.Su27, up.Su27 }, z = { left.Su27, right.Su27 }, roll = roll.Su27 } limits_6DOF[PlaneIndex.iSu_33] = { x = { aft.Su33, fore.Su33 }, y = { down.Su33, up.Su33 }, z = { left.Su33, right.Su33 }, roll = roll.Su33 } limits_6DOF[PlaneIndex.iSu_25] = { x = { aft.Su25, fore.Su25 }, y = { down.Su25, up.Su25 }, z = { left.Su25, right.Su25 }, roll = roll.Su25 } limits_6DOF[PlaneIndex.iSu_39] = { x = { aft.Su39, fore.Su39 }, y = { down.Su39, up.Su39 }, z = { left.Su39, right.Su39 }, roll = roll.Su39 } limits_6DOF[PlaneIndex.iMiG_29] = { x = { aft.MiG29, fore.MiG29 }, y = { down.MiG29, up.MiG29 }, z = { left.MiG29, right.MiG29 }, roll = roll.MiG29 } limits_6DOF[PlaneIndex.iMiG_29K] = { x = { aft.MiG29K, fore.MiG29K }, y = { down.MiG29K, up.MiG29K }, z = { left.MiG29K, right.MiG29K }, roll = roll.MiG29K } limits_6DOF[PlaneIndex.iA_10] = { x = { aft.A10, fore.A10 }, y = { down.A10, up.A10 }, z = { left.A10, right.A10 }, roll = roll.A10 } limits_6DOF[PlaneIndex.iF_15] = { x = { aft.F15, fore.F15 }, y = { down.F15, up.F15 }, z = { left.F15, right.F15 }, roll = roll.F15 } limits_6DOF[PlaneIndex.iKA_50] = { x = { aft.Ka50, fore.Ka50 }, y = { down.Ka50, up.Ka50 }, z = { left.Ka50, right.Ka50 }, roll = roll.Ka50 }
    1 point
  37. An amazing video: Lolled hard at 00:54 and 01:08 :laugh: :thumbup:
    1 point
  38. F-15 - это доблестные джедаи, у них синие световы.. маркеры. Их много. А ситхов всегда двое: учитель и его ученик и у нас красные маркеры.:)
    1 point
  39. Вэд, как ты мог вот так бессовестно разрушить все усилия тёмной стороны? :)
    1 point
  40. На всякий случай инстракшн по переустановки дров: полное удаление драйверов: - Отключите джойстик от компьютера; - затем Пуск -> Выполнить; - впишите команду nx -Mu -Sk и нажмите OK; (если не команда не прошла впишите эту ny -7) - далее вам следует удалить драйверы Saitek из меню "Установка и удаление программ"; - пройдите в директорию C:\Program Files и удалите папку Saitek; - перезагрузите компьютер; - теперь пройдите в директорию C:\Windows\Inf, и в папке Inf найдите файлы OEMXX.inf, где XX - это число; - открывайте все файлы OEMXX.inf; - убеждаясь, что в них встречается слово Saitek смело удаляете их вместе с принадлежащими им файлами oemXX.PNF; - выполните Пуск -> Поиск. Задайте в поиске "маску" sai*.* когда закончится поиск удалите все найденные файлы; - входим в реестр выполните Пуск ->regedit. задаем поиск по маске "Saitek" и удаляем все где только встречается это слово. - перезагрузите компьютер; - все драйвер и програмное обеспечение полностью удалено с компа. Проблема 1 и 2 решается одним действием: вам нужно полностью заменить дрова и саму программу Saiteka (SST). для этого скачиваем драйвера и программу по этим ссылкам: только для 32-х разрядной системы !!! ftp://ftp.saitek.com/pub/software/xpvista..._32_Drivers.exe ftp://ftp.saitek.com/pub/software/xpvista...32_Software.exe после этого сначала ставим драйвера, перед этим джой должен быть уже подключен к компу. И только потом ставим саму прогу (SST). При установке дров и проги рекомендуется проматать лицензию вниз до упора (имитация прочтения) т.к. были случаи, что это тоже решало некоторые ошибки. Дрова и прога скаченные по данным ссылкам можно ставить поверх работающих драйверов. но лучше перед установкой снести старые дрова вышеописаным способом. После того как вы поставили новые дрова и новую прогу старые профили (*.dat) у вас работать не будут так что придется переделать их.. (с) NeroFyF/wed
    1 point
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...