Gizmokev

The NASA Data clearly shows the trim positions are correct. All the talk about, "I think it should be this or that" is irrelevant when IRL data provided shows your thoughts are wrong.

For those of you interested here are the docs used by PC to ensure the S&L trim settings are correct according to the NASA test data. Essentially all the trim data came from there. There was some artistic licence applied for speeds above 148kts to allow for RBS and other such things. Once these were in it was merely a case of refining the feel of the cyclic and collective to make sure she feels as close to the real thing as I can remember. Regards the ability to take off. You will need to pre-position to cyclic to the left and rear (look at the trim data). Pull collective and watch the nose as it starts to move left and counter with right pedal and at the same time correct any lateral movement with the cyclic until you reach a 5ft stable hover. I strongly recommend flying with no centering springs to get the truest feeling of the FM and how you need to position the cyclic now. I would imagine a lot of the oscillations are PIO from over correcting/pushing against the springs/being used to the old FM. NASA Data 0-40kts with grids.pdf NASA Data 40-160kts with grids.pdf

Is the FM FUBAR'd.......asking for a friend?????

Is the FM not up too standard then??????? Asking for a friend..........

As the title says....can you put the stck extensions available from VKB onto the NXT????

I like the sound of this........

And off you go again......like a broken record....

Dont you ever give up or shut up. Every post is banging the same drum over and over and over again......Not one point on the video...... You quote that everything is right in the video post 20 minutes.....are you claiming that I dont have IRL hours on it, that I never flew the thing IRL, that my experience of the airframe is void????? Really what are you saying is correct and whats not????? DCS is a GAME....The definition of a Game is as follows noun 1. an activity that one engages in for amusement or fun. I enjoy it as a GAME.....with people who enjoy it as a GAME.....I enjoy faffing about the place in the Gazelle as a GAME.....if I wanted the real thing then I would do so IRL.....but hey in case you missed it...DCS IS A GAME......you turn it on and you switch it off......its a GAME!!!!! I would venture to say you are a muppet noun INFORMAL•BRITISH noun: muppet; plural noun: muppets an incompetent or foolish person. or at best a keyboard warrior noun: keyboard warrior; plural noun: keyboard warriors a person who makes abusive or aggressive posts on the internet, typically one who conceals their true identity.

Also get rid of your curve.....you want a linear movement and the curve will just mess you up.

Ok guys here is the link to the latest video created by Sly. Here is talks with Gizmo about the intricacies of the Gazelle and how to get he best from it as it stands now.

Might be an idea to find a local friendly in another country to purchase it for you and then ship directly to you........

I am trying to get the information from the F10 Markers you can place in DCS. I primarily want the coordinates......this is what I have so far..... EngageArea:HandleEvent(EVENTS.MarkChange) --- @param Core.Event#EVENT self -- @param Core.Event#EVENTDATA EventData function EngageArea:OnEventMarkChange(EventData) MarkerCoord = COORDINATE:New(EventData.pos.y, EventData.pos.x, EventData.pos.z) EngageArea:SetVec2(MarkerCoord) end However I am seeing nothing in the logs to show me where I am going wrong......can anyone help me as I am confused as hell.....I can see the data I want in the logs on the event change but for some reason it isnt showing me why I cant utilise it to do other things.

Ok here goes trying to explain my predicament. ARTY has the ability to use text from the F10 map to create a fire solution for artillery units. I am looking to adapt the script to create something new to do with the entering of script in he F10 menu. So far I have managed to decipher the script to the point of pulling what I want but I am stuck. In the moose lua file at line 76036 or thereabouts is this local = assignments {} --this creates a table called assignments-- assignments.engage = false assignments.battery = {} --another table-- assignments.loadsofotherstuff = tables and false entries In my head (not ever done any scripting before) this means there is a table called assignments with data inside like so [1] assignments.engage boolean result [2] assignments.battery table [3] assignments.loadsofotherstuff either tables or boolean After loads of scripting mainly taken from moose lua the script ends with return assignments end So in my script I then try to do a function like this if assignments.engage = true then do something I get an error in the log which says expecting <'name'> after if What am I missing? Is it the fact that the assignments.engage is actually under a name of engage as the assignments. bit doesnt count or is it something completely different? You help is greatly appreciated in educating me on my errors

Answers in bold. FWIW the gazelle is a cracking little mod. You can go it alone in the lima to take out minor target with rockets and guns or be a little more punchy with the Mike using tows to take out heavier armour. Or if you really want a challenge take any one of the 4 variants and no ammo and become an proper OH guy behind enemy lines reporting in to a friendly A10 or similar to bring in the fire on targets you discover......stay low cos the perspex screen isn't a great barrier against anything fired at you. Its simple to learn and doesn't require much reading of 9" thick manuals to get it working.. There are issues with the FM and things are not perfect but wrt the real airframe the "feel" of the module against the real aircraft is great........ Get it on a sale or pay full price....up to you but I havent regretted buying it at full price. As for servers come onto LLH or BSD where there are regular missions focused purely around helos.

Go 9 line....... at last....finally......phew. @Adam if you want any advice give shout......

Aaaaaaand back on the ignore list you go........... "shakes head slowly with a wry smile on his face"........you can lead said horse to water but if the horse don't wanna drink its gonna die eventually of thirst......maybe then it will have understood you were trying to help.......

This as well......

As someone who actually flew P1, Right Hand Seat in the real thing I find it frustrating that you with no real life experience of being in command of the actual Gazelle are attempting to validate your opinion on the reactiveness of the cyclic controls against the real airframe. What point of reference are you referring too? Is it the video on the controls v graphs from the flight manual by the engineer. If so how do you know that the control view is exactly replicating the instruments used in the flight test? You dont!!! Are you referencing other videos on Youtube and making assumptions based on where you assume the cyclic is based on the look of where the cyclic is during a particular manoeuvre against the Controls View? If thats the case then how do you know where dead centre is to reference all movements from? I will inform you now, once and for all......we all know the FM isnt perfect, exact, is missing a few elements but the fine control of the airframe requiring micro movements on the cyclic is exactly as per the real airframe. How do I know because I have real stick time and experience of the actual airframe gained from when I won my Military Wings on the Gazelle. Now if you wish to continue any discussion on this and want a true and accurate perspective from an actual IRL pilot with actual time on the Gazelle please ask away and I will let you know but please dont for one second ever think you can tell me I dont know what I am talking about.

Based on IRL experience on the gazelle and what I remember wrt to amount of cyclic deflection here are my settings using a short throw stick with a purpose built collective and VKB yaw pedals. Y Axis - Pitch - 50% Y Axis - Roll - 50% Everything else is 100% no curves

Done.......peace and quiet from here on in...... :D:D

Did you know that IRL there was a time limit imposed of 3 seconds when pulling from 0 pitch to IPS through the flight manual and FRCs. Perhaps you might want to consider the possibility that is the reason why your collective responds slower if you simply yank the collective up. Its protecting you from breaking the gearbox by using improper flying techniques......

So one thread gets shut down and you guys all jump on another one.......wow.... For what its worth to anyone who cares to actually listen......the sat levels are not there to fix the FM issues they are there to compensate for a short throw stick and dampen the twitchiness of the airframe. I for one only reduce my sat levels to 50% on pitch and roll on the Y axis alone.

I simulated the mortar or artillery coming using explosion zones to negate this in my last mission.....based on your exact words of wisdom Statua or was it Fargo......I cant remember now.....but it was sound advise. Simulate ground fire by making infantry units small (2 or 3) and make them immortal to keep the fire fight going for as long as you need it too.

I too have IRL experience on Helos one of which was the Gazelle. Shall we play top trumps??? Have we not already beaten the crap out of this discussion many many many time before????