Dutch has released a public beta of Version 1.2.0 via this thread on the FS Captain forum - http://fscaptain.pro...play&thread=508He has taken a lot of recent user input and added some cool new features. Now you can set your airline configuration to require you to park at the gate or ramp which your dispatcher can select for you. Worried that an AI pilot may take that spot and leave you stranded? You'll be assigned another (and another) if that happens.ATC is no longer your enemy, from your company's perspective that is. If they put you in a holding pattern and make your passengers late, your time flying in circles or on roundabout vectors will be accounted for. You also won't be dinged if you find yourself 12th in line for the morning rush. So call your flight attendent to bring you another cop of joe and watch the incomings and outbounds take their turn on the runway.The beta is published as an update to existing installs, so you'll have to have FS Captain installed aready... or you can install the time-unlimited demo and update it to 1.2.0 status.

This addon is just amazing.. I don't fly without it any more.. at all. And now with so many new additions it's even better. If you're using Radar contact like me, you'll be happy to hear it also monitors AI traffic on the ground close to you, if you're using ASE there are efforts to make this compatibility also. Again, great addon!

I tend to agree, but there are some things that haven't been solved since the release:1) the adding of the gauge to planes is still a pain in the neck. Try to add it to a Carenado 206 - without knowledge of the panel.cfg you are lost.2) Saving settings is random at best. So often changes are ignored, resulting in frustration. Better edit the files by hand.3) Calculation of flight times is way off with shorter flights. 4) On a lot of airports (especially addons), you are punished for overshooting the runway during a perfect landing.5) Payload management is full of errors, especially with planes that have a payload manager. Once again, saving of stations is random.Apart from that, the idea behind the software is great. But I stopped using it due to the many problems, even with the latest build (1.6)

1) the adding of the gauge to planes is still a pain in the neck. Try to add it to a Carenado 206 - without knowledge of the panel.cfg you are lost.2) Saving settings is random at best. So often changes are ignored, resulting in frustration. Better edit the files by hand.3) Calculation of flight times is way off with shorter flights. 4) On a lot of airports (especially addons), you are punished for overshooting the runway during a perfect landing.5) Payload management is full of errors, especially with planes that have a payload manager. Once again, saving of stations is random.

1. Adding gauge to planes is as easy as can be.. use FSCOM Installer and it installs it automatically. I use only payware airplanes (PMDG, LevelD, CaptainSim, Cerenado, ..) and I had 1 such problem which was solved by the help of the author. 2. I think this is only problem with Windows 7 and some administrator rights. I have Windows 7 and I don't find this so frustrating as you.. ok, sometimes you have to save twice or so or maybe even open notepad.. I hope Dutch will solve this nag.3. Are you importing any 3rd party flight plans?4. You can add exceptions on such airports... problem with AFCAD (or something) I believe, not FSCaptain.5. What kind of errors? I use FSCaptain payload management for example Level D 763 and I cross checked the numbers between FSCaptain, LvD Payload Manager and TOPCAP.. I didn't find full of errors.This is evolving software developed by one person so the bugs are expected.. but if you find them and report to the author there is great chance they will be solved. They may be already solved in new 1.2 version (now beta).

1. Adding gauge to planes is as easy as can be.. use FSCOM Installer and it installs it automatically. I use only payware airplanes (PMDG, LevelD, CaptainSim, Cerenado, ..) and I had 1 such problem which was solved by the help of the author. 2. I think this is only problem with Windows 7 and some administrator rights. I have Windows 7 and I don't find this so frustrating as you.. ok, sometimes you have to save twice or so or maybe even open notepad.. I hope Dutch will solve this nag.3. Are you importing any 3rd party flight plans?4. You can add exceptions on such airports... problem with AFCAD (or something) I believe, not FSCaptain.5. What kind of errors? I use FSCaptain payload management for example Level D 763 and I cross checked the numbers between FSCaptain, LvD Payload Manager and TOPCAP.. I didn't find full of errors.This is evolving software developed by one person so the bugs are expected.. but if you find them and report to the author there is great chance they will be solved. They may be already solved in new 1.2 version (now beta).

1. Carenado 206, Quest Kodiak, pretty every plane that has not only livery variations, but also model variations.2. UAC is turned off, I AM running as admin, and neither FSCaptain nor FSX is on the wicked C: drive.3. No. It's the internal routine. Both in the dispatcher and the gauge.4. Great. But there are two problems: 1) I don't have the time to make 75% of all Orbx airports exceptions and 2) you never know beforehand which airport is affected (welcome to a big surprise in Rome - where it happens every second flight or so *g*).5. Just one example: with the E-Jets, FSCaptain ADDS the payload to the existing payload which has to be entered into the FMC for meaninful flight plans. And it gets pax and cargo mixed up in the stations.I have been in contact with the developer for a long time about a lot of errors (for example the inability to recognize addon airports in earlier versions), because I am one of his first customers. But - for me - the program still doesn't deliver. Your mileage may vary, though.

Hi Darem,Developing for the FS world is always an adventure -- there are so many options out there, and FS itself has so many quirks that we are all (developers) battling to accommodate them. It seems to be a never-ending fight :) The new release addresses some of your concerns, some still remain.

1. Carenado 206, Quest Kodiak, pretty every plane that has not only livery variations, but also model variations.

The Installer tries to figure out every panel.cfg, but there as many quirky variations to account for. It's improving. I did include instructions to manually add a gauge. Plans are also in the works for a complete external FSCaptain that uses FSUIPC/SimConnect and runs outside FS. But work won't start on this until 1.2 is stable and live.

2. UAC is turned off, I AM running as admin, and neither FSCaptain nor FSX is on the wicked C: drive.

My next task after correcting a list of issues with 1.2 Beta is to tackle the problems permissions are causing in Vista/Win7. These problems bedevil many windows developers not just FS ones. And they are rare and inconsistent too. Many people have no problems in Vista/Win7, others have weird stuff going on. I will do everything I can to make sure FSCaptain isn't contributing to this situation.

3. No. It's the internal routine. Both in the dispatcher and the gauge.

ETE calculations for short flights are improved with 1.2.

4. Great. But there are two problems: 1) I don't have the time to make 75% of all Orbx airports exceptions and 2) you never know beforehand which airport is affected (welcome to a big surprise in Rome - where it happens every second flight or so *g*).

I'd love to find some automatic way to detect airports where the surfaces are messed up. So I'm sure would about 50 other developers out there :) I do compile a list of ones I find and others users find and update the Exceptions.cfg with every release. It's also possible to add the line DISABLESURFACE=1 to the options.cfg file and then you can drive your 747 around your granddad's horse pasture and Dispatch won't know it's not a runway :)

5. Just one example: with the E-Jets, FSCaptain ADDS the payload to the existing payload which has to be entered into the FMC for meaninful flight plans. And it gets pax and cargo mixed up in the stations.

Again, compatibility with every add-on, and their many ways of going outside FS to handle payload and fuel, is always a struggle. That's why the options to turn off the autoloading exist. Not optimal to do that, but incompatibility issues plague us all. I'm sorry that in your situation so many seem to happen at once :(Thanks to all who contribute to this thread and FSCaptain to make it a better product. It will continue to improve and evolve. But I will never name a new version FSCaptain Evolution ... I promise :)Dutch

Dutch, as I wrote to you in a personal mail: I know that you are actively working on improvements all the time, and this is why I am happy customer even though I am not using FSCaptain at the time being. I didn't want to give the impression that FSCaptain is a pain in the b.tt, just wanted to point out some problems I encounter.

Hi, FS capatain is a great add on. I enjoy it very much. There may be some remaining minor issues but I am confident that Dutch will fix them, as usual...Great support by the way.

It's worth looking at the FS captain forums - looks like a very nicely supported addon.I'm really tempted, but with Cargo Pilot and FSPax already installed I just don't think I get enough extra. If I didn't have either, I might well be tempted to go for FSC.