Jump to content

JetNoise

Member
  • Posts

    105
  • Joined

  • Last visited

Posts posted by JetNoise

  1. On 1/21/2024 at 12:05 AM, Nico - Gumby said:

    The OFP comes directly from Simbrief, we can't change it.

    Hmm, maybe there is a misunderstanding. See attached image.

    First time i am seeing it that misaligned.
    Are you guys using a specific font to display the import from simbrief?

    Maybe thats causing the issue of the misaligned presentation.

    A character-set with fixed letter size and spacing would fix it then ...  , idk, just a guess...

    FlightSimulator_kLEd4sWrix.thumb.jpg.d60c6de351aab051a868d2ff83c52405.jpg

  2. This is indeed a very strange bug for you guys.
    Nevertheless, it cannot be stressed enough, that you all check your Hardware controllers for ANY key binds that may conflict. 
    Important ! Some binds are set AUTOMATICALLY for your attached hardware inside MSFS. HC Alpha and Bravos especially.

    Since i am using SPAD.Next, I've cleared out ANY of them and kept only the Nosewheel steering assignment, since that is common for most of my aircraft.

    NEXT: Whenever i update an aircraft or 3rd party tool, i am also clearing the "m-files" which are compiled by some of them.

    They will be (automatically) recompiled on the next load of the addon. No harm is done by deleting these files.!

    You can find them here for the respective addon:

    C:\Users\YOURUSERNAME\AppData\Local\Packages\Microsoft.FlightSimulator_8wekyb3d8bbwe\LocalState\packages 

    DO NOT TOUCH the "work" folder, unless you want to loose your settings for that addon and start setting up from scratch.

    Important !: Once you have loaded into the addon, bail out of MSFS again and reload for your flight - DONE.

    It has become a habit and so far i have not had any issues. Especially now with the ini A300.

    Next thing i noticed: If you leave MSFS via //42 FLOW Pro - EXIT, the A300 (only one i noticed that) 
    may CTD.

    If MSFS is exited the normal way via its Menus - no CTD. 

     

    Maybe this helps ...

    Oliver

  3. 6 hours ago, vaudes said:

    Since V103 I made 2 flights. One was normal.

    On the second one I get an Cabin Altitude Warning passing 10000ft. 2 flights configured the same on pressurisation panel.
     

    Ignition Selector off ?

    • iniBuilds 1
  4. Hi,

    i am pretty happy about some new features and bug fixes in this version.

    For a future release, can you please have the OFP being displayed in a more formatted way. Its really hard to read, the way it is now ...

    Thank you, keep it up

     

    Three greens

    Oliver

  5. On 1/7/2024 at 11:19 AM, Timma said:

    Actually worse after the update, performance is crap on this AC ,first and last time i purchase anything from INIbuilds 😞

    Completely wrong, it runs perfectly fine on a WIN11 8600k, 2080ti, 770GB in Community. No stutters, (almost) no lags ...

    Its just a well maintained install ...

     

  6. 14 hours ago, Crabby said:

    60+ hours in the plane, flights over 4 hours.  No CTDs.  My experience, and that of many others leads to this being some kind of local issue.  A CTD can occur WHILE using a certain addon or BECAUSE of a certain addon.  Step one to trouble shoot is forget what happens or not with other addons.   Empty your community folder of all but the aircraft with default house livery and rebuild your exe.xml as noted above.  See what happens. 

    The easiest way is to rename your "Community" folder. Create a new one (MSFS is even creating that for you on start..)  and COPY the stuff over you want to test.
    Once finished RENAME the folders back.  
    You can LEAVE the folder, created for testing where it is. (PROVIDED it is not called "Community" anymore.

    NO deleting or moving of stuff required !! Pls spread the word ...

    Oliver

  7. 23 minutes ago, Letterman said:

    She fell out of the sky for me as well, unfortunatley I wasn't at the desk until after impact while it was cartwheeling across the ocean surface.   

    [AIRHONGKONG, FREIGHTER, V1.02]

    Route: WSSS VMR M771 DULOP Q1 CARSO V551 SUKNER V542 BETTY VHHH 
    W&B: 151.2t TOW / 126.7 ZFW / 26.1t Fuel / TOMAC% 29.5 / ZFWMAC% 26.2
    Last known position: DAMVO, 1:36 into flight, Cruise FL320 ~M0.80, TRK 034, Good Weather (wind ~070/10), Fuel 14.7t onboard, ~1:40 ETE.

    Observations from the cockpit after event (paused the sim during aforementioned cartwheeling):
    - AP was OFF
    - AP Modes were engaged as I had left them (AT/NAV/ALT)
    - Recall was normal
    - Engines were running, values were nominal. 
    - Overhead switches all good. 
    - ENG 1 analogue gauges had some weird graphic overwritten on the digital readout.
    - Fuel distribution was strange maybe? (Not A300 savvy). All of the inboard fuel had found its way to the CTR/TT like 6t of it.  CTR and Trim tank pumps were on (normal??).
    - Outboard fuel untouched (normal I suspect) at ~3.7t per side. 

    Addons installed and running
    -SIMLINK (for navigraph charts position and telemetry)
    -FSLTL injector (up to date)

    Previously, I similar length flight was conducted in the same jet under V1.01 VHHH to RJBB, uneventful.
    Don't usually have issues with addons and modules. 

    Is something causing the AP to disengage? 
    Is the jet running into invisible terrain knocking it off course? (crash detection off for VATSIM purposes, all other realism maxed out). 

    Yours truely 

    Add, i have the MSFS Aircraft Stress Damage OFF, i had a weather change knock out a different ac a while ago ...
    Maybe it was even the A310 ...

    Oliver

  8. If that helps for the time being ...
    It should work without going through that hassle, tho.

    Same as "Crabby" reported here: Haven't had a single CTD with the A300 since release.
    Community folder has a 766 GB of content now, carefully tested and using only a few Mods.

    WIN11 debloated, latest NVIDIA drv, DX12, DLSS swapped to the latest dll, TAA, NVidia 2080Ti, Intel i7-8700K , 5Ghz pretested.
    Running with a locked 30FPS ...

  9. 12 minutes ago, johnathon76 said:

    Good for you but other people are still getting this falling from the sky. so its no fixed

    You didn't get the point ;-)

    In general, the airplane is not falling out of the sky.
    Now the goal is to find out why it is doing this for others.

    Without good testing and writing good reports, it will be hard to replicate for the Devs.

    Did you report something in that regard somewhere ?
    Did you test with an emptied Community folder ?  (with the A300 installed oc )

    (RENAME !! the existing one, create a new one, COPY the A300 over and START the Sim.)  RENAME the community folders back afterwards. )

    Blue skies,

    Oliver

    • Sad 1
  10. 10 hours ago, Trevor said:

    Hi Mark

    I see your hardware is very similar to mine - 9700K and a RTX 3070. Would you be willing to share your msfs graphics settings and NCP settings. Curious to see how they compare. I would like to push some settings higher.

    Cheers

    Trevor

    I used these as a starter
    https://www.flightsimulator.blog/2023/12/04/best-graphics-settings-guide/

    It gets updated regulary, too

    Don't miss the link to "PERFORMANCE BOOST TRICKS" at the end of that page ...

    Key (for me at least) is, don't get triggered by FPS hunting. 
    SIM is not a shooter game.
    I go mine locked to 30FPS, no lags, no stutters, no greaf ;-)

    Oliver

  11. On 1/6/2024 at 11:04 AM, JetNoise said:

    Have not seen that behaviour. 1st flight with the updated version. Winds 4kts cross. No curves set at all. TRP rudders in use. Nosewheel on extra axis ...

    Oliver

    Quoting myself:
    And to be correct: It has become more sensitive with the latest update, maybe too sensitive.....
    With good rudder controls (Thrustmaster TPR Pedals) it is handable ....
    These airplanes in MSFS seem to have no mass. Most of them behave like light GA aircrafts.

    I'd really like to see that being fixed !!!

    Oliver

     

  12. 58 minutes ago, p919h_lm said:

    Can confirm this behavior. This happened to me in LFBD while landing to rw 05 and chose to use rnav approach. - - The plane descended using vs mode to platform altitude but remained in alt* mode and never went to alt mode.

    - MDA was set in the to/appr page

    - The final x.xx was confirmed in to/appr page. VDEV appeared in that page and the it was below glide path according to it.

    - NAV mode was the selected lateral mode.

    - The plane was not past the FAF.

    - Despite meeting these conditions, while pressing the profile button in fcu, nothing will happen, i.e not getting the blue P.Des and P.spd armed in FMA.

    - if i don't do anything, the plane just flies level, I had to select altitude selector knob to mda and use vs to descend, i.e old school rnav approach.

    Fishing in the dark, but
    I noticed that ALT*  (STAR) never changes to ALT, only if you press ALT (HOLD).  Maybe that info gets lost in the code for LNAV/VNAV since the update ...

     

  13. 53 minutes ago, p919h_lm said:

    There was a tutorial from iniBuilds the dh was enabled and set to -5 during preflight preparation. I think the reason for this was something similar to what you heard. You may take a look at the a310 tutorial videos that iniBuilds did for MSFS.

    or the fantastic YTs for the A300-600 for X-Plane ...

    Oliver

  14. Couldn't get RNAV to work, which worked before. P.DES blue etc missing now ...

    Tried at EDDL and LFSB runways ....


    Despite that on climbs and descents FMA remains on ALT*

     

    • Like 2
  15. idk, but in real life, you would use the tiller to steer the aircraft on the ground. Once on take-off roll, rudder takes over at higher speeds, bc of increasing rudder authority.

    So u need to shift from tiller steering to rudder steering dynamicly....   

×
×
  • Create New...