Aerosoft Support

[Crystle Rike]

Thesystem suggested that I probably forgot my password so I requested a new password, but did not receive anything. I checked again and was informed that my email address was not registered. This was probably the 10 th item that I purchased.

We're sorry you've experienced a problem with your order. I have notified the appropriate person who will be in touch with you. If you have a different email that you would like to contact you at other than the one for your FORUM account, please PM it to me and I will be happy to forward to the person who will be helping you.

This was posted on Sunday, it is now Friday, and I am no closer to being able to upgrade my Helgoland for AFS2 to v1.1 than I was on Sunday. I can't seem to get anyone to actually read the emails that I am sending to sup...@aerosoft.com. I keep getting "canned" replies that direct me to an old account that does not have any purchases in 2018. Everything listed is prior to 10 February 2017. Unfortunately, I purchased the original Helgoland on 20 Feb 2018 on purchase order number 1130946. (see attachment)

If I could just find someone that could point me to some sort of support link that would allow me to download the latest update, I would be happy. Maybe just a "click here" to download would be great.

All straightened out now. I was being directed back to the old 2017 accounts and not given any directions on how to find the current accounts. All is well now. You can delete this whole thread if you like.

I think some people need to adjust their expectations. There has been made a deal between 2 business partners. And there is zero obligation against anybody for those business partner to unveil details about the deal they have made. The only question that is important for existing customers is, can they expect support for the product they own. And this has already been answered.

Two days ago I purchased the F-14X from the Aerosoft store for FSX: Steam Edition. I'm a big fan of the jet and the addon seemed worth an investment. Things went perfect with the module until I tried to launch from the CAT on the Kittyhawk in the pre-saved Free Flight Carrier Operations with the F-14A and the F-14B. When I went to crouch the gear and deploy the launch bar, it would go halfway down and then seemingly stop and go back up. Using the Shift + I command locked the F-14 into the CAT, but it seemed to be shaking on the deck. Hitting Shift + Spacebar (My mapped Takeoff assist command for the carrier), nothing happened no matter how many times I tried. I went back through the manuals to see what I was doing wrong and even checked my keybindings to make sure I wasn't messing it up. I tried reinstalling the F-14 (twice) and even reinstalling FSX: Steam Edition. I've contacted support twice who sent me an update containing versions of the:

When I tried reinstalling them, to include both overwriting previous files, skipping the files it was trying to replace, and even running the installer as the Administrator on my laptop, nothing seemed to work. I really would love to get this to work because the F-14 addon is an absolute joy to fly, I just can't seem to get it to run. I've also checked my key-mappings and my SimConnect.msi file. I've noticed others have dealt with a similar issue and any help with this would be appreciated, thanks.

Hi, please see this Aerosoft F14 ( -cat-launch-issue-kneelno-launch/ ) topic. You need to file a support ticket and you should receive a reply to a "DropBox" account where there are some revised airplane/aeorploane folders which you will need to place into your SimObjects folder in FSX:SE.

Yes, that is quite likely. with PMDG aircraft if you calibrateyou get conflicting values so the throttles jitter. With some other add-on aircraft they just don't process the controls at all at the level FSUIPC has to inject them after calibration.

Thanks you for the reply. I am currently using the PFCcom64.dll to calibrate. I use the automatic calibration option in the quadrant menu, but I cannot make the throttle 1 to go down to the 0 THR position. I am assuming the parameters from PFCcom64.dll are transfer to P3D. does this parameter in the ini file play a role in this "ThrottleSyncEngine2=No". Finaly do I read those parameters correctly:

I think the problem is that you are taking the range 0-16383, which is the full throttle range inside the sim, and using it as the parameter for an Axis Throttle set control. Those latter controls are only used for forward thrust -- they hav no reverse zone. Furthermore they use the whole range -16384 to +16383 for forward thrust. So your idla, 0 , looks half=way through.

Only the old "ThrottleN set" controls, originally used in FS98, have a reverse range. That's what FSUIPC's calibration uses. They can be assigned in FSUIPC, but I doubt they'd work in your aircraft (though you could try that first I suppose).

There are really no throttle units with throttle levers doing anything but provide a continuous range. The only difference between the forward thrust and the reverse is a matter of interpretation. Standard joystick levers when calibrated in Windows give the range -16384 to +16383. With standard Sim assignments, that's ALL forward thrust, with idle at -16384 (plus maybe a set null zone). For reverse of the same lever a portion of the lever movement is designated as reverse, and treated differently. The turboprop one is no different -- it just has markings and maybe a detent. the lever is just the same.

Reverse thrust in the sim is obtained either via a different control, or, as used n FSUIPC, an old FS98-dated control (still supported though unpublished) which has the range below 0 used for reverse. Internally -16384 to -1 is all reverse, though each jet imposes a reverse thrust limit, specified in its AIRCRAFT.CFG file. eg the737 would have a figure of 0.25 there, meaning 25%. So the reverse range is -4096 to 0.

If both are providing the same, correct, values, and both are assigned in the same way and noeither calibrated in FSUIPC, then they simply cannot act differently. Therefore wither your calibration is not done properly, or your assignment is different one to the other.

I always do it manually. You control eexcatly where things start and stop, and set null zones at either extreme so you know you can always set them. Do not trust those pots to always return the same value in the same place. They use resistance in wire or carbon, and that varies with temperature, humidity, and so on. set the minimum and maximum positions allowing a little movement beyond.

A "null zone" is just a part of the lever movement which is not taking part in sending different values to the sim! You set a null zone at both ends by pressing the set buttons with the lever a little away from the stops!

Your "NULL ZONE" is not recorded in the settings, only the places you marked minimum and maximum: 10-121 for Thr1, 7-119 for throttle 2. If your true measured min and max values are outside that range the difference is your Null Zone.

I'm afraid I've no idea what your aircraft is doing, throttle control wise. It makes no sense at l that the same actions on each of two throttles have different results. Maybe the aircraft itself is mis-installed. Might be worth uninstalling and reinstalling it. If that doesn't help, try logging Axis events (an item in the FSUIPC Logging tab). Then you can see exactly the results of your assignments and actions. You can see this in real time by enabling the console log 9you may need to make the sim run in Windowed mode to see that).

Not necessarily. There are only a maximum od 127 possible values those throttles will return. Even if you had them all 9whereas you only have 111 ad 112 respectivel0, there would still be 256 FS throttle units to just one difference in your throttle output. 3280 - 2595 = 685, so only a little more that 2 values. To get two pots which provide exactly the same value at exactly the same position may not be impossible, but it is certainly very difficult using normal resistive pots, which is what PFC used.

I wouldn't worry unduly. Even if the difference was enough to be noticeable with the resulting thrust (N1%), just adjust the throttles appropriately. Except in a brand new freshly commissioned airliner the throttles are unlikely to line up to give the same thrust in any case. I've had many cockpit rides (when it was still permitted and easy to get into) and they are rarely in line.

As you can see, T1 sits higher to the 0 THR mark but T2 is ok. This is the way they are when I load the plane in Cold and Dark state and they stay that way until I take off or land. I would like the throttle1 and 2 to be equally set at 0 THR. when I am un the ground, like this :

If the same sort of values are being sent -- i.e. close to 0 or -16484 (depending on which control is assigned) at idle setting -- for both throttles, then they must surely react the same! The Log you attached earlier did show that 0 was being sent by both. (Though see below for questions on that).

I don't think that aircraft likes being given THROTTLE1_SET controls. I don't know how they managed to make the two throttles behave differently, but you could try unchecking the throttles in the PFC calibration and instead assigning them in FSUIPC "direct to calibration" and calibrating there (ensuring in the calibration you set for "No Reverse Zone").

But it could be that they are sent by the aircraft code, so could you do similar logging 9without prssing the NEW LOG button, with a different, maybe default, aircraft please? If it is the device the log will show similarly.

Finally, the Log seems to only really show the same thing repeated over and over 9which is why I suspect the aircraft itslef of originating these). What you need to do is move both Throttles to max and then back to idle so that the log shows all the changes between those.

3a8082e126