Jump to content

Wilde

Members
  • Posts

    231
  • Joined

  • Last visited

Personal Information

  • Flight Simulators
    LOFC
  • Location
    Deutschland
  1. Tried it with Tomcat but it wouldn't lift. At the end of the runway I was going 320 knots or something and Betty yelling at me to "gear up" but I couldn't get airborne. I left a nice crater behind me lol. One would have to find out where exactly the limitations are implemented. I assume there might be some setting, that removes large amounts of lift when wings are folded. This is probably the wrong place to look for a solution. Looking at the AI flying those planes with sweeping wings they seem to automatically use the sweep depending on airspeed. If we'd know what triggers it maybe we could apply it somehow. But so far I have no clue where to even look for it.
  2. Nice pics. About the sweeping wings I found out, that you can use the "folding wings" command for it. It is not present in every input scheme. For testing I copied it from the Su-33 into the Tomcat's keyboard lua. Indeed it does sweep the wings. But it only works on the ground, because it's the command that lets the Su-33 fold it's wings on the deck of a carrier.
  3. I didn't say it was. I was merely stating, that there are certain things of reality that are impossible to simulate in a game. Things like cost, training, maintenance and so on are not for free in the real world. But they are ingame. Furthermore the Flanker was not designed to operate versus Eagles in a vacuum with nothing else to consider. It is only a piece in a large war machinery. And now there are you telling me I should get the facts and provide them to ED. Hm. I think you have no clue what I was talking about. It's the difference between "fact sheet realism" and reality.
  4. Hahaha, don't make yourself unhappy man. ;) I didn't test any weapon usage yet, but I was already expecting it being impossible to use bombs with F-15 cockpit. Tomorrow I'll try to find out if there is any way to access wing sweep for the planes that have it. Obviously that's impossible with the stock input-commands we proposed in this thread. But as the AI can do it there might be some way to have it in this custom modded FC2 too.
  5. Well it is. But in LOFC it is more superior than in reality. There are multiple reasons. In the game you get new Eagles for free and it only hurts your ego when you get shot. Yes, that's why I call it game, not simulation. And of course there are a number of features the game lacks versus the real Russian birds. That's especially for BVR combat. Has been mentioned in this thread a couple of times. Another thing is realistic environment. In a real war you couldn't just fly over unprotected hostile ground scanning for prey all the time. Yet in this game that's normal especially in MP. People claim it's all about realism. But it's not "real realism". It's more like those card games from the 80ies ("Top Trumps" or something?!), where you beat your buddy if your card read 270km/h top speed and his only 245... ;)
  6. This is how I did it: 1. X:\LockOn Flaming Cliffs 2\Scripts\Database\planes\Tornado_GR3.lua Change HumanCockpit variable to yes 2. X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\aircraftNames.lua Add the following line before the last closing bracket: ['Tornado GR.4'] = _('F_2'), 3. X:\LockOn Flaming Cliffs 2\Scripts\Aircrafts\_Common\CustomHuman.lua Add the following line after the one for the A-10. CustomHumanData[PlaneType.F_2 ] = CWSType.iCWS_F_15 As Butcher explained you can also use any other available cockpit. 4. X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\f-15c copy this directory to X:\LockOn Flaming Cliffs 2\Config\Input\Aircrafts\Tornado GR.4 5. x:\LockOn Flaming Cliffs 2\Config\View\server.lua Here 7 new lines will suffice. I assume this is the first plane you turn into human controlled. First you need to give the Tornado an index value. This is done in the first section called "PlaneIndex". So you need to to add the line iF_2 = 10, (don't forget the commas) right behind the KA-50's index. Next section is called "PlaneIndexByType". Here you need to add the line [F_2] = PlaneIndex.iF_2, behind the KA-50. And then you need to add the camera-instructions for the Tornado in the 5 block-like sections in this file. I simply copied the F-15 line of each block and added it at the end of the repsective block. Change F_15 to F_2 for the newly added lines obviously. Example first block: CockpitLocalPoint = {} CockpitLocalPoint[PlaneIndex.iSu_27] = {8.15, 1.38, 0.0} CockpitLocalPoint[PlaneIndex.iSu_33] = {8.35, 1.35, 0.0} CockpitLocalPoint[PlaneIndex.iSu_25] = {3.5 , 0.4 , 0.0} CockpitLocalPoint[PlaneIndex.iSu_39] = {3.406, 0.466, 0.0} CockpitLocalPoint[PlaneIndex.iMiG_29] = {4.92, 1.35, 0.0} CockpitLocalPoint[PlaneIndex.iMiG_29K] = {4.9, 1.254, 0.0} CockpitLocalPoint[PlaneIndex.iA_10] = {3.991, 1.55, 0.0} CockpitLocalPoint[PlaneIndex.[b]iF_15] = {6.5, 1.238, 0.0}[/b] CockpitLocalPoint[PlaneIndex.iKA_50] = {3.188, 0.39, 0.0} CockpitLocalPoint[PlaneIndex.[b]iF_2] = {6.5, 1.238, 0.0}[/b]I think you get the idea. 6. X:\LockOn Flaming Cliffs 2\Config\View\SnapViews.lua In step 5 you created an index value for the Tornado. In my example it was index number 10. For this index you need to add a new snap view. I copied the the entire "Snap[1]..."block and changed the 1 into a zero. It sucks to do it manually so just copy the code below and add it at the end of the file: Snap[10][1] = {} Snap[10][1]["y_trans"] = 0 Snap[10][1]["x_trans"] = 0 Snap[10][1]["hAngle"] = 0 Snap[10][1]["viewAngle"] = 71.824691772461 Snap[10][1]["vAngle"] = -32.458889007568 Snap[10][1]["rollAngle"] = 0 Snap[10][1]["z_trans"] = 0 Snap[10][2] = {} Snap[10][2]["y_trans"] = 0 Snap[10][2]["x_trans"] = 0 Snap[10][2]["hAngle"] = 41.045925140381 Snap[10][2]["viewAngle"] = 33.361835479736 Snap[10][2]["vAngle"] = -40.805656433105 Snap[10][2]["rollAngle"] = 0 Snap[10][2]["z_trans"] = 0 Snap[10][3] = {} Snap[10][3]["y_trans"] = 0 Snap[10][3]["x_trans"] = 0 Snap[10][3]["hAngle"] = 0 Snap[10][3]["viewAngle"] = 30.427543640137 Snap[10][3]["vAngle"] = -41.808967590332 Snap[10][3]["rollAngle"] = 0 Snap[10][3]["z_trans"] = 0 Snap[10][4] = {} Snap[10][4]["y_trans"] = 0 Snap[10][4]["x_trans"] = 0 Snap[10][4]["hAngle"] = -32.597400665283 Snap[10][4]["viewAngle"] = 34.392349243164 Snap[10][4]["vAngle"] = -35.293746948242 Snap[10][4]["rollAngle"] = 0 Snap[10][4]["z_trans"] = 0 Snap[10][5] = {} Snap[10][5]["y_trans"] = 0 Snap[10][5]["x_trans"] = 0 Snap[10][5]["hAngle"] = 129.01266479492 Snap[10][5]["viewAngle"] = 87.468338012695 Snap[10][5]["vAngle"] = 14.54797744751 Snap[10][5]["rollAngle"] = 0 Snap[10][5]["z_trans"] = 0 Snap[10][6] = {} Snap[10][6]["y_trans"] = 0 Snap[10][6]["x_trans"] = 0 Snap[10][6]["hAngle"] = 0 Snap[10][6]["viewAngle"] = 43.977935791016 Snap[10][6]["vAngle"] = -4.9515771865845 Snap[10][6]["rollAngle"] = 0 Snap[10][6]["z_trans"] = 0 Snap[10][7] = {} Snap[10][7]["y_trans"] = 0 Snap[10][7]["x_trans"] = 0 Snap[10][7]["hAngle"] = -129.01266479492 Snap[10][7]["viewAngle"] = 87.468338012695 Snap[10][7]["vAngle"] = 14.491871833801 Snap[10][7]["rollAngle"] = 0 Snap[10][7]["z_trans"] = 0 Snap[10][8] = {} Snap[10][8]["y_trans"] = 0 Snap[10][8]["x_trans"] = 0 Snap[10][8]["hAngle"] = 82.862922668457 Snap[10][8]["viewAngle"] = 87.468338012695 Snap[10][8]["vAngle"] = -9.5 Snap[10][8]["rollAngle"] = 0 Snap[10][8]["z_trans"] = 0 Snap[10][9] = {} Snap[10][9]["y_trans"] = 0 Snap[10][9]["x_trans"] = 0 Snap[10][9]["hAngle"] = 0 Snap[10][9]["viewAngle"] = 87.468338012695 Snap[10][9]["vAngle"] = 38.979362487793 Snap[10][9]["rollAngle"] = 0 Snap[10][9]["z_trans"] = 0 Snap[10][10] = {} Snap[10][10]["y_trans"] = 0 Snap[10][10]["x_trans"] = 0 Snap[10][10]["hAngle"] = -82.461265563965 Snap[10][10]["viewAngle"] = 87.468338012695 Snap[10][10]["vAngle"] = -12.843997955322 Snap[10][10]["rollAngle"] = 0 Snap[10][10]["z_trans"] = 0 Snap[10][11] = {} Snap[10][11]["y_trans"] = 0 Snap[10][11]["x_trans"] = 0 Snap[10][11]["hAngle"] = 15.618312835693 Snap[10][11]["viewAngle"] = 68.786628723145 Snap[10][11]["vAngle"] = 7.5224981307983 Snap[10][11]["rollAngle"] = 0 Snap[10][11]["z_trans"] = 0 Snap[10][12] = {} Snap[10][12]["y_trans"] = 0 Snap[10][12]["x_trans"] = 0 Snap[10][12]["hAngle"] = -15.683433532715 Snap[10][12]["viewAngle"] = 69.165199279785 Snap[10][12]["vAngle"] = 8.5491504669189 Snap[10][12]["rollAngle"] = 0 Snap[10][12]["z_trans"] = 0 Snap[10][13] = {} Snap[10][13]["y_trans"] = 0 Snap[10][13]["x_trans"] = 0 Snap[10][13]["hAngle"] = 0 Snap[10][13]["viewAngle"] = 87.468338012695 Snap[10][13]["vAngle"] = -9.5 Snap[10][13]["rollAngle"] = 0 Snap[10][13]["z_trans"] = 0If you want to add more planes later keep in mind, that you shall not use index 11 and 12. Those are for the cockpit mirrors. So every further plane should have an index of 13 or higher. Hope it helps.:joystick:
  7. Ok, doing a little testing I got it to run for Su-30, F-16A, FA-18C, Mirage, F-14 and the Tornado GR.4 eventually. As for Mirage, Tomcat and Tornado it didn't work with the filenames given in \Scripts\Databasedb_units_planes.lua for me. Instead I had to use these: ['mirage 2000c'] = _('Mirage'), ['f-14a'] = _('F-14'), ['Tornado GR.4'] = _('F-2'), Mirage and Tornado don't show any artefacts when using F-15's CockpitLocalPoint. Tomcat does have clipping, because it's not far enough in the front. Haven't found an ideal coordinate for it yet. Should be somewhere around {8, 1.2, 0.0}.
  8. There must be more to it. At first I made the Su-30 flyable with Su33 cockpit. Worked just fine. Then I tried around with Tornado and F-14 and couldn't get the cockpit right. Removing them and adding F-16A worked fine. Adding F-18 broke it again. Strange. Also changing CockpitLocalPoint doesn't seem to have much effect. I increased both X and Y coordinates just to test it. (X: 6.5 -> 8.5 Y: 1.2 -> 1.4) Looked exactly the same ingame though. Hope someone finds out what to do and how to do it right. This kicks arse. :pilotfly:
  9. 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.
  10. Well, I don't even know if the server allows lua-export. I can't check the server's configs or verify it's script-integrity to mine. If I knew for sure I was in a vanilla game I would happily make use of ECM together with my radar knowing that you'd only get a bearing. But if I don't know I have to assume you make use of LEAVU or else I'd get surrounded by your whole crew. And if I didn't know about there being LEAVU and you using it I'd simply fly into your bunch ECM'ing all the way making it super easy for you to kill me. I think there's a whole lot of difference between the possible scenarios. I know! But there is a whole lot of stuff that can be calculated from the output of multiple pilots. It changes various game mechanics a lot. It goes as far as people can implement things like auto-track. Yoda mentioned in the other thread that it is possible to automatically point the radar in the right direction for a specific target at any given time. Not only does a mod like this provide superior situational awareness but you can go as far as having sort of an "aimbot" as ridiculous as it sounds. I'm sure you did. Many of the changes are great for sure. Over all FC2 is a much better simulation compared to FC1.1. Yet forgive me if I'm not so happy with particular developments that coincide with your preferences. It's like a red line and I can understand your thinking. But it's not easy to brush it off. Makes me feel like giving in to being brainwashed just to be allowed to watch my favorite tv-show.
  11. I know what LEAVU does. I have read the other thread. There is no need to talk to me in a condescending way. There is not much for me to try. You guys didn't implement anything for the planes I can fly properly. And neither did anyone else. And I'm not blaming you for it. But I'm skeptical anyways. The reason is, that the whole thing is completely in-transparent. You see, if I join the server without it I have no idea who uses it. You on the other hand know at least a few persons using it, namely yourself and your buddies on your LEAVU-server. Then it's open source. Nobody can check which version you're running or what you've tuned it into. You guys seemed to try calming everybody down how dlink was limited to LOS, or just recently how ECCM gives very inaccurate information. But how do I know what people change it into when I don't even know they're running "enhanced" FC2 at the first place? Ultimately this isn't specifically about LEAVU. It's about the benefits and dangers of lua-exports. Everybody dreams of a custom pit of highest standards, which surely needs exported data in realtime. See, if you really cared about that issue you could have influenced ED to employ CyBerkut's suggestion from like 5 months ago. Of course, why bother when you already have what you want...
  12. Yes, that was the sensation of finally flying against actual intelligence as opposed to artificial one. But do you remember how you managed to get comfortable with it? You only needed to get used to it and soon you had a leveled playing field, only less experience. Now what I meant to say was, that with LEAVU/LRM that's not the case. You'll never have a leveled playing field unless you install it yourself or actively find servers that disallow it. That is after you found out there is something going on beyond vanilla FC on your server (hinting at the 33% voting answer 3). Some pilots may never find out and eventually quit flying, because they feel inapt or whatever. Don't get me wrong, I'm not the one to tell everyone how to configure their servers. I'm just raising my opinion about it. And to me the reasoning of the server-owners who oppose client side modding sounds quite logical.
  13. MoGas, I was talking in general. You can actually fly offline for years, perfecting your skills in all flyable aircraft, mastering every available system. I am sure the majority at least learns one aircraft thoroughly before trying to fight with human players online. These people are the ones you want to see keeping the community alive, aren't they? And these people will get a cold shower once they start flying online because of the reasons I stated.
  14. The fact, that about 1/3rd of the voters chose "Don't know what it is" tells me, that they have no clue what you're doing with LEAVU/LRM2 or however you call it. So after having flown offline for months to learn how to fly their birds they join your server. They get totally owned, because they have no idea of there suddenly being datalinks, ECCM and all the stuff. Then there's 3 ways for them to proceed. (1)Stop playing online, (2)start using it themselves or (3)hoping to find servers that disallow it. The latter being difficult, because you can't realistically check the server configs. Best thing they could try was installing the program and searching for servers that wont let them in, only to deinstall it again to fly there, i.e. a major pita.
  15. But the desktop icon only invokes the following command: "C:\games\LockOn Flaming Cliffs 2\bin\x86\stable\Launcher.exe" --console or "C:\games\LockOn Flaming Cliffs 2\bin\x86\stable\simulator.exe" --net gui The former for single-player, the latter for multiplayer.
×
×
  • Create New...