Scarp

If it's the same policy as with their xp10 vs xp11 models, then you'll have to buy them all over again from what I can gather. Xp= X-plane.

I know, there should have been a "easy access" hidden clickspot so you didn't have to look down (for us using panning with the joystick it takes forever) between the seats or uses key combinations. If you have a spare button on your controls you could tie it to SHIFT + 2 too. I think I wrote the wrong key comb earlier ha ha, it should've been SHIFT instead of CTRL. Just thought I'd throw it out there so before I get chastised.

I use the default key combination CTR + 2 (or maybe it was CTLR + 3) if I remember correctly. Haven't used the sim in a while so I don't remember exacty.

Use high power setting only when you're ready for take off. Otherwise ground idle. Same thing after landing, ground idle can be set once below 35 kts. (if I remember correctly, if not use 30 kts

@Mik75 The via/to and scrolling is a feature of airbus, as real as it get's Startup: check that APU and APU bleed is on + turn the button below the actual individual engine starters to "start". Also make sure throttles are at idle. Climb: Did not notice anything out of the ordinary, it accelerates to 250 below FL100 and continue to accelerate above. I do recall that the previous version had a bug where the spoilers got deployed when you armed them, but there was no indication in the cockpit and if I remember correctly neither visually visible from the outside either. So if you experience problems, try and hit the spoiler button on the keyboard and quickly retract them again. If the speed picks up then, the bug persists. I don't think it's a common bug for everyone and I don't know what triggers it. But so far I haven't experienced it in this version. Managed decent: Here I see no improvment from previous versions, and this is my biggest critizism. I dont even think they have omplemented this yet, which is beyond me considering all these years gone by (been customer since 2012). In the real bird you usually start TOD 5-10 miles out. Then the aircraft will go into a shallow decent until it intersects the vertical path. But not this bird, for all intent and purpose it dives down to the first restriction (if there are any) or down to the altitude entered in the AP regarless of the vertical profile. This means dangerous flying in mountain areas. I also suspect that the logic between mac and kias during decent isn't working either, coz my plane slows down to 250 kias no matter what cruise altitude I'm at and keeps it all the way down to activation of the approach (in the MCDU). In addition I observed on my last flight some erratic behaviour as far as the pitch and VS goes. It was bobbing up and down a little too much before it settled. So either something got messed up during installation or, managed decent isn't implemented yet. So besides the lack of managed decent, everything else seem to be working as it should. I've only tried 3 short flights with both the A330 and A340. Take off and climb works, obviously cruise works, but the decent part seem to be totally missing unfortunatly. And finally approach and auto land works. I'm gonna try and reinstall just for the sake of it and I cross my fingers that it will solve the lacking managed decent, because that was the one thing I was really hoping would be added in this new version. If it isn't I will be very dissapointed.

It should be on when the master switch is on, I think it's off by default. The knob on the instrument itself only switches between DME 1 and 2, I don't think there's an on-off switch as far as I can remember. But don't me on that :Whistle:

Check if the master switch is on, right overhead bottom row in the middle, check battery switches and generators while your at it. VOR 1 needs to be set on the GPS unit, VOR 2 is on it's own radion on the pedestal. Personally I don't like the GPS solution, it's hard to operate and hard to see, wish we had a similar unit for VOR 1 as we do for VOR 2. VOR 2 will show direction on the RMI left side of the main panel, same for VOR 1 as well as the ADF. You switch between displaying VOR and ADF by clicking the little button at the bottom left side, on the right side you swich between VOR 2 and ADF 2, although I don't think there's a ADF 2 on this plane.

As I can remember from the POH the aircraft should avoid operations below 67% in ground idle and minimum 96% while in flight.

The pop up screen behaved the same way, could not close it down. So I just ignored it, and after a few minutes it dissapeared by itself, haven't seen it since.

Check that the master switch is on, it's off by default. It's located on the right overhead panel between (and a little below, big T-switch) BATT1 and BATT2 switches.

Aircraft works fine in P3Dv3. Slayer, check that the master switch is on, it's on the right overhead panel (between BATT1 and BATT2).

Edit: Misread the OP.

Strange, I did a test flight just before I wrote my post with the A330 and made a flawless autoland (I usually fly approaches and landing's manually coz I think it's more fun). Must be something wrong with the AFCAD file then? Or maybe an older version of the BBS. I'm using the v.0.81.5. Have you tried landing at a different airport? On a side note, it is not uncommon that the AFCAD file in sceneries, especially in terms of correction/alignment of ILS's get overlooked by scenery developers. I did my landing at ENAT using the AoN* scenery, and I know the developer is a stickler when it comes to making a proper AFCAD files for his sceneries, so technically you could land anywhere in Norway where there's AON scenery. I believe AoN covers all major airports in Norway, but I'm a bit unsure how accurate AFCAD's are when it comes to the none-AoN payware airports. I seem to remember there was some problems with the AFCAD file in the ENGM payware package from AS back in the day. And I don't know if it's been corrected. (I've been away from simming for a while, just getting back into the saddle again *AoN - Airport's of Norway - remarkable freeware scenery covering most of Norway.

If you do everything correcty it could be that the ILS/AFCAD is not aligned with the scenery correctly. Have you tried on other airports? Here's how you land a airbus with autoland: when the PFD displays the ILS, press the ILS button. Then press LOC. When the localizer/glideslope indic starts to move, select APPR and the second AP (that last step should arm the autoland function, should automatically engage around 400 ft).

I usually press the downward button to make sure the plane is sitting on the ground after slewing, otherwise, if there's elevation changes slewing from A to B you can bounce a bit because the plane is off the ground, even if only by a few feet.

There's a slew plugin which I use, cant paste the link but it's in the .org library. Just do a google search.

Well there's enough negatives to point at, I dont disagree with that. But there's no point in making assumptions and state them as facts, that's all. As a actual matter of fact, you could have saved yourself from this if you had your fact's in order in the first place On a more ligh hearted note, I bought the plane when it wasn't even released. Had a heated email exchange with the developer over that way back when, because from the advertisement you would've believe it was. They later changed that and renamed it (if my memory serves me correct), but that's all water under the fridge now. And I totally agree that thing's move rather slowly and that there's been build's that broke the whole plane where you had to wait for month's until the next update. Their customer support I won't even touch, and their insistance on dealing with customers over FB is the most *bleep* thing ever, IMHO. Having said that, the newest A320 isn't bad, the VC still look's pretty much the same despite the update. But handling has improved, but they've still not implemented managed decent. And the lack of managed decent is a dealbreaker for me personaly, and only because of that I don't fly it as often. I think they frown upon us calling it a beta, but that's what it is and that's how I look upon the project. And I'm fine with it. In terms of long time development, it's not unusual for complex aircraft, just look at the FSLabs, they started around the same time, and I have no knowledge of their resources or how many people work on it, but it's not released yet. It will be in my hangar when it does tho. But with BBS we do know they're just 2 individuals who work on it, and compared with other similar developers they seem to be on track in terms of time spendt. Just remember the quality bar (in general) is pushed upwards with each year, even new sim's have appeared. My personal view is that on the bright side of being a paid-tester, we've been able to see and fly the different beta's instead of just hanging on a forum asking questions for years, like other developers. Pluss we got a new model as well in addition to all the different versions of the A318's, 319's and 320's when they introduced the A321. On the negative side the feedback loop is rather botched between the dev and customer at times, unless you use FB. And most times serious bug's have only been addressed after month's of waiting in the past. They've improved on that last part somewhat with the latest builds though by issuing fixes shortly after releasing the main builds. So again, I look at it as beta/early access, and I have no doubt's that the end product will be good. I just hope I live long enough to see the end

That's just silly talk, there was a update in may or the month before. Claiming they've dropped development in favour of another product is just plain misinformation. If you dont care or like the plane it's up to you, but it's never clever to shoot your mouth off on thing's you obviously aren't aware of. As far as I gather they are cross developing between the small and big busses, and the updates are carried over from one to the other each time. Apparently because the developent of the MCDU logic is the same. Last update for the 320 had a updated VC too, although not as developed as the comming bigbus update. But I recon that the system upgrade as well as a equally improved VC will carry over to the 320 once the 330/340 is out the door.

Well that's strange, one thing comes to mind. Btw: do you see any indication of the axis in the MCDU calibration page. You should see a green line when moving the throttle from idle to full throttle? I know, I know, I just have to ask anyway. Anyway, there could be some interference if you have assigned axis in both FS options and FSUIPC. You could try and remove the throttle axis within FS and assign the axis through FSUIPC instead, and obviously calibrate it as well (within FSUIPC). If all that is set and it still doesnt work, you can try and reverse the axis within the FSUIPC interface. See if that helps. Actually, I think I have the same joystick lying around somewhere, but it's very late night here now, so I wont be able to test it until tomorrow (if I can find it).

FSGRW has a demo too, I think. For me it is the best because it no-B simple interface without fancy graphics and billions of buttons for everything (that probably has a performance impact). And it also creates weather on par with the rest, no doubt. I have it configured so that it loads in the background when I start the sim and it does everything automatically and I dont have to do a thing. Getting weather info from other airports is as simple as typing in the ICAO code. And to top it iff, once Xplane 10.40 is released, it will also work in x-plane, in addition to P3D, FSX and if my memory serves me, also FS9/fs2004. But it is purely a weather generator, so no new cloud textures or anything, in my case, I use REX for texture replacements and FSGRW for the weather part.

FSGRW for my part, very happy with it. Saying that as a previous user of most of the other programs.

Without knowing anything about what hardware you use or how you tried to calibrate, I can only run over the calibration process in general and under the assumption that your joystick is correctly configured and calibrated in both OS and in your FS. First off, there is no zone to calibrate the reverse axis, only the position from idle to TOGA. Meaning, you set your throttle lever at idle, then press the button on the left side of the MCDU/FMC next to where it reads idle/set. Then move your throttle to lightspeed (aka full throttle) and press the button on the right side of the MCDU/FMC next to where it says TOGA/set, and you should be done. If you have reverse thrust on your throttle hardware, it should automatically work now. If you don't have a reverse axis on your joystick/throttle console, you might be able to fake one. If the latter is the case, when calibrating the idle/set position, move your throttle to somewhere of your liking but above the physical idle (of your joystick) and press the left button on the MCDU/FMC in order to tell the airbus that this is the new idle position. I dont know if it'll actually work, but in theory it should

No problem lftt205 777200LRD: You should use the pss_native. There is no installer pr.se, so you have to drag the navdata folder from the zip file and drop it into the FS*root*folder/Blackbox simulation folder and just overwrite the files in it. Of course, if you need to make a backup of the original navdata it would be obvious to do so before you drag and drop the new cycle XD

In regards to the update, I suddenly became uncertain of which model you are actually talking about. Are you speaking of the widebody (A330/A340) package or the prologue (A318/319/320/321) package? The update that is around the corner is for the prologue, current version is 0.8.1 while the widebody is currently at version 0.81.5. So my previous post, I did the test in a A319. And yes, I did a planned flight from takeoff and cruise and did my manual AP flighttest during the decent and approach phase. Due to confusion as to which product you're haveing problems with, I did the same flight with the A330 too. In this test I took her out of managed mode during climb out, set a manual heading a bit off course, engaged VS and manual speed as well, then after a while set a new heading to intersect the planned route and took her back into managed flight again. Did the whole cruise segment in managed but repeated the same manual flight portion as I did with the A319 flight, testing all manual modes. Can't report any problems. But if you were talking about the widebody and your version is 0.8.01 has me a bit stumped, coz I cant find any version on my HD with that number. I do have a v.0.8.02 which was released in january, then a v.0.81 was released in march. That version had a few serious bugs in it, which promted the developers to issue the current version v.0.81.5 which fixed those issues. Of course I could have deleted a few of the earlier versions, so technically there could have been a v.0.8.1 I just dont remember anymore. Anyway, if you are talking about the widebody, then you're far behind in terms of versions. The newest version has a new VC (or more refined/developed model with some degree of baked textures etc) and, as I understand, new system logic coding. According to BBS, they did rewrote the whole coding into a new format and some of that is now part of the A330/A340 package. The same update (upgraded VC and sys logic) is expected for the update to the A320 package, which I mentioned is around the corner. Current version of the A320 package is 0.8.1 and was released in june 2014. Not sure what you mean by "setting up the FMC and doing a complete run then disengaging it?" But as mentioned earlier, I did program the flight through the MCDU/FMC and I did go in and out of managed mode to manual AP mode and back again, and I did test all the four manual modes (speed,HDG, ALT and VS), both induvidually and different combinations. Just a tip, the current versions are a bit sensitive when it comes to system initiations. Best way to check that everything is as it should be, is to open the MCDU/FMC and go to the performance page as the very first step before you do anything else and make sure you see the take off page and not the approach page. If the latter is true, you will see the magenta question about activating approach in the lower left side of the MCDU display and you should click affirm in order to reset the systems. If you ignore this, funky things might happen during flight he he he. So, from having my flights go haywire I've learned the hard way to always make sure to check the MCDU/FMC and make sure that the systems are in fact reset before I do anything else while on ground starting out. Most of the time they are, but slewing and repositioning of the aircraft sometimes put the aircraft sytems into thinking it's in flight. Hope that it helps you in some way, the A330/340 versions are quite enjoyable in it's current state and desite it'slack of managed decent. The A320 update that is on the horizon, as I understand it, should have at least the same updates as the widebody (meaning new sys logic/coding and updated VC) and they've hinted at maybe even more (crossing my fingers for managed decent). That has me exited, even if it just up to the level the A330/340 package is, I'd be happy. My negative comments is in the same vain as others, there has been long times between some of the updates, but I do credit them with the benefit of doubt when it comes to the reasons behind them (death in the family + complete rewrite of sys logic code). I have no reason to disbelieve them because the latest update for the A330/340 was a significant upgrade. But alas, it is still a beta (in my mind), but knowing that, and seeing that there have been significan updates, I do have faith in them and that it will be a solid product by the time v.1.0 is released. So I am a happy, paying beta tester. I could rephrase that and say I am a happy "early access" user instead. So to anyone wondering about 'should I or not'....I am not gonna give any recomandations. It would be dishonest on my part because I have no influence on neither the developers or know anything about tomorrow. As with any beta/early access software, you do take your chanses, what else can I say? But I will round off my rather lenghty mambo-jambo by re-stating that, with everything taken into consideration, I am satisfied because, what is implemented works as intended and I see it is moving in the right direction.

There is supposed to be a update around the corner. It was announced to be released by the end of july, but now we're at the end of august. So, theoretically it could be released anywhere from the next minute....through to infinity XD As far as the AP and manual/managed flight, you do know that you activate managed control by using the left mouse button, and manual guidance by using your right mouse button? I just did a small test flight my self, and had no problems, manual settings ALT, SPD, VS and HDG worked as they should.