Jump to content

mmerelles

Members
  • Posts

    1,190
  • Joined

  • Last visited

  • Days Won

    30

Everything posted by mmerelles

  1. First of all, the aircraft is more efficient, faster and consumes less fuel at higher altitudes. So, for descends, the FMC will try to keep the aircraft at higher altitude as much as possible computing a valid descend profile that does not violate any procedure constrain, neither aircraft/commercial descend rates. XXXXXA means the aircraft must cross that waypoint at that altitude or above. It means, you are not authorized to descend more than XXXXX. But the aircraft can cross much more higher actually if required. XXXXXB means the aircraft must cross that waypoint at that altitude or below. It means by the time the aircraft arrives to that waypoint it must be already at that altitude or even below if required. XXXXX (in bold) is a hard specific restriction, the aircraft must cross that waypoint at that specific altitude, not lower, not higher. That being said, if you are 31000 and next WPT is 16000A the FMC knows it can not cross that waypoint below 16000 but any altitude above. By the rule of higher if possible is better, the FMC will cross higher than 16000. How much higher? depending on waypoint restrictions ahead. The farther away next restrictions are, the higher the FMC will cross because it has no need to descend that much yet. By contrary if you are 31000 and next waypoint-1 says 16000A and next waypoint-2 is pretty close to waypoint-1 having a hard strict 15000 restriction, then the FMC will cross waypoint-1 quite close to 16000 because it has to continue descending to 15000 in a short distance to meet waypoint-2 Hope you have the idea. note: please note during descend the aircraft may be flying undesirable higher than the vnav profile due to lack of DRAG. Watch your FMC messages and watch your VNAV descend profile on the ND. The FMC will let you know how you are regarding the target profile.
  2. mmm not sure i am understanding what you are asking for. If the waypoint says 14000A the aircraft can cross that waypoint at any altitude above 14000. At which altitude? the altitude that the FMC computes is best to pass above 14000 for that waypoint and comply next waypoints ahead. Maybe you should provide an entire route explame to understand better your point. All the route including runways, sid, route, star, arrival procedure, etc. So we can double check what you are asking and eventually try to replicate if there is a potential bug
  3. Lets suppose your aircraft ZFW is 45592 ZFW has a formating of XXX.X this confuses many people and tries to enter 455.9 (this aircraft can not weight 455 TONS) you have to enter 45.5 (45 tons and a half) And yes, this aircraft you enter the ZFW and the FMC calculates GW doing ZFW + FUEL hope this clarifies
  4. There seems to be a misconception about fuel pumps on any aircraft being required for the fuel to reach the engines or they won't work. This is wrong. All engines have their own mechanical internal suction pumps that pull fuel. If you do not turn on any external fuel pump they will work anyway. External fuel pumps (the ones you manipulate on the cockpit) are there to guarantee fuel to the engines in case their internal fuel pumps fails, and during full throttle or critical phases of flight/attitude/maneuvers to guarantee the right amount and constant positive fuel pressure on the lines.
  5. The doors and the cabin are not available for version 1. It will not work.
  6. ops... glad you managed to fine tuned the solution i assumed the CRJ200 was also compatible to xplane navdata.
  7. 1. for fuel trip planning, you look at the aircraft charts (or internet planning tools) for the fuel burnt per hour according your flight parameters (weight, pressure altitude, etc.), you do some basic maths as per your trip distance +including reserves, alternate, etc and you get the total. 2. during flight, you look at fuel flow consumption display, you do the maths vs remaining distance/time and you know your fuel. note: no matter fmcs does provide this information, pilots are required to do their thing to cross check. You better know how to do it, it is rewarding to have as much knowledge as possible. If it is not on Saturday, i presume it will be available on a few weeks so no big deal.
  8. oh men WHAT A GLORIOUS DAY and those 2 pictures are amazing by the way, looks so real. Weekend plans cancelled
  9. You are not getting 01/19 on the SID/STAR because you have an oudated cycle on the CRJ-200 and the runways renumbered by the end of 2015. Assuming you are running xplane 10.45, if not then update xplane, it is free (xplane 10.45 includes cycle AIRAC1602 (2016 - February). 1. go to your /xplane 10/custom data/gns430/ and copy the folder navdata (and all of its content, so copy the folder) 2. to your crj-200 navdata folder, usually located at: /xplane 10/Aircraft/CRJ-200/plugins/CRJAvionics/ (there should be a navdata folder here already, replace it entirely, delete the old one first!) now your crj200 will have the cycle 1602 on its database including sid and star
  10. disregard, i am an idiot plain and simple i was testing all different settings and combinations to get the best balance to go un xplane rendering and skymaxxpro+wrc and missed to disable extended DSF on the second imac. It seems having extended DSF on the rendering settings disabled on the master but enabled on the slave makes the slave camera go crazy under the still spot view. Just in case someone else has this crazy behavior, here is the answer, not wrc. i will do some flights and report back how wrc works to me on a dual imac setup. So far the install went smooth and the fps are the same on the ground
  11. I have purchased and installed RWC on a dual imac setup runing skymaxpro for a very long time, updated to 3.1.1 first. first thing i noticed -really weird by the way- when selecting the "view is still spot" slave camera goes crazy, no longer works. please see atached 3 pics. 1 view from the cockpit interior. Works great. 2 chase view. Works just fine as well. Tower view, runway view, they all work just fine. 3 still spot. Slave machine goes crazy and points to a water view. I also tested it while on the air, same result but pointing to the ground any ideas what could be wrong? Thanks!
  12. Due to earth magnetic declination changes VIGO airport had to renumber their runway from 02/20 to 01/19 by the end of 2015. Why did you install an older CYCLE1512 (2015 - DEC)? xplane current version has already included CYCLE1602 (2016 - FEB) I presume the older cycle you installed has a bug with runway renumbering not properly updated on all procedures. I am not at the sim now to check that the newest cycle included with xplane 10.45 does not has the issue. edit: misspelling
  13. Nothing is bug free, not even the real aircraft has bug free systems! Be sure some quirks will arise when released for such a massive complex detailed simulation. Anyway, i fully agree with you the IXEG bird will raise the bar substantially on xplane and i am quite confident we will get a marvelous product for the money that they been working on for years with passion and proper skills.
  14. As the message says install latest version 3.1.1 not 3.1 you have.
  15. i did read all the description, highlights and features -very impressive by the way- but still unable to get any info about dual computer setup. I am particularly intrigued to know if real weather connector can be installed on a dual xplane/computer setup for achieving a bigger filed of view and cloud placement will be consistently on both machines so you have them in sync under a split computer bigger field of view. thanks!
  16. can we expect in sync views from real weather connector under a dual computer setup? or anything specific to know about this setup?
  17. sorry i guess i missed that. it could happen being spanish speaking guy
  18. fantastic bird small observation, is the flaps needle moving too fast?
  19. This aircraft is unable to taxi single engine, this is wrong compared to the real thing. It has been reported already, developers have said they will look at it. No further update that i am aware of still.
  20. i have a vague idea that yes, landing without applying reverse also has the issue but not sure. maybe an issue with hydraulics? braking getting stuck? can you try to land on a long runway applying reverse but not braking now? and then trying to taxi... i do not think it is xplane ground issue, because when leaving the gate prior to takeoff the aircraft taxies out clean and crisp, it is very responsive to power lever beta input. Any time i have seen this issue was taxing power after landing. I need to get back to home to open all datarefs make lot of testing and compare taxi parameters (engine, torque, blades, thrust, rpm, fuel, hydraulics, etc,) prior to takeoff against after-landing.
  21. glad it is getting better for you as well. I do not want to post much more and keep speculating on this. I will try to spend some time next week when able to come back on this and see if i can figure out what is going on for providing the developers better evidence about this in the meantime enjoy this bird, is one of the very best available for xplane.
  22. ohh men this aircraft is going to be amazing. hopefully it gets released soon, i have been awaiting patiently but it is starting to get difficult...
  23. Thanks for sharing, this video shows the aircraft -as said- has no such behavior, and when put out of reverse mode to ground idle it keep rolling freely and nicely. These are my observations on this video. 1. at 1:02 CLs goes to max as part of landing checklist, just in case of a go-around is required maximum torque is available. 2. at 2:22 power lever goes to reverse mode following touchdown, left & right beta mode engages. 3. at 2:33 power levers goes back to ground idle as per the procedure (speed). the aircraft rolls nicely and captain is required to control final exit speed via braking. 4. clearing the runway at 2:54 they perfom after landing checklist and CLs goes to MIN as part of the procedure (this is not required by the aircraft to taxi) 5. at 2:58 while making 2 hard turns to the right the captain adds a bit of beta power lever to complete the turn, the aircraft keeps rolling nicely. on the sim however, this aircraft sometimes tends to get stuck on the runway no matter you moved the power levers out of reverse mode 10 seconds away, increasing power levers on beta mode doesn't help either. It takes abnormal amount of time to regain thrust again. Following the Argentina's sol real procedures i found putting the CLs to MIN restores thrust immediately by coincidence but it shouldn't work that way. This is not a big deal for me i can live with that, but seen others may have this behavior as well i will try to spend some time testing if i can get a repeatable and reproducible behavior for providing better evidence.
  24. Yes i know, that was my whole point when i reported this bahaviour when landing the condition levers are set to max, just to have torque under a potential go around once you landed you apply reeverse and braking, then you clear the runway in beta mode. As you said, It shouldnt matter you leave the cl at max. well, the weird behaviour is you leave them on max and the aircraft may get stuck on the runway for more than 15 seconds while you try getting thrust moving the power levers wirhin beta wirh no luck i found that moving the condition levers to min after landing makes this weird behaviour go away this only happens after reverse/landing ground operatio prior to takeoff works flawlesly The real thing does not have this issue
  25. I do not have installed any driver. I go to xplane joystick and assignments and set left throttle lever to throttle1 and right lever to throttle2 and they work flawlessly in all my payware birds (ff757/767/777, fjs727/737, rotate md80, saab340 and awaiting for the ixeg 737CL ) For the reverse handles i assigned them to xplane max reverse thrust hold. i can not control how much reverse but they work flawlessly and feels great pulling those levers after landing. I tried assigning the flaps lever to flaps also, and they do work. But as jojo3800 said, the xplane flap lever dataref goes 0.0 to 1.0 and you get crazy flaps settings like 13.2, 14.8 and whatever in between. The goflight tqm has a physical detent for flap settings. if could set ranges for the dataref it should work biggest problem is when closing the lever to 0, sometimes the dataref it is still 0.0001% and you rip the flaps inflight.
×
×
  • Create New...