Jump to content

46Pilot

Frozen-Inactivity
  • Content Count

    65
  • Donations

    $0.00 
  • Joined

  • Last visited

Everything posted by 46Pilot

  1. Hi @Wickedbacon92, Please, can you send me a link from where I can download the files for TAROM ATR? All the best, Alex
  2. Yes, but I've reported it already, the crossfeed is not working as it should be..
  3. But if MilViz will release their ATR in the meantime...
  4. It is a pity that such words have been said and, instead of doing good things for the community, we are fighting...
  5. I don't know, I don't have the beacon light issue... Have you installed the version 1.1? Maybe a bug in V1.0, but I cannot check it as I have installed V1.1 ...
  6. I didn't see any problem with tank capacities, I will check again. Should be 4500 kg in total. On AFCS the altitude below 10000 does not have a leading 0. CPL light with clickspot, yes, it should be. If you consider that we can do a patch without legal problems from the carenado, and your think I can help you, send a PM to me. Carenado team members don't reply to my emails so I took it as a "No", they don't need my help.
  7. Yes, it is VERY noisy! No, it is not required for the GPU to be connected, but without it you don't have any electrical power source. The batteries feed only a few things and they drain quickly. Another interesting info is if the batteries are dead, you cannot connect the GPU, because the GPU feeds the aircraft through them and even with GPU on and plugged-in, the AVAIL light on the upperhead panel with not come on (even if you press the button, there will not happen anything). You can either plug in the GPU, turn on the batteries then connect the GPU by pressing the pushbutton, and after everything is done, start the engine no 2 in hotel mode, or turn on the batteries and start directly in hotel mode, if no GPU available, for example.
  8. It doesn't matter. The role of hotel mode it's to provide electricity and air for conditioning. For example, in real life, you land at an airport and taxi to the parking position. There, you engage prop brake and continue to use the engine no 2 in hotel mode until the GPU is connected to the aircraft, after that you can shutdown the engine. There is no reason to release the parking brake now. At startup, you will need to use the hotel mode, because the ground crew have to disconnect the GPU before propeller rotation, to take the chocks etc. All of this in hotel mode. After everyone is away from the aircraft, only then you can release the propeller brake. Rarely, after shutting down the engine with prop brake engaged, we release the prop brake for the maintenance personnel to work something at the engine and after they finish we re-engage the propeller brake for the following engine start. I hope it's clear now. Long story short, it doesn't matter, you can do it however you want, but there is no reason to release the propeller brake before engine shutdown.
  9. You can anytime reduce the power levers out of the notch to keep the speed under the limit. Also, from top of descend all the way down to the runway, we continuously keep the hand on the levers and adjust them to keep as much as possible a constant speed. Also, for the airplanes with older engines or with engines approaching the end of time (they need to be replaced), usually the ITT tends to go over the limit, also when cruising we reduce a little bit the power levers, to keep the ITT a little bit cooler.
  10. In real life, the ATR 72 is a little bit underpowered. It's very funny to fly it during hot summer days or in the winter in icing conditions... it's a 4 tons heavier aircraft than the ATR 42 with only 300 hp added power..
  11. Yes, it really is full of bugs...
  12. Please check this document and we will talk after that. You will be looking for "42 PEC" (with blue background) actions. You will also find the differences in operation for all types of the ATR. This is the document underlying daily operation under normal conditions. https://www.theairlinepilots.com/forumarchive/atr/fctm-norm-proc.pdf PS: What kind of operations do you want to do, only "Hot and high"?
  13. @FDEdev leave him alone, it doesn't worth to waste your time with him if it's clear that he doesn't want to learn something and he is trying to convince himself that he is wright.
  14. What would suggest you the name "100% OVRD (override)". It's to override the AUTO mode, when something it's not working as supposed. There are a few situations when you use the CL on 100%, but those are abnormal situations and the checklist will tell you when to use them, as explained before. To takeoff in "extreme conditions"..... if you kill your engine at takeoff, just to get every horse power available, what do you do with the rest of the flight? There are other actions to be taken for takeoff, for example bleeds off takeoff, limited takeoff weight and others. But, if this is the way you want, ok, go with that, it's just a sim, you won't break anything... PS: it's my last post on this subject.
  15. Established, sorry, typo. Corrected now.
  16. Affirm, at minute 1:30 it shows very clear the position of the levers. I saw an youtube clip by carenado where they explain the operation of the prop brake and it's a little bit wrong, as they put the CL in 100%. I've tried to explain them also why this is incorrect, but they don't want to collaborate and to make it accurate, so I think I will make a step back and cancel my intentions.. The idea with CL on 100% OVRD could be an operator procedure, but the manufacturer don't say you have to put the levers there. More than that, there is no normal checklist done by the ATR which says to put CL on 100% OVRD.
  17. @Fresjay76 you have to uninstall the existing version, go to into your carenado account and download the installer again.
  18. @FDEdev oh, ok... as far as I know, it's not allowed to start the final descend until established on the localizer..
  19. I've decided to create a new topic and to have all the discutions regarding the bugs in a single place. I took this decision because there are several topics talking about systems or bugs and there could be informations lost or missed. If someone knows how to contact an admin and to move the posts to a single topic, it will be great. The abovementioned topic is  Thanks, All the best, Alex
  20. I've decided to create a new topic and to have all the discutions regarding the bugs in a single place. I took this decision because there are several topics talking about systems or bugs and there could be informations lost or missed. If someone knows how to contact an admin and to move the posts to a single topic, it will be great. The abovementioned topic is Thanks, All the best, Alex
  21. The ATR doesn't have VNAV autopilot function, only advisory informations on the EADI.
  22. Hi to everyone, Some of you know as we talked on other topics about the ATR by Carenado that I have started a bug list and I have reported since then many anomalies of this product. The respective topics are: - AND If an admin would consider it more appropriate, I would like also to move all three topics in a single one, to have it more clear for everyone what we have discussed during the time. In the following, I will present an updated list with all the bugs that I've discovered on the ATR 42 and everyone is invited to comment about this post and to add if they found anything else. Today a version 1.1 of the ATR has been released and even if I've written in the past what bugs I've found and sent the list to the Carenado team, for some reason, they didn't replied to my email and some of the bugs are still present. I tried to contact them via other channels, as you may know this already and they said that they have received my emails, but they hesitate to tell me if the manager of the team accepts to join the team and to offer them my help, knowledge and materials, for free, to build a patch for this aircraft, to simulate it as real possible, to solve all the bugs and to make it for real the most ambitious and biggest project. The first thing I would like to say about the ATR is: Congratulations for the external model, the PBR looks stunning! The propeller brake is correctly simulated, as well as Power Management (PWR MGT) settings, power ratio, fuel flow and flight performance. There are many other things looking good or correctly simulated, but lets concentrate about what's wrong. So, below is the list of what I've found so far: PART A - The status of the systems, button and switches is not correct in "Cold & Dark" mode. (see Cold & Dark status below, part b.) - When the battery is switched to ON position, MFC test is not performing. In fact, when selecting the "Cold & Dark" option, the MFCs are selected OFF, which is incorrect. When the MFCs are performing the self-test, MFC 1A & 2A should flash 3 times, then 1B & 2B. After that, DC power will be available to the aircraft. - External power not modelled correct, or not fully available. It appears as AVAIL both on DC and ACW a short time after switching battery on, but after a short while, DC EXT PWR goes off - it is the main EXT PWR in real life, not the AC one. When the DC EXT PWR AVAIL light goes off, the ACW remains on, but has no effect on electrical system. If possible, would be nice to add a power cart like the one from the S550 Citation.. - ENG OIL alarm at startup, for both engine. It shouldn't come on as modelled in the sim. - "ON"/"FAULT"/"OFF" lights for the pushbuttons do not lit according to the status. They don't work at all if loading the sim with the ATR from the start, you have to load the sim with another aircraft and after that load the ATR. - Big issues with the hydraulics. With the Condition Levers on FTR position, "OVHT", "LO LVL" and "LO PR" are all lit, which is incorrect. - NP values are too high for the FTR and AUTO positions of the Condition Levers. In FTR detent, the NP should be around 15%, and in AUTO detent, the NP should be stabilized at 71%. - LO PITCH is illuminated when the engines are off. LO PITCH lights illuminate after 15 seconds from unfeathering to low pitch (moving condition levers from FTR to AUTO). - When engaging IAS mode, the minimum speed on the ADU is "0 (kts)", which in fact should be "80 (kts)". - Electrical "OVRD" (override) and "UNDV" (undervoltage) lights are always on. - Recirculation fans are FAULT if no engine started and ON with engines started. The recirculation fans can operate independent of the engines, they just recirculate the air inside the cabin. - In HOTEL MODE operations: Recirc Fan 1 fault, Pack Valve 1 Fault, OVHT & Leak on Bleed 1. In hotel mode, only Bleed 1 should be fault, because the engine is not providing air. Pack valve is operative via ground crossfeed valve (GND XFEED VLV) from bleed no.2. OVHT & Leak should be off (extinguished). - Nav waypoints are always ON on the EHSI display and all of the nav waypoints near the aircraft are displayed. This is incorrect, because in real life, only the waypoints from the GNSS flightplan are displayed and maximum 5 waypoints at a time. - ATPCS test is not modelled. - "INST" (instruments) rotary buttons controls all the lights inside the aircraft, including the cabin lightning - it should control only instruments lightning. - "LT FLOOD" is not modelled. In fact, INST button is controlling the flood light also (yellowish light beneath the AFCS panel). - Storm light is not modelled - it is a powerful neon light beneath the AFCS panel. - NAV BRG selectors: on NAV 2 selector (ADF/VOR/NAV), if you click on the side of the selector, it changes NAV 2 selection. If you click on the upper side of the selector (white line), it changes NAV 1 selection. This bug is only valid for the NAV 2. NAV1 BRG selector works correct. - No RDR/TERR mode available. - RCL/CLR/TO INHI modes are not modelled, as well as GPWS test. - If you press a button, it remains on. For example, if you press once HYD AUX PUMP button, to engage the prop brake, the READY light will be always on, until if you press again the pump button. In real life, it is on for only 30 seconds. - No ALT Alert during climb or descend, when 1000 ft apart from selected altitude. - If you press HDG bug, it syncronizes the HDG. For CRS, it shows a direct to value. This is not correct for the real aircraft. - You cannot intercept a VOR radial or the ILS if you are in the FMS mode and showing the map, you have to be in NAV mode and full rose mode or arc. In the sim, you can intercept the ILS while in FMS or FMS map displayed. - With CL in FTR, ACW GEN FAULT, BLUE and GREEN hydraulic main pumps LO PR. This is correct. AUX PUMP LO PR, OVHT, LO LVL lights should be off. - SVCE UNLK does not come on when the service door is open. - Some sounds should be changed, because there are no vocal aural alerts, as for example "Altitude Select" or "No takeoff". - If a pushbutton is in OFF position, no "FAULT" light should be illuminated. - When engaging the autopilot, if Yaw Damper has not been previously engaged, it engages automatically when pressing the AP button on the AFCS. - Fuel crossfeed not working properly - still taking fuel from both tanks. - The last two indicators of the engine parameters (Fuel Flow / Fuel Used) are two separate gauges. The analog one, the needle, shows the Fuel Flow, which is the current fuel flow per hour, and the digital one shows the fuel used, how much fuel we have burnt so far. In the sim, the both of them are showing the fuel flow, but no fuel used. - When APP mode armed, the glideslope can be captured before the localizer. - The sounds of the AFCS (autopilot) are not accurate, because the knobs don't have steps, so they do not "click" when turning left or right (heading, course, altitude selector, pitch wheel) - As a suggestion, if possible, main entry door, cargo door and service door to be opened separately via windows manager. In the version 1.1 I've discovered the following bugs: - When pressing on the "OVHT" annunciator light, the PACK Valves comes ON or OFF, depending on the status (if ON, they will switch to OFF and vice versa). - When performing an Annunciator Light Test - the master warning sound is triggered and it shouldn't. - "EMER DOOR UNLK" on the overhead panel is ON when the doors are open, but this is incorrect, the emergency door is in the cockpit ceiling. PART B Cold and Dark status: NOTE: 1. Here is included only what should be changed, what is correct is not mentioned below. 2. This list was created for version 1.0, but some bugs are still present in the version 1.1. 1. OVERHEAD PANEL: · LOOP A & B (both engines) pushbuttons - ON · MFC pushbuttons - ALL ON. NOTE: When battery is switched ON, MFC should perform an autotest as described above. · Fuel Pumps - OFF · Electrical "OVRD" & "UNDV" - OFF (extinguished) · DC BUS 1 & 2 EMER BAT CHG pushbuttons - ON · DC GEN 1 & 2 pushbuttons - ON (engine being shutoff, FAULT light illuminated) · PROP BRK - ON or OFF (depending on the operator) · HYD Blue & Green Main Pumps pushbuttons - ON (due to lack of ACW Generators, FAULT light illuminated) · HYD AUX Pump pushbuttons - ON · HYD XFEED pushbutton - OFF · ACW Generators 1& 2 pushbuttons - ON (FAULT light illuminated, no propeller spinning) · AFR AIR BLEED pushbutton - ON · Oxygen pushbutton - OFF · Exhaust Mode - ON (NORM) - no light - · RECIRC FANs, PACKS, BLEEDS pushbuttons - OFF (correctly shown in sim.). OVHT, LEAK and FAULT lights should be OFF (extinguished). · ATTND CALL: "EMER" and "CALL" annunciators are separate, depending on what button the flight attendant is pressing to call the cockpit. 2. MAIN PANEL: · CRTs - OFF · Red flags on RMI - OFF (Flags on RMI indicates the AHRSs are not aligned properly, not that there is no signal from the ground station, as simulated now). · Takeoff bugs (white triangles) - 90% · Captain left side - TERR - ON 3. Pedestal: · Gust lock - ON · Radio stations - OFF · Transponder should have also an OFF position. Radio COM stations cannot be switched off in sim, altough there is an "OFF" position. Wish you all the best, Alex
  23. Unfortunately, it's too buggy right now. For someone who just wants to hop between two airports, could be ok, but for someone who wants something more.... 😞 Here is another topic where different stuffs about the ATR are being discussed.
  24. As far as I remember, you have to use your F1 configurator (a desktop app) and there you choose different options. I haven't used it since some time ago, but this was the procedure, more or less.
×
×
  • Create New...