Jump to content

swetters

Members
  • Content Count

    15
  • Joined

  • Last visited

Community Reputation

1 Neutral

About swetters

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

458 profile views
  1. I have also the CRJ installed, BUT the old one... But what I did, I updated the Airbus... Sounds like there is now some bug in RAAS locked versions... Maybe that same RAAS update came with Airbus too...
  2. Yes I have, but only the Airbus included locked version. I think that was it... Thanks for the help, I found in RAAS configuration window that field "Transition Altitude" and there it is, 18000 ft... The only thing is now... No need to update that value manually ever before... Haven't even been in that configuration window ever before and I think that altitude value has been updated automatically from flight plan entered to MCDU... So what if I fly e.g EFHK (5000 ft) to EGLL (6000 ft)... So need I now manually change that value from RAAS configuration before approach..? Could this be some bug in Airbus update (anyone else having this same issue?) or did that update just broke something in my installation and how things work together..?
  3. Airbus started to give me false "altitude setting" warnings since yesterday. This haven't been issue before, so I think every setting in MCDU and FCU are correct. Descending through FL124 to FL90 and altimeter set to Std how it should be at this altitude... Destination data correct, so TRANS FL is 5000... Automatically correct so no need for manual input... Still I'm getting constantly audio warning "ALTITUDE SETTING" and looks like it starts below FL180 so maybe there is somewhere P3D default U.S. information affecting to this..? What is different since last time when all was working correctly: - Airbus updated to version 1.2.5.2 - Navigraph AIRAC cycle updated to current 1913 - P3D navaids updated to cycle 1913 (https://www.aero.sors.fr/navaids3.html) Everything else are exactly the same as before, when it was working correctly. So which part of these three is the affecting one to Airbus's callouts? And maybe if it's some file easy to edit manually (e.g. correcting some transition level numeric value to the right one), what can this file be and where to find it? I think it might be of course the individual value for every airport, but at least I could modify these to the airports where I mostly fly, if there is not some other fix for this yet...
  4. Some update for this issue. First of all, I was today able to fly full flight EDDT-LSZH without CTD. I had PNG->DDS converted TrueGlass texture files in use. However, when loading the Airbus, it will still write those same error lines to content error log. But this is only when loading the aircraft, not anymore during the flight. During testing, I realized some other problems. It looks like the forward main windshield is not working how it should. I made some tests in a rainy condition and it looks like there are water drops on side window. The main windshield however looks like nothing. When accelerating, water drops on side window starts to move like they should, but fwd window is still like "empty". Can it be possible, that there are something more broken in TrueGlass, that only those formats differences in texture files? There are also some other threads about TrueGlass and/or RealLight related issues on this forum. Could it be possible, that these different issues are at least mostly caused now by some same base reason in TrueGlass/RealLight?
  5. Hi, Great that you was able to get it work DagelijksGamer. I'm not so familiar with different graphics formats, so can you tell more specific to which file format you converted those files. I have no clue what is the difference between those: I tried to do that with DXTbmp and chose the file type "DXT1 (no alpha)". Result: about 10 minutes after takeoff CTD and same ContentErrors.txt lines again: [error.55] error=Texture AB_WIPMASK_LFT.DDS failed to load (FE_REQUEST_STATUS==13) [error.56] error=Texture AB_WIPMASK_RGT.DDS failed to load (FE_REQUEST_STATUS==13) Then the speculation part: Could it be possible, that the CTD is caused by so called "mass effect" or "chain reaction". I mean, at least regarding to my experience you can't never get 100 % "clean" error log in P3D. Especially when many scenery, aircraft, etc. addons installed. For example in my sim, even the P3D default ground traffic vehicle Mitshubishi Pajero is writing some .cfg error lines to ContentErrors.txt. The fact is, that most of those errors are so called "normal" and those are not causing the sim crash. However, in certain conditions, can it be possible that different errors at the same time or too close this .DDS load failure are "too much", and the sim crashes. That could also explain why both of us got this CTD so randomly. Sometimes just after loading the flight and sometimes later after takeoff.
  6. Hi, I have exactly the same kind of problem after update 1.2.2.1. Some times the sim crashes just after loading the Airbus, sometimes I'm lucky and CTD comes after 5, 10, 15, etc, minutes after, but it will be the result anyway after some time (done about 10 test flights during last days). Not sure of course if this is same problem or not, but at least it sounds very similar. I did some investigation, and last entries in ContentErrors.txt are: [error.51] error=Texture AB_WIPMASK_LFT.DDS failed to load (FE_REQUEST_STATUS==13) [error.52] error=Texture AB_WIPMASK_RGT.DDS failed to load (FE_REQUEST_STATUS==13) Tried to find those files, but... There are only files named AB_WIPMASK_LFT.PNG and AB_WIPMASK_RGT.PNG in every simobjects/airplanes/aerosoft a3XX professional/trueglass/textures folders. Can it be possible, that something has been changed in TrueGlass (= file formats) and pathing isn't correct in somewhere else anymore and that will cause the sim CTD?
  7. Renaming works to the first issue, but those two antennas now got some weird blue and grey colors...
  8. Finnair CFMSAT -version. During this year Finnair is installing SAT domes to all A319-321 aircrafts. Some of them are already installed (for example OH-LVI). http://www.airliners.net/photo/Finnair/Airbus-A319-112/4955695?qsp=eJwtjbEKwkAQRP9lay1EsEgXKwUhFmK/7A3x4MwdexswhPy762E3vHnMrCR5MnzssRRQRxWs8qIdFVZ%2BV%2BpWUoyxmrLFPPViMyf3hsv%2B9ry6V7PaeXES2NCLoBjCnw8aoL8KVdrk6BcHD9B7y3Q8OQ%2BxlsRtA8Yx0bZ9AVYYMkc%3D There are great repaints already to whole Finnair fleet, but these all are "before SAT dome -versions". Maybe someone has knowledge how to correctly convert these to SAT dome versions? Instructions what to do or some update pack to download... Tried to tweak this by myself (thought that it's only one white dome on the roof) and just changed the 'model = DAIBA' to 'model = CFMSAT' in aircraft.cfg. Result: Didn't work so good I expected...
  9. Navigraph FMS data now supports A318-319 so I tried this with it too. Results: Changed runway and STAR after flying over LUSEP and NAPUN total 5 times from rwy15 to rwy04L and back again. Everything works perfectly and no errors in FMGS.log. So in my case I think changing navdata from NavDataPro to Navigraph solved this issue.
  10. I'm not sure how it's working in real aircraft, but in sim, especially if using default ATC, it's very useful feature you can change the approach without problems when you already are flying the first approach programmed. Normally you get the runway from default ATC so late, that the last enroute waypoint is already far away behind you. In my both cases, NAV mode was on when I just changed the runway and STAR from MCDU. After change of course HDG mode, because there wasn't anymore route to fly with NAV mode. I supposed that aircraft just starts flying the new selected one... This is how it worked with previous version of Airbus in FSX without any problems.
  11. This is happening with NavDataPro which came with the Airbus. I have Navigraph subscription but my Navigraph FMS Data Manager is not yet recognizing the new Airbus. However there should be come new AIRAC cycle on 19 Jul so maybe I'm able to change the data after that and test also what happens with Navigraph. Thanks for checking this!
  12. Tried to copy that flight and got following results. NDs and MCDUs did not stop to work at this time. Instead of that, all previous waypoints before final approach was lost. EFHK RWY15 and LUSE1M selected Changed to RWY04L/LUSE1B This is what there was left after change FMGS.log. I noticed those errors from it I have marked with orange. Maybe those had something to do with the previous error too..? [16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [PODOM] via [ILS04L]. [16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [EMPEV] via [ILS04L]. [16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [HTV06] via [ILS04L]. [16/07/2018 19:23:41:603]: FP change: WPT1 added: 12, [HTV20] via [ILS04L]. [16/07/2018 19:23:41:604]: FP change: WPT1 added: 10, [580] via []. [16/07/2018 19:23:41:604]: FP change: WPT1 added: 10, [MANUAL] via []. [16/07/2018 19:23:41:604]: FP change: STAR added: [I04L] @ [04L/ILS04L]; 10. 102. Many [16/07/2018 19:23:42:635]: PSDs (DI:1) 20.2 - DEC... entries between. I thought those have nothing to do with this, so I erased them to keep this more readable. [16/07/2018 19:23:53:004]: FP change: WPT1 added: 2, [LUSEP] via [LUSE1B]. [16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [NAPUN] via [LUSE1B]. [16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK890] via [LUSE1B]. [16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK897] via [LUSE1B]. [16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [NEMVI] via [LUSE1B]. [16/07/2018 19:23:53:005]: FP change: WPT1 added: 2, [HK802] via [LUSE1B]. [16/07/2018 19:23:53:006]: FP change: WPT1 added: 2, [HK801] via [LUSE1B]. [16/07/2018 19:23:53:006]: FP change: WPT1 added: 2, [PODOM] via [LUSE1B]. [16/07/2018 19:23:53:006]: FP change: WPT ersd: 12, [PODOM], at pos:12. [16/07/2018 19:23:53:006]: FP change: STAR added: [LUSE1B] @ [04L/]; 2. 79. [16/07/2018 19:23:53:006]: Prev WPT error. [16/07/2018 19:23:53:006]: Prev WPT error. [16/07/2018 19:23:53:053]: Prev WPT error. [16/07/2018 19:23:53:904]: PredDes: 15,175 (total dist: 28.87). [16/07/2018 19:23:53:904]: DECEL dist: 8.30. TotalDist: 28.87, Phase=4. ALT=27396, ApprAltThr=7363. Managed=1. [16/07/2018 19:23:53:904]: FlightParams: [27389, 197, 269] [-21.1, 0, 0, 0]. FM=-0.38,-2.27. TotalDist:29. DI=1. [16/07/2018 19:23:54:111]: FP change, TMPY INSERTED A. [16/07/2018 19:23:54:111]: MCDUAppType: 1. [16/07/2018 19:23:54:111]: Arrival EFHK ILS04L, 3.0. [16/07/2018 19:23:54:122]: RAD NAV: ARR ILS autotuned to: 111.90 (CRS 39). [16/07/2018 19:23:54:133]: PredsPrAppr2: 0,12. [16/07/2018 19:23:54:189]: FDComBankReq 1: -2.22, MGD:0. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[1:3]. [16/07/2018 19:23:54:189]: PredDes: 3,12 (total dist: 0.00). [16/07/2018 19:23:54:189]: FlightParams: [27384, 197, 269] [-22.1, 0, 0, 0]. FM=-0.36, 0.42. TotalDist:0. DI=1. Many [16/07/2018 19:23:54:243]: FDComBankReq 1: 0.42, MGD:1. AB_AP_HDGmode_setDisp: 1... (like three rows above) entries Error in putPt(): LUSEP(9692), CAS=-1008.963606. Error in putPt(): NAPUN(9693), CAS=-1198.485772. Error in putPt(): HK890(9694), CAS=-1350.894954. Error in putPt(): HK897(9695), CAS=-1462.536892. Error in putPt(): NEMVI(9696), CAS=-1534.641634. Error in putPt(): HK802(9697), CAS=-1534.641634. Error in putPt(): HK801(9698), CAS=-1509.173042. Error in putPt(): EMPEV(9686), UTC=-803.842156. Error in putPt(): HTV06(9687), UTC=-787.619156. Error in putPt(): HTV20(9688), UTC=-706.914146. Error in putPt(): EFHK(5), UTC=-650.474065. [16/07/2018 19:23:55:014]: FDComBankReq 1: 0.53, MGD:1. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[3:3]. [16/07/2018 19:23:55:014]: Prev WPT error. More [16/07/2018 19:23:55:069]: FDComBankReq 1: -2.24... entries [16/07/2018 19:23:57:067]: Prev WPT error. [16/07/2018 19:23:57:133]: FDComBankReq 1: 0.71, MGD:1. AB_AP_HDGmode_setDisp: 1; AB_AP_HDGmode: 0.00. Phase:4, modes:[3:3]. [16/07/2018 19:23:57:133]: [fly_lnav] Empty WPT LUSEP skipped.
  13. A319 CFM both NDs and both MCDUs froze on approach. I had already selected runway for approach on F-PLN and I changed it to another runway and approach on F-PLN . After this change both MCDUs and NDs stopped working. None of MCDU buttons didn't work anymore in VC or in 2D panels and ND range swithch or WX-radar swithches didn't affect to NDs anymore. Everything else was working fine and I was able to land without ND and MCDU. After landing I tried to switch engines, APU, batteries and all IRS switches off. Everything else turned off, except those NDs and MCDUs. Tried to power up aircraft again and those NDs and MCDUs still not working. Is there some error log somewhere in Airbus or P3D folders to figure out what happened? Or have anyone else had the same problem?
  14. Ok, thanks for information. I'll wait to next week and test my recent purchased "deal of the week" LSZH instead of EGLL at this weekend. At the first sight it looks awesome too!
  15. I have FSX version of Mega Airport London Heathrow Xtended purhased and trying now to upgrade it to P3DV4 Professional version. I found the voucher field at first page at checkout, but when I paste my old serial key there, nothing happens. No error messages or something like that. It just reloads the page again and the price is not changing. What I'm doing wrong or is there some issue to change the discount to another because of that another 25% sale going on right now?
×
×
  • Create New...