Jump to content

artox67

Member
 View Profile  See their activity

  • Posts

    64

  • Joined

  • Last visited

 Content Type 

Posts posted by artox67

    CTD on loading flight

    in Systems

    Posted

    10 hours ago, Crabby said:

    How many times?  First load (after install or update)?  Ideas require more info.  For example, with the exception of the last update, I had a CTD on first load (including all prior updates).  However, it would never happen again until another update.  V1.08 was the first time I did not CTD on first load.  Not saying this is normal, as it is not, but that has been my experience. 

    Yes, that's what happens. Always after an update, the first load is a CTD.

    Afterward, everything is ok.

    • Like 1

    CTD on loading flight

    in Systems

    Posted

    Faulting application name: FlightSimulator.exe, version: 1.36.2.0, time stamp: 0x00000000
    Faulting module name: mf3055c24e74fe5af_0.dll, version: 0.0.0.0, time stamp: 0x65d8800d
    Exception code: 0xc0000005
    Fault offset: 0x0000000000e16484
    Faulting process id: 0x0x17E0
    Faulting application start time: 0x0x1DA6649BA71AC72
    Faulting application path: C:\Program Files\WindowsApps\Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe\FlightSimulator.exe
    Faulting module path: C:\Users\XXXX\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages\inibuilds-aircraft-a300-600\mf3055c24e74fe5af_0.dll
    Report Id: 1ade0561-d429-4168-9717-9b7a4f8b4554
    Faulting package full name: Microsoft.FlightSimulator_1.36.2.0_x64__8wekyb3d8bbwe
    Faulting package-relative application ID: App

     

    Any ideas?

    1.06 LNAV issue

    in Systems

    Posted

    2 hours ago, vaudes said:

    Hello, all

    On last update, acft doesn't follow LNAV, am I the only one?

    You purchased from the marketplace? If yes you are on the old version. Maybe 1.04

    Updates at the marketplace always a way behind the store version cause Microsoft needs longer 

    A300-600 Performance

    in Systems

    Posted

    I can't confirm this issue. For me, the A300 is running like a charm.

    Most settings on Ultra with DX12 and FG on. Using RTX4080 and Intel I9 13700

    Flown a lot of flights 3h+ and no FPS drop or CTD.

    Starting, landing at EHAM, EDDF, EGLL or ESSA causes no studders.

    Maybe worth a test to fly only the A300 and the two airports you want to see if the culprit, another addon.

    Will say there are only a few pilots with the issue and not thousands of them. 

    Radio not working with vpilot

    in Systems

    Posted

    On 1/14/2024 at 3:02 PM, johe_ini_2312 said:

    Hello,

    since 1.01 I have the problem that the radios are shown powered on but when I dial a VATSIM vpilot frequency like tower or radar for example there is no transmission at all...

    Keep in mind the A300 radio works different. You'll have the active freq where the radio switch is showing in direction to.

    • Like 1

    Turn off Beacon turns off yaw dumper and pitch trim

    in Systems

    Posted

    36 minutes ago, Crabby said:

    Can't replicate.  Check all of your bindings, especially if using the in-sim profiles.  I use AAO, so I would not see that issue.  

    I’ve absolutely no key bindings. I clicked the beacon switch with the mouse and the four switches above turned off as well

    ETA for ToD still wrong

    in Systems

    Posted

    31 minutes ago, Marcocessna84 said:

    Simple fix for that is to calculate the TOD: 

    ( Current FL - Airport Elevation that you x by 3  ( 33000 ft - 364 ft = 32636 ft x 3 = 97.8 NM before Airport you would start your decent). 

    To calculate a good rate of decent would be to take your speed and ÷ by half and x by 10  ( 280 ÷2 =140 x10 = 1400 ft decent rate. ) 

     

    This is a temp solution until the team can fix it. Cheers mate. Math is part of flying. 

     

     

    Thx for the hint but I'm aware of the formula.

    The issue is the ToD is shown correctly on the ND, but only the ETA in the MCDU is wrong.

    Cheers

    ETA for ToD still wrong

    in Systems

    Posted

    The ETA for ToD is still wrong.

    It is the same time as the next WP, doesn't matter how far away this WP is.

    e.g. EDDM ESSA ToD was 80NM before NILUG but shows the same ETA 11:24 UTC

    Cheers

    T/D point

    in Systems

    Posted

    Unfortunately yes.

    The ETA doesn't match the time to reach the ToD. Currently the ToD is calculated without the STAR. After entering the STAR the ToD should be recalculated but it doesn't.

    I assume this should be fixed.

    Cheers

    • Thanks 1

    ILS Autoland vears off right before landing.

    in Systems

    Posted

    On 12/29/2023 at 11:31 PM, Nico - Gumby said:

    Would be good to know if this also happens with non iniBuilds aircraft. Depending on that I either move it to airplane or scenery team haha

    Same here today at LPPT.

    Autoland and the AC turns right from the RW. Without autoland evrything is ok.

    Cheers

×
×
  • Create New...