Jump to content

Take Command! Saab 340A v1.6.1 Update Released!

Cameron

By Cameron
in Saab 340A

 Share

Recommended Posts

Cameron Mentor

Cameron

Posted
Posted

Hello All,

This will serve as a formal forum announcement that we have released the version 1.6.1 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.6.1 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:

  • First Officer RMI Needles (wrong variable assignment)
  • Autopilot Climb Mode Speeds (not updating XP Dataref properly)
  • Autopilot IAS Mode Speeds (not updating XP Dataref properly)
  • Vertical Sync
    • Fixed bug causing crash when Vertical Sync Button was pushed
    •  Adjusted logic to set XP Dataref in Vert Sync Mode
  • CRS1 Knob (corrected OBS command for CRS1 knob when NAV2 is HSI Source)
  • Door OH Annunciators not functioning (wrong variable assignment)
  • Charts (Fixed overlapping Mesh)
  • EHSI From/To Flags (Fixed incorrect logic
    • Note: Per the AOM the from/to flag is never displayed on "second course" of the EHSI.
  • Altimeter Needle Animation (wrong Dataref assignment)
  • System Temps (Verified all for accuracy Deg F vs. Deg C)
  • EHSI Nav Mode Annunciator(s) (LOC vs. VOR)
  • CTOT (Left Engine not responding properly on CTOT knob decrement)
  •  Right Engine Condition Lever
    • Fixed right CL logic for engine start.
    • Fixed Electrical System Relay and Bus logic for engine start (Motoring/Direct)
    • Changed Engine Start Switch Logic (Motoring/Direct)
  • Starter Motor (fixed sound logic)
  • Cargo Door Handle (changed animation init value
    • Cargo Door (changed animation speed)
  • Main Door (changed logic to prevent closing if stairs are deployed)
  • Changed default prop disc texture(s) to .png (xEnviro bug)
  • Standby VOR (fixed logic to write per frame)
    • NOTE:  From/To Flag is reversed and will be fixed next release
  • IAS Mode EADI Annunciator (flashing continuously)
  • Engine Heat Visuals (added back in)


Additions:

  • Brake (hold) Commands
  • Gear Uo/Down Commands
  • Logic to allow binding flaps control to joystick (lever)
  • ITT Temps (changed logic to include ambient)

 

Reported as bugs. These are NOT bugs!...
  • Use of Experimental Flight Model
    • NOTE: The experimental flight model is NOT required for the Saab. As of 11.52 you can use the EFM if you choose.
  • HGD/SLAVE BUTTON
    • Previous versions of the Saab modeled this incorrectly because we didn't have accurate Flux Detector errors. The HDG/Slave button(s) in v1.6.0 now provide slaving to the flux detector for error correcrtion.
  • Nosewheel Tiller
    • There seems to be some confusion on how this is implemented. We have provided two (2) options (selectable in user preferences):
    1. Use Tiller Checked (ON) - This allows you to use the in-cockpit tiller (manipulator) to steer.
    2. Use Tiller Unchecked (OFF) - This allows for mouse/hardware steering.
    • In addition... steering is only available when the following criteria are met
      • On the ground (WOW)
      • Hydraulic PSI >= 1500
      • Aircraft is moving
      • Tiller is engaged (depressed)
 
  • DME not indicating distance on ILS
    • The specific ILS being referred to did not have DME.
 
  • C/L not syncing with hardware when moving the hardware levers fast
    • You must keep your hardware in sync with the manipulators (use the TQ viewer)
  • GPU available with chocks/no brakes
    • We will consider this feature for v2.0

 

INSTRUCTIONS:

The engine start procedure has changed slightly and now exactly matches the AOM. 

After you have established how you are going to provide power for the start, the two sequence options are as follows:
 

MOTORING START:
        
  • Ignition Switch to "OFF"
  • Condition Lever to "FUEL OFF"
  • Move and Hold Start Switch to appropriate aide
  • Check Engine Stabilized (approximately 20% Ng and ITT Below 175˚C)
  • Move Condition Lever to "START"
  • After 1 second (but within 2 seconds) set Ignition Switch to "NORM"
  • After Light-Up release Start Switch
(If you want to see detailed example of a motoring start just use the Auto-Start Feature and follow the steps)


DIRECT START:
  • Move Condition lever to "START"
  • Move Start Switch to appropriate side and hold for approximately 2 seconds
Monitor Power Plant parameters accordingly.

That's it! Once the engines are started you can proceed with the rest of the necessary steps to go flying.
 
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.
  • Like 1
  • Upvote 1
JGregory Apprentice

JGregory

Posted
Posted
1 minute ago, Pedro Sousa said:

V. 1.6.1

There are still a few things which should be corrected, but SAAB 340A is now an excellent add-on!

I found something... See the piture.

should_be_corrected.jpg

Please provide the frequency you had selected for Nav1.

StuartC Newbie

StuartC

Posted
Posted
3 hours ago, Suprex said:

Hello, the parking brakes "On" works only mouse (no keyboard "V"). Correct?

The attached FlyWithLua lua script will create a command which you can bind to a key or joystick button to toggle the parking brake.

les_sf340a.lua

Tim013 Newbie

Tim013

Posted
Posted

Just did a flight from Sioux Falls to Minneapolis.  Everything needed to complete the flight is now in place with 1.6.1.  The little touch up stuff like brake, or LOC vs VOR, will be nice, but honestly not that important to me.  Autopilot worked great, PL's are good, CL's are good, CTOT works nicely.  The ground handling with the new power controls is a joy to taxi.

  • Like 4
StuartC Newbie

StuartC

Posted
Posted
8 hours ago, Robster said:
  

where we put this parking brake file in which folder?

FlyWithLua can be downloaded here, https://forums.x-plane.org/index.php?/files/file/38445-flywithlua-ng-next-generation-edition-for-x-plane-11-win-lin-mac/ .

You place the script in the FlyWithLua plugin's Scripts folder.  If you load straight into the Saab you will then find a FlyWithLua command with the description "Toggles the LES Saab 340A parking brake on and off." which you can bind.

Don't worry, I'm sure LES will address this and the missing GS indication soon.

flyingtost Newbie

flyingtost

Posted
Posted

Great update! Thanks a lot! :)

 

The "hold brakes max" and "hold brakes regular" functions seam still not be working for me.... left and/or right brakes can be assigned, but i use a Logitech Extrem 3D Pro, where I use only one button for both brakes. (with the above key binding).

Am I missing something?

If not, any chance this could be implemented in the future?

 

Many thanks,

best regards,

Tom

accentedpassingtone Newbie

accentedpassingtone

Posted
Posted

V1.6.1 - Glidepath symbols are missing from flight displays when legitimate ILS frequencies are dialed in Nav1.  Also, when an ILS freq is dialed in, it should say “LOC1”, not “VOR1”.  The autopilot seems to still recognize a glide slope and captures it when coupled, it’s just that the symbol is missing from the screen. 
 

JGregory Apprentice

JGregory

Posted
Posted
1 hour ago, accentedpassingtone said:

V1.6.1 - Glidepath symbols are missing from flight displays when legitimate ILS frequencies are dialed in Nav1.  Also, when an ILS freq is dialed in, it should say “LOC1”, not “VOR1”.  The autopilot seems to still recognize a glide slope and captures it when coupled, it’s just that the symbol is missing from the screen. 
 

Please review the forums before posting about potential bugs.  The issue with the ILS symbology has been mentioned in these forums many times.  It's a known issue and will be fixed in the next update.

  • Upvote 1
Candid Newbie

Candid

Posted
Posted

The authors are great! Quickly fix bugs and communicate with virtual pilots. Thank! But, they broke the animation of the propellers !!! This is bad.

saab.jpg

mjrhealth Community Regular

mjrhealth

Posted
Posted
11 minutes ago, Candid said:

The authors are great! Quickly fix bugs and communicate with virtual pilots. Thank! But, they broke the animation of the propellers !!! This is bad.

saab.jpg

Why????

Candid Newbie

Candid

Posted
Posted

Feel the difference))) And also this sluggish twisting of the knobs for setting the height, speed, etc. When you need to quickly change something, you will not succeed. You will rotate the mouse wheel until you completely erase it. Why not take the best from others? I specially fly on the Saab 340 from Сarenado for comparison. t.

saab.jpg

mjrhealth Community Regular

mjrhealth

Posted
Posted
13 minutes ago, Candid said:

Feel the difference))) And also this sluggish twisting of the knobs for setting the height, speed, etc. When you need to quickly change something, you will not succeed. You will rotate the mouse wheel until you completely erase it. Why not take the best from others? I specially fly on the Saab 340 from Сarenado for comparison. t.

saab.jpg

Dosnt take long to set Altitude as for Decision Height it has being raised they will address it, and I dont know how you could possibly compare Carenado to this. There are other minor issues being addressed.

Candid Newbie

Candid

Posted
Posted

And in what speed can you wind up the altitude from 0 to 20,000 feet in turbulence? I do not scold the model and do not say that Karenado is better. Here, after all, a forum, right? It's just that Karenado has a more user-friendly interface in models. And here, for the sake of realism, they sacrificed ease of use. That's all.

  • Like 1
Guest
This topic is now closed to further replies.
 Share
Go to topic listing

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...