Japo32

hahaha.. everybody ask me about liveries.. I cannot do every of them!! haha... That is why the templates will be there to make the liveries. With Gimp or Photoshop, the make of them is easy and even I would say fun to do. Right now I am making the ones that I most like visually.

First I used the most powerful engine model of the Jetstream32. and after some testings I found that was the best configuration to maintain almost all the time near the 100%. You can say to Plane Maker, "do this" that he will do "that". Even if you notice at iddle it is not at 72% RPM, where the manuals says that in Taxi position. I didn't find a good manner to do that. I could manipulate for the 72% the throttles so the iddle would be 72% but the plane would have push so any time someone would release parking brakes the plane would move. There is a parameter for iddle and max RPM and more or less it respect it but yes.. it is true.. when going to flight level it increases to 103%. I want that increase because can be produced. If the mark is there, and it says in the caution limits, it is possible. Even the temperature was always going farther than 650º when I didn't program it. Now I control that (if you set the TTL computer) So yes.. you have to relax throttles at cruise flight... and take care in take offs because also it goes to 103% but as soon as you climb it goes back to 100%

Added Macair Jet

No.. for now now.. but in a future update I will make the break of the engine as the cockpit decal limitations is set. I didn't do it because I was going to change some things inside the plane first. In this 1.01 won't come.. but in next one if I see everything is stable I will introduce that new failure. So better for now fly correctly to learn how to do it when the RPM % failure comes.

Do not apply full power at the first moment, be gradual, and if you didn't put the TTL computers, do it.

Well the general forum is not the right place to have support of the plane. I move it to support. I would say in resume. Read the manual. It is not 64bits compatible and WON'T be inmediatelly the 10.20 is not beta. I will need to wait to learn how make the plugins compatible with 64bits, and thats not take some hours after the 10.20 is final. About the windows.. Read the manual.. is all there, why you cannot open the window and door. Sure you will enjoy discover how to open them. Y gracias por la felicitación! igualmente y a ver si dejamos la crisis atrás de una santa vez.

Added the US Airways Express.. No.. I preffer with the antenna. It is nice to have the shadow of it over the fuselage. I like it!!

Making some of them... In the 1.01 I will include the templates.

I always think that if you give something different to people that is good (in this case I think is good because totally simulates the lock of a controls! and stick pusher) they usually don't like it because they like the confortable way they were using. Sometimes changes are pain, but if they are for good, for me are always well received (after using them sometimes). I remember when I flought the ATR-500. To make that plane load correctly, first the user had to load the cessna default with engines stop. In this case, this is the same but when exist xplane. but that solution is good if it still locks your joystick. How many times when I was taxing I almost hit with something because didn't unlock UPPPSS!!!

Ok.. FD fixed and working now as it should be. I always treated it as a trend indication, not totally follow indication... So at the end yes.. the plane must end with the cross in the center, but in the middle of the flight it only indicates where you should go. Up-down, Left-right. But Niebieski was right in something I never considered that was the Vertical speed mode, where you have to have to correct angle. So I had to make it that way and I think is fixed. Here there came 2 problems. When I fly virtually and the little numbers I made it in reality, I always made it VFR, or if in autopilot (only sim) always with servos on, so I never paid too much attention to the FD Bars. And the second problem was that I trust the xplane default datarefs, and checked with Goran, they seems to have an extrange behaviour... Anyway.. fixed for the 1.01.

I will!! Read the manual. Page 59 in teh copyrights: "This plane is not certified by Bae Systems and not pretend to" I am based in the plane in lot of things but xplane is not the reality. It has really great things that are like the real thing, but others that are less or over. This is one of the over. I said before in other place: In real life we have 4 hands piloting the planes. Here we have only 2. We can put a hand in a knob we are not seeing and the other eye in the front window to look outside. In X-Plane not. In X-Plane we don't have any real failure - maintenance system by default, in real life you have to take care of that. So my plane will never be the same as the real one (and that is why "not pretend to" because limitations of be seated in our houses in front a computer. I started building planes for sensations to be flying. For me the soul of my planes are not in the systems. I am tired seeing planes full of good modelling systems. You can buy any in FSX, and now comming to X-Plane. While there are people that concentrates in that only, I try to do my best there, but always i put more energy in the SENSATIONS to be seat in the cockpit. That is why I made the rain fx, fog, ice, good texturing... and want to leave the over right wing drop even is over-done by xplane, because for me is a challenge in each take off (well not so much once you learned it).

anyway... I believe you did the video with good intentions, but that was not the good way of doing. Help always have to be giving when someone ask for it, or after a "yes, please" when this magic words comes before: "do you need help?" What I felt, was nothing but help at the very first moment but burden.. but didn't had a word with Cameron about that. Maybe he just thought the same as I did. Anyway, some fixes are comming. But I learned 1 thing in all these years making and selling planes. What a person may think that something is really bad done and it is a dissaster, other would say that is perfect for him. I always try to stay in the middle. well I think you and me didn't start the right way: you: ding dong!!! me: just awaked, "yes?" you: entrying fast the house with an smile. "I bring you 12 possible bugs for you righ now!! they are very important!!! you have to fix them!!" me: oh my good. Earth eat me? why the Mayas didn't have success in their prophecy.... as said.. anyway.. going to work. I put too much energy in this post.

I think I start to follow you.. But in your example.. if the FD tells me 15ºup and the plane is climbing already in autopilot 15º Up, then it should tell me the FD to climb 30º Up instead of 25.. isn't it? So to calculate the correct pitch angle I should always do MypitchbarPosition = FDDataref - ADIPitch position, don't you think? So if the Ball is 0º pitch.. and is pointing me to 15º up the dataref, then it coincide. But if I climb those 15º up, the FD should go to 0º pitch. If that is correct, the code is easy. I didn't thought about the ball rotation. With roll the same? or not.. mmmm because in that case the translation of the bar in roll are not angles but distance from center.

I usually put the trim far to the right.. and it goes well. BUT of course, once I lower the thrust I have to trim back again to the left. Are you using the TTL computers? If not you have more torque.. so more force to right. Usually with that trim I fly correctly.. but I am touching a little the surfaces of control (not the trims.. but ailerons and elevators.. and ajusting the CG. In 1.01 will be out. But the plane still goes to the right if you don't trim. One thing I do is put the solutions per frame to 2 instead 1. I think it flies better.

I have been looking at the position of flight director datarefs and mines.. When climbing they are set to 13-15º pitch up and even if we are set correctly in the VS mode they never go to the center (I mean the dataref) in your video if I don't remember bad, the FD pitch bar once the plane was pointing to the good Vertical Speed I think it was going to cero. But in xplane, the datarefs don't go to cero until it is reached the altitude... My bars are doing what the dataref tells them.

going to repeat it in case this was miss. the behabiour is correct. I you read carefully the manual (crying.....) you will see how the switch down is for recovering memory. The extrange thing is that I stored the 115.20 in the nav1 mem and always will be that frequency (to mem something), and you had your up memory the same.. and that is what happening. But everything is explained in the manual (cryinnggggg...)

Fixed to just change 1 by 1 in each click in the version 1.01.

Fixed already to 1.01 version the right numbers to a maximum of 77.

Well. first those things has to be done internally as Cameron is suggesting you. And second. My skills of programming are so limited that include any code from outside that I don't totally understand is something I cannot do.. Right now the bars are picking the right FD datarefs... The problem comes when comparing to make an smooth transition from dissappear to appear.. is a simple IF comparison and a ratio of animation that has to be touched. If I find the solution I will do it. Don't worry. But there are other problems that need faster solution and I am with them. I am only 1 person and must decide which is more important or not. The FD right now is not the most... and the autopilot also wasn't but because it was an easy solution I did it. You have been 5 hours decoding the plugin... I have been 1 year making all the plane. Step by step.

the 2 right ones or the 2 left ones are you saying? Can it be for example a 3586 code? or only 3577? If so I only knew the limitation in the 2 of the left so you could only put 7777 max. But right now it cannot achieve a code upper than 7777.

Doing that you are (or the user making the video) breaking other animations and behabiours the FDs has in my plugin.

Yes.. the roll to the right is as said several times because the plane has 2 CCW engines. I am touching a little the flight dinamics to make them a little bit more heavy in flight.

RIght, you can press them even the lights are not illuminated. Right now thinking how to make in programming the stick pusher to be softer and gradually.

Fixed that for the 1.01 version. Now selecting the modes only choose the Flight Directors on. Have to switch on the autopilot button to switch on the servos.