spacebaby

Does any one know what file the aircraft tail number info resides?? In most aircraft it is located in the aircraft.cfg file, since Carenado doesn't have that format as far as I can see in their aircraft folder how do you change the tail number for any of the planes? My new paint work.

Captn. Kevin Thanks for the replay as you can see I dont have a / ini file in there

Good one Sierra Hotel ! I preformed maintenance on the brakes and tires and it worked . Am I going to have to do this on every flight, Hope not . Thanks for the help . FYI; If those of you are making a recommendation for FSUIPC explain where this FSUIPC ini. file is ,for those of us that don't know so everyone can benefit.

Only using FSUIPC free for 3rd party integration were necessary , I do not have it assigned to anything on any of my aircraft. Thanks for the suggestion. Wonder why it didnt happen with the Q.O.S. B744

It seems after landing there is some sort of brake issue. The plane will not taxi in spite of the auto brakes being off and there is no over heat warning on the display. This never happened before the B747 8i expansion. I owned the Queen B744release, had no problems at all. I have seen others report it before the new expansion.This is accruing now with the B747-8i Is there a fix ?? Please help......

I am having the same issue as well, however I don't have any over heating warnings displayed . Can it be a bug or is there a realism setting that can be changed?? Makes for frustrating conclusion to a flight when you have 2 other aircraft waiting to enter the runway.......

Ok guys this is what I did as a work around. I first loaded in to one of the default liveries, then I load the Allegaint and seems to work, however I do believe there might be an issue with one of the files I dont think it is a cfg. problem .

Thank you so very much have been waiting for Allegaintt livery since the release. Kind regards to you sir!

Any one interested in Allegaint or newer Alitalia that would be sooooo great please !!

Is there no one willing to make an Allegiant repaint since they are one of the only current operators in the USA with MD-80's . Please consider.Thanks

I wanted to create some additional wing views for the great Maddog MD-80. https://library.avsim.net/download.php?DLID=203542

Dave, I would like to think is was my graphics card ,however it seem others are have this issue and it only happens in the Maddog. If this was a reoccurring problem with other aircraft I would speculate it being a graphics driver glitch. No other aircraft does this. I do have the latest drivers and Sim platform loaded. I can get you the info, sure seems excessive.A complete disclosure of my entire system is that necessary.It seem you are looking every where but at your product. I am a little frustrated at this point sir. Would you like me to become a Beta tester? I would be happy to. I truly believe it is the plethora of 3rd party variables out there that do not exchange all their info and coding ect. When there is not a thorough investigation and developers guess that's when problems arise. I was told yesterday that they have found vpilot model matching for carenado aircraft only has caused them grief and encountering issues with that, why who knows Thanks for responding anyway. I was hoping for a solution

No replay, I sent the info you requested 3 days ago ?? Also This power loss that others are experiencing is happening as well clearing all data in the FMC. I have to go to the pull down and select "ready for take off" while taxing to the runway Geees.

I have the same issue loosing power clearing FMC. Also crash to desk top when expanding my screen from full to minimum

Okay thanks for the link to the app crash. Just so you know I have implemented the new update 2.0 clean install. The plane is much more flyable now which in good., however every time I try to reduce or expand my screen it still crashes my Sim. only in the MD-80. Hope can get to the bottom of this. Here the info you requested. Version=1 EventType=AppHangB1 EventTime=131633293453092642 ReportType=3 Consent=1 UploadTime=131633293559426503 ReportStatus=97 ReportIdentifier=d0f992a2-72e8-4df9-963c-3163f4903a52 IntegratorReportIdentifier=9b6d0d16-1011-4d2e-88ed-aa5b88c8df45 Wow64Host=34404 NsAppName=Prepar3D.exe AppSessionGuid=00001490-0001-0056-2ebd-4ae3c6a7d301 TargetAppId=W:0000f0e3cd7a622a9f58f96eda9e904fcd8500000904!0000fe4ba4844cdbd482c25c2fa58f1644d0a18615dd!Prepar3D.exe TargetAppVer=2018//02//08:17:04:44!2cfb45!Prepar3D.exe BootId=4294967295 TargetAsId=722 UserImpactVector=286265616 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=4.2.21.24048 Sig[2].Name=Application Timestamp Sig[2].Value=5a7c832c Sig[3].Name=Hang Signature Sig[3].Value=0000 Sig[4].Name=Hang Type Sig[4].Value=134217984