!! Windows 7 no longer supported !!

As Microsoft will stop supporting Windows 7 on Jan 20th we will be unable to test any of our
products on that platform. It may work, or it may not, but no guarantees from our side. 

Jump to content

alfatango

members
  • Content Count

    18
  • Joined

  • Last visited

Community Reputation

1 Neutral

About alfatango

  • Rank
    Flight Student - Groundwork

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Good morning, actually, to add up on what the OP has written, I have also noticed that the pitch trim has become much less responsive with version 1.0.0.6 (both parking brake and choks off). Up to 1.0.0.5, a full turn (360deg) of the mousewheel would change the pitch trim by something like 0.3 deg, which was nice. Now it is almost impossible to change the trim with the mousewheel - it would take tens of turns - and I have mostly to change it using the mouse pushbutton (1 click = 0.1 deg change in the THS). No change has been made the controls sensitivity - including the mouse - between the updates. alfatango
  2. Good afternoon to all. I am having the same problem/question mark as magna91. I have just updated the Airbus Professional 318/19/20/21 to 1.3.0.0 (full reinstall). A330 is at 1.0.0.4 (waiting for the dust to set before making the update to the next stable version). A3XX fuel planner correctly accepts selection of the various models and correctly calculates fuel, however takeoff trim setting is always in the "down" range. In the past, i.e. before installing the A330, TO trim settings were in a more reasonable "up" range. I have just tried a flight from LEMD with a A320; T/O weight 67,100 kg, fuelplanner gave a TOW % MAC = 36.6%, ZFW % MAC 30.3 and 1.8 DOWN trim setting. The slider allows adjusting the TOW CG only between 34.3% and 37.3% Using the same input data on another W&B online calculator for the A320, I obtain a TO CG of 28.4% and a takeoff trim setting of 0.0 (UP). Using the fuelplanner that DAVE provided in this thread suggesting to swap one for the other when using the widebody or the narrowbodies, I obtain slightly different results, TO COG calculated as 35.3% and TO trim at 1.5 DOWN, but still largely negative. alfatango
  3. OK, Dave, thanks for your feedback, and yes, your understanding is correct. Happy update (your message crossed with mine): 1 - loading a default plane first did not solve the issue, and I do not think it can be assumed it is due to other add-ons, but 2 - As I have read several times that kernelbase.dll errors are often linked to .net framework issues, I have run the MS .net framework repair tool. Strangely enough, the tool reported no errors, but it did send a message like "restarting the .net framework". after which Airbus Professional (all models, narrowbodies and A330) are working ok. Maybe sometimes, on exiting P3D, something is messed up with .Net Framework? It could be something else, but I am having this problem - admittedly, rather random, maybe once in twenty cases - only after a fresh P3D launch after PC boot, only when selecting an Airbus Professional and only when I had flown an Airbus Professional as a last flight before shutting down P3D and the PC. I will keep monitoring and report if I improve or disprove the statistic. Alfatango
  4. Good evening. I have completed several successful flights with the A330. Then, after completing one flight, I exited P3D and shut down the PC. After a few hours, I switched on again PC and fired up P3D; now, P3D crashes to desktop any time I select an Airbus Professional (318/19/20/21 or the A330). All other add-ons work OK. I had in the past a similar problem with the A318/19/20/21 but then the solution was NOT to change the simulator time in the welcome windows, letting the plane load with the system time and then changing the time. Now, this does not help and P3D crashes upon selecting the plane and giving the "OK" in the welcome screen after few seconds of black screen (the scenery loading bar never appears). I have tried to start from a default plane/airport and then selecting the A330 (or A320 for that), with no change: screen goes black and then after a few seconds CTD. I had A330 ver. 1.0.0.2 installed; I have installed ver 1.0.0.3, which automatically installed Visual C++ runtime, but the situation remains unfortunately unchanged. What is baffling me, is that now also the A318/19/20/21 stopped working, and that no change had been done to the PC (it was switched off!) between the last successful flight and this. AppCrashView reports "a string binding is invalid" in module: kernelbase.dll Needless to say, I would appreciate some suggestion, to be able to fly again the entire Aerosoft Airbus Professional range. Alfatango Appcrash report: Version=1 EventType=APPCRASH EventTime=132209052799790963 ReportType=2 Consent=1 UploadTime=132209052804478428 ReportStatus=268566528 ReportIdentifier=48fe5598-a923-44e8-b130-52e709761bc3 IntegratorReportIdentifier=7b489968-3eeb-4164-938a-87ebe200e217 Wow64Host=34404 NsAppName=Prepar3D.exe OriginalFilename=Prepar3D.exe AppSessionGuid=00003414-0001-0021-4512-7ca06eb3d501 TargetAppId=W:00000f3fb95a9975fc51260b15dcb7eb0e2400000904!0000c739329fda381e3735d40dca7542b7bc8256c368!Prepar3D.exe TargetAppVer=2019//09//25:01:14:59!2cf4ea!Prepar3D.exe BootId=4294967295 ServiceSplit=1915613601 TargetAsId=437 UserImpactVector=858796336 IsFatal=1 EtwNonCollectReason=1 Response.BucketId=9f5526e4032bb3652f67f9fa6199eef4 Response.BucketTable=4 Response.LegacyBucketId=2263052191551581940 Response.type=4 Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=4.5.13.32097 Sig[2].Name=Application Timestamp Sig[2].Value=5d8abf93 Sig[3].Name=Fault Module Name Sig[3].Value=KERNELBASE.dll Sig[4].Name=Fault Module Version Sig[4].Value=10.0.18362.535 Sig[5].Name=Fault Module Timestamp Sig[5].Value=50cc8d5a Sig[6].Name=Exception Code Sig[6].Value=c0020001 Sig[7].Name=Exception Offset Sig[7].Value=000000000003a839
  5. Good afternoon to all. I have just purchased the A330 and I am overall quite impressed by the plane: smooth, good flying performances althought I also note a certain sensitiveness in the longitudinal (pitch/elevator) axis (but not a RL A330 driver, so might be just a wrong feeling). My question is related to the pre-set VC views: they generally appear to be "tilted" some degrees in the SW-NE direction (see picture). They can be manually adjusted (space bar + mouse) for orthogonal viewing angle, which I would prefer, but then they revert to default perspective when re-selected. Is there a way to store the manually adjusted view (perspective) as default? Additionally, as noted in other threads ,the views are designed for the wide-view aspect ratio enabled. Other add-ons do not require this setting (actually, they work better without it). Would it be possible to have two sets of pre-defined views, one to be used with WWAR set and the other with WWAR off? Thanks in advance for any suggestion and congratulations for producing such an excellent add-on. Alfatango
  6. Dear Fernando, not sure if it is the same problem I had a couple of weeks ago. The symptoms are: - CTD at selection of the Airbus - Appcrashview reporting "string binding is invalid" in kernelbase.dll If this can help, for me, the problem was linked to selecting a simulator time different from the system time in the initial P3D screen (the one with selcetion of the vehicle, selection of the airport and, in the bottom right corner, selection of the time of the day) Workaround was selecting the 'bus leaving the time of the day unchanged in the first screen, loading the plane and then changing the time of the day. Notably, I have this problem only with P3D4.5HF2, latest Windows update and the Aerosoft Airbus - Mathijs reported having the same problem with a PMDG addon, but I do not own any of them, so I cannot comment on this. Alfatango Edit: Sorry, I just realised that you mention crashing 20 minutes into the mission not at selection, so your case is different from mine.
  7. Thank you Mathijs for your support. I am now able to consistently reproduce the issue: The Aerosoft Airbus Professional, and only this add-on, crashes on selection, if and only if I change the simulator time of the day in the welcome screen. Leaving the time of day unchanged (=system time) when selecting the Airbus and then changing it after loading the plane works fine. This is the workaround I am using now. In case the developers/programmers are interested in looking into this, the extended appcrashview report includes: Sig[0].Name=Application Name Sig[0].Value=Prepar3D.exe Sig[1].Name=Application Version Sig[1].Value=4.5.13.32097 Sig[2].Name=Application Timestamp Sig[2].Value=5d8abf93 Sig[3].Name=Fault Module Name Sig[3].Value=KERNELBASE.dll Sig[4].Name=Fault Module Version Sig[4].Value=10.0.18362.418 Sig[5].Name=Fault Module Timestamp Sig[5].Value=fba22159 Sig[6].Name=Exception Code Sig[6].Value=c0020001 (My note: this is labelled as "the string binding is invalid") Sig[7].Name=Exception Offset Sig[7].Value=000000000003a839 DynamicSig[1].Name=OS Version DynamicSig[1].Value=10.0.18362.2.0.0.768.101 alfatango
  8. NOW I am totally confused, as it seems that the behaviour is not consistent. Out of maybe 15 attempts, I had: 2 successful selection of the Airbus by loading an add-on plane first and then selecting Vehicle -> Airbus Professional (once the 320, once the 319) 1 successful selection of the Airbus (320) directly from the welcome screen, no successful attempt when loading first a default plane and then selecting the Airbus (but this might be just a statistic) 10+ CTDs, even when repeating the same procedure that was successful in the previous attempt. FWIW, and in case it gives a hint to the programmers, on at least one of the successful attempts (actually, the only case when I looked at it), while running the checklist I noticed that the elevator would not move on the MFD display/FTL CTL page but did move in the exterior view and did normally pitch the plane during flight. Thick mystery.... I confirm that at least 7 or 8 other add on planes work as ususal. alfatango
  9. Many thanks to you, Dave. Yes, I try also to load a default plane before selecting the Airbus Professional, but the result is the same. If I load the Airbus first, I never get to the scenery loading progress bar screen - the sim crashes after a few seconds of black screen. If I load a default aircraft, everything is fine, then, when I go to "change vehicle", select the Airbus, the screen goeas black for a few seconds and then CTD. The Event Viewer error log is as follows: Log Name: Application Source: Application Error Date: 09/11/2019 08:11:27 Event ID: 1000 Task Category: (100) Level: Error Keywords: Classic User: N/A Computer: LAPTOP-SAOMJFOR Description: Faulting application name: Prepar3D.exe, version: 4.5.13.32097, time stamp: 0x5d8abf93 Faulting module name: KERNELBASE.dll, version: 10.0.18362.418, time stamp: 0xfba22159 Exception code: 0xc0020001 Fault offset: 0x000000000003a839 Faulting process ID: 0x1a70 Faulting application start time: 0x01d596cc88974003 Faulting application path: C:\FltSim\Lockheed Martin\Prepar3D v4\Prepar3D.exe Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll Report ID: 9a89e69e-5a4d-4c8b-a045-78f881d5228a Faulting package full name: Faulting package-relative application ID: Event Xml: <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event"> <System> <Provider Name="Application Error" /> <EventID Qualifiers="0">1000</EventID> <Level>2</Level> <Task>100</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2019-11-09T07:11:27.553122200Z" /> <EventRecordID>3115</EventRecordID> <Channel>Application</Channel> <Computer>LAPTOP-SAOMJFOR</Computer> <Security /> </System> <EventData> <Data>Prepar3D.exe</Data> <Data>4.5.13.32097</Data> <Data>5d8abf93</Data> <Data>KERNELBASE.dll</Data> <Data>10.0.18362.418</Data> <Data>fba22159</Data> <Data>c0020001</Data> <Data>000000000003a839</Data> <Data>1a70</Data> <Data>01d596cc88974003</Data> <Data>C:\FltSim\Lockheed Martin\Prepar3D v4\Prepar3D.exe</Data> <Data>C:\WINDOWS\System32\KERNELBASE.dll</Data> <Data>9a89e69e-5a4d-4c8b-a045-78f881d5228a</Data> <Data> </Data> <Data> </Data> </EventData> </Event> What baffles me, is that I have never had problems with the Airbus before, I was able to load it directly from the welcome screen, and then from one day to the next the behaviour changed. On retrospective, I realised that the last thing I had done before switching off P3D on the last successful session was installing and activating a scenery, so - even if I do not understand how a scenery could cause this CTD - I deactivated it, but without effect, still CTD. All other airplans add-ons, including pretty complex ones and even Aerosoft's own CRJ 700/900 work flawlessly as before. Any help will be very much appreciated, as at this stage I wonder whether even a P3D client reinstall would be helpful. alfatango
  10. Three days ago I used the Airbus Professional 319 (v. 1.2.5.0) and everything was OK. After the flight, the computer was shut down and not used till today. Today, I started the PC again, fired P3D (V4.5HF2) and the 'bus would not load, with CTD after selecting the plane (black screen for a few seconds and then CTD). Same happens with all Airbus Professional models (318/9/20/21) I have tried to uninstall the Airbus, re-install it, update with the 1.2.5.2 experimental updates, to no avail: P3D crashes to desktop upon selection of any Airbus professional. All other aircraft add-ons (including Aerosoft's CRJ 700/900) work OK. Is anyone else experimenting the same behaviour? Maybe a hidden Windows update in between? Thanks for any help Alfatango
  11. Yes, the old but good disinstall/reinstall trick did the job.... So it was probably some fonts that got overwritten, maybe during a MS (auto)update. Win10 1803 build 17134.523 Thanks for your help Alfatango
  12. With Airbus Professional v. 1.2.2.1 update I have noted that all ring dials on the ECAM display have disappeared, leaving only the needles and numbers visible (see pictures for both engine and press pages). As I have MS updater on, the problem may have appeared upon last update of the 'bus and remained unnoticed, or upon last Windows 10 update. Are the dials contained in a font? If yes, can the font be re-installed assuming that something went wrong with the font set? Or is there another way to repair the dials? As far as I can see, all other cockpit objects/fonts are OK. Thanks in advance for any help Alfatango
×
×
  • Create New...