Jump to content


  • Posts

  • Joined

  • Last visited

About M20RUM

Recent Profile Visitors

582 profile views

M20RUM's Achievements


Newbie (1/14)

  • First Post Rare
  • Collaborator Rare
  • Conversation Starter Rare
  • Week One Done
  • One Month Later

Recent Badges



  1. If I recall, 5.5/6 hours is achievable with max fuel load and low pax, some other members may be able to suggest some adjustments that could be made to get the A/C to reach the same sort of range the NEO LR versions might do. Do remember though the pro narrow body buses are not based on NEO's but CEO's.....
  2. Hi all, After a fortnight of an absolute nightmare with the bus and the jumping, FPS drop and frankly it being unflyable and frustrating (loss of control, pitching up down, left right, overspeeding etc). Never had this issue and I've been flying the bus since 2012... I've pretty much read every forum post about this and set about my own investigations, my system isn't at fault, its getting on for 5 years old now but still on spec. I'm happy to report I've fixed it and want to report where I found a problem. Simply, where are you running your bus from? I personally have my P3D on an external USB SSD drive....as we all know since moving from FSX to P3D the size of the install has increased several fold especially when using lots of addons. This appears to be the issue. As P3D made access to the drive for things and the bus did too the drive hit processing capacity, a micro stutter occurred, FPS dropped and the bus went mental. I've now installed the bus on an internal drive, separate to the P3D install and that seems have really smoothed things out. In addition I also deactivated trueglass (involves deactivating the gauge) and as I'm not an EFB user I've also deactivated the webserver module to keep that blacked out. But my better mileage really did come from the bus accessing a different drive to P3D. In addition I did also delete and let P3D rebuild my shaders folder. I wanted to post this as to date the developers haven't asked or mentioned a drive access/bottleneck as possible issue or resolution and thought it might be worthwhile letting anyone else scratching their head that this may just work for you! Drive access could be causing the micro stutters! I'm now flying at 30-40fps (externally) locked, with AI traffic models, ORBX, ASP3D and more add on scenery you can shake a wing at! The bus is back! Matt PS for all the other issues that people get when selecting a panel state with regards to auto pilot issues/ not following NAV, needing to input a DIR before following the plan. After loading up, load cold and dark. Wait, put kettle on, then go for desired state (mine normally being "turn around state").
  3. Its been asked before, the four Air Transat A330's would be great. Matt
  4. For those of you not running the Aerosoft professional A321 please add the following to your aircraft.cfg: [FLTSIM.XX] title = Aerosoft A321 WizzAir HA-LTD sim = A321 model = SHARKLET panel = sound = texture = WizzAirLTD kb_checklists = kb_reference = atc_id = HA-LTD atc_airline = WizzAir atc_flight_number = ui_manufacturer = Airbus ui_type = A321-231 IAE ui_variation = WizzAir ui_typerole = Commercial Airliner ui_createdby = Aerosoft atc_parking_types = GATE atc_parking_codes = WZZ description = Aerosoft A321 IAE / WizzAir HA-LTD I also edited the aircraft.cfg as all the fallbacks related to the airbus x extended to: [fltsim] fallback.1=..\..\Aerosoft Airbus A320_A321 Base\Texture_Fallback_VC //fallback.2=..\..\Aerosoft Airbus A320_A321 Base\Texture_FallBack_A320 fallback.2=..\..\Aerosoft Airbus A320_A321 Base\Texture_FallBack_A321 fallback.3=..\..\..\..\Scenery\Global\texture fallback.4=..\..\..\..\..\..\Scenery\Global\texture Hope this helps. Matt
  • Create New...