Holton181

And you are talking about the airdrome navpoint, reached by hitting the third button to the left, counting from top left? (They are never together with the other six WP:s, top left button). First one is always your closest starting airdrome. You can indeed get the second populated with airdrome data, have played many missions with it, but I don't know exactly how it's done, automatically or by other means. There is a way to prepare the aircraft as you like while making a mission by going into the cockpit, prepare it and return to ME with those preparations saved to the mosdion file. I don't know how it's done but surely it's described in the manual.

Not stabilize you, quite the contrary. But it will reduce the needed power to stay airborne. When you learned to hover close to ground (in ground effect, IGE) reasonably steady with the help of previous comments, have a glance at how much power you are using. Then climb a little bit, say 3-4 rotor diameters, and do the same (out of ground effecr, OGE). You should now be using more power than close to ground. Mind you, due to the small rotor you really need to be close to ground for IGE in the Gazelle I believe, and it's hard to really hover without any forward/aft and lateral movement when at some height.

Frank is right. Overall, all information can, and should, be given to the player in the briefing and possibly in the naming of the ABRIS WP as i real life. Remember the ME with its functionality is for directing all movable units, player(s) and AI, not only the Ka-50. The 'type' is definitely something for the AI and initial configuration of the player aircraft. Neither of the ABRIS or the PVI-800 really has any 'type' designations anyhow, except for naming in the ABRIS. The PVI-800 can only cary 6 WP:s so its a good thing the initial WP in the ABRIS isn't included, and your starting airdrome (or the closest one if on a FARP IIRC) is always incuded in the PVI-800 as the first airdrome navpoint. I'm not sure, but I also believe the landing airdrome, if different than the start one, is available as the second airdrome navpoint (of two available in the PVI-8000). Landing WP:s (for the player) can simply be made by an ordinary WP with a given altitude/height at ground elevation to get the vertical navigation right. Simply no bugs as I can see.

[emoji106]

I did, and tested it on the TF-51D first. Sorry to say I get this: That is the same I get when trying to do my thing with the Mi-8, and it can't be flown (in 2.5.1 OB). I tested both edit the TF-51D as instructed in the tread (as for 2.5) and using the downloaded version. I even tested to only copy TF-51D.lua and keyboard\default.lua to maybe enable the MP functionality (not sure this would work at all). But nothing worked, rendered it unplayable. The Mi-8 have already "player slot 2" and "player slot 3" with their respective key-binds. The Mi-8 version of the TF-51D.lua isn't located in the Mods\aircraft\Mi-8MTV2, but I believe it's the one located in \Scripts\Database\helicopters, don't know for sure though. That's the only one left for potentially making it multi-crew in MP.

Added screenshot.

Edited the first post with a screenshot.

It's LWin+H in both Mi-8 and Huey, otherwise correct. The keybinds are under "Gunners AI Panel" in Options->Controls

Will see what I can do when I get the time.

This is what I started to suspect. But it can't be about the files in the bin folder, since the Bell47_2 works perfectly in both 1.5.7 and 2.5.1 (as long as you have the Huey activated), and it's entire bin folder is a copy of the Huey's. That was what made me believe a simple copy of the entire Mi-8 would be a piece of cake, with some edits to the entry.lua and creation of some data lua file,but no. I suspect what stops us to do that is lack of knowledge about exactly what should be in that data file. I'm afraid yes, for the views.lua at least. One can still mod it in other areas though. And I agree with you, odd. Think it was introduced just a few updates ago. Can you still use the mod you created? It includes some edits to the views.lua. If you still can it seems the views.lua SP IC might be for some modules only.

No biggie

My pleasure, happy you like it. But as you can see in my first post I linked to a Mi-8 version. It has three positions, one for the engineer back in the cargo compartment (not changed by me), and my Mi-8 version has a vertical angle of 75 while my Huey one has 65 for both pilots. But if you like the Huey numbers better for the Mi-8, just remember to have the engineer portion present.

Thanks for your suggestion, interesting project, but if I can't fly it (in SP that is, not interested in MP), what's the point of that mod? My experiment was to see if it was possible to bypass IC for SP use. And honestly I don't see any point at all for IC in SP.

Does this still work?! I'm asking since I believe editing the view.lua will make the module invalid, not flyable. It does for me and the Mi-8. That's the reason for all this.

AP and SAS are two different things. AP is flying the helicopter for you, the SAS is a stabilization system to make the flying easier for you but you still have to fly it yourself. The SAS might perfectly well have an effect on the jaw behavior you describe. Try turn SAS and also the gyro off. I don't know how you do that (don't fly the Gazelle) but I'm sure someone here can help you.

I have it, got it in early beta stage long ago. As for the reason, I mention it above. I don't plan to do anything illegal.

For anyone experience the Cargo View as being unnatural I have made a small MOD to locate it slightly differently. Instead of looking 80 degrees relative the nose making flying while having your head out the window a bitt disorientating, at least more than it has to be, I have turned the head at an angle of 10 degrees instead (0 degrees isn't natural either). The vertical angle and head position have also been modified. You can of course edit the file yourself if you are not happy with the result. I fly with TrackIR and adopted the file according to my own preferences. There is two versions, one for 1.5.7 and one for 2.5.1 OB (test both if you have other versions, the head is turning in the wrong direction if you use the wrong MOD). OvGME ready. The location isn't "perfect" by will. I want to move my own body and head slightly, it adds to the immersion. Enjoy /H PS I've done the same for the Mi-8 Uh-1H adjusted CargoViewAdjustment 1.5.7.zip Uh-1H adjusted CargoViewAdjustment 2.5.zip

For anyone experience the Cargo View as being unnatural I have made a small MOD to locate it slightly differently. Instead of looking 90 degrees relative the nose making flying while having your head out the window a bitt disorientating, at least more than it has to be, I have turned the head at an angle of 10 degrees instead (0 degrees isn't natural either). The vertical angle and head position have also been modified. You can of course edit the file yourself if you are not happy with the result. I fly with TrackIR and adopted the file according to my own preferences. It works with both 1.5.7 and 2.5.1 OB (and everything in between I assume). OvGME ready. The location isn't "perfect" by will. I want to move my own body and head slightly, it adds to the immersion. Enjoy /H PS I've done the same for the Huey Mi-8 adjusted CargoViewAdjustment 2.5.zip

Start a flight and practice for a while. End the flight. At the lower part of the briefing window that appears there is a button in the middle called "Save Track". Click it, give it a name and save it. Done!

Well, I consider myself beaten on this. I believe I made a correct entry.lua but run into problems with something called a "Data LUA" by you SkateZilla in an old thread at SimHQ. I believe I understand what it is supposed to do, and I copied much information from the Scripts\Database\helicopters\Mi-8MT.lua with the bell47_2.lua as a template, but still nothing. I guess I need some proprietary information for it. I also realize that other files than contained in the bin folder are worth protecting somehow. It's just a pity ED forces integrity checks on us even for SP usage. I understand it perfectly for MP but if I want to cheat while playing SP that's up to me right? Thanks guys.

What is your weight? What's the outside temperature? At what elevation are you when you start? All those effects the need of blade pitch and power setting, i.e. collective. Not hard at all to end up never leaving ground with full collective, if the circumstances are right (i.e. wrong). Try full armament and full fuel in NTTR at noon in the beginning of August. What's the wind? With no wind you should only move the pedals slightly and carefully in the direction you want and then equaly smooth back to the same position, you need to anticipate when to start moving them back, inertia will easily push you past the heading you planned for. And remember, moving clockwise is slower than counterclockwise, they are anti-torque pedals after all. Now add some wind... I'm sorry, but you can't be more wrong than this. Remember this isn't a modern helicopter with autopilot stabilization systems of any kind, you are forced to fly it all by yourself, with the only exception being the throttle. ALL controls, cyclic, collective and pedals, ALL THREE have an effect on the other two AND ITSELF! Especially noticeable during hover. Move the pedals slightly and both cyclic and collective, ESPECIALLY collective, has to be corrected. And due to the corrected collective less or more power is needed (here you get some help with the throttle) and hence the torque is changed and THE PEDALS need correction! And it goes on and on like this, constant correction of ALL controlls SIMULTANEOUSLY! Not "first this, then that" but all att the same time. You can never relax on any of them. It's all about balance, and balance needs practice. The better you get the smaller movements you need on the controls. This is the tricky part. There is actually three things you are forced to do, curves/saturation or not, and those three things are: 1) Practice 2) Practice and most important 3) Practice!

But how did Upuaut manage to modify the Huey into the Bell47_2 then? There you only copy the bin folder from the Huey, but that's the most important to protect, and many other files in the Bell47_2 download package are taken from it as well with different levels of modifications. I believe it exists other community modules based on official ones out there. I'm not really modify it either, except a small correction I wish Belsimtek would do, but they tend to let these small bugs stay unattended for a long time. Unfortunately ED made it difficult to do it yourself.

... and the Cargo View. It's slightly bugged but a small edit of the joystick default.lua it works. Not at my computer so I can't show you right now. Edit: Not the keyboard default.lua, but the joystick default.lua! Sorry.

He isn't looking for an update, rather a "downdate". He is on BS 1.0.1!

Well, I'm not actually mowing it. I keep it at the original place, this is only a copy. The reason is more of an experiment to see if there is a way to bypass the restrictions to edit the Views.lua, only for SP use that is. We are some people believing the file is slightly wrong in its Flimits_6DOF for the pilot and we like to edit the file according to Chic in post #4 in above thread. I have the MOD Bell47_2 by Upuaut that is based on the Huey working so I thought it would be a piece of cake to simply make a vanilla copy of the Mi-8 as a MOD without the Views.lua editing restrictions (any original module get disabled if edited). Hopefully I can get the MOD by Chic to work this way. The best thing though would be if Belsimtek could do the edit themselves. If you look at the numbers in post #4 and compare them to the co-pilot and engineer, I believe you would agree they most likely just accidentally mixed the left and right limits for the pilot.