Jump to content

Leaderboard

Popular Content

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

  1. It's a bit difficult, but you can make other aircraft like the KC-10A, F-16A, IL-78M and some other aircraft flyable. To make them selectable in the game is not the problem, but to make them flyable was a bit harder. First you have to edit the correlate *.lua file, for my example the F-16A.lua 1. X:\LockOn Flaming Cliffs 2\Scripts\Database\planes\F-16A.lua here you have to change the HumanCockpit = "no", with HumanCockpit = "yes" 2. edit the X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\aircraftNames.lua and add following line: ['f-16a'] = _('F-16A'), 3. now you have to add a new folder within : X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts bsp. X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\f-16a into the f-16a folder you copy anything you find for example in the f-15c folder wich is also within the Aircrafts folder!! 4. after this, you have to edit the CustomHuman.lua wich you can find here: X:\LockOn Flaming Cliffs 2\Scripts\Aircrafts\_Common. here you must add the following line: before: after: thats nearly all. But these settings have a little disadvantage, the cockpit is not where it should be, it is set in the mass of centre of the F-16A frame, but i found a solution! There is one more thing you have to do: into the folder x:\LockOn Flaming Cliffs 2\Config\View, you have to edit the server.lua file before: after: now you have the cockpit where it should be and it is 6dof capable!! Unfortunately i was not able to make all planes flyable, the KC-10A and the IL-78M are relative easy (i didn't test here the cockpit settings), the F-16A i had to play a bit with, but until now i was not able to make the IDS Tornado flyable. There are some more planes like the Tornado GR.3 and then there is the F-2 which should be the Tornado GR.1, so i don't know what i have to add or which variables to set. Problably some other can find it out. Maybe someone find other problems, so i have allways a ctd if i add the F-15C pit to the KC-10, The KC-10 was only flyable with the A-10A or the Su-33 pit. Don't know why, so do not ask At least i could not add more then one plane into the server.lua, if i add more, i have no hud anymore and the pit is in the centre of mass again! If someone can build an f-16 pit for FC-2.0 would be a great thing!
    2 points
  2. Probably Not For Unlocking Externals: Take your £%^&^%.miz.trk file and rename to .miz (Just snip the 'trk'). Load into editor. Change mission options to allow externals. Save. Reverse name back to .miz.trk (Courtesy of 159th_Shallow_Grave) Load and Replay.
    2 points
  3. Релиз группы хэви металл " FC2" - альбом Люди гибнут за металл ( за железо PC ):). Вот геммморой свалился на голову. А может Вы тоже деньги возьмете на время - пока активации не кончатся , а закончатся и деньги назад. Справедливо однако. Без обид. Любимая игра. И такая лажа.:noexpression: .
    2 points
  4. 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
  5. I like triggers, truth is I've be experimenting and learning as much as I can of the Black Shark ME in anticipation for FC2.0. So I've got a few idea's up my sleeve for possible scenarios, the thing is it's kinda opened my eyes up to the possibilities of what we can create for multiplayer. So my question is, are you interested in any of these ideas... 1. Triggers used to keep Ground targets random, server also has similar status quo setup in terms of where ground targets are, and flight times. 2. Scalable Co-op missions made for large number of players. Requires teamwork to be successful, ATC and voice comms might also be highly recommended. 3. You enter a server flying the role you choose. The idea is to somewhat replicate R/L combat operations. For instance a CAP pilot doesn't stray from their cap zone unless they absolutely have to. 4. Triggers used to make it slightly more fair and prevent vulching. 5. Long Format tries to offer something unique at all times of play. Triggers could be used to randomly launch AI strikes against the enemy base and to keep the mission populated. 6. Take the best from FPS and RTS online gamemodes and bring em into LockOn. Black Shark had their TF2 like CTF mission with the game. Perhaps CTF doesn't fit perfectly with a flight sim, but protecting assets, controlling parts of the battlefield, and capturing an airbase do.
    1 point
  6. Get this then it may help more, this one has the cockpit fix for the A10 Simmod 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
  7. I've done the same with the AIM-7, the default one looked horrible on Gys' new F-15C model :music_whistling:
    1 point
  8. GAU-8 in FC2 is more realistic than in FC1. It is armed with DU only, and bouncing aside, it does its job.
    1 point
  9. Just keep using FC1. What's the problem?
    1 point
  10. Me too but only to be sure. Here they are... do not try to outturn it! But please - do not start to cry: "They get blues down!!!" Remember that F-15 can outclimb any plane... except MiG-29...
    1 point
  11. What is it a helicopter model?
    1 point
  12. Its a question of unchecking 2 boxes in "gameplay" settings and you will have full reality back.
    1 point
  13. Thx! Is it possible that we can get charts of aircraft performance as moddeled by ED (NOT the source material which im sure is ED property/classified/off the record pilot testemonial etc etc). Community efforts to graph them despite good intentions will always have errors of measurement/consistency/uncontrolled variables/personal bias etc.. I just think a gold standard reference would be great for us dogfighters out there.
    1 point
  14. Try Win+F1. Shaking of the cockpit might be realistic, but shaking of the viewpoint isn't.
    1 point
  15. Mention your files being checked in the mission briefings that are displayed when you highlight the server before you click join. I know from experience though that a lot of people don't take the time to read the brief. RTFB :)
    1 point
  16. Обнови ДиректХ через интернет.
    1 point
  17. Touche lol :joystick:
    1 point
  18. To customize the HUD color go to "Config/View", open view.lua with notepad++ and modify these lines: -- HUD RGB color HUDColor = {} HUDColor[PlaneIndex.iSu_27] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iSu_33] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iSu_25] = {255, 255, 0} HUDColor[PlaneIndex.iSu_39] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iMiG_29] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iMiG_29K] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iA_10] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iF_15] = {[color=red]0, 255, 0[/color]} HUDColor[PlaneIndex.iKA_50] = {[color=red]0, 255, 0[/color]} Can't tell for transparency tough Voilà!
    1 point
  19. The list connects player names and IDs, and you need the ID to kick/ban people manually. The pool does not show the ID. (Same for mission IDs) :)
    1 point
  20. That's the great thing about DCS, failures or problems with your helicopter are usually occur for a reason and there are almost always preventative measures to take against it :).
    1 point
  21. What Wilde asked is if someone has not altered any files how does he know if server he joins has stock files also and does not allow for LEAVU etc? I think there is no way unless like you said... you deliberately change some files to see if it'll let you in, but this is very annoying thing to do as you'd have to change back and forth... not a good solution at all.
    1 point
  22. I did some testing myself tonight 35000 pounds weight, clean configuration (no weapons or fuel tanks) so I matched the chart provided in earlier thread. Altitude: 9000ft 200 kts / Mach 0.350 ... ~ 16.36 deg/sec (chart ~ 13.00 deg/sec) 250 kts / Mach 0.444 ... ~ 15.65 deg/sec (chart ~ 14.00 deg/sec) 300 kts / Mach 0.532 ... ~ 15.65 deg/sec (chart ~ 14.50 deg/sec) 350 kts / Mach 0.622 ... ~ 15.65 deg/sec (chart ~ 15.50 deg/sec) 400 kts / Mach 0.713 ... ~ 16.36 deg/sec (chart ~ 16.00 deg/sec) Altitude: Sea Level 200 kts / Mach 0.300 ... ~ 21.18 deg/sec (chart ~ 17.00 deg/sec) 250 kts / Mach 0.380 ... ~ 20.00 deg/sec (chart ~ 18.00 deg/sec) 300 kts / Mach 0.455 ... ~ 18.95 deg/sec (chart ~ 18.50 deg/sec) 350 kts / Mach 0.530 ... ~ 20.00 deg/sec (chart ~ 19.00 deg/sec) 400 kts / Mach 0.610 ... ~ 20.00 deg/sec (chart ~ 19.75 deg/sec) Now, there is definitely some error in measuring (timing the full turn) so it shows why some values are same (nearest accuracy in measuring time I could make is 1sec). I've kept the speed and altitude pretty spot on so there should be minimal error in there. This shows the trend and its obvious that the lower you fly to sea level and slower you get the more the values are off what they should be. Up higher and with more speed it gets more accurate but slow and low it's off... no question about it. I didn't even try with flaps, I think there's no need for it. @AS, so maybe you should appologise to Dubb now as you can see he was not so off like you claimed and "giggled" about it ;) EDIT: Thanks Yo-Yo for having this fixed... patch will be good :)
    1 point
  23. Not commenting on who's right or wrong here AS so I'm not talking about the figures. But I have to say this, I'm pretty sure I speak for a lot of us not only 3Sqn when I say check your attitude at the door. Your consistent "talking down" to other Lomac members is appalling. It must be lonely at the top
    1 point
  24. Which takes us back to another question: how do you know it's a stock server? Besides intentionally altering export.lua and trying to connect is there any other way to find out? Because that could be a royal pita.
    1 point
  25. Myself, I don't use LEAVU just beacuse I have a single 19" monitor and I have to Alt-Tab every time I want to have a look at the displays. I hosted the DL once with Yoda while FC2 was still in development and I was amazed by the gameplay improvement it gives. So for me it is definitely a feature, a great one, not even near to be considered a cheat. I keep wandering though where some of you guys get those 'cheating' ideas from...
    1 point
  26. Every Single time you release a new/reviewed Flight Sim you give us an awesome gift. ґCause a FS like FC 2 or DCS Black Shark for that money is a gift. How many hours flying and enjoying for barely 30$? Many thnks Wags and ED development team. We DO love you.
    1 point
  27. не знаю у меня каждый 10 килл пушкой. Не надо ее снимать оч клевая пушка в ГС2.
    1 point
  28. Прицел правильный и коллиматорный. у нас пока нет инструментов (или я о них не знаю) как сказать драйверу что на данный момент (в момент отрисовки коллиматорной информации ) модифицировать матрицу 3D драйвером не нужно
    1 point
  29. 1С по ходу не торопится диски с 2.0 нарезать.... Вчера видел ЧА в новой упаковочке от 1С., цена 149 руПликов. есть шанс, что и 2.0 будет по такой цене хотя не факт... время покажет... всё больше людей не выдерживают и скачивают 2.0 с сайта. цена как бы не очень большая но вот, КОГДА ДИСКИ БУДУТ В ПРОДАЖЕ? . команда ЕД всё обговорила с 1С?
    1 point
  30. Здравствуйте. Поскажите пожалуйста как можно поднять FPS, ато в сетевой игре проваливается до 5-8. Читала про это в ветке у вертолетчиков, но можно ли это применить к LO. Спасибо.
    1 point
  31. Try this, fresh installed 5 min ago .... This goes to HDD:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\f-15c f-15c.rar
    1 point
  32. Heh, Keep argure as you want. Keep in mind. there is ALOT of features in APG-63 radar that are MISSING from Flaming Cliff's F15C's agp-63 verison, that because contents are still CLASSIFELD. I could imagine that is WAY beyond what APG63 radar technology is able to do stuffs. I find it very Sad that you just automatic accuse it is a aimbot, You accuse yoda's mods as a aimbot. in reality, it's probably way more than what yoda's ERI mod or FC are capacity of. my 2 cents :-)
    1 point
  33. Thanks for the vid Daokakao.. I liked the music. I made a new one also.. A fighter sweep with my buddy DIngo. Its a full mission with take off and landing. Offoucrs sqeezed together in 10 min. This one has no Music and is pure game sound. I also have the same vid with some AC DC music Shoot to thrill. Go to this link. http://www.youtube.com/watch?v=-1OZtpu1D7c
    1 point
  34. That's fine Yoda but in this sim that's not like that... so anyone flying stock sim will not be able to do this, people using LEAVU will be able and more. That is the difference.
    1 point
  35. Total made good point about extra number of screens, in game F-15C has 1 MFD and RWR... if I was in F-15C and was asked for BRAA from 1 I'd have to switch to nav mode, drop radar picture, tell the BRAA then switch back to radar mode... it takes time and if in fight it's not very advisable to do so... now with LEAVU you can do this no problem, much quicker, even if you are engaging someone already ;) Maximus, if you say it's definitely not an aim-boot because if it was all the missiles you fired would hit, that's no argument at all. If you fire way too far even if radar points and locks at the target missile will miss because you fired too far... LEAVU doesn't enhance/add anything to the missile modeling, it enhances/add more functions to the radar... also LEAVU data link allows you to see contacts that are on your 6 which is not possible in game... you get the point?
    1 point
  36. I think the key words here are 'enhancing' and 'changing'. HOTAS, TIR, Steering wheels, TS, Ventrilo, bigger screens, etc. all 'enhance' your gaming experience, its still the same game. Whats being suggested here is literally 'game changing'.
    1 point
  37. You're kidding me right? You think I'm that stupid? My technique is simple and reliable, but requires 7 measurements per data point to ensure good statistics, increased degrees of freedom and greater confidence in the numbers.
    1 point
  38. http://i067.radikal.ru/1004/f1/d232d02ff5a0.jpg http://s57.radikal.ru/i155/1004/ac/b61de588e17e.jpg http://s006.radikal.ru/i215/1004/a0/46c87f2e91d5.jpg Ну вот примерно так))) Причем при подлете к филду противника на него вражеская наземка никакого внимания не обращала, так он из пушки ее и выносил)))
    1 point
  39. Никто на вас не обижается))) Вам дали трезвую оценку, есть над чем поработать и исправить баги. Есть и хорошие моменты никто не спорит. К сожалению баги пока что перевешивают все новшества. Как например бороться с лагами при включении шквала? Каким образом самолет без крыльев и с горящими движками долетел до филда перезарядился и в таком же состоянии пошел на задание (на чем там ракеты держались я не знаю)))) могу скрины выложить, знать бы еще как). И т.д.
    1 point
  40. так у тебя видюха слабая - это же обрезок...тебе минимум 8800GT надо
    1 point
  41. Here's the result of my test. This is almost the opposite of what it is supposed to be. This is a standard setup - 50% fuel, 1000ft, 8 missiles. The flaps down performance at low speed is ridiculous, and the supposedly 350KIAS corner speed turns out to be one of the slowest. Who was the Beta Tester for flight dynamics? These are all sustained turns. On page 235 of the FC2 Flight Manual ENG is a diagram of the typical flight dynamics used, however, this has not been the case for the F-15 after these tests. The F-15 is basically a raptor with flaps down... it would be wonderul if ED could invert this graph.
    1 point
  42. @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
  43. Understand what you are saying Total and yeah I have to agree as well as the fact of the two extra MFD's being in a static position vs ingame's dynamic position given your pilots head movment. would allow a pilot with LEAVU to have better SA while maintaining greater flxibility of head movement. Target Step is my biggest concern, though I like the idea of the new random failure features. It clearly gives a pilot with Target Step about a 3 seconds advantage for weapon release vs a pilot without (in regards to both coming out of a notch to face up).
    1 point
  44. 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
  45. Очень подробный обзор с подробными фото (на англ.) http://blog.gaingame.com/2010/03/03/saitek-flight-system-review-pictures/
    1 point
  46. FC2.0 = F-15 Strike Eagle simulator... Looking more and more like that... 380+ pages on the Russian speaking forums arguing with ED about numerous changes that are completely biased. So, just get used to it... or don't buy FC2.0. its sad.
    1 point
  • Recently Browsing   0 members

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