I agree, Jetpack is the most honourable and helpful guy and is the glue that keeps this forum going.
admin should apologise, not to me as I'm past caring, but to the forum members, they got it dead wrong. I made a simply statement of fact. The fine line between censorship and dictatorship was crossed and sadly that's when it's time to leave.
Thanks for deleting my post, guess you guys really do have a thin skin
Larrylynx aircraft productions is hereby terminated
To all, keep safe and to quote Spock
Live long and prosper
Too many fingers in too many pies = slow development
FS2 is getting left behind
Are landing lights also covered by this "professional" version. To my knowledge this is the only sim not to include any method of lighting the ground. Even FS9 and probably before has this feature. It obvious you can do it so how about giving it to us poor people 
So if landing lights are available for VRM which I assume uses FS2 for its simulation how come we haven't got it ????
Hi Christoph
Whilst I agree both the Lynx and AH64A appear to rotate in the incorrect manner on power application this could simply be due to the lack of directional stability in the TMD file setup. IE, not enough automatic right pedal being applied to counteract torque reaction. On a real helicopter this is built in to the mechanics and design, something we have to simulate through number crunching and testing.
We have to remember the only flight stability system I know about, is the one that Jetpack and I worked on in the early days of helicopter development. There is zero documentation on any helicopter specific TMD coding. A lot of the systems for my helicopters are specific to only that helicopter and were developed from my knowledge of the real systems. I am not party to any improvements or new stability systems that were developed for their EC135.
Also the Lynx and AH64A are designed to be flown with the AFCS/Stab on. We do practice flying the Lynx with AFCS out and it's very much like being balanced on a ball bearing, it's not very comfortable 
and you end up chasing all your inputs as it reacts faster than you do.
All the best
Steve
Legonook was built for a reason, to see if I can get the flight dynamics to work. If ok I'll build a Chinook. Need to work out the rotor and flight control systems
PS
I guess standards are slipping in FS2 helicopters 
Strangely enough my sim really stutters with the Legonook
Hi All
Many thanks for the best wishes, that's what happens when your part of a great community 
Sunburn may be great now and again but it drains you when you have it 3 times a week for 4 months 
Hi Paul, more than happy to post the theory my brother and I have been working on for 12 months or so, still working on Part 2. It's a mere 20 MB and a 20 mins read, Ok, that's a lie, it's more than 20 mins but lots of pictures 
Drop me a mail with your email and I'll send it to you. More people that read it the better, if you think it's rubbish then feel free to say so, can't be any worse than the gang are doing at present. Part 2 is proving our locations which I am working on, managed to find 20 plus thanks to Jerrs Ariel Photography, well worth a watch.
Steve
Not at the moment. Had 4 months of skin cancer treatment which made me feel very tired most of the time. This did however give me time to solve the Curse of Oak Island and locate the treasure 
CH53E has been abandoned for the moment as it still refuses to play nice in the sim. Mulling over new projects so will get back in the saddle soon.
To my knowledge this is no Blackhawk. There is a Lynx MK7 and a AH64A.
To model and programme a helicopter from scratch takes about 6 months of one's time. I don't see any way of converting an existing helicopter either, to many systems, control locations etc that need re-modelling. Plus you will need access to the helicopter specific code from IPACS which is not very easy to obtain.
Sorry to bring all the bad news but that's the truth of the situation
Steve
Hi
What you need for a mouse action point is contained in the controls.tmd file. I would suggest looking at the jungmeister as it is simple and sort of works with what you have. Each aircraft should have a aircraft tmd and a controls tmd. The latter is not always needed unless you want to interact with it by mouse.
Copy the controls.tmd from the jungmeister and place in your aircraft folder, open it up. The only section you will need for the moment is 187 to 226 as this deals with the stick or bar in your case, the rest can be removed but do observe the file correct structure. Unless you have other mouse input areas this should be all you will need for your controls.tms file.
Again from the jungmeister, the lines that you need from the jungmeister.tmd are 899 to 946 and 1874 to 1899. I normally like to make a temporary file, copy in the controls section, dynamics section and graphics section entries. This way it's normally a small file to look at and follow the flow, saves bouncing back and forwards in the tmd files ( which can get very big on more complex stuff). Once your happy with the flow, copy the entries into the relevant tmd and cross your fingers. If the dreaded red cube appears it's much easier to look at your small file to try and track down the error.
Forgot to add, do remember to change the pivot points to reflect your model and also the geometry list.
Steve
I think you do designers a dis-service with your comments.
From memory the weather engine does not belong to IPACS so until they replace it with their own they cannot let us do as we please.
There are numerous scenery developers out there that produce fantastic products for the sim, most of it is free.
Granted aircraft and helicopter design is somewhat limited. Not by FS2 but by investment in time. This is mainly because FS2 is so rich in what can be done, it takes a lot of time to master and commercial developers don't want spend that time.
I think it was me that's broken not the link ...DOH 
Hi Apache drivers.
Just posting an update to the Apache.tmq file over at . This should make the Apache work with Mac systems. Thanks to Jetpac and Michael for there help. This does fix errors that should have also caused the PC version to fail.
https://flight-sim.org/filebas…entry-add/&categoryID=135
Steve
This would appear to be a MAC problem as the PC version works fine even with these errors. I have corrected most of the errors (plus another one) as seen in your TM.log
I am stuck on the NAV1Frequency.Set error. I plan to ask Jetpac for help but he is on a well earned vacation at the moment so it will have to wait.
Once I have corrected this error I will post a new TMQ file.
Steve
Hi Michael
Thanks for the updated log file. The new file did find yet another minor error which I have corrected. Quite why it didn't find this error the first time is past my pay grade.
We do still have the NAV1Frequency errors but I can't see why that should be so I will consult with Master Obi Jan next week. He's on a well earned break so I'll leave him in peace.
Happy New Year to you and all the other forum members
Steve
HI Michael
It would seem the MAC is less tolerant than the PC as it runs with no errors on the PC.
I looked at the errors in your file and I have hopefully corrected them. Perhaps the 4 "NAV1Frequency.Set" may still cause me problems. They relate to the TACAN, which works perfectly on the PC.
I will PM the updated file as I don't want to include a updated TMQ file on the forum until I know its working fine. Once all is Ok I will post it over on the Flight-sim.org site so everyone can update.
Steve
On the PC version we have a TM.log in the C:\Users\XXX\Documents\Aerofly FS 2. Does this file also exist on the mac. if so can you post it.
This file will normally explain why the dreaded red cube has appeared
Also, many thanks for all the messages, really appreciated
Steve
Sorry unable to help as I do not have a Mac, perhaps Jetpack or other Mac users will offer some advice. Please ensure you downloaded the Release version as the WIP versions didn't have the options files and it's normally the lack of these that causes this error.
Steve
