Arnaud

In case you missed it, I suggest you go and check out this thread.http://forums.avsim.net/dcboard.php?az=sho...id=95460&page=1Hope this helps,

I want to throw here my own personnal experience of what one can hear in a 747-400 cockpit during start-up, since I was lucky enough to experience it twice: almost nothing, no sounds of the engines. A tiny vibration maybe, that's all.You can see the engines starts running by looking at the EICAS actually.So I am for one satisfied with the silent start-up. I've always found on other add-ons exagerated the way the engine start-up sounds was done, way too loud.The very slight sound of the 747-400 SU1 is ultimatley realistic for me.As it was said previously, during start-up you hear mainly the air conditionning and flight attendant coming in the cockpit to report that the cabin is checked and ready-to-go!Regards,

Henry,See this thread:http://forums.avsim.net/dcboard.php?az=sho..._id=95289&page=

No Alex,This had not been fixed in the update. I had spotted it indeed in the old forum, but this had not been adressed yet.To fix this, one might want to edit the aircraft.cfg (I'd caution you doing that tough)and go to GeneralEngineData section and change the value for engines 1 and 4 to the correct values (using ACM for instance) ...Well, actually, I did not do that myself although I know how to do it, because I was unsure if adjusting those lines would have any impact on the flight model.If someone could tell us it has no impact on the flight model, then I'll post here the correct settings.

Rico,I was very happy with the interim patch as well (which I kept on my HD just in case) but you can trust me when I say you'd be even more happy with SU1. It's a bit tricky to install for some users, but definitely worth the hassle...There are so many improvements. I simply had to uninstall the whole 744 and fresh re-install with SU1. Before that, except if I didnt have CTD, I also had some gremlins under the windscreen and under the captain's seat.Dont stay like that :-)

Dear Alex, Only one word: madening, right ? :-) Completely off-topic, about my catastrophic landing in LGA, I checked the ILS22 there, the localizer was indeed c0ompletely misplaced!http://aiarnaud.free.fr/pics/iurd.jpg]Fixed that, one more (even if 100% OT) good point for that flight!Best,

Hehe, Marc, that looks delicious :-) Cant wait..Regards,

Ryan and Alex-We do appreciate your help here. actually, I come back to report because I had enough time today to complete a full long haul flight,first one since SU1.Took off from Manchester and headed to New York City-La Guardia airport (wanted to try a landing on 22R, short one;-) , and for the pleasure to land facing Manhattan)...Appart from the VERY bad surprise to find out a few nautical from therehold that the scenery ILS was screwed (due to a bad add-on AFCAD most likely, will replace it ASAP), and that I was about to land beside the runway, everything during the flight went absolutely perfect and fabulous -despite some CAT over the Atlantic Ocean.No overspeed, trustfull LNAV, VNAV, everyhting.The fuel prediction (I read at top of climp on PROG1 fuel over destination 16.4T at 19.20Z, and arrived with 15.t at 19.33Z: not too abd for a 6 and half hours flight I'd say)Now, why am I boring you with all this here?.......I didnt get the FUEL DISAGREE message.Upon shut down, the CALCULATED only displayed ./.. No error.Which makes me think that the problem is very inconsistent after all.It happens all the time on very short flights, and on longer flights it doesnt. Wanted to report that.Regards,

Hi Martiro,Seems like you missed this thread about the first subject:http://forums.avsim.net/dcboard.php?az=sho...id=94520&page=1Hope this helps.

* cough *Sorry to bring this back again (!)I completed two short flights again today, and while looking at the FUEL DISAGREE situation carefully, it somehow became clear to methat it must be link with the new/fixed RESERVES feature that is included in 1.10.Basically, it seemed to me that the fuel difference between TOTALIZER and CALCULATED was very closely linked to the amount of RESERVE fuel input in the PERF page. Something is happening when landed as if the FMC retrieved the RESERVE amount set in the PERF page to the TOTALIZER amount, thus creating a DISAGREE on PROG 2.I also encountered a display error I had up to now never witnessed:the TOTALIZER data on PROG2 was simply not displaying at all., and there was no way to get it back untill the return flight I made afterward.

I have encountered some LNAV problems already too, that was before the SU1 released DEC01 (patched patch).The plane in some occsions would turn the opposite direction when reaching some waypoints. In the meanwhile, during some flights, everything was ok as for LNAV.But now, even with the updated SU1, I still get errors from time to.The problem occured this morning once more:http://aiarnaud.free.fr/pics/path.jpgStranger than before: before reaching the headed waypoint, the plane correctly turned toward the next, but afterward it began to turn again the opposite direction, and finally lost the track.In order to join the tracked route again, I proceeded a DIR TO the same waypoint, and again it couldnt stay on track.So I think there is some eratic issue with LNAV here, and that untill we know something from dev team about that subject, it's usefull to always keep an eye on the APBest,

Alex, :-) Thank you so much...Actually, you know what? Been doing a short flight again this morningto check the LNAV mode: I had errors with LNAV modes, but upon landing I didnt get the FUEL DISAGREE: the CALCULATED displayed only the ./. symbol as I assume it should.Anyway, again thank you Alex.Regards,

Hi Alex,I'm sorry but I dont quite understand your last post: are you meaning that this had been found to be a bug, or does that affect only few of us? I've been reading the whole CTD thread (serious one) so I just wanted to make sure we are not only few fellows to have this problem.Regards,

All right Alex,But please note that the fuel calcultation is also wrong wihtout any route in the FMC.Regards,

Guys,I have been doing few test flights again, trying to define more precisely when the problem happens.This time, tested at Miami Intl, KMIA.First case, with a valid route input int the FMC. After landing, same result:http://aiarnaud.free.fr/pics/fuel5.jpgNow second test, withtout any route input in the FMC, same runway same MIA airport:http://aiarnaud.free.fr/pics/fuel6.jpgbasically, the fuel amount difference between TOTALIZER and CALCULATEDpopps up when disconnecting AP prior to runway exit.Hope to see some other results here.

Alex-Thanks,I am afraid you dont need to do the exact same flight I did. Just take off from your own usual airport, only a take-off/landing with a small valid route in the FMC and see what happens. I will do more short flights today myself to see what happens.

Alex......:-( For some reason, this was bugging me, so I decided to do a quick test on my own - not starting from a cold and dark cockpit alas.Took off normally from LFPG, just climbed 6000 feets and went back landing at LFPG straight away with a small route input in the FMC.everything goes fine untill touch down actually.Then, once I cleared the runway I stopped on the taxiway and I checked the PROG 2 page:http://aiarnaud.free.fr/pics/fuel1.jpgThe calculated fuel displays a big gap with the TOTALIZED, first shot.Then, when resetting the ROUTE page (deleting origin airport), I get this FMC message:http://aiarnaud.free.fr/pics/fuel2.jpgGoing back to PROG2, I read the difference, and the most weird is when pressing the USE prompt, it erase all CALCULATED data...http://aiarnaud.free.fr/pics/fuel3.jpgYou can see between the time of touchdown and the moment I stopped on the taxiway, the CALCULATED fuel even went lower, as if the FUEL was still being computed.http://aiarnaud.free.fr/pics/fuel4.jpgI do not want to say anything, I am just waiting for some others to do the test and see what they get.Again, I did not use any cold and dark start situation, and I never use any saved flights. Also, I did not make any change to the route in the FMC when airborne.I installed SU1 (DEC01) on a clean released version.

Rudeiger,I also once encountered after SU1 the PROG2 FUEL DISAGREE message, and about 10 000 lbs difference between CALCULATED and TOTALIZED, without any reason.Even more strange, after pushing the 'PREV PAGE' to display PROG 1 the TOTALIZED fuel amount compeltely disappeared from display on PROG 2. So your question hits me, but it happened only once and at the end of a flight during which I had made LOTS of change on the route...I havent had the time to check the manual yet about that FUEL DISAGREE message.So I dont know if there's an issue or not.

No, the latest version is dated december 1st.

I've made a flight fro O'hare to LAX last night, using the built-in PMDG route: as an quite happy end, everything went just perfect, including VNAV and LNAV modes.http://aiarnaud.free.fr/pics/ual.jpgOn a side note (obsessive compulsive) I noticed that the APU, which is supposed with SU1 to burn 600kg/h if I remember well, actually does NOT. Seems like it runs without burning any fuel anymore. Any idea?It did burn fuel before SU1, now it doesnt anymore. Watched it for about one hour.

That was fast :-) Robert, thank you. Yes, I am obsessive compulsive, no doubt!However, I think the ADF needles are not minor details because although the 744 is able to perform all kind of approaches notably RNAV approaches, it is fun sometime to perform 2 NDB approaches (like in Russia or Africa)...And without those needles, well, pretty dangerous.Regards,

Hi Vangelis, Thank you. I understand very well your explanantion, that is why I said in my very first post:"I first thought that it was because of the 180 degrees angle, unfortunately, at the next waypoint which is a less than 20 degrees turn the plane went again the other way round."I wasnt alarmed about the first 180 turn, but by the second, which was as I said less than 20 degrees angle. Maybe Jack can tell us a bit more about it as he seems to experience this too. Jack?Anyway, as Robin states, it is quite unusual to proceed such turns in a normal flightplan. Robin, that was just some test flights I was doing :-) About your PS, Vangelis, yes, I could actually NOT miss the high speed buffet, because I think I was the one who brought this to the attention when the 744 was released and so I actually was eagerly waiting for itHere's the thread in the temporary forum:http://pmdg.forumsplace.com/message-2092.htmlAs you say, it's really a pity FS cant really reproduce that though.Again thank you for your replies,Regards,

I noticed that as well. I suppose it's for the upcoming Cargo Dispatch center. Fully functionnig ACARS? At least is it what I thought of when I saw it.But I might be wrong of course.

Oh...Lefteris, now that is a very good new ! Thanks a lot.Do you think the LNAV problem could be linked to it somehow?I'll keep on investigating and report back if needed.Regards,

Thank you Mats, :-) Yes, I will eventually try to do that indeed. But from the latest esasy test I have just made, I dont think that will help: I've had the idea to load the 737NG, just in order to check the ADFs: theyare fully and correctly functionning with the NGs. Same for default planes. Thus, I doubt its an FSUIPC related issue.Only the 744 seems messed. Also, its not the only glitch I found:the whole VNAV mode seems to be screwed as well. FLCH modes, SPD, VNAV etc behave in a very impredictable way and most of the time the green SPD, THR on the PFD are no more displaying anylonger.