Japo32

Tested in xplane 10.20 beta8 and it is working good. As it should be. Only de-icing the front 2 windows (as said that is the way I like it. More challenging). Of course only in 32 bits by now! In future also will work in 64bits.

Only a word here. Simulate the reality in a simulator sometimes is imposible. It is very difficult to manage radios while you are taxing because you have to be looking at the radios and not the runway... so you can crash. Aso you have a copilot with you that helps you.. When I make a plane I take this in consideration. Maybe here are people saying that "this is not real, bla bla bla" "the real plane" but when you port a real thing to a simulated thing you have to change things.. people like or not. This is not only because the radios. For example... a complete drain of the batteries in the real plane is produced in 5-10 minutes.. I set a little bit more of energy (not to more) because lots of people would complain about that. I really know well. So that is the reason about the 20 volts, the reason of the avionics on on start up.. and the reason of the other things you mention to be changed a little. We do not have a copilot side by side helping us.

Tested in xplane 10.11 and it is working. Here is an screen of what it should be. Also is working the Pitot heats. Both.

Yes.. both values of voltage are written in the manuals. 24v is not recomendated, 20v do not start engines. -Avionic masters... I preffer to set all first before waste fuel. Of course if the start is from main battery is better to not drain them with avionics on and start engines as fast as possible to put generators. -Reset the generators it is not normal but one pilot told me that was good to do it. - Hyd shutts on start. Again as you say is usually they are.. BUT I chose the configuration that the pilot had to open them. If I leave all good, pilot has less challenges. Remember the plane don't pick up the leaved configuration of previous flights. So I preffer to set all off. - I have to correct the feather position of the blades in TAXI position. that is a bug... but in this plane there is not a problem starting them feathered. But you have less impulse -fuel pumps again on in take off. Well.. in guess is an option also in case the engines are stopped to run them again in middle of flight quickly. 2 pilots, 2 ways of pilot the planes!!! Which one is the correct? Both if you are landed safe.

in Flight models per frame put 2 instead of 1 and try to maintain far from Vmo. and: 1. Trim axis in joystick = No recommended 2. Trim buttons in joystick = Recommended.

The anti-icing windows only affects to the pilot and copilot front windows. Not to the side ones or the cabin ones. I leaved that way independently of what is is the plane. I just saw filament heaters in those 2 windows only (didn't see in the rest) so I just did it in those 2 windows. if applying both sides of the windshield heaters both 2 (of the 7 cockpit windows) don't deice then there is a problem. I think that is good for flying xperience because it makes pilot exit the icing conditions as quick as possible, or use flying helping instruments. also the new datarefs of de-icing engines of the beta are inside the plugin. I think they didn't change anything of the windshield one. 1. if you put both windshield heaters with ice and only 2 windows of the cockpit are deiced, but the rest and also the cabin ones continues then that is correctly working. 2. if only one or none (after some time of deicing) is not deicing.. then that is wrong and there is a bug.

Please read the manual. All the questions to most of the "problems" people find are aswered there. I do not know why I write manuals. Next time I won't do it.

I spend too many hours writting a manual to solve the questions that I think people are going to ask me in forums ..... and it is one of the most boring work I find because I write in the english I know that is not perfect. align images.. etc.. Very boring. I hope every user read the manual before pilot the plane. People will find solutions to a lot of questions they may have. Anyway.. I pretend in future to just leave those buttons that changes fast, to make 1 change over each click we make.. but I need vacations first!!

The switch down is for recover the memorized frequency. Please read the manuals carefully. Thanks.

Fraps.. but any that captures the screen works. For the camera.. TrackIR4 Is hardware, so the camera follows your head movement.

"what are you suggesting? That I should not use the joystick axis for pitch and roll?" Yes.. that is what I suggest everyone, Not only this airplane but any. The reasons are well explained in the manual. The micro-inputs of not well calibrated (and usually are micro-impulses) trim axis produces the disconnect of the autopilot IN ANY airplane of xplane. But if you try and you see it is good.. then ok. Remember that everytime you touch any trim.. the autopilot will disconnect. And that is an xplane stuff. Not my plane. About the second part of the question.. yes, sorry about my english. It is not "To" but "Do" Do it (the trim function) with buttons assignations to your joystick. In the menus of joystick, in one of the tabs (right now I don't remember), you can assign any button of your joy, to several fuctions inside of xplane. Like the reversers_hold as I say in reverses area, or the trims. In the real plane (or any 99% of times) the yokes have little buttons to trim the plane. They are electrical trims. So you can do the same in xplane.

Hello! I think they just fly normally at FL150-220 or so, but I have heared here total flights at 5000ft. Still the fuel consumption has to be better defined. To to it lots of flights has to be done. I tested several to match close to the real one.. but it is very difficult to find documentation about this. The only way is know the range of the plane and fly to match that range at cero wind speed. Changes will come in future updates I guess. about the not change of the RPM with change of the condition lever ratio position. well the real one only have 3 positions and there are no reasons to put in the middle, Down, Taxi and flight. Maybe in future I just make a click to just put the lever in those positions only. In planemaker is really difficult to achieve a number of RPM at a certain position of the condition levers. You can set the number but other thing is what the engine does in xplane.. because depends in several situations. My principal purpose was to be near the numbers.. but specially in the 100% torque area independently of the position of the thrust levers. But yes.. as said.. I have planed several little modifications inside the flight dynamics of the plane. Which I must say that I am happy with them.

Lock them as the word says. Not move them... so accidentally you can move something when you should not. The function is in the real plane and I just put it there. Also as said the stick pusher deletes TEMPORALLY your pitch axis assignation.

In two parts. Enjoy:

all is explained in the manual. Please read it carefully. But I will tell you that the plugin is reading in each stroge the looping change of all the functions of the GPS. That is "bad" for this case of the press of the CDI, or good with the letter selection because is fast choose them. The key is to make quick (normal.. not stay pressing the mouse) clicks of the mouse to change one by one. This happens in the GPS and the DME systems. Bus as said the manual says everything about this: Pag32: RIGHT KNOBSTheouter one controls the change of the pages the GPS shows, and the inner one the subpagesof each page.The control of this knob has to be done with short mouse strokes because is very sensitive.This knob also controls the letter-number selection for the “direct mode”. Pag21: DME: CH PUSH BUTTON -Selects between Nav1 and Nav2 channels. You have to press a quick mouse stroke tochange it because the continuous pressing makes a full run over both 2 channels.SEL PUSH BUTTON -Selects between KT (Ground speed in knots), MIN (time to reach nav aid in minutes) or IDdisplay (shows the name of the nav aid tuned.User has to press a quick mouse stroke to make a good sequence of functions. Continuous pressingchanges quickly between system.

beta is the reason maybe? Install a demo of xplane 10.11 and try there. I don't have problems if you do maybe is a good idea to report to laminar. Of course this plane loads more textures than others. That is enough reason to bring a medium-low computer to his knees but you have 1gb or VRAM.. so.... anyway.. try with a clean install of the 10.11 final demo.

In xplane9 is final decision.. in xplane10 I think I have a posibility to not load other plane.. BUT if you read the manual (that I think I put it in 4 places) you don't have to load another aircraft to exit xplane IF you leave the lock controls not locked. You just leave the controls unlocked before exit and you don't need to load other plane to exit. The reason is: Lock controls? in reality pilots cannot move the joystick. Here in this plane the same. So I delete some joystick axis (pitch,roll,mixture,yaw and diferential brakes). The plugin has a order to restore the user axis when the plugin is not loaded or stop. But the only way to do it is loading other plane or deactivating the plugin in the plugin menu. If while the controls are locked (so deleted those axis assignations) someone quick xplane, the order of saving back your preferences won't come so you loose your axis. Is a risky decisión but there is no other way to lock controls in some situations (for example, also is locked the pitch when there is a stick pusher). I tried to give the joystick axis a values I wanted (for example 0.0 value) but always in the reading loop of the plugin there are input from the user that changes jumping from the value the user tries to give, to the value the plugin says. So I thought the best was do to what is doing right now. I included the remembering of unlock controls or load other plane before quick inside the checklist. Maybe is a little strange at the beggining but checklist are for that. I simulate a real lock of controls.. and several times I crashed because I forgot to follow the checklist. Now following them I have no problem at all, and like it because it is a little bit more challenging.

The intensity of the cabin will be touched in future updates. I mean the cabin one to not affect so much to the cockpit one. The flood and the reading lights are already separated in the cockpit area, as well as the front panels (3 of them)

The plane won't run correctly in 64bits for now. In future I will compile the plugin for 64bits when all is stabilized. If you usually run the xplane in betas, it is normal you have such up-down of frames. I fly always in the final version.. which in this case is 10.11. Because you are saying that fly 64bits, sure you are going in beta 10.20. With a computer quite similar as yours I have in HDR 40-80 frames depending wich part of the world I am (cities or flying up)

About the pitch axis violent. That is because the stall protection that has a stick pusher.. Read the manual to deactivate the stick pusher please.

Ok... always do this: 1. Load other plane at the start of xplane. See if you have you axis assigned there, if not assign them there. 2. Load the Jetstream. 2a. if you are loading the plane with engines stop, the yokes won't move and the pedals. You have to unlock the controls in the right-botton side of the pedestal. putting the lever down. 2b. if you loaded the plane with engines running you should have the controls enabled, so you have to do anything. 3. fly the plane as you like to fly the time you want. 4. When you end it in your case ALWAYS do it with controls NOT LOCKED. Load other plane. Check if you have your axis correct there. quick xplane. in next session in xplane load again other plane, you should have your axis ok.. if you never exit xplane with controls locked and the jetstream loaded.

ahh ahhh!! ok ok

Mmm I think you are not understanding... This plane does not have FMC or xFMC or whatever.. if it is working an external FMC then that is not the proper way to fly the plane because you are having an extra help is not in the real plane, or at least in this plane. So forget about input of waypoints. The GPS is normal GPS of xplane. I don't used too much. Only for direct to airports. Never chosed VORs or NDBs.. so if the default one doesn't choose them, this aircraft is not going to do neither because the gps used is the default one. There is a RealityXP option with real Garmin GPS that will try to insert in future. But only for windows. The proper way to manage this plane in navigation is manually.. with at least a VOR following navigation. So you have to be choosing one by one the vors, ndbs in the radios.. and following with the HSI.. like it was done old days.. (and even today, because this plane is still flying, and fly as said without any computer, and there are some of them that even they don't have GPS inside).

As said before the plane still is not ready for 64bits.. so no lights, no engines.. no systems would work in 64bits. Only 32bits for now. When the beta comes to final AND Ben send me a template of how configure C++ to compile in 64bits, then there will be 64bits version. Now that everything is changing and what is working now next beta is not going to work I don't want to work on the 64bits.

FMS???? in the Jetstream??? maybe you wanted to go to the CRJ200 support area.