(...)

I still think some of the computed speed values in the AXE are a little low (including VAPP), so I tend to increase by 5% or so.

 

 

Good call! Managed speed on final seems a bit ... static to me, too ...

This wouldn't affect roll rate. The whole point of Normal law is to give you the same predefined roll rates and pitch authority with different speeds, angle of attack, gross weight etc etc.

 

.....in the real Airbus yes, but perhaps not in this simulation.

This wouldn't affect roll rate. The whole point of Normal law is to give you the same predefined roll rates and pitch authority with different speeds, angle of attack, gross weight etc etc.

 

Edit - since we are talking about FS and not the real thing your above point could be very true.

 

 

Got caught by my own Airbus Gotcha's - I have to stand corrected for that one!!!

Good call! Managed speed on final seems a bit ... static to me, too ...

managed speed on your final approach will always give you Vapp, Vls + 5 knots in config full. It is up to you to enter the correct speed additives deepening on wind conditions. If you fly the standard Vapp on approach chances are you flying the wrong speed unless winds are calm.

Found some document that reads differently. Not sure, though, whether my reference is correct and up-to-date ...

Here is a nice simple explanation I found online. It also briefly explains ground speed mini.

 

 

The actual VAPP value is calculated as follows:

 

Assuming the tower reported steady state wind is entered into the MCDU APPR page.

 

 

 

VAPP = VLS plus 1/3 of the tower headwind component. The value of VAPP is limited so that it is never less than VLS + 5 or more than VLS +15.

 

As a result, VAPP is increased above its minimum value for runway headwinds above 15 knots. VAPP correction is not increased further for headwinds exceeding 45 knots.

 

The groundspeed mini function does not change VAPP, instead, it increases the target (bug) speed when the headwind is greater than the expected landing headwind - the wind that VAPP was based on. This is done so that if this greater headwind disappeared all at once (windshear), the airplane would be at VAPP not VAPP minus the loss of wind.

That sounds good.

 

Just checked in the AAX: Vapp doesn't change with whatever wind is entered - simply stays at Vls+5 ...

I had the throttles working fine since the aircraft came out (after resolving a no reverse thrust problem), but After installing V1.1 I'm not able to get the throttles to work at all despite trying everything in the Aerosoft forums and instructions. In fact, they're locked into Idle. If I move the VC Throttle Levers with the mouse, they immediately return to Idle. 

 

I'm far from a noob, and this product has now become more trouble than it's worth to me. I'm just not going to spend several hours figuring out the correct settings and tweaks.  Instead I'll jump into a model that actually works when it's installed.

 

Besides, the aircraft is only BARELY compatible for those with multiple monitors and a real pain the rear to use with them. Enough people run multiple monitors these days, it's not like it's something new.  So why didn't Aerosoft provide panels for multiple monitor users to prevent the Windows Processing bug that trashes one's frame rates?

 

 

What the HECK is with Aerosoft hard binding the Virtual Cockpit key command to the Dash View which can't be changed (moved around) with the Hat Switch?  Man, that should have never gotten past Beta and the person who did it, well, let's just say that I can't begin to understand what they were thinking. Someone did the same thing with the Dash 8, and did it exactly the same way. Same person maybe?  Just fundamentally wrong on so many levels.

 

Just because something is new and different, doesn't make it worth the cost, or worthy of praise. A lot of Captain Sim users found that out the hard way.

(...)

Edit - since we are talking about FS and not the real thing your above point could be very true.

 

 

Just checked the AAX FBW with the roll and pitch axis: I cannot exactly determine constant roll rates with constant joystick deflection - but it really feels that way!

 

And it keeps up the turn rate without joystick deflection (neutral sidestick) - that's the FBW overpowering the airframe stability for sure!

Did they add wings, so you can see them from the VC, or is she still wingless from the VC?

I had the throttles working fine since the aircraft came out (after resolving a no reverse thrust problem), but After installing V1.1 I'm not able to get the throttles to work at all despite trying everything in the Aerosoft forums and instructions. In fact, they're locked into Idle. If I move the VC Throttle Levers with the mouse, they immediately return to Idle. 

 

Dave, do you only use the mouse to move the throttles? The AAX throttles are supposed to be controlled by a hardware throttle (axis). Under certain circumstances they can be controlled by key commands, too (F1 for idle, F2 for reverse, after touchdown, for example).

 

I'm far from a noob, and this product has now become more trouble than it's worth to me. I'm just not going to spend several hours figuring out the correct settings and tweaks.  Instead I'll jump into a model that actually works when it's installed.

 

Besides, the aircraft is only BARELY compatible for those with multiple monitors and a real pain the rear to use with them. Enough people run multiple monitors these days, it's not like it's something new.  So why didn't Aerosoft provide panels for multiple monitor users to prevent the Windows Processing bug that trashes one's frame rates?

 

I've just tested that and I have to confirm a fps drop, when dragging the MCDU, for example, to a 2nd monitor.

 

What the HECK is with Aerosoft hard binding the Virtual Cockpit key command to the Dash View which can't be changed (moved around) with the Hat Switch?  Man, that should have never gotten past Beta and the person who did it, well, let's just say that I can't begin to understand what they were thinking. Someone did the same thing with the Dash 8, and did it exactly the same way. Same person maybe?  Just fundamentally wrong on so many levels.

 

That's true for the "2D clone view" reached via F9. Pls. try 'CP main panel', for example, for panning with the hat switch.

 

Just because something is new and different, doesn't make it worth the cost, or worthy of praise. A lot of Captain Sim users found that out the hard way.

I'm very reluctant to put those two developers into the same camp, Dave ...

 

I had the throttles working fine since the aircraft came out (after resolving a no reverse thrust problem), but After installing V1.1 I'm not able to get the throttles to work at all despite trying everything in the Aerosoft forums and instructions. In fact, they're locked into Idle. If I move the VC Throttle Levers with the mouse, they immediately return to Idle. 

 

I'm far from a noob, and this product has now become more trouble than it's worth to me. I'm just not going to spend several hours figuring out the correct settings and tweaks.  Instead I'll jump into a model that actually works when it's installed.

 

Besides, the aircraft is only BARELY compatible for those with multiple monitors and a real pain the rear to use with them. Enough people run multiple monitors these days, it's not like it's something new.  So why didn't Aerosoft provide panels for multiple monitor users to prevent the Windows Processing bug that trashes one's frame rates?

 

 

What the HECK is with Aerosoft hard binding the Virtual Cockpit key command to the Dash View which can't be changed (moved around) with the Hat Switch?  Man, that should have never gotten past Beta and the person who did it, well, let's just say that I can't begin to understand what they were thinking. Someone did the same thing with the Dash 8, and did it exactly the same way. Same person maybe?  Just fundamentally wrong on so many levels.

 

Just because something is new and different, doesn't make it worth the cost, or worthy of praise. A lot of Captain Sim users found that out the hard way.

Well, for MANY people and may I emphasize MANY again - since the ratio of sold copy to the number of people reporting a issue is extremely low, it work well out of the box. 

 

I am sorry to hear of your issues, but venting your anger/disappointment and not wanting to find a solution to you problem is well, kind of pointless to rant it here.

 

If you done a little search, you would have already found many answers to your multi monitor problems. You are wrong to say that many users have adopted multi monitors and hence it should be the de facto standard.  (and yes I have the figures on who uses it, and who dont)

 

What I strongly advice you to do is to simply take a chill pill, come down to the AS forum, and I will help you in any best way I can. 

 

Did they add wings, so you can see them from the VC, or is she still wingless from the VC?

 

 

Sorry, only the lift of the wings is simulated in VC view ...   :rolleyes:

Shame as when you have ITracker I find it useful and nice to look back out the VC window.

The Q400 added wings and props from the VC in there first patch. it's very helpful to see if ice is forming and to then turn on Anti Ice, just like a pilot would do IRL.

Aerosoft could have made it an options as people without Itracker flying with there eye point fixed in a vice like grip might find it pointless. But just adding a bit of wing like you would see in a real A320 is a no go for them.

Glad to read with 1.1 it is finally working for all the fans.

 

 

JoshuaC, on 09 May 2013 - 12:39 PM, said:

You are wrong to say that many users have adopted multi monitors and hence it should be the de facto standard. (and yes I have the figures on who uses it, and who dont)

wow could you tell me if I have 1 or 2 or even 3?

wow could you tell me if I have 1 or 2 or even 3?

Sure. 95% Chance you have only a monitor, 3% Chance you have 2 monitor, and 2% you have other configurations.