We have at this moment problems with e-mails coming to us via Microsoft servers (Outlook, Hotmail, Live, etc). We are in contact with Microsoft to solve this issue.

Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation

7 Neutral

1 Follower

About atav757

  • Rank
    Flight Student - Airwork

Recent Profile Visitors

796 profile views
  1. Ah okay! Good enough, I assume we'll see these features added in awhile. Thanks
  2. I for the first time opened the AB_fuel.xml and saw the code so I didn't need to post all this. But I do see it's now handled partially by a dll? So I suppose the things to be fixed are when engines are off, and the slat extended thing.
  3. Is the center tank fuel system being worked on still? When looking at the ECAM it doesn't seem to follow logic of the real airplane after the last few updates. I notice it's showing "off" when you turn the pumps on, if the engines are off. Of course in real life, they'll be on even if the engines are off, in auto mode. They don't work like the Boeing style. For the soundset I made, I created some code for it, feel free to use it: Includes manual logic, auto logic (120 second timer, 300 second timer, slat logic, etc.) Obviously, red text should be deleted. <!-- FPC1+C2 --> (L:AC_POWER_ON,number) 1 == if{ General conditions where C pump 1 would be powered (L:AB_OVH_FUELMODE,number) 1 == (L:FUEL_PUMP_AUTO_LOGIC,number) 1 == and (L:AB_OVH_FUELMODE,number) 0 == or (L:AB_OVH_FUELPCL_FAULT,number) 0 == (L:AB_OVH_FUELPCL,number) 1 == and and if{ 1 (>L:FUEL_PUMP_C1,number) } els{ 0 (>L:FUEL_PUMP_C1,number) } General conditions where C pump 2 would be powered (L:AB_OVH_FUELMODE,number) 1 == (L:FUEL_PUMP_AUTO_LOGIC,number) 1 == and (L:AB_OVH_FUELMODE,number) 0 == or (L:AB_OVH_FUELPCR_FAULT,number) 0 == (L:AB_OVH_FUELPCR,number) 1 == and and if{ 1 (>L:FUEL_PUMP_C2,number) } els{ 0 (>L:FUEL_PUMP_C2,number) } Auto mode logic (L:AB_OVH_FUELMODE,number) 1 == if{ (L:FUEL_TANK_CENTER_qty_check,number) 0 != if{ (A:LEADING EDGE FLAPS LEFT ANGLE,degrees) 0 == If tank has fuel and slats are 0 if{ 1 (>L:FUEL_PUMP_AUTO_LOGIC,number) } els{ (L:ENG_START_IDLE,number) 1 == If slats are NOT 0, check to see if an engine has been started in the last 120 seconds if{ 1 (>L:FUEL_PUMP_AUTO_LOGIC,number) } els { 0 (>L:FUEL_PUMP_AUTO_LOGIC,number) } } } els{ 1 (>L:CENTER_TANK_EMPTY TIMER Running,number) } If tank is empty, start a 300 second timer, then if tank is still empty, shut the pumps off (L:CENTER_TANK_EMPTY Timer Running,number) 0 == if{ (P:ABSOLUTE TIME,seconds) (>L:CENTER_TANK_EMPTY Start Time,seconds) } (L:CENTER_TANK_EMPTY Timer Running,number) 1 == if{ (P:ABSOLUTE TIME,seconds) (L:CENTER_TANK_EMPTY Start Time,number) - (>L:CENTER_TANK_EMPTY Elapsed Time,number) (L:CENTER_TANK_EMPTY Elapsed Time,number) 300 >= (L:FUEL_TANK_CENTER_qty_check,number) 0 != or if{ 0 (>L:CENTER_TANK_EMPTY Timer Running,number) 0 (>L:FUEL_PUMP_AUTO_LOGIC,number) } } } (A:SIM ON GROUND,bool) 1 == Logic for engine "started and idle" in last 2 minutes if{ (L:AB_PDS_Eng1Master,number) 1 == (A:ENG1 N2 RPM, percent) 20 &lt;= and (L:AB_PDS_Eng2Master,number) 1 == (A:ENG2 N2 RPM, percent) 20 &lt;= and or if{ 1 (>L:ENG_START_VAR,number) 1 (>L:ENG_START_IDLE,number) } Consider engines "starting" when master on and N2 < 20% (L:AB_PDS_Eng1Master,number) 1 == (A:ENG1 N2 RPM, percent) 60 >= and (L:AB_PDS_Eng2Master,number) 1 == (A:ENG2 N2 RPM, percent) 60 >= and or (L:ENG_START_VAR,number) 1 == and if{ 1 (>L:ENG_START TIMER Running,number) } Consider an engine started and start the timer when an engine is master on and N2 > 60% (L:ENG_START TIMER Running,number) 0 == if{ (P:ABSOLUTE TIME,seconds) (>L:ENG_START Start Time,seconds) } (L:ENG_START Timer Running,number) 1 == if{ (P:ABSOLUTE TIME,seconds) (L:ENG_START Start Time,number) - (>L:ENG_START Elapsed Time,number) (L:ENG_START Elapsed Time,number) 120 >= if{ 0 (>L:ENG_START Timer Running,number) 0 (>L:ENG_START_VAR,number) 0 (>L:ENG_START_IDLE,number) } After 120 seconds, consider the engine no longer "started and idle" } } }
  4. Glad it worked! Kind of hard to explain but let me try: So, the FSX/P3D way of starting engines is terrible. The fuel flow, EGT, N1/2, etc. is pretty badly modelled. Developers tend to modify the aircraft gauges using algorithims to make it seem more realistic. What you end up getting is some compatibility issues. For example, there's a famous 737/747/777 developer ( ) who changed the way the engine start works by introducing fuel at the "right" time (according to the gauges and EICAS), but telling FSX/P3D that it's actually happening about 7-10 seconds later. Why? I don't know specifically what they were trying to replicate, but I think it was to make the sequence be of a realistic timing. So, the CTRL+SHIFT+F4 seems to always work. Hopefully AS can make this permanent!
  5. My solution since back in the day on the flawed engine start is: as I put engine 2 master to on, I also press CTRL+SHIFT+F4 (well before combustion is supposed to happen), the engine start interruption doesn't happen when I do that. I can make a video to show that. If AS just adjusted the gauges to make FS internal sim variables think combustion is happening even a couple of seconds before it actually is, the problem would go away.
  6. Well, moving the lines from the appdata add-ons.cfg to the programdata add-ons.cfg fixed the issue for me!
  7. I suddenly out of nowhere have this issue too Updated with a full uninstall/reinstall of the newest bundle version.
  8. Thought as much, thank you sir! Do I have to officially report as a bug?
  9. I don't think you fully read my post, my cruise altitude was 14000, and the temp at 14000 was +7. I don't fly A320s IRL but I fly a different aircraft and that one lets us put in any range of CRZ temps, positive or negative. Looking at my company manuals, it doesn't say anything about zero or negative only on the 320 or 330.
  10. Any idea how it's done in the real world then? Today at FL140 the temp was +7 down in central Florida.
  11. Unable to put in a positive value for temp. I've tried /+1, /1, etc. Today trying /+7 /7 (I'm doing a real world flight from SRQ/MCO which is very short and low). The number reverts to -7.
  12. If you guys have it modelled at 800-1500 then that's exactly right! It's just that it doesn't appear to work for me, anything below 1000 returns a OUT OF RANGE. I'll PM you now. EDIT: I'm an idiot... the airline manual says right on it that when entering the altitude if it's below 1000, a leading zero MUST be entered.. so 818/818 should be entered as 0818/0818, is this how it's modelled with AS? (I'm not at a computer now to try). In that case, case closed! "PERF key . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Push Enter/modify/check the following: • Enter planned V‑speeds. • TRANS ALT will default to the area of operation. • THR RED/ACC ALT: set both to the MSL values printed on the ACARS runway data message. Normally, both are 800 feet AFE. Other values may be specified to meet operational requirements. Note: Values must be entered as 4-digit numbers to include a leading zero if the value is less than 1000 (e.g., 0851)."
  13. Is it possible in a future update to allow THR RED and ACC altitudes to accept values below 1000msl? The company I'm referencing uses 800AGL as thrust reduction and accel altitudes as standard. Of course it works fine at higher elevation airports as I can just at 800 to the field elevation. But taking off from KSFO and putting in 813/813 doesn't work. Maybe for the future?
  • Create New...