Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/06/2017 in all areas

  1. I just want to let you guys know that you have at least one customer who is happy that you are actively working to bring your excellent product up to date. I am enjoying your work and look forward to whatever you can bring to the platform - after all, we bought an XP-10 aircraft and you are working to make it work across another completely different program just because you care about your customers. Thanks, John
    3 points
  2. The above question illustrates the challenge for XA in developing a robust installer. The installers used have to be programmed to handle a wide variety of cases and some unknown number and type of files that may or may not be changed by the IXEG team in the future. This requires some time of fore-thought to determine what will be required by users and ensure those cases get coded into the installer. Bandwidth on this level is quite expensive so just downloading everything every time is not a valid option...so crafting a "smart installer" is where the time is going currently. The payoff will be a robust and quick installer for future updates. This whole transition to V11 has caused a bit of a "traffic jam" in our infrastructure and that's all this is....best to proceed through it cautiously lest we end up missing something obvious. Once past it, we expect a clearer road for updating. -tkyler
    3 points
  3. Hello All, This will serve as a formal forum announcement that we have released the version 1.4 update for the Take Command! Saab 340A. All customers who have purchased the Saab 340A up till now have been sent an e-mail by X-Aviation with complete instructions on how to obtain your update. We have made this a very simple process! For those that purchase the Saab 340A from today forward, your purchased download will already be updated to version 1.4 for you. What if I didn't get the update e-mail? If you did not receive your update e-mail don't fret! X-Aviation has updated our system to allow all customers to update with ease, regardless of whether you received an e-mail for the update! Here's what to do: 1. Login to your X-Aviation account here: https://www.x-aviation.com/catalog/account_history.php 2. Find your original Saab 340A download and re-download the file. It will download as the latest version! The following is a list of additions/fixes included: What's New / Changed: Fixed bug in Fire Extinguisher logic. Added XP version 11 incompatibility warning. Your feedback about this update in v10 will help us fix bugs prior to release of the patch in X-Plane v11. Adjusted fuel logic to fix engine “run-on” with non-start. Fixed bug when pressing Vert Sync button on yoke. Added restriction to ALT selector init. Condition Lever Joystick assignment has been redesigned. Users can now simply assign their joystick(s) to “prop1” for the left condition lever and to “prop2” for the right condition lever. Increased number of (Nav) charts to 10. Adjusted GPWS Mode 4A logic to prevent inadvertent “TOO LOW GEAR” warning on second and subsequent takeoffs during same sim/Saab session. Fixed incorrect scroll wheel mapping that appeared when displaying WXR on CoPilot EHSI. Added User Pref for GPS course pop-up display. ACF hydraulic system logic adjustment Changed engine rotation to allow for Laminar torque fix. Changed logic for prop_mode assignment Revised logic for hydraulic relay and pump Added new logic for nose wheel steering (requires Tiller to be in “ON” position to enable steering and restricts steering when aircraft is not moving). Fixed bug where the gear was able to be extended/retracted with the locking pins where still in place. Fixed bug in right engine throttle logic. Fixed bug in right generator annunciator logic. Fixed a bug in the CONFIG system preventing proper warning. Fixed bug in cockpit hatch animation. Fixed bug in prop disc rotation code. Changed hydraulic qty gauge animation. Changed font path reference for G530 Fixed bug in sound engine reporting false errors. Modified logic for ITT to simulate asymmetry between engines. Transponder manipulator logic fixed to prevent digits greater than 7. Scripts version is now written to the logs. Fixed drawing of OpenGL text/lines onTQ Viewer GUI . Fixed bug where wind vector was not displayed on the CoPilot EHSI. Corrected HSI NAV1 and GPS course handling and interaction. OBS OPERATIONAL NOTE: OBS Mode must be TURNED OFF when the Saab is loaded. If it is ON you will need to turn it off and then reload the aircraft. In addition, using the OBS button on the GPS pop-up will cause conflicts with the Saab manipulator systems, you should only use the OBS button on the 3D Garmin 530 in the cockpit. Not following these instructions will cause improper operation of the OBS (Course1) dial and the EHSI (Course1) display. These requirements may be lifted in the future when we get the needed DataRefs from Laminar. As always, thanks for being a customer with X-Aviation. We appreciate your feedback and support! Enjoy these latest updates, and stay tuned to the forum as we continually announce the latest happenings.
    2 points
  4. This has always been this way, just as in the real aircraft.
    1 point
  5. theraygan... if you want to discuss the "why" of LES decision with regard to updates, that is fine. We have our own business model and have created an upgrade path that we feel is best for our customers If you don't "like" the path we have taken, that is fine also. However, we ARE NOT Flight Factor. So don't bring that comparison here as it does not apply.
    1 point
  6. Given your latest posts, "I think" we have a miss understanding what -compatibility- means. compatibility = it has been tested and certified by the developers for loading properly, it doesn't crash, all systems are fully working, it can be used on the sim with no trouble. full xp11 bird = it has been reworked as much as required for the aircraft perform spot on to the manufacturer performance charts on all aspects, it will also take advantage of all latest sim tech like PBR rendering Going back to your FF / IXEG notes, both are under -compatibility- status, both have released updates to assure they are compatible to xp11, BUT both are still working on full xp11 bird updates. Go & try to compare climb ratios, or speed brake performance, etc. etc. etc. xp10 vs xp11 and you will be quite surprised about the findings. Go and re-read 767 xp11 policy carefully from FF which was released under XP10 as IXEG737 and as SAAB340 to compare apples to apples. Whats the deal about SAAB 1.4 and 1.5?? as you said, they look the same... yes! 1.4 is fully tested by the developers on xp10 and it introduces fixes for all known issues for their large user base still here (they didn't perform any testing on xp11 at all, if you use it on xp11 is entirely at your own risk) 1.5 is the same than 1.4 yes, but fully tested by them on xp11 and applied any fixes required to make it load, not to crash, systems working, etc. Yes it could happen nothing is required, or minimal, and in the end it looks the same than 1.4 for xp11. 2.0 is when they will develop and release a full xp11 bird. they will recalibrate the entire model to guarantee it performs by the charts, they will take advantage of latest rendering stuff.
    1 point
  7. Consider they have to take care of a broad audience, preferences, simmer priorities. There are a lot of people that do not care on realistic aircraft performance by the charts and just wanna have fun, some people can not read/care about performance charts, neither are pilots on real life to feel the difference on an aircraft performing right or not. If you look around the forums a bit, you will notice there is a large user base that switched to XP11 from the early public beta1 trying to load, putting patches via planemaker, sharing workaround on the forums to make the xp10 birds load and just have fun. i do not see anything wrong from them delivering a compatibility patch for those, so all systems are functional. This is what most developer are/have been doing by the way to attend than demand on the first run. Release a compatibility patch, not fully redone birds in the meantime. Having said that, there are other people (like myself) were having an aircraft that perform by the chart is all what counts. For those of us, we are awaiting full XP11 birds from all developers we like. Delivering/retuning an XP11 aircraft by the charts requires a lot of work, because the ground model changed, drag model changed, engine model changed, flight dynamic changed and also the cosmetic thing due to the new PBR rendering engine. If you follow laminar's developer page you will also notice Laminar is still tweaking XP11 model release after release, they are not done yet. This makes developers lives even more complicated to be spot on over a moving target. They are not saying you have to pay and wait 1-2 years! The way i do understand this: 1. If you are still having XP10 as your primary sim (large user base), this is the newest 1.4 update that fixes/improves several known issues for the best experience. 2. If you are an xp11 early adopter that wanna use the bird on xp11 no matter what, a basic compatibility fix is coming (lot of simmers are on this category as well) 3. if you are awaiting for this aircraft being full xp11 performing by the charts and having latest tech on rendering you are set for 2.0. (given the implications i wouldn't expect this to be fee, maybe a discount for existing customers, but this is just my pure assumption not any statement). You can jump onboard at the timing you feel confortable to given the facts if you are not customer already. just my 2 cents
    1 point
  8. It's been 5 hours since the update was published. Jim is asleep right now, and is not even aware of the update being out. Please just exercise a little patience. As soon as he gets up, he'll check the forums, see the issues, and get them fixed. The XP10 update was always going to be released. We've made many mentions of this, and no one was objecting. On the contrary, we were getting praise from many people for not forgetting the XP10 users. The XP11 update will not take anywhere near as long as this update to release. I'm not the programmer, so I'll let Jim address this when he see's the forums. Regards Goran
    1 point
  9. especially when ver 1.3 worked with copied GNS430 from xpl10 "just fine". I dont know anybody who is flying xpl10 these days. It's dead.
    1 point
  10. After resetting my SMP settings, everything appears to be working again. SMP really is a great piece of kit, good job Sundog team. Shots below from a hazy and hot summer evening here in the UK. CAVOK with random patches of cloud, couldn't have been a better portrayal. Flown at daytime to enjoy the landscape.
    1 point
  11. Yes. Mr Cameron please close the thread as it will turn into world war 3 again. Obviously, it is very disappointing that software delivery is severely slowed down by a vendor but there is no other way about it at the moment. Let's wait
    1 point
  12. Is that it? That's all that's needed to make it cozy??? Some dust and a few scratches on some used leather seats? Gotta be faster than that, Radek. I did that (and a lot more) months ago. Note: Some mesh shown is not accurate and has since been fixed. Disregard the "shine". That's a specular issue that will also be fixed, depending on how it looks with the exterior around the seats and cockpit.
    1 point
×
×
  • Create New...