Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 08/29/13 in all areas

  1. Hello everyone, I wanted to take the opportunity to first of all extend our hopes and wishes that everyone is feeling well and safe from the COVID-19 pandemic that has befallen the world. Please be careful to follow your government's instructions and advice so that this can become part of stories and folklore we all one day tell our grandchildren. Lockheed Martin's release of Prepar3D v5 is now behind us and I would also want to take a moment to discuss our roadmap regarding updates for the already released product line and a bit of detail on what the future holds regarding our upcoming releases. Prepar3D v4.5 - New HotFix 3 was released (did anybody notice?) First of all - while the spotlight has been on the P3Dv5 release - LM also sent out an update to P3Dv4, the new version being v4.5HF3. This will require that our existing products be updated to support it, so expect a quick compatibility-only update to roll out within the next few days, once our beta testers have taken some time to ensure everything still works as before. This update will strictly be for v4.5 HF3 compatibility reasons and will not add new functionality or features. NOTE: If you update to the latest P3D v4.5 HF3 before this compatibility update is released, we cannot and will not provide support for any problems that might surface, other than to say "please roll back until our compatibility update is out". Prepar3D v5 - What is new? What can work? We are deep in the process of testing our product line with the new platform. As a lot of you are also discovering now, there are a lot of underlying engine code changes in that base platform that are causing us to take time to ensure that we can safely release the products to you. Most of that effort revolves around the change from DX11 to DX12, but also there are some PBR modeling updates that we are looking to take advantage of as well, going into the P3Dv5 world. We are also investigating what the effect of DX12 will be on our testers with older / less powerful graphics cards, as reports are already coming in where users are running out of VRAM causing their sim to either crash unexpectedly or show the DXGI error that means their graphics card couldn't handle something and crashed the sim. We are aware that LM are also actively looking into this matter, so we'll make sure to keep you updated with our findings as well. Product updates and roadmap As I've explained in previous announcements, our development team focus has been on the new exciting Sharklets add-on, however we have also been adding new features and updating our existing product line in parallel with the Sharklets effort. We are looking forward to releasing these to you in the coming weeks - I would like to take the opportunity here to list the most significant of these additions and updates. Note that the order I am presenting the product line below is most likely going to be the order that our products will be rolling out, but this as always is tentative and subject to change at any time. FSLabs A320-X Those of you who have been with us since the FSX days know that we continuously update and improve on already released products for years after they first come out. The A320-X is a true testament to this philosophy, so we are going to be releasing several exciting features and new logic. Among the most notable of the updates and new features that the A320-X platform has received are: Added S8 software updates to the FMGS MDA/DH replaced with BARO/RADIO UPDATE AT deprecated IRS INIT page updated FIX INFO pages updated DMC updates for Profile/VDEV and approach identifiers Flight Guidance NPA logic revised Added CPDLC systems Added DCDU displays Several external model and virtual cockpit improvements All new PBR textures on the external IAE and CFM models That last part (PBR textures) requires that we release an updated paint-kit to go along with the updated model, to support the necessary PBR changes. We expect to also roll out new versions of our FSLabs-supported liveries for the models very shortly after the main product release that will feature those individual liveries in PBR textures. FSLabs A321-X We expect the A321-X product to be released relatively shortly after the A320-X update. It will also receive the updated S8 version of the FMGS logic and benefit from those code changes that the base A320-X platform receives. We're also looking into some PBR enhancements that can be added to the model, mainly for when it loads into the newer P3Dv5 platform. FSLabs A319-X While our testers are busy testing the A321-X update, we will also be updating the A319-X to receive the same amount of love and attention shown to its bigger brethren. This means we'll also be updating the external model to receive PBR textures and add the same FMGS, CPDLC and DCDU updates as in the other two aircraft variants. Expect this to drop sometime after the A321-X, followed closely with an updated paint-kit and PBR textured liveries, in a staggered roll-out release. FSLabs A320-X SL / A321-X SL "Sharklets" We have been paying special attention to our upcoming NEW expansion product, the "Sharklets", as it contains not one, but two aircraft variants, the A320-X SL and the A321-X SL, each having two individual engine variants - CFM and IAE, released together as a single product package, at an attractive price. I've been noticing several posts on social media asking why this is taking as long as it does as it's "just a few model changes on the end of the wings and some painting". Oh how I wish it were so... but it's not. Here's a by-far-not-all-inclusive list of the major differences / updates and new items that are in this product package: Electronic Flight Control System Load Alleviation Function (LAF) Aileron Anti-droop system Flight Model: Each of the four variants operates within a narrow margin of operational data, making this a true simulation of the specific aircraft, giving customers the unique opportunity to discover the intricate details and flying characteristics that until now, only pilots could comment on. FMGS S8 version update (as above) Fuel System: New fuel system supporting center tank jet pumps Updated FQIC and FLSCU logic Updated FWC to latest software standards Updated SDAC to latest software standards New ISIS model New DU LCD colorset for better contrast DDRMI now optional SATCOM Radome now optional iPad-style Electronic Flight Bag now optional Lighting: All lights are now LED Each LED light has accurate warm up / cool down times (exclusive FSL feature through FSLSpotlights technology) Anti-strobe blocker option to prevent cockpit glare Oh, and did I mention the sharklets added to the wings? Fun aside, the external model features many differences - some subtle, some not so much, like the upper wing to body belly fairing which is new... (see if you can spot them in the images below) Will there be a cost involved for the updates to roll into P3Dv5? No. The updates to all our existing products will be free of charge for existing customers, so you can continue to purchase P3Dv4 versions today and not worry that upgrading into P3Dv5 will cost extra. However, please keep in mind that this transition is not easy or simple for our development team, so there might be a period of time required while the details are worked out. Can I take my existing A320-X/A319-X/A321-X and copy the files over into P3Dv5? No. This will not work. If you manually attempt this and break your product by doing so, our support staff will not be able to assist you in recovering it, sorry, you're on your own! ---- One last thing, and as I do with most of my announcements: as a way of saying thank you very much for your continued support, I've added some screenshots the team collected for your viewing pleasure! Stay safe please!
    249 points
  2. Hello everyone, I am happy to announce that our latest update (v5.0.1.126) for the A320-X, A319-X and A321-X for P3D v4 and v5 (64-bit) is now live and available through our download page. This is a maintenance update which fixes several issues identified since our last public release, mostly related with connectivity with GSX and some tweaks to the external lights (positions and light intensities). We also fixed the rain / snow effects showing through the Logo lights. I would also like to take this opportunity to wish everyone happy holidays from all of us at Flight Sim Labs - this past year has been trying for most of us with the Covid-19 pandemic changing our lives so much. We have all been greatly affected and we sincerely hope that you and your families have stayed safe and protected as much as possible. We hope and expect that 2021 will bring significant improvements for the world - the remedies that are now becoming available should return us to a semblance of normalcy and we hope to see you all again soon if and when the flight sim expos return (Cosford and others). On our little corner, we are looking forward to releasing the A320-X and A321-X Sharklets products in early 2021. A tremendous amount of work has been dedicated to putting together very comprehensive releases and we are receiving excellent feedback from our beta team on their progress. You will be getting more detailed views of what's to come soon, as we are coordinating with those of our beta testers who also stream regularly in order to showcase the multitude of new capabilities added to what we feel are the most feature-rich products so far to come from our development efforts. I would be amiss not to also mention the work that has been going into the Concorde-X which will also be released this coming year - there are impressive features added which deserve their own release note, so I will be doing that at some point soon. Once again - we wish you all the best and may the year 2021 bring happiness and joy - and some long-required reuniting with our friends who we have missed dearly! Thank you, as always, for your support!
    169 points
  3. Hello everyone, I am happy to announce that our latest updates (v5.0.1.114) for the A320-X, the A321-X as well as the A319-X now, are live and available through our download page. This is the first update that makes the A319-X compatible with P3D v5, which brings improvements in performance, as well as several updates and fixes to the base code. In this update, we spent significant time to update the external model with PBR texturing for the A319-X, to bring it up to v5 standards, adding several improvements which follow the A320-X and A321-X updates, such as dynamic cabin window blinds logic, newly tuned dynamic lights, effects and splashes, overlays redone using PBR techniques, contrail fixes for P3D v5 and other small cosmetic fixes which add to the immersion. We also added several fixes to the code, such as S8-related FMGC updates to the PERF TO and AC STATUS pages, FADEC improvements for manual start crank logic, updates to P3Dv4 external lighting effects, PFD "STALL STALL" message added, and others. Liveries for the A319-X are also updated, so please feel free to download your favorite airline colors from the relevant download section, as previous livery versions are not compatible with this update (they should be available within the next hour or so). Together with those improvements, we’ve continued to work with FSDT on the integration with their new Ground Power Unit. In order for our aircraft to integrate properly with the new service systems, we needed FSDT to extend GSX further to facilitate our requirements, which is an ongoing process. You can therefore expect to see our titles fully integrated with the electrical system that GSX offers in due course. We are also very happy to now announce that our entire Airbus product line is now fully compatible with the Thrustmaster Airbus hardware line of products. Beginning with this update and upon first detection of a TCA Airbus SideStick or TCA Thrust Quadrant, our software will automatically configure and allow full functionality of all knobs and switches found with the corresponding simulated counter-part, with no action necessary on the part of the user (small exception to this is calibration of the thrust levers, as described in our documentation for any comparable hardware thrust levers out there). AP and AT disconnect, Engine Master Switch On/Off, Ignition Mode Switch, and the upcoming Speed Brake and Flaps axes, Gear Lever, Autobrake, Rudder Trim and Parking Brake knobs are all recognized and compatible with our Airbus line of products directly with no setup necessary. I would be remiss not to mention that development of the Concorde-X is once again well under way and the initial release will be for Prepar3D v4/v5, using latest modeling techniques available in the P3D v5 SDK update. As usual, we don't offer release dates, but we expect to be putting out some more information for you soon. Last but not least, I wanted to touch a bit on our plans for Microsoft Flight Simulator, as well. As we've mentioned before, we have been enjoying a very close collaboration with the good folks at Asobo and Microsoft. They have been requesting, and we have been providing information on all the technical aspects that are required to make our product compatible with this new platform. As many of you are aware however, the complexity of migrating products with such a high level of fidelity as ours requires that the underlying platform, and particularly the development kit for aircraft add-ons needs to grow and mature before it can sufficiently host them at the level required. We are confident that the Asobo team has the talent to make that a reality. Until that time, we are going to keep our focus very strongly on getting our upcoming product line for Prepar3D released as previously announced. Here's a more complete list of the improvements and updates that are part of this release: ATSU Various updates and fixes to takeoff performance system DMC Logic update to immediately sync PFD/ND on return to internal views STALL STALL added to PFD messages Effects Updates for V4 external lighting Added GPU smoke effect FADEC Fix for manual start crank logic GSX GSX Services integration improved GPU now callable Input handling Now allows keyboard as well as joystick button inputs to be set Auto configuration for Thrustmaster Airbus hardware FMGC Perf TO page S8 updates AC Status S8 updates Inhibited PERF APPR page insertion below 700R Inhibited RADNAV ILS data below 700R and not on ground As always, and as a way of saying thank you very much for your continued support, I've added a few screenshots the team collected for your viewing pleasure!
    136 points
  4. Hello all, I would like to extend our most heartfelt thank you to all of you who have already purchased our new Sharklets products! We are overwhelmed by its almost universal acceptance and the very positive feedback we have received so far. I would like to take this opportunity to inform you that we are tracking a small number of issues identified with the new Electronic Flight Bag infrastructure. We are working with a number of customers who are helping us diagnose these issues and solve them for everyone. Our primary focus at the moment is assisting those few customers who cannot turn their EFB online within the Virtual Cockpit. We also discovered and are tracking an issue with the moving map included which requires us to take the map back-end offline until we can ensure the integrity of the services provided. As a result, expect the moving map feature to possibly become unavailable while we make some updates to the infrastructure to adequately support the feature moving forward. We will be sure to keep everyone updated as soon as we have more information to provide. Thank you again for your continued support!
    129 points
  5. Hi guys, I did say we are planning a shorter promotional period with these titles. So please don't be disheartened by the lack of any updates. We are extremely busy behind the scenes. I've just finished working on our Promo film that we will premiere before release. We can't wait to show you more of what we've been working on. Thanks again for your continued support and your patience - the wait is almost over. We are still planning to update our wing-tip fence fleet in the interim. Testing is now complete and we're finalising the installers. Lets keep this hype-train going. We love reading your comments
    123 points
  6. Hello everyone, I am happy to announce that our latest update (v5.0.1.151) for the A320-X, A319-X and A321-X for P3D v4 and v5 (64-bit) is now live and available through our download page. This is a maintenance update which fixes several issues identified since our last public release and in preparation for our upcoming A320-X and A321-X Sharklets products which are soon to be released. In this release, you will find that we have expanded our Input Controls management and handling logic greatly, to allow and include all Airbus input device controls, such as dual side stick input, dual tiller support, spoiler and flap axis input controls, rudder and brakes handling as well as more complete management for the Thrustmaster TCA Airbus series of hardware (A320 side stick, Thrust Quadrant as well as TQ add-on axes, like flaps and spoilers, together with the landing gear lever, auto-brake control and parking brake etc). In the input controls management dialog, support was also added for slope and null zone handling as well as axis reversal. We also fixed several small issues on our external models, reported since our previous release. You should also notice a smoother wing-flex model which we feel looks and behaves better than the previous rendition - this took quite a bit of effort, as it is work that carries forward into the Sharklets models and their wing structure. A notable fix for the external lighting is the one where beacons / strobes would sometimes freeze depending on dynamic light allocations around scenery. This is now taken care of as well. Modeling improvements are also to be found in the Virtual Cockpit, where animations were added to the AP Disconnect buttons (it was long-time coming and the addition of dual input control handling with AP DISC button management only made it more obvious that they were missing) and we added logic to dynamically provide proper numbers on the speed placards for all variants, depending on aircraft Maximum Takeoff Weight configuration. For those of you who wish to connect two side sticks simultaneously (we are aware of several sim cockpit enthusiasts who are expanding their hardware collection) you will notice that input priority logic is now fully incorporated into the product line, with associated warnings and control allocation according to the real world counterpart. Speaking of hardware - very soon after we make this update available to you, we will also be releasing the updated Hardware Interface which brings compatibility with the full complement of the Skalarki hardware suite. We have been promising this for awhile and we are quite excited to make it happen! If you look at the detailed changes and improvements log that I am adding below, you will notice that we're continuously adding and improving FMGC logic as well. We made several improvements regarding VAPP logic recalculations, fuel prediction fixes, a fix for TROPO entry causing predictions to be lost, as well as several FG fixes, such as protection logic improvements. We are still working on some more major fixes, more notably among them are some shortcomings in HOLD logic as well as adding OFFSETs which are two of the often discussed items in the FMGC. We are hoping to have more on these in coming releases. For those of you who fly online, we have updated our AOC logic to follow new VATSIM protocols and we fixed some connectivity issues when users were on non-English Windows setups. You will also find that D-ATIS now checks/pulls FAA source as well. For the failure-minded among you, there were quite a few fixes in several failure conditions. For example, the aircraft will now correctly switch to DIRECT LAW with FLAPS 2 instead of Gear Down, when all 3 SEC computers are failed or off, as Gear Down digital signals are not carried over when all SEC computers are off, so the system has to rely on FLAPS 2 conditions to switch to direct law instead. A small fix, you might think, but one that indicates the level of detail found in the product line (this one was a favorite of mine as it involved spending quite a bit of time inside the Schematics manuals and configurations - thanks Sam!). We also fixed a small issue where the AIRAC cycle was incorrectly reported on the MCDU - most years have 13 cycle releases, but last year was a fun exception with 14. This condition will not reoccur for "quite a long time" and it's now fixed. For those of you using our PANEL STATE logic in the MCDU, you will find it has been extended: Customers will now find a new AUTO DETECT state listed under the DEFAULT STATE options page on the MCDU. This mode will allow the aircraft to detect if the simulator is loaded on the runway, in which case the aircraft will load ‘Engines running’ – or at a gate/on stand, where the aircraft is loaded ‘Cold and Dark’. It was a feature brought in primarily for testing purposes – but we considered it beneficial to our customers too. Please note that this system relies on your Runway.bin being up-to-date. On a separate note, I'd like to mention that I am now the proud owner of a HP REVERB G2 VR set (which I fully recommend for those of you who feel the need to spend 800 Euro on a whim!). I find the product very solid - it introduced me to a world that is full of possibilities and opportunity in how flight simulation will evolve from here (but also showcased some glaring omissions from P3D itself, like the absence of proper VR controller handling, unless I am missing how they are connected / working in the sim - please feel free to tell me in a separate forum post). I mention this purchase, so as to inform everyone that we also fixed the issue where a large white rectangle would appear in front of the VR virtual cockpit - this was due to our cockpit light sensor which we now made transparent so as not to block your view while in VR. A small fix, but a good one at that! The complete log of fixes and improvements follows below. I would also like to mention that work on the Concorde-X continues - I mentioned in our previous announcement that it "will be released this coming year" - please replace the "will" with "may" as life in general sometimes might not agree fully with our planning strategy, just so that expectations are not set in a way that people become upset and disappointed. Rest assured that our priorities have not changed and we're still working very hard towards its release. On a closing note I'd like to take the opportunity to mention that the Covid pandemic has taken a toll on everyone. While I am among the very fortunate ones (so far) to not have experienced any direct loss of life in immediate family or friends, there have been several people in my immediate circle who caught the bug and it was very distressing to go through this ordeal. Please continue to exercise caution and care in how you protect yourself and those around you and, if you have that ability, please vaccinate. If not, mask wearing and distancing helps a lot! I am not going to turn this note into a political one, but health and safety should always be above any political opinions and beliefs. Please - please! - take care of yourself and family! We also like to wish everyone a Happy Easter (ours is coming in May, but there are quite a few of you celebrating next week)! As a way of saying Thank you, as always, for your support, here are a few new images of our product family for your viewing pleasure! ----- 2D Panels Flap placard spds now correct on F/O side 2D panel now draws BRAKE FAN only when installed ACP Fix for 2D and VC knob lighting in test model AOC Updates to follow new VATSIM protocols VATSIM Connectivity with Non-English Windows fixed Fix for Lat/Lon points on FPLN uplink D-ATIS now checks/pulls FAA source ATSU Uplink optionally omits SID/STAR CVR Updated test logic DMC SD F/CTL page fix for THS fluctuations Alternate law detection logic fix EFCS SPD BRK DISAGREE with SEC1 off now appears SEC 1+2+3 FAIL/OFF now causes DIRECT LAW with FLAPS 2 Effects Contrails tweaked for night time EFIS FD engage on ADIRS align ELAC Logic improvements for FG loop control Fix for stick input during flaps movement Elevation model Fix for memory leak above certain altitudes Engines / FADEC CFM Engine start logic updates (IGN and FF) IGN FAULT START message logic improved (IAE) IAE EEC ARINC output fix for BMC fault conditions External model Inner wing fairings gaps fixed Wing metallic textures updated Logo light texture updated Various improvements / fixes External lights Fix for beacon / strobe logic issue which caused lights to freeze sometimes FAC Fix for VLS when BUSS is active Flight Model Spoilers correctly dump lift on ground FMGC FM: PAGE PERF DES now allows spds up to .82 Mach VAPP logic recalculation improvements Fix for Fuel predictions Fix for TROPO entry predictions lost issue Fix for PERF TO page CHECK TAKEOFF DATA message conditions CHECK TO DATA message conditions corrected SET MANAGED SPEED message logic improved XXX IS DESELECTED message logic added PERF APPR page data entry logic improved FG: AP 1+2 INOP / CAT2 conditions logic tweaked Protection logic improvements Automatic speed protection logic improved FSL Config Check for DirectInput if any joystick axis detected Small fix in airframe parsing logic logic for Direct Input requirement when TCA hardware used Glareshield Chrono button logic tweak for right-click/release functionality Input Controls Added all input axes in FSL Input Controls dialog Brakes Rudders Spoilers Flaps Thrust levers Tillers Fix for crash when joystick was being set up the first time sometimes Fix for axis detection to now use relative movement (1.5% change now used) Gate Controller logic fixed for engines off scenarios AP DISC logic tweak Null zones / slopes consideration for single-sided axes (brakes) ISIS Improvements in timer logic (NEW ISIS) ALT flag logic corrected MCDU Fix for LAT/LON printing when minutes at 59.95+ User options Single/double digit entry now considered Tonnes or Thousands of Lbs. User options Added EXT CTRL GSX page for control over GPU Panel States SEAT BELTS / NO SMOKING off on Cold & Dark state New "AUTO DETECT" Panel State added Fix for loss of flaps / slats conditions Fix for cabin/cargo/eng oil temps on GPU/C&D states Panels Added popup ISIS and DDRMI (disabled by default need to edit panel.cfg) Radio Management Panel Fix for Seat Selection control of VHF1/VHF2 knobs SFCC dual hyd loss prevents halfspeed flag from turning true G+B HYD FAULT further logic improvements ALPHA LOCK logic improved Sounds AEVC and DUAL INPUT sound infra improvements Fix for sound disappearing briefly on VC view change SSTU Dual flight stick support added Virtual cockpit Added animation to AP DISC buttons Speed plackard now shows proper speeds for all variants depending on MTOW RESET BTN text clipping fixed Various gaps fixed Virtual Reality Tweaked sensor transparency to make it invisible while using VR devices
    121 points
  7. Hello everyone, I am happy to announce that our latest update (v5.0.1.160) for the A320-X, A319-X and A321-X for P3D v4 and v5 (64-bit) is now live and available through our download page. This is a maintenance update which fixes a few issues identified since our last public release, which I will include at the end of this note. More importantly, you will need this update installed because... We are now happy to announce that we are pushing the boundaries of desktop flight simulation even further with the release of our A320X-SL and A321X-SL for Prepar3D x64 (v4 / v5)! Built on entirely new visual models – the A320X-SL and A321X-SL bring the latest technologies to flight simulation – including an electronic flight bag suite, accessible not only from within the virtual cockpit, but also from any external device using a web browser, adding a completely new dimension to the simulation experience. Equipped with a whole suite of tools available in the palm of your hands, the EFB not only increases situational awareness within the simulator but also allows for tasks such as flight planning, performance calculations and communications to be conducted without leaving the virtual flight deck. Furthermore, the EFB can be loaded onto any external device using a web browser – such as what you can find on Apple, Windows or Android tablets, for an increased immersion experience! The newly released aircraft carry an extensive list of changes to its predecessor – a completely new fuel system modeled on the newer ‘jet-pump’ design – new Fuel Quantity Indication Computer and Fuel Level Sensing Control Unit components, Flight Warning Computers and SDAC updated to F9C standards. New ELAC L97+ computers featuring Load Alleviation Function and Anti-Aileron Droop. Updates to the Flight Management Computers – including a new ‘Jump Ahead’ feature for skipping down route. With a combination of range, capacity and increased performance thanks to the sharklet fins – the A321-SL is the ultimate airframe in our A32X series. Practice short-field operations in the Greek islands with the newest A321X-SL title from Flight Sim Labs, and experience the thrill of getting a 90-ton aircraft out of a tight spot! New custom sounds, animations and lighting effects differentiate the Sharklets from our other titles, both inside the cockpit / cabin as well as outside, with new LED lighting. Differences that collectively, create the immersive simulation experience our customers have become accustomed to. Particular attention has been given to the subtle differences in aircraft handling – increased lift generated from the 2.3-meter sharklet fins will see you out-climbing the rest of the Airbus fleet. They also extend the range and performance of the aircraft, making it ideal for short field operations. The Flight Sim Labs Sharklets aircraft represent the latest effort in simulating a modern-day airliner – now you can experience the thrill of flying some of the most popular airframes in our skies today. As a way of saying Thank You, as always, for your support, here are a few images of our newly released products for your viewing pleasure! A320X-SL: A321X-SL: and some inside shots: and... on to the next one: Update notes for v5.0.1.160 (that very few people will read now ): ATSU Updates for LBs option CIDS Updated / Improved logic External model / Virtual cockpit Cabin lighting improved Fix for beacon lights in P3Dv4 Various small fixes FMGC FG: Updates for Go around logic FSL Configurator Fixed case where corrupt registry settings would cause crash Improved logic to handle airframes Added error logging FWC "Dual Input" pin programming now persistent IDG Temperature logic fix Input Controls Tweaked axis detection logic MCDU Payload page fix User options - FWC dual input option now persistent SFCC Issue with slat angle reporting fixed
    115 points
  8. Hello everyone, I am happy to announce that our latest update (v5.0.1.119) for the A320-X, A319-X and A321-X for P3D v5 (64-bit) is now live and available through our download page. This update should also fix a couple of small issues (namely, the NEW CRZ ALT rounding issue and a few other niggles). EDIT: There are some GSX related updates as well that I forgot to mention: Once loaded in on stand, click MECH HORN to setup the aircraft. This will: - Call Stairs followed by GPU on remote stands - Or Call Jetway into position - This process can take up to 20 seconds When you switch from EXT PWR to APU, if the GPU is connected, it will be removed For departure without pushback, once all aircraft doors are closed and on APU: - Press MECH HORN to remove Jetway/Stairs and Chocks For departure with pushback - if the GPU unit is connected, it will be removed before GSX Push is invoked. When arriving onto a remote stand: - The GPU and Stairs will be requested first - Once the GPU is connected and the truck is clear of the aircraft, deboarding will be invoked - This process can take up to 60 seconds Note: If EXT PWR is connected when GSX removes Jetway or GPU power, the EXT PWR source will trip Please make sure you have updated to the latest version of GSX! As always, thank you very much for your continued support!
    110 points
  9. Hello everyone, Lockheed Martin's official announcement of Prepar3D v4 means we are finally free to share and discuss what we've been quietly working on for the past few months. Keeping up with LM's familiar methodology of incremental upgrading of the core platform, P3Dv4 brings a lot of small updates but also a few very significant ones, with the transition into a 64-bit code base being the most important. This means the platform is now able to take advantage of the underlying hardware without being artificially limited by the 32-bit memory space of 4 Gigabytes. Word of caution, however: This does not mean "no more OOMs" - if add-on developers are not careful, we will soon realize that as soon as users turn everything to maximum, there is still a very real possibility of 8GB or 16GB of installed RAM not being enough any more to support 4096 texture sceneries, full autogen, ultra 7cm resolutions, etc - not to mention that nagging will now be transformed from "oh - my bleeping thing OOMed!" to "oh - my bleeping thing is crawling at 4 Frames Per Year (tm)". This is what progress is all about, however and we welcome it wholeheartedly. As a matter of fact - and with the NDA finally lifted - we're now free to disclose that we've been working closely with LM on the v4 beta for quite some time now, so as to make the transition as smooth as possible for our A32X product line. Here's what our road-map looks like for the remainder of this year and into 2018 therefore: FSLabs A320-X - As soon as Prepar3D v4 releases, we will be able to share our x64 compatible A320-X version with our beta testers. There has been very significant and complex code changes to allow for x64 support so we want to take some time to ensure that everything works out smoothly before rolling the product out to our customers. - Once the P3Dv4 A320-X is released, it will be available FREE OF CHARGE to all existing A320-X P3Dv3 customers *** as of that date ***. - Around the time the P3Dv4 A320-X is released, the upgrade discount path from FSX into P3D (any version) will be discontinued. - We have been working on the A320-X Service Pack roll-out for quite some time now. A lot of the bug fixes will find their way into the A320-X x64 release as well as into an interim update for the 32-bit versions. This update will be in the hands of our beta testers very soon as well. - Support and bug fixes of all versions of the A320-X will continue normally - we expect that Service Pack 1 will be the last major update with new functionality for 32-bit versions of the product line and our focus will shift to the 64-bit platform(s) afterwards. - We are working to identify and correct the Enigma protection error that has been an issue with a few customers. This is very much on our cross-hairs and we're doing our best to fix it. FSLabs Application Manager Facility - We have been working on our FSLabs Application Manager facility which will be our one-stop installation and product support facility for our aircraft and liveries. Once this facility goes live, all updates and support of our products will be provided online through this feature. - We anticipate releasing the FSLabs Application Manager facility sometime after the initial x64 A320-X release. FSLabs A319-X - We have been working on the A319-X add-on to our A32X product family. As of today, we expect that the A319-X will be offered on both 32-bit and 64-bit platforms, but we'll make a more firm commitment on the platforms once the A319-X is at a later beta stage. Pricing for the A319-X will be announced around that time as well. FSLabs XXXX-X - There is another FSLabs aircraft add-on product in the initial stages of development at the moment. We will not say much more about it however, except that it can take... well... more fuel than the A320-X series :). ---- Some more bits of information that I'd like to share with everyone that don't fit our road map above: - Prepar3D v4 is a major release and as such, it is bound to be followed by a few fixes or updates. We have been working with LM to get some internal simulator functionality exposed and will continue to do so for their later updates. Once those appear, we have a few new lovely features to showcase that we are still keeping secret in our continuing efforts for innovation. - A note for our FSLabs A32X Home Cockpit and Professional Versions future customers: We are working with select hardware providers who have been eager to lend us their products so that we can ensure full and correct compatibility. Delays in releasing compatibility kits have been inevitable due to the various simulator platforms being released simultaneously. We hope and expect to have something for our customers by the end of the year. - We understand that our Concorde-X customers might be feeling a bit left-out with the absence of any information regarding the Concorde-X for P3Dv4. We are looking into that possibility but at the moment, we need to focus entirely on our A32X product line as we need to be very carefully administering our development resources. We would love to revisit the Concorde-X however, so that door is not closed for good yet. We will make a decision on this matter once the new x64 platforms have been stable for awhile. - Some of our friends noticed that we updated the text on our Facebook page to include Dovetail simulators as part of our target platform group. We enjoy a close relationship with Dovetail developers but at the moment, we do not have any significant news to offer on that front as the platform is still in early release mode. ---- As a way of saying thank you very much for your continued support, we added a couple of A320-X images from P3D v4 for your viewing pleasure! Cheers!
    110 points
  10. Hello everyone, I am happy to announce that our latest updates (v5.0.1.166) for all variants of the A320-X family, including our Sharklets, are live and available through our download page. This update mainly allows compatibility with the newly released P3D v5.2, as well as several updates and fixes to the base code. ***NOTE*** YOU WILL NEED TO UPDATE FSL Spotlights to v5.0.0.3 for P3D v5.2!!! You will also be happy to know that we restored the EFB Map functionality which was temporarily disabled in our previous release. To once again receive this EFB Map functionality, you need to upgrade with today's release. For the Skalarki hardware users among you, please note that the Hardware Interface software is also updated to support v5.2 as well as the Sharklets products, fixing several small issues along the way too. Thank you, once again and as always, for your continued support! ---- Here's a more complete list of the improvements and updates that are part of this release: - Prepar3D v5.2 compatibility - Base code support logic improvements - Compatibility with Hardware Interface v123+ ACP Added logic for PA Xmit button double-click functionality External model / Virtual cockpit - Various cosmetic fixes Performance Model - Fix for DC ESS FAULT flaps / slats recognition - Fix for B+Y HYD RSVR LEAK flaps / slats position recognition Sharklets-specific ELAC - Anti-droop logic improvements Electronic Flight Bag - MAP stability fixes - MAP Rendering optimizations - Drag/scrolling functionality fixed
    108 points
  11. Hello all, as we're finalizing the A320-X for release and preparing our server infrastructure to accommodate the new product versions, I thought a small way of saying "thank you" for your patience would be to publish a non-exhaustive list of changes and improvements as compared to the older FSX/P3Dv3 products. The A320-X for P3Dv4 is not a simple 64-bit code port, far from it. It brings a multitude of exciting new features and improvements which increase the immersion factor to unprecedented levels for a full simulation experience. Here's what was added, changed and/or improved in this A320-X for P3Dv4 first release: - New P3Dv4 Addon path Installation logic Security protection mechanism overhaul - Added Licensing Authority Administrative Security (tm) mechanism - No Enigma Internal Protection Error External Model - New v2.0 FSLSpotlights used - Dynamic lighting techniques with variable brightness depending on day / light conditions - Various new effects added for lights in low visibility fog conditions - Haze effects added in cabin - Various model parts updates - Texture resolution / quality improved - CFM engine significantly improved - Rudder Weather vane logic improvements - Livery installers updated to support P3Dv4 Virtual Cockpit - New v2.0 FSLSpotlights used - Several model part fixes / improvements - New and improved high resolution textures - Oxygen test logic added - PEDAL DISC button clickable and fully animated - Jumpseat camera viewpoint improved - Floor / Console lighting added - Aircraft shadow model added Sounds - 3D Engine overhaul - IAE / CFM Engine entirely new 3D sounds - PA recordings added - ACP can now be heard through headset - Over 200 distinct sounds added - APU sounds improved - Ext Pack sounds improved / added - Aft outflow valve sounds improved / added - Avionics sounds improved - PTU sound improvements - Cabin power xfer sound effect added - CFM clanking sound added - Doppler effect logic added FMGC - SEC FPLN added - FIX INFO added - S4/S7 AMI choice introduced - FM - Flightplanning analysis logic overhauled - Discontinuity logic improvements - AF logic improvements - AWY work in LST - Terminal/SEC/ALTN PLAN ND Display corrections - CRZ ALT updated to PPOS ALT if DES is initiated while PPOS ALT > CRZ ALT - DIR TO list not selectable if in TMPY - FPLN page negative distance logic improvements - NEXT WPT operative - NM/DIST FPLN page indication on SEC/TO WPT now PPOS-based if applicable - ND SEC MSAP path and SEC ALTN path now white - Lateral path logic improvements for Nav Intcpt calcs - AIP 3600 entry now considered as track 0 - BLOCK PRED improvements - Climb predictions tuned - TRANS ALT/LEVEL adjustments - Tracking improvements: - Velocity sampling for Rho estimation - Radial out logic - FA/CA/VA legs dynamic placement - SPD CSTRs now working for dynamic legs - CRS CAS predictions tuned - APPR automatic engagement requires NAV in MANAGED mode - FG - FPA calculation fixes with windy conditions (GS instead of TAS) - AP disconnect with AProt active logic fix - CMB logic update for CSTR - Bank limit for takeoff phase tuned - Mode fixes / impossible modes protection - Windshear active fGlimit - Min speed now based on FM speeds for DES/APP/GA and FAC for CLB/CRZ - Bank limit in NAV/APP NAV/FINAL APP now for engine out only - Various smaller fixes ATSU - Weather request logic improvements (ARPT stays in the list after request) ACSC - Fix for packs regulation and zone thermal balance - Hot air valve fix - TAC control logic - TAVR logic fix - Cabin temp logic improved ECB - Logic improvements for AUTO SHUTDOWN FWC - DB loading improvements - Various logicsheet fixes - Rx side logic fixes SDAC - DB loading improvements FAC - Rudder pedal tuning for improved ground handling - Reactive windshear logic added ELAC - Fix for bank > 33 and overspeed roll - Flare law elevator transition fixes MCDU - AIRCRAFT STATE infrastructure added (can be configured and saved per livery / airline) - Four distinct AIRCRAFT STATES supported: - COLD & DARK - ON GPU - ON APU - ENGINES RUNNING - Set default panel state logic added - MCDU / SUBSYSTEM intercom rate adjusted (faster MCDU I/O) PFD - FPV fix for FCU 1+2 FAULT E/WD - CFM N1 indications now EIS2 compliant - CFM MREV annunciation fixed ADIRUs - ADR warn light logic improvements Brake logic improvements - Surface Condition affects keyboard max deflection - Brake disc logic upodates / fixes - A/SKID OFF ECAM message fix Failures - STUCK OUTFLOW VALVE added Keyboard selection - Crash bug with entering new keys fixed Tiller - STEERING_SET event now subscribable for default P3Dv4 control axis - FSUIPC axis use now optional Visual Effects - Dynamic Light intensity now dynamically configurable - Cabin mist effects added And a multitude of smaller bug fixes and improvements that didn't make the individual list. We really hope you like them!
    98 points
  12. Version 2.0.0.15

    70712 downloads

    ---Now supports Prepar3D v4.1 to v4.5 --- Flight Sim Labs, Ltd. announces the availability of FSLSpotlights v2.0, a revolutionary new product for Lockheed Martin's Prepar3D v4.1 (and above) that allows the simmer to import and control up to 60 different fully three-dimensional dynamic spot lights in any existing aircraft virtual cockpit. Each light can be used individually as a single lamp or put together in groups with a single on/off switch and a brightness regulator control. Light attributes (beam position, pitch, heading, angle, range, attenuation, color) can be modified and parameterized to provide the correct look and feel depending on desired light type: This way, the user can add narrow focused lights to shine on map holders or tray tables, series of smaller lamps for main panel flood lighting or wide dome lamps for turning a dark cockpit into a lit area. Each lamp holds its own attributes which can be tweaked using a configuration manager that runs as a separate process and communicates continuously with Prepar3D, giving the simmer an unlimited number of lighting configurations and setups.
    96 points
  13. Hey folks. I decided to transcribe the chat BlackBox711 and AirbusFTW had with Andy and Lefteris live in the Discord. I've since cleaned these up a little and have turned them into the notes below. These aren't entirely verbatim but I've tried to be as close to it as I can. Anything where I wasn't sure what was said has not been included. I hope you enjoy the answers. Some of them shine some light on to the challenges of developing this brilliant software. Credit to @Andrew Wilson and @Lefteris Kalamaras for spending so much time answering questions, and to BB711 and AirbusFTW for hosting their streams! --- Will the EFB have a performance impact? Andy: I don't think it will have any. I didn't notice any, nor have the beta team. It will work in a browser on any external device. You can have two instances of the EFB in the cockpit. An external device can act as a third EFB. If you have another, that can act as a fourth. EFBs will be in the SL models initially. They'll come to existing products (WTF) eventually. Our focus is on sharklets publicly, but behind the scenes it's known that we are working on quite a lot, quite a few projects. Lefteris: We like to under-promise and over-deliver. Regarding Honeycomb integration: Lefteris: They have communicated with Honeycomb about working with them, but no responses from them. If anyone from Honeycomb is watching, please get in touch. Regarding PDFs in the EFB: Andy Wilson: You will be able to drop PDFs into the FSLabs folder so they then show in the EFB. Regarding performance impact of the EFB: Andy: We haven't seen any issues with FPS. A lot of work into it to make sure it didn't impact performance. We didn't want to degrade that. A lot of effort went in to make sure tablets don't affect performance. Neither I nor the team have noticed a performance hit. Lefteris: The performance of the existing product should be more fluid now. A lot of the improvements that have gone into the sharklets have gone into the 150 update. Regarding v4.5 compatibility: Andy: Sharklets will be compatible with v4.5. Lefteris: Performance is better in v5.1 though. Regarding requested features: Andy: No news about shared cockpit. There is a list of features that we’ve been working through over the years. ATSU was first. EFB was second. More features are listed for development. We do listen to feedback and we’ll keep at it. Regarding liveries: Andy: Range of liveries will be available upon release. Around 25-30 liveries available. Regarding release news and pricing: Lefteris: We are working out some interesting ideas about the pricing. Andy: Projects are being worked on in the background. When we have more news to share, we will. Work is underway on those projects. Lefteris: The project with more fuel has not been revealed. Regarding new MCDU features: Lefteris: Step altitudes/holds etc not ready for sharklets, but they are coming. We have heard a request for an application to install updates and it is also on our radar. Regarding wing effects and lighting: Andy: The wing condensation effects haven't been updated. The lighting has. The strobes, on the A320 sharklets, at night time you'll notice the strobe light from the shark fin will have some glare on the VC. It was a design flaw in the real aircraft. They fixed it by adapting strobe blockers a few years later, which they put on the wing to deflect the beam. You can either add those as an option because we figured if it annoyed real pilots it might annoy virtual ones. You can drop the blind behind the captain's / FO's seat to also mask out the glare, too. I personally like the glare at nighttime. The ethos is that we try to capture every little detail because that makes the immersion. Will there be an A320 NEO and are there plans for an MSFS release? Andy: Are we doing an A320 NEO? I am going to say no comment Andy: If there was contact from Asobo, we would be under an NDA which would prohibit us from disclosing any information. I'm going to have to say no comment again, I'm afraid. AirbusFTW: NDAs mean that even if we wanted to say more, we can't. Andy: The first thing that happens when you work with another company is that you're hit with an NDA. Lefteris: You can't even say if you're under an NDA. Regarding the map overlays such as traffic and weather: Andy: Traffic is hooked into the P3D AI system. It doesn’t pull it from VATSIM or IVAO. One of the benefits is that you can see the aircraft moving around in real time. You can see aircraft taxi around in real time. There are small details we have implemented. Map overlays, the rain and thunder icons are greyed out in Blackbox’s stream because Blackbox is not flying in real time. Radar overlays would be shown in real time, so you’ll see weather in real time. The EFB came into its own with the event where people flew to see Santa. Could see everyone in the hold. You really notice it with the WTF because it’s something you miss. Especially with the taxi markings on the EFB. VATSIM velocity will reflect in the EFB too because if they’re being injected at higher speed, they’ll be reflected in the EFB. Regarding performance calculations and if the Satdome makes a difference: Andy: We work very hard and closely with professional crews and we’re always updating the performance routines and it allows us to go in and change airfield data. We can hard-code obstacle gradients. We are always playing around with the performance tables. The satdome doesn’t affect the CG but it does affect the fuel burn. It’d be something that an airline would recognise over several hundred cycles. We’re just doing one type of satdome. As fleets in the real world mature, there’s no reason why we wouldn’t stay in line with that. At the moment we’re releasing with what you’re seeing. Lefteris: We did discuss this with Margerita. We put in an option where the satdome could be moved. Locations could be changed. But we’re not 100% sure so I’ll get back to you on that. Regarding the EFB coming to the Wing Tip Fence model: Andy: A321 and A319 will get the EFBs as well. It’s something we’ve always done. New products first, then we work their way back into older titles. At the moment, our plates are pretty full for the immediate future going forward. We’re not looking to update the wing tip fence in the next few months because we want to push forward with the exciting products we’re working on. At some point, is the final answer. Regarding the anti-droop function on the wings and the sharklet coding process: Andy Wilson: The WTF is on ELAC93 and the Sharklets have ELAC97+ -- it's modelled as components. The sharklets have the EL97 wired in. Regarding these features, it's not going to be an overnight change. It requires going in and rewiring the entire aircraft. When we first started writing the sharklets code, we started with the fuel system. It's just a mesh of relays and wires. They needed recoding and repinning. When we finished it, it was throwing up errors. The Flight Warning Computer was just going mad. The version we had, F3B, just wasn't programmed to work with the newer system the sharklets used. That took a few months. That's 18 months down the line. All these things that you think might be simple coded changes aren't that easy to change. At some point we need to have a cut-off because you can just go on forever. There are so many minor differences between these airframes. Lefteris: The Flight Warning Computers have over 3500 sheets of coding programmed. It's about 300 or 400 pages of updates. Will the sharklets have the halogen lighting too as an option? Andy: One or two operators are running sharks with halogen but the majority are LEDs so that's what we're going with here. Regarding future plans: Andy: We’re not answering questions about A330/A350/A380. They really do take months of investigating, analysis, market research and understanding what resources are available to us. It's based on months if not years of research into these titles. We've said all we can say. We are working on something that does take more fuel, it starts with an A3! And it's not the Concorde. Time will show what it is that is going on in the background. And people are saying A330 confirmed, I didn't say that! The Jump Ahead feature: Andy: Jump ahead is something where you can go through a list of your waypoints and you can select it. It'll populate the data in that page with where the aircraft would be, it'll then allow you to jump ahead to that waypoint. It’s a really good feature to jump through your route, or if something happened with your sim and you had to restart, it's a system we used in testing but it's something we thought our customers would enjoy too. It came into its own with a group flight. P3D crashed. The group carried on flying. I could then jump ahead and carry on with the group flight. Lefteris: Please don't use the jump ahead on VATSIM, unless you’ve had a crash! Regarding new failures: Lefteris: Blackbox and I were talking and I think he was doing some sort of landing gear failures, like a gear door failure, and I think these are in the new update and they work. Blackbox711: And also the engine start issues are implemented, which is cool. Lefteris: Gear door failure also results in more fuel burn. Any EIS plans: Lefteris: To retrofit EIS1 would be a huge undertaking right now. It's an entirely different system. Short answer is no. Regarding the time it’s taken to code the Sharklets addon: Andy: Sharklets development started early summer 2019. It's been a project where we've learnt a lot about the aircraft. We initially thought a couple of wingtips and fuel burn. But it turned out not to be the case. It's a tip of the iceberg job, once you look under the water you realise there's a lot more going on. It's not just figuring that data out but working out how to get that on to people's desktops. Lefteris: There are other products that are introductory products. But we're about detail. We're victims to that detail. Regarding the level of detail: Blackbox711: It feels like I’m at work, because the EFB is so lifelike. It’s what I would use every day that I fly.
    87 points
  14. Hello everyone, I am happy to announce that our latest update (v5.0.1.169) for the A320-X product family for P3D v4 and v5 (64-bit) is now live and available through our download page. This update brings compatibility with Prepar3D v5.2 HF1 which was released a couple days ago. As always, thank you very much for your continued support!
    85 points
  15. Hello guys, I appreciate all of the hype going on already and I am super excited to see all the anticipation reaching amazing levels! In fact, I wanted to share that, while we don't expect the release to go out tonight as our beta team is still going through the usual uninstall / reinstall of the new HF2 client and testing the latest version, we are actually quite confident that what is coming is going to make everyone very happy! We also expect to lift the NDA within this weekend to allow our testers to showcase some of the beautiful new features we've put in place - I am sure a lot of you have watched several streams where our beta tester friends show PBR models, S8-related features, etc, but those are not all that we have been doing while you waited! Andy reminded me of one of his favorite features that was added just very recently - this example showcases how the team is able to build on each other's strengths and improve our products above and beyond: Margarita was able to add quite a lot of immersion to the external model by remodeling each passenger window individually in detail, to allow all of the beautiful PBR retexturing work that had gone into the visuals to, erm... well, shine! Together with the individual window remodeling, she actually took the time to model individual cabin window blinds and add animation to them. The idea was that we'd now be able turn blinds on and off, adding to the immersion factor with each of our updates. When we discussed this internally, Andy threw an idea that felt that could take the immersion level a step further - in typical FSL fashion... so I'll let him explain what he did in his own words . All I am going to say is... this is just another small example of what it means to be #FSLabbed... Take care and have a nice weekend!
    68 points
  16. ****PLEASE READ - CONTAINS INFORMATION ABOUT PRODUCT END-OF-LIFE AND INSTALLER UPDATES FOR EXISTING PRODUCTS**** Hello Everyone, I wanted to take a moment to update everyone regarding news on upcoming products, information on older products being retired, our plans going forward and offer some comments on the latest announcement from Microsoft. Transition from eSellerate to FastSpring As all of our customers know, we've relied on eSellerate for all our product sales and transactions. We've enjoyed a very solid relationship with them for over ten years now and have been very happy with their professionalism and support. Unfortunately, Digital River, the parent company of eSellerate, have globally decided that eSellerate discontinue any new sales operations starting June 30th, 2019, while retaining product activation/deactivation capabilities for existing customers until September 30th, 2019, at which time the eSellerate infrastructure will no longer be available. As soon as we were informed of this news, we started looking for the most appropriate eCommerce provider to match our customers' requirements. After a thorough market search, we selected FastSpring (www.fastspring.com) as they rate very highly in customer satisfaction and have a stellar reputation in handling payment processing in a fast and efficient manner. I'd like to provide some details on how we're going to transition from eSellerate to FastSpring and how this affects you as a customer below. To do so, first I'd like to discuss what will happen to our existing products: Prepar3D v4 (P3Dv4 - 64bit) All our products for P3D v4 will continue being sold and supported through our web site. This includes the A320-X (P3Dv4), the A319-X (P3Dv4) and the upcoming A321-X (P3Dv4). Existing installers for purchases before June 30th will continue working until September 30th, 2019. Starting June 30th, existing customers will be able to transition to new installers by following a free license transfer process through our web site to receive new activation keys that the new installers will require. We aim to make the transition process as easy as possible - details on the transition mechanism will also be available as a separate announcement and email. We expect that our upcoming A320-X update will be part of this transition. Prepar3D v3 (P3Dv3 - 32bit) We will stop selling any P3Dv3 products (Concorde-X / A320-X) effective June 30th. At the same time, we'll stop providing free upgrades from P3Dv3 to P3Dv4 for our A320-X product line. Support will continue for at least one year (June 30th 2020) and product activation will continue working with existing installers until September 30th, 2019. After that date, we will provide updated installers through our Redownloads page which will allow activation without contacting eSellerate's activation mechanism. Flight Simulator X (SP2/XPack/Steam - 32bit) As with the P3Dv3 products, there will be no further development work done on the FSX products, but sales of the A320-X for FSX only will continue until September 30th. This will conclude sales of all FSLabs 32-bit products as they have reached end-of-life and development for them will no longer take place. As with the P3Dv3 products, we will provide updated installers through our Redownloads page which will allow activation without contacting eSellerate's activation mechanism. As a result, effective June 30th, all new sales on our web site will no longer be processed by eSellerate and will be handled through FastSpring's popup storefront system. How does this affect you as a customer? New customers (purchasing after 30 June): Only 64-bit products will be available for purchase. All sales will be handled by FastSpring. Sales through eSellerate will no longer be possible. Concorde-X (32-bit) will no longer be offered for sale for any platform. We expect that the A320-X for FSX will no longer be offered for sale after September 30th, 2019. Existing customers who have already purchased one of our products: 64-bit product updates released after June 30th, 2019 will use installers that will require FastSpring order IDs (starting with "FLI") and new activation keys. Details on this will be provided in a separate announcement and email. We are aiming to make the transition as easy as possible to better serve and support you going forward. Upcoming products Work continues on the A321-X - we will provide a separate announcement with more details on exciting new features and new functionality as time goes by, but we think the A321-X is shaping up to be our finest product yet - we know it’s a favourite amongst pilots and we’re sure our customers will develop an equal appreciation for this airframe with its rather unique characteristics. The model already looks superb and the liveries that Vassilis has been producing are shining with their new Physics Based Rendering textures. I expect several preview pictures to follow in the coming months, along with some lovely surprises in the cockpit. The Concorde-X for 64-bit is now officially on pause. While we received some strong support from customers regarding future sales on P3Dv4, we have to ensure that we align our business model with the significant development news that we received from Microsoft, and since the aircraft is so specialized, we prefer to evaluate further once there are more details on the new platform. The A3XX-X is also in its early stages of development, we'll have more news on that when available. "Microsoft Flight Simulator 2020" (working title) We were very happy to read the announcement of the new Microsoft Flight Simulator platform (which most now affectionately call "MSFS 2020"). It signals the return of one of the most prolific products that our good friends in Redmond have developed and we are all very excited to take a preview look into what looks to be technologies bringing the simulated world to a new level of immersion. We've seen the same previews as you have and they are certainly breathtaking! We cannot, however, provide any details or answer any questions about "MSFS 2020" at the present time, other than to say that our excitement about this next version is the same as yours! That's all for now, expect more details on the transition to FastSpring these coming days! Thank you always for your continued support!
    66 points
  17. As promised, some shots of our A319-X in P3D v5:
    64 points
  18. One step closer now: The product family is now updated to v151.
    61 points
  19. Thank you all for the messages of support... I am sure Mike is up there reading this and appreciating every single post! However, this thread was supposed to be about the upcoming update, and with the news of P3D v4.5 just released, I am happy to reveal that it's exactly what we had been waiting for. The next step is that we will give our beta testers a compatible version tonight and a couple days to let us know nothing is broken (as is usual in every P3D minor version release) and then we'll push it out for all to enjoy! Thank you all once again for such a huge show of support, love and appreciation! Once we get a free breathing moment, we'll make sure to split out the posts relevant to Mike into their own thread, as he deserves to have that pinned in our forum.
    59 points
  20. Hello everyone, I am happy to announce that our latest update (v5.0.1.115) for the A320-X, A319-X and A321-X for P3D v5 (64-bit) is now live and available through our download page. This is a compatibility update to bring the product family up-to-date with Prepar3D v5.1.8.26742. As always, thank you very much for your continued support!
    57 points
  21. Hi all – As Lefteris commented on, one of my favourite areas of the updated models, besides the PBR, is the cabin windows. Each window has now been remodelled in detail - and we've also modelled the cabin window blinds, individually. You'll notice the blinds moving as you fly - depending on where the sun is relative to the aircraft and flight phase. For example, should the sun be shining on the left side of the fuselage, then you'll see more cabin blinds close on that side. As the sunlight becomes more intense before dusk or after dawn - more blinds will close. During dusk/dawn, we figured the passengers might want to view the sunrise/sunset - so expect more blinds to open. As you fly into the night and your passengers settle down to rest, you'll see more blinds close again. And, of course, all window blinds will be opened for takeoff and landing. As you know, we love to add the smaller details, that collectively, make the immersion experienced when using the A320-X series quite unique. Here's a shot on the return back from Faro this morning.
    56 points
  22. Afternoon everyone, I asked our beta team to collect some high-res screenshots of our updated virtual cockpit for the A320-X in Prepar3D v4 so that I could share these with you. We are in the final stages of testing the A320-X in Prepar3D v4, which as I mentioned previously - features a new high definition sound package, new modelling and texture work, new FSL Spotlights which utilise and extend the new dynamic lighting found in P3D v4. Users can now load, save and set a default panel state through the MCDU. The FMGS now includes SEC FPLN, FIX INFO (both S4 and S7 standards) and extensive work to support upcoming features such as wind predictions, offsets, equal time points, energy circles, step climb/descent and required time to arrival logic. There is a LOT of work that has gone into this aircraft since our last update - and we'll be providing a full list of details of these new and updated features upon release. Oh - and then there's the other little thing we're working on too...
    56 points
  23. I've elected to stay away from this until now as it gives people an opportunity to joke around, vent their frustrations on a "perceived delay" of our release (even though I've explained the reasons behind the delay) and has so far been kept casual and light-hearted. It seems things are starting to derail now, however. When our beta testers are starting to be called "fanboys" and the requirement that "claims need to be backed up" arises, people's feelings are starting to be hurt and I am not liking the direction the thread is taking. So - without further ado - if you do not wish me to lock this thread and/or start muting people (which I hate doing), take the direction back to the main road it was going on before. Keep having fun, keep spreading hype, but the rest should stop here and now. Any more inflammatory posts and I am taking more strict measures.
    54 points
  24. Hi guys- just a small note to say that we're fixing some issues we found while testing the release - nothing too major but it might take a little bit more time to do. That, in combination with the upcoming P3Dv5 HF2 which we feel will fix a couple other very important shortcomings, is delaying our release. Just wanted you guys to know, so you don't expect the release to drop within the next couple of days at least.
    53 points
  25. Hello all, We’re pleased to announce the release of version 2.0.1.258 of our A320-X for Prepar3D v4.2 and v4.3! Along the way we’ve been listening to all your feedback on problems and ideas for improvements, and we’re confident that this update will solve a great deal of those little niggling issues that some have experienced. One important thing to note is that this new updated version will support P3D v4.2 and v4.3 only. v4.1 users will need to update their sim to take advantage – something which we recommend everyone does in any case, as each incremental update to Prepar3D brings numerous fixes and improvements to the overall sim experience. As is often the case with these things, there are literally too many little changes, fixes and improvements to list in detail, but overall we think you’ll enjoy a smoother, more stable experience. You’ll find a non-exhaustive list of the main highlights below. You can get the updated installer by heading to our redownload site and entering your A320-X license information. FSLSpotlights v2.0.0.9 Alongside the A320-X, we have also updated FSLSpotlights for Prepar3D v4 to v2.0.0.9. This version includes P3D v4.3 support and is required for v258 of the A320-X to work correctly. As a reminder – as we announced in our last update, Spotlights is now a totally free product and you’ll be able to use it in all your add-on aircraft, not just the A320-X. You can download it from here. A319-X for Prepar3D v4 One of the reasons we were keen to get the A320-X update out is because it includes a great deal of infrastructure which will be required for the upcoming A319-X. The good news is that we are now wrapping up the very final stages of testing the A319-X and provided no last-minute showstoppers leap out at us we hope to have the Baby Bus in your hands very soon! A320-X 32-bit Update We are still in the final stages of beta testing the update for 32-bit platforms and we hope to have this in your hands soon after the release of the A319-X. A320-X v2.0.1.258 Changelog - P3D v4.3 compatibility update - FSL Configurator: - Logic improved when SSAA / FXAA entries missing - Policy Ignore logic fix - External model: - Fix for IAE fan animation logic - Fix for CFM fan animation logic - Improved CFM cone geometry / texture - Nose Gear Inner part textures reworked - Parking brake light added - Various small cosmetic fixes - Virtual cockpit: - Pedestal ACP click events updated - Side windows updated / improved - Guarded switches initial position logic fix - Trim wheel animation improvements - Trim wheel indicator texture / lighting reworked - Main panel lettering quality improved - Captain window shader fixes - Various small cosmetic fixes - GSX: - Auto-door logic implementation - Fix for crash when loading/unloading with GSX - Autoflight: - Fix for FCU Speed Selected - FMGS: - FM: - Fix for NAV->HDG downgrade crash bug - RNP translation fixed (requires updated nav database) - OPT FL during CRZ CLB/CRZ DES fix - Pause at TOD now at 20nm before TOD - Lateral fix for nearly codirectional segment flaw during path minification - DIR TO fixes when pseudo waypoint exists between TP and TO - APPR PERF page fixes - Fix for intl date line logic bug - X424 updates for APT listing - Radial Fix Info page RETURN logic fixed - FG: - Tuning for Autopilot in ALT* modes - Radios: - COM Radios tune to 122.8 / 118.1 by default now - Oil Temp: - Several logic fixes - Fuel: - Several logic fixes - FRV Flow rate reverted to 300Kg/h - Fuel tank sun exposure area improvements - Fuel Temperature model overhauled. Main features: - Fuel Pumps affect temperature - IDG thermal model added - Sun power and shade logic added - Sounds: - Several logic improvements - Fuel pump sounds tuned - APU Volume reverted - IAE Sounds improved - CFM Engine sounds improved - PA logic improvements - Fix for multiple sound device related crash - IDG: - New thermal model completed - DMC: - E/WD Fuel ECAM page fix - Fuel used logic fix - Fix for Chrono running in Paused state - BSCU: - Autobrake MED distances / deceleration tuned - AOCService: - Minor fixes and enhancements and new file detection algorithm As always, thank you very much for your continued support!
    53 points
  26. Hi everyone, After our pre-release note on September 6th, I am very happy to now announce that our FSLabs Control Center, our new utility which allows easier management of our product family and simplifies tasks such as installation and uninstallation of FSL aircraft, liveries, airline packs and utilities (e.g. FSL Spotlights), is now available for download to all our customers! Its primary aim is to allow for a one-stop update facility for our product line and improve the customer experience by providing micro-updates and rollbacks without the need for individual installers or long downloads, allowing our customers to update their entire product line with a few simple clicks. Multiple simulation platforms are supported and a search facility for official liveries is provided to allow for a quick selection and installation of your favorite airline colors. It features an 'Update All' simple, one-click update function which allows streamlined downloading of any new available updates for all the customer-installed products, rather than having to download individual installers each time we update our product line. There is also a bulk uninstall feature which allows the customer to uninstall all products at once, so that license keys are once again deactivated and ready for future use in preparation of hardware changes or replacements with no need to contact support to request license reactivation. Apart from the stable public release channel, a provision is made for an "experimental" channel as well, whereby the customer can, at their option, choose to be part of our upcoming open testing channel, whenever available. Last, but not least, the opportunity to enter optional items such as your Hoppie ACARS logon and Simbrief username is available through FSL Control Center, as well. As you make your way through FSLabs Control Center, we would love to have your feedback in the newly added FSL Control Center forum - go through the FAQs and User Guide you will find there and feel free to let us know your first impressions as well as any issues you might find. As always, we thank you for your continued support!
    52 points
  27. Hello, The long waited winter is finally just around the corner. Ever since FSLabs released the A319 with icing features I have been eagerly waiting for the cold weather and icing conditions to reach us. Icing has always been one of the interesting aspects for me in simulating my flights and I am extremely happy to finally see proper modeling of winter/icing operations including on ground de-icing/anti-icing. Because icing has never really been properly simulated with ground operations included I decided to write up some information that you may find useful before you go try to tackle the challenges that winter provides every day flying in North America and Europe. However, I want to also say that I am just an enthusiast and don't fly planes commercially in real life. So there may be mistakes and things that can be discussed and discussion is always welcome. Let's begin then! Icing in general First of all I would like to talk a little bit about icing in general. Where it occurs, why is it so dangerous and what can we do to fight against it. In general terms, icing conditions apply when the outside air temperature or TAT is below 10 degrees Celsius and visible moisture in any form is present. Such visible moisture can be clouds, fog, low visibility, rain, snow, ice crystals etc... Remember that icing conditions also apply when on ground there is snow, water, slush or any other kind of contamination that could be ingested by the engines. So even if there is no precipitation, you may still be in icing conditions and especially engines are at risk in this case. Usually once SAT goes below -40 degrees, the air becomes so cold that all moisture will turn into ice crystals and not form ice should form on the airframe anymore. Why is icing so dangerous then? Ice forming up on the leading edge of the wing changes the airfoil significantly, adds drag and weight to the plane. This results in reduced wing lift capability, increases stall speed and decreases climb capability. Simply put, the flight characteristics of the plane don't apply anymore and you enter an unknown territory where the aircraft was not designed to be flown in. In worst cases the problem can become so severe that the aircraft becomes uncontrollable. Same happens for the engines as the blades essentially are wings that are directing air into the engine. If that airflow is disrupted the jet engine loses performance significantly and in the worst case can result in a stall, surge or complete engine flame-out. Also, once you enter icing conditions, without any protective actions things can develop really quickly and get to a point where there is very little you can do anymore to make the situation any better. Luckily we have developed systems and procedures to fight against icing. We have mechanical systems on board the aircraft for both wings and engines and we also have developed procedure on ground where we "wash" the plane with different kind of fluids to remove contamination and protect the airframe from new build ups. These mechanisms can be essentially put in two categories: anti-icing and de-icing. It's good to remember that there is a difference between these two. De-icing means ice and contamination removal while anti-icing means ice prevention. On board the Airbus A320 aircraft there is anti-ice & de-ice systems (heated air) while for example, some propeller planes like Dash 8 have only de-icing systems (inflatable boots). On Ground we also have fluids for both de-icing and anti-icing that can be used to protect the aircraft from the effects of icing on ground before takeoff. We can also do one-step or two-step procedure (At the time of writing, as far as I know, FSL only supports one-step procedure). In one-step procedure, the aircraft is de-iced and anti-iced with the same heated fluid that will remove all contamination and also apply a protective layer for limited anti-ice capabilities. In Two-step procedure the aircraft is first de-iced from any contamination with hot water or hot type I fluid (more about the fluids later) before applying the anti-icing fluid on the second step. Because on two step procedure the anti-ice fluid is spread on a clean fuselage without any contamination the anti-ice fluid will provide maximum anti-ice capability. Two-step procedure also better cleans the aircraft from any existing fluids on the fuselage that have already lost their anti-icing capabilities. The general rule is that if there is any visible contamination on the airframe, it should ALWAYS be de-iced before the flight. If icing conditions apply such as rain or snowfall, clouds etc... the aircraft should also be anti-iced. Engine anti-ice shall be used whenever the engines are running and icing conditions apply (visible moisture + OAT/TAT below 10 degrees C) and wing anti-ice when positive airframe icing has been observed. Engine anti-ice works more as an anti-icer because you want to prevent ice forming up on the nacelles altogether. If ice forms up on nacelles and it's then de-iced it can remove large chunks of ice that can be ingested by the engine damaging the fan blades and leading into bigger problems. Wing anti-ice, however, is used more as an de-icer to remove the ice formed on the wings. This method provides the cleanest airfoil surface, the least possible runback ice formation and the least thrust and fuel penalty. On ground de-icing/anti-icing Moving on to something new that has never been seen before in consumer flight simulators in full effect. Something that makes me truly excited! On ground de-icing/anti-icing. You may have heard about different kind of fluids but have no idea what they do and how they are used. Hopefully I can help you here so that you can select the best fluid for your flight and also know a bit more about holdover times and other things related to on ground de-icing/anti-icing. First of all, on ground de-icing/anti-icing is provided both on gate and on remote aprons designated to de-icing. To know exactly how the airport you are flying from operates you can take a look on your charts (Navigraph for example provides this information usually on AIRPORT BRIEFING (DEP) section). Unfortunately right now GSX only allows de-icing at the gate before pushback. So if you want to see the de-icing vehicles around your aircraft, you have to limit yourself to de-icing at the gate. However, FSLabs still allows de-icing on remote aprons without any problem. The only drawback is that there are no GSX animations. Cockpit preparation De-icing can be completed both before engine start on the gate or while engines are running on a remote stand. It has to be noted though that while engines are running, no under wing treatment can be completed. Before treatment can take place there are few items in the cockpit that have to be checked. Cabin press mode selector - Check AUTO ENG BLEED 1 & 2 - OFF APU BLEED - OFF DITCHING pushbutton - PUSHED Thurst levers - IDLE Once the treatment is complete Ditching pushbutton - OFF OUTFLOW VALVE - CHECK OPEN ENG BLEED 1 & 2 - ON De-icing/anti-icing report - RECEIVED 3 minutes after treatment APU BLEED - AS REQUIRED (if de-icing is completed with engines running, APU bleed will be off by default and is not needed anymore. The delay before re-enabling the APU bleed is there so that no fumes from the fluids enter the cabin) Fluids Let's talk about the different kind of fluids then. There are four types of fluids: I, II, III & IV. On top of that there is also hot water that can be used for de-icing in two-step procedure. These fluids are then mixed with water in different concentrations to get the wanted result while still saving money and environment. More water means that the freezing point of the fluid is higher (closer to 0) but more fluid means higher costs and more environmental damage. Type I: Type I fluid is orange in color and is always applied heated at high pressure primarily serving as a de-icing flying. It has low viscosity and it flows off the surfaces relatively quickly. In extremely low temperatures type I fluid may be the only option and it's sometimes used even in one-step procedure despite it's short hold over times and very limited anti-ice capabilities. The freezing point of type I fluid should be at least 10 degrees C below the outside air temperature. Type II: Type II fluid is colorless or light yellow fluid that has a thickener in it to prevent immediate flow off aircraft surfaces. It serves as an anti-icing fluid because it stays on the surface for longer and in higher speeds. The use of type II fluids is dimishing in favor of type IV fluid. The freezing point of this fluid should be at least 7 degrees C below the outside air temperature. Also this fluid has lowest operational use temperature (LOUT) of -25 degrees C at 100% concentration without special conditions applying. Type III: Type III fluid is usually light yellow in color. It's used more on a slower aircraft with rotation speed less than 100 knots and therefore I won't go too deep into this fluid as it's practically never used on A320 family aircraft. Type IV: Nowadays probably the most common fluid. It's light green in color and is used primarily as an anti-ice fluid. It provides longer holdover times than type II fluid and can be used for de-icing as well in one-step procedure when heated. The LOUT for this fluid is same as for fluid type II at -25 degrees C at 100% which is the reason why in extreme temperatures fluid type I might be the only option available without special conditions applying. Concentration Now that we have all the fluids covered let's talk a bit about concentration. As I mentioned above usually these fluids are mixed with water to save environment and money. The concentration level depends on the temperature. The concentration is reported with two numbers like 50/50 where the first number is the percentage of the fluid and second number is the percentage of water. In this case we would have 50% of de-icing fluid and 50% water mix to spray on the aircraft. In general terms type 1 fluid is mixed by the de-icer to meet the requirement of freezing point at least 10 degrees C below the OAT. Because this fluid is used primarily as de-icer and has limited anti-ice capabilities due to low viscosity, it's not really feasible to calculate the concentration to meet certain hold over time requirement because the fluid would flow off the wing anyways before that. With type II and IV fluids it's possible to play a bit more with the concentration if delay is known. Higher concentration allows longer holdover time. I will provide a link at the end of this post to FAA holdover tables, so you can see yourself how the holdover time is calculated with different temperatures and fluid concentrations. However, as temperature drops, you have to use higher concentration anyways. With temperatures > -3 degrees C or above 50/50 concentration may still be used. Between -3 and -14 degrees C 75/25 concentration is the lowest that can be used and below -14 degrees 100/0 concentration has to be used. Holdover times For holdover times it's easier to link you this table rather than explain all the different conditions. Hopefully you find it interesting https://www.faa.gov/other_visit/aviation_industry/airline_operators/airline_safety/media/FAA_2018-19_HoldoverTables.pdf So here is a bit of information that will hopefully keep you safe when flying in the harsh winter conditions. If you have any feedback, corrections, tips or whatever, don't hesitate to join the discussion. We could make this one big megathread for winter flight operations if people are interested to share their knowledge. Now it's time to grab a hot chocolate, get cosy in your home cockpit and enjoy the warm heat coming from the fireplace while trying to keep your aircraft safe in the virtual skies during the long and dark winter months. Happy flying! Jouka
    52 points
  28. I promised a short video showing off some of the sound (and dynamic lighting work) we've done for P3D v4. In this video you will hear some of the new HD sounds we have added using our new custom built sound engine, which allow us to fine tune our new HD sounds and manipulate them by a whole range of camera and atmospheric properties. Our new power plant sound-sets, crafted using HD recordings from both an A320-212 with CFM 56 5B4's and the A320-232 with IAE 2527 A5's utilize our new infrastructure to it's full potential - and provide a truly unique sound environment that surpasses the limitations of the default sound engine of Prepar3D. The aircraft cabin has it's own unique sound-set, and depending on where you choose to sit in the cabin, you'll hear a variety of different sounds - buzz saw from the engines, the electric hydraulic pumps, lavatories flushing, even the slight knocking from the application of wheel brake. In addition to this, we have also added a complete set of cabin PA's that play throughout your flight and are fully integrated with the aircraft. These can also be routed through the Audio Control Panel on the flight deck to either the speaker system, or a chosen headset device. We've also added the ability for pilots to record their own announcements and have them play back in the cabin. And lastly, notice how our dynamic lights fade in and out. In our next set of previews, we'll be showing more of the updated VC in P3D v4 in 4K, with our new Spotlights redesigned for P3D V4.
    51 points
  29. Gents- this is not going to be product-related... and it's not going to be customer-related either. As it's a nice Sunday evening and I am sure everyone is now enjoying their favorite sim aircraft, I'd like to give a small word of thanks to the people who are selflessly answering your questions, queries and support requests. Our staff of volunteers who could actually be doing something else on their Sunday but instead they are here. Helping. Answering. Configuring. Managing the forums. Posting replies on FB. John. Tim. Karl. Norm. George. Fritz. Simon. You guys are awesome and I want to thank you... you deserve all our gratitude. The entire FSLabs development and QA team loves you... and I personally bow before you. Thank you again!
    50 points
  30. Here are a couple of shots of the VC, showing a handful of new features we've added. We are in the early stages of beta testing - I'll ask one of our beta team to take some 4K screenshots to share.
    49 points
  31. UPDATE: Available at http://wabpro.cz/A320/ Hey everyone, I am planning to publish my take-off performance calculation website in a few days. Figures are based on FCOM performance charts. Basically it downloads the current metar, finds the MTOW for current conditions. Once you enter your actual take-off weight, it calculates FLEX temp and V speeds for you. Let me know if you can think of something useful to be included so I consider adding extra things before I publish the website. Also, if any of you has access to real life take-off performance software, please let me know so I can verify I few assumptions I have having read the FCOM...
    48 points
  32. Hello all, I wanted to start this post by wishing you all a Happy New Year! 2016 has been a wonderful year for us at Flight Sim Labs as it was the year we finally released the A320-X for FSX. We wish to take a small moment to humbly thank you for the overwhelmingly supportive comments it has received and for the fact it's now a candidate as the Best Aircraft add-on for 2016 (feel free to vote for us here: https://fselite.net/editorials/fselite-2016-user-awards/ ). So let's talk about what's to come in 2017: The next update in line for the A320-X for FSX (which should come very soon now) will feature several bug fixes (autoland flare and the MCDU freeze among the more significant pain points with the current release) as well as improvements in handling (the "sticky" comma key for using the tiller and rudder pedals with a single axis). Expect a more complete list with the update itself which is now in beta testing, as Andrew already discussed. We'll continue issuing more updates down the line, eventually reaching a large "Service Pack" update which will include some generally wanted missing functionality (detailed WINDS, SEC FPLN etc). We're working on that as we speak, but to do that successfully, we've broken the tasks into smaller updates which fix bugs that you guys have identified, as well as improvements that you feel are necessary to enjoy the aircraft more or bring it in-line with customarily accepted "sim-isms" that might part with what happens in real life, but are helpful when the simmer is using the aircraft without all the necessary hardware that a line pilot has in the cockpit. What about the P3D version? Simultaneously with the testing of the FSX update, we're also beta testing the A320-X for P3D. The main part of the work is done, there are no 'major bugs' remaining that are stalling the release currently on our end. A few of you have wondered why we have still not released it therefore, even though the FSX version has now been out for a few months. We are also a bit frustrated with this, however the reasons for the delay could be understood if you also visit the LM forums to notice what's been going on with the latest v3.4 hotfix releases and the issues people are having with memory usage and DXGI_DEVICE errors. We feel that there are still some problems with the current version of P3D that is available and that until the good people at LM have had a chance to resolve those, we are hesitant to release a product only to start receiving complaints for situations which are not quite caused by our software. As such, we're working closely with them to do everything in our power to help them identify and correct those bottlenecks. We'll do our best to keep you updated with our progress on it. What's going on with the "cockpit builder" features? We had the opportunity to meet with several hardware vendors during our Lelystad visit in November. All of them were very impressed with the quality and depth of the A320-X and were very eager to have our software drive their hardware (or vice versa? ). We've had several discussions with the larger vendors and we are going to be providing interfaces to their hardware to allow such usage. Those interfaces will be available once we have the cockpit builder licensing ready and we expect that we can be providing hardware-specific add-on modules to our A320-X in collaboration with those vendors. So - if you are an interested vendor party or you are a customer who loves particular hardware, feel free to tell your vendor to contact us directly so we can discuss options. We are also looking into interfacing for freeware vendors (such as LINDA) to allow communication with particular hardware supported by those solutions, but we haven't yet decided the exact licensing specifics for this effort, so more to come on this, a bit later on. "And the forum? I can't easily find what I need there..." We have already taken steps to improve the forum structure - you may have noticed we cleaned up our main A320-X support forum, moved helpful "readme first" topics into their own sub-forum and are working hard to further improve or even add some new support facilities. We're examining several options to provide a more streamlined knowledge base as well as an open issue tracking system. You all know we're a small team, so this might take a little longer than we'd like, but please be patient with us as we are doing our best to provide the best experience for everyone! The work continues! Again - thank you all VERY much for your wonderful support in 2016 - we're looking forward to better serving your simulation needs in 2017 and beyond!
    48 points
  33. Hi all, I trust and hope that you've all had a good time during this holiday season - current conditions in Europe and the World don't make for much festive spirit (especially in my home country, where unemployment is so high and people's moods are very somber) but I'd like to always keep an optimistic view and think: The best is yet to come. This is certainly true here at the Labs, where our development has been strong and on-going and we're having a great time coding the A320-X. So - what have we been up to: We're (still) doing great. It's been a couple months since my last report and during this time, our development team has passed quite a few (internally set) milestones which bring us even closer to release. Soon enough (uh oh - did I say "soon enough"?) we will be requesting new applications for beta testers (This does NOT mean now - OK?) as our plans bring us closer to release. As you know, we're delving into previously uncharted waters in terms of Airbus logic development - I can safely say there's been no previous (or upcoming) product in the desktop simulator market which features so many details in wiring, systems and logic, and that is even without the features that are reserved for the training and professional platform releases. Discussions about "Anti-Ice / Packs effects on engine parameters", "pitch variability with trying to maintain 1g under high-altitude conditions", "fluidity of pressure drop when hydraulic systems are disabled" are in the daily regimen of our development process. As I promised in my last report, however, I will not delve into too much technical jargon this time. As is evident in your posts here and also in our Facebook page, you really want us to give you some new pictures of what our product looks like, so I hope the next few images will give you a glimpse of what we've done so far and what you're going to be seeing when we release our product. (We're still holding back some features for the moment, but those of you with a keen eye will notice some goodies we put together last year) As always, thank you for your continued support - we really appreciate your candid comments and welcome all your thoughts and well-behaved feedback. Talk to you soon!
    48 points
  34. Hello everyone, I am happy to announce that our latest update (v5.0.1.116) for the A320-X, A319-X and A321-X for P3D v5 (64-bit) is now live and available through our download page. This update should fix a performance issue noted in P3D v5.1 and also allows the installer to properly detect older P3D v5.0 versions. Note that we anticipate another update once Lockheed Martin release their P3D v5.1 hotfix in the coming days. As always, thank you very much for your continued support!
    47 points
  35. Please expect an announcement tomorrow (Wednesday 15th) - we want to showcase some of our latest work.
    47 points
  36. Another Friday evening preview (where did that week go!?). The first - preparing for departure back to Gatwick out of Munich as EZY13AQ. The airport was fully staffed on VATSIM and offering clearance via datalink, which our aircraft now handle in the new ATSU (Air Traffic Service Unit). Having requested the pre-departure clearance (PDC) via a separate request page, Munich replied with the departure clearance. This is how a lot of departure clearances are delivered to the aircraft these days. Our simulation will now allow customers to follow real world PDC/DCL procedures and we'll be sharing more details on how these can be used. The second is a shot taken on climb out of Arlanda, Stockholm this week - they've had snow showers all week; and here you can see after breaking through the cloud that the icing indicator, center post and windscreen wiper are iced up. These areas are key points of interest to pilots on the A320 series - as they suggest airframe icing is present and that counter-measures are required (wing anti-ice and engine anti-ice). Given that airframe icing is simulated authentically on the A320-X series - these are not just 'visual effects' to be ignored! The third shot is one of a repaint by John Tavendale on our new A320-X model. Fantastic work as always John! Enjoy your weekend guys. Stay warm!
    46 points
  37. Gents- this thread has run its course. If you have specific issues, please post in another thread in appropriate forums. Thank you for entertaining us for so long with this one until the Sharklets had released! Enjoy them now! We'll see you in the virtual skies!
    45 points
  38. We're very busy behind the scenes Here are a couple of shots from a test flight this afternoon.
    45 points
  39. We’re testing the release candidates for the A320 - so we’re close. It’s a fantastic update with a tremendous amount of effort from the whole team.
    43 points
  40. And yet... he is still able to fly them... how much does that tell you about him?
    42 points
  41. Hi gents, The incoming version of the 320/319 will feature what we call Advanced Aerodynamic Flight Model which enables flight characteristics for the first time in flight simulation. As we are able to inject our flight model data into P3D, we are able to model the lift, drag, momentum independently from the old inherited FS flight model architecture. This opened a wide range of possibilities and I will present a few ones corresponding to lift in usual terms. First, the "mach effect on lift": When a modern airliner airfoil gains mach speed, it's coefficient of lift curve CL vs AOA has its slope increasing a bit but in the mean time, the 1G When the airplane exceeds its critical Mach number, then drag increases, which can cause the aircraft to upset, lose control, and lose altitude. These two limitations all put together give you an accurate coffin corner rendition. It's the first time in FS such limitation is modeled because FS flight model engine just multiplies the CL vs AOA curve found in air file and multiplies it by a factor which is a function of mach speeds ranging from 0 to M3.2 with 0.2 increment. So mathematicaly it's not possible for standard FM to depict accurately that reduction of stall AOA with mach speed. I conducted several tests in XP and found it was not depicted as well. As we are not limited, we computed the CL vs AOA vs Mach curves we needed (same for drag and the rest :D) and use this hyper .air file to feed our AAFM engine. Second, the icing effect. Similarly to mach, icing does affect the CL vs AOA curve by reducing progressively stall AOA. This effect can be found in the literature as well. Initially it's not sensible, for the pilot. The fine pilot will just catch the drag is increasing by monitoring the required thrust to sustain its speed. Once the icing has become sgnificant, the stall AOA has greatly reduced (up to 30 % in some Wind tunnel test and 2D CFD studies). This is where it gets dangerous when the pilot has to execute gload demanding maneuver such as a turn or encounters a turbulence. In such a case, to sustain the apparent weight of th acft, pilot has to pull aoa to get the corresponding CL. By doing so, the AOA might come into the iced stall CL vs AOA range and leads to a buffet or even worse a stall. This also is the first time it's correctly model in FS. Usually, a coefficient is simply applied to the CL affecting the whole CL vs AOA curve. SO the pilot can spot in early stage of icing he has to pull up to sustain apparent weight. Third, the high lift devices. High lift devices regroups slats and flaps which have complete different results on lift characteristics but are very complementary. While Slats are not changing CL vs AOA slope, they do extend the stall AOA. Flaps however increase the camber of the airfoil reducing stall AOA but shifting up as well the CL vs AOA curve. The configurations are made so that the mix of slats and flaps are optimized in terms of lift, and we modeled indepedantly slats and flaps effects to depict what I explained above. This work becomes really interesting when you simulate an hydraulic failure leading to slats only or flaps only configurations... In FS, slats and flaps are modeled the exact same way and you can't change the shape of the CL vs AOA curve at will. Of course you will see on the external model the high lift devices in an awkward positions, but if the developper didn't bypass P3D FM engine, then in backstage, there are huge chance you still have all your flaps and normal flight characteristics. I will stop here, because I think I have lost a majority of readers, as this topic is not as sexy as beautiful graphics or functionnalities, but I am very proud of what we achieved and am happy you will soon be able to put your hands on it. Fly safe ! Philippe
    42 points
  42. Gents- another quick update on status, as it stands at the moment: As I mentioned before, we have been tracing an issue that we considered important enough to fix before allowing a release to go out (it is a transient bug in our electrics network wiring logic that, as all transient bugs, is very difficult to pinpoint and trace). Some of you might have noticed it in streams that our beta testers were showcasing over the past few days. We believe that we might have found the cause for this bug and are shortly going to produce a new build to our beta testers to play with, that should actually fix this issue. As with any bug fixes of this nature, while we're very anxious and eager to release this to you as well, we should allow our beta testers enough time to test this release, before it's deemed "fixed". I will give you another update when I have more news.
    42 points
  43. Thank you ALL for contributing into this thread - the simple fact of the matter is (as we've said in other posts) - the update is in its very final stages of testing and should be released very shortly - as it was NOT a simple "compatibility update" however and includes significant updates (one of the most major ones as we explained in Cosford, being the revamped ELAC which you all should find very improved), it takes a bit longer than expected. That said, we've put mechanisms in place whereby if this happens again in the future (a new HF), we should be able to issue simple compatibility updates much faster (without any other code having to be implemented with it too). Thanks again for your feedback - we ARE listening! (Let me lock this thread for now, I'll reopen it when the HF update is released).
    41 points
  44. No - the A320-X will form the base product (I.e it will be required). The expansions will each be priced at a fraction of the cost of the A320-X. We're quite excited about these expansion titles. Technically speaking, no one has offered a fully simulated A319 or A321 expansion that offers a true-to-life rendition of these individual airframes; they've always been 3D models using A320 systems/flight models. For the first time, people will have the opportunity to experience the intricate characteristics of the different aircraft in the A320 family. The A319 is noticibly more slippery in the air - and the A321 has significant differences in the fuel and flight control systems. Each variant will have its own individual engine performance model (example the A319 will have IAE V2524-A5's and CFM 56-5B7's - derated/higher pressure ratio from those on the A320); different drag, lift, weight and balance models. We'll be posting some previews soon
    41 points
  45. The EFCS has received a significant update encompassing months of work and testing - none of the autopilot or flap ballooning issues will be a concern going forward. You guys will really enjoy the next update. We're finalising the release candidate today and anticipate a release within the next couple of days.
    40 points
  46. Hi Danny, yes the plan will be to allow streamers to continue flying the sharks and also allow our beta team to discuss/share screenshots. Right now the teams are focussed on the release path, a complex and intricate phase of the project cycle and one that requires a lot of care and attention to deliver a successful product launch. Something we pride ourselves on - and that our customers have become accustomed to.
    39 points
×
×
  • Create New...