JGregory

You need to assign a keystroke or button to the release switch command. That way you can "hold" the switch while using the gust lock. This was already discussed here.

Jim, Isn't this the same question you asked here?

No, the scripts should be updated in the download that you received with your purchase.

AJ, While I appreciate your input you are missing the point regarding Vinny. He seems to need to post things that are simply irrelevant or are a rehash of what has already been said. We (developers) need to monitor the forums for REAL problems, which takes time. Someone who posts just for the sake of posting, repeats already posted problems (after the issue has been solved), posts something that is completely irrelevant, or posts something that makes no sense whatsoever (see Vinny's post (#9) above) is a waste of our time. We try to be tolerant of language barriers, etc. Non-English speakers also need to be tolerant and try their best to post in a coherent manner. Repeat offenses tells me the poster is NOT trying hard enough and not listening very well. I don't think the issue with Vinny is one of not speaking English, but rather something else entirely.

The systems in the Saab will affect the pitch in a stall situation (yoke pusher). Otherwise the systems DO NOT affect the pitch or yoke in any way. So, if your not in a stall condition, I don't think the Saab is creating the issue you are experiencing.

Roger, I just tested this with the waypoints you provided. I cannot reproduce the problem. See attached screenshot. This is frustrating. It seems to be very isolated and to date we have not been able to reproduce this behavior on our systems. Are you using any other plugins?

Jim, I did some brief testing and cannot reproduce this as you described it. What you are describing would obviously be incorrect, but I can't make it happen. The lateral mode should change between VOR1 and VOR2 (which it did in my tests). Are you sure when you selected NAV2 that it was a valid frequency and within range? The TTG only indicates the DME time of NAV1 for the pilot side and NAV2 on the copilot side. So, selecting NAV2 will cause the TTG to show "---" on the pilot side. "---" will also show when the nav aid is out of range. If you can provide more details I will test this again. Please tell me where you were flying (ie. airports from and to), VORs selected and their frequencies, altitude, etc.

Vinny, If you are unsure whether or not what you want to post is relevant then don't post it.

Vinny, How can you say that when you said this… "I'm having the same fuel x-feed problem like what eMko is having! Thanks!", that you really meant this…"I meant to say is the strange fuel x-feed is fixed in Saab 340A v1.1?" These two sentences are not even remotely the same! Please be sure to read the entire thread before you post anything and make sure that what you post is relevant. In addition, you are apparently still confused. The x-feed issue was discovered and fixed AFTER the v1.1 update was already out. It will be part of the NEXT update.

Vinny, I'm wondering why you thought this post was necessary? I had already acknowledged the issue and fixed it. You telling us that you have the same problem does not contribute in any way.

They are lights.

Vinny, Cameron was asking if there was something lacking in YOUR experience with the simulation regarding the inverter. He was NOT asking what Goran thinks.

I am sure they will see this thread and respond accordingly.

Vinny, I was not involved in the development of the DC3.

Vinny, I have tested this many times in several different ways. The sounds are working as they should.

Vinny, The systems in the Saab are VERY complex. Your question is too vague… what happens depends on WHAT systems are on/off/broken. I suggest you experiment and find out how things work.

That has been my experience as well. Thanks. It's just not as easy as you make it seem.

A cross-gen start of the second engine DOES NOT guarantee that a GPU was not used. There are many other examples on YouTube and elsewhere of Saab engine starts with GPU starting the first engine and cross-gen start of the second. I'm glad you now realize that you were incorrect when you said... Obviously (as per the video) the Saab can take that long to start. Just saying

Use the pop-up throttle quadrant to view the positions of the throttles and condition levers.

This will be changing…. no promises as to when.

Are you referring to the physical animation of the dials, or the speed at which the frequency changes?

The pixel drag works much better.. it just requires a different setup by the developer. We will revisit this.

The radio frequency manips are "drag and hold"… at which point the frequency will continue to increment until you let go. No need to keep dragging.

With regard to the radio XFR/MEM switch… if the animation of the switch is "reverse" to the direction you are dragging then that is an XP manipulator problem that we have no control over. If the animation is correct (moves in the direction of the drag) but the functionality is changing intermittently then that is another problem. Let me know which it is.

No, it is not possible to assign a keystroke or button to the altitude preselect.