Jump to content

Update to 1.4.1.2


IBE1133
 Share

Recommended Posts

This is a strange behaviour topic. with different components involved. If administrators feel this it is a wrong place for it, please consider moving it to the right one.

 

I think this is going to be my last try. I have been having several issues since I tried to upgrade from 1.4.0.0., to 1.4.1.1 and 1.4.1.2. ASUpdater issues too, P3D v5 CTDs, and now, it happens to be an unflyable aircraft. I have made several fresh aircraft installations from scratch, to drive d:, to drive c:, no matter what I do, always the same result: No way to fly.

I have included a screenshot of my cockpit from my last installation. I can move my sidestick, with a cross in my PFS reflecting the moves, but nothing changes in F-CTL screen at ECAM.T he aircraft does not recognize any sidestick movement. I can't change the aircraft state anymore, as you can see.

Everything worked fine (or I think so) with default installation (1.4.0.0).

 

I am running a P3D v5, updated to last HF, windows 10 home 1909, GTX 1080 ti with 11 Gb, 16 Gb RAM, 2 SSD disks (C: y D:), thrustmaster T16000 and pendular rudder pedals.  Don't know which additional information I should add to have your support. Does anyone have an explanation for this strange behaviour?

 

Thanks 😉

 

 

Issues above 1.4.0.0

1412_a320_issues.thumb.JPG.f99c12818e0a34965bc9a09894111a3c.JPG

 

No issues at 1.4.0.0

1400_a320_no_issues.JPG

Link to comment
Share on other sites

  • Aerosoft

Hi, This is certainly not correct behavior.

Could you dscribe the whole reinstallation process that you go through? Did you delete all previous files before reinstalling? Running all installers with antivirus off and as administrator? Do you have P3Dv4 installed or the P3Dv4 version of the aircraft installed etc. Please be as detailed as possible.

I recall at least one user having similar issues but if I remember correct the issue there was trying to run P3Dv4 version of the aircraft in P3Dv5.

Link to comment
Share on other sites

Tnaks for your fast reply.

 

Some time ago I first installed the P3Dv5 bus via Aerosoft installer, into my D drive. Version 4 was in another machine. I believe (not sure) that even updating to 1.4.1.0 was right.

Some day I tried to update to 1.4.1.1., and I got the issue. As I was not able to get any workaround or solution, I uninstalled it and reinstall it to 1.4.0.0 (drive D).

I saw 1.4.1.2 available so I thought it would be a good idea to try it again.

 

Process is simple: 

Uninstall A-320 through Windows 10 Configuration (the former Control Panel) and then, install through Aerosoft installer, to 1.4.0.0. FIrst try installing the bus into drive D (usual procedure for me). Everything seems to be working ok, so I run ASupdater. Update to 1.4.2.2. and then, I got the issues.

Repeat all process, but installing to drive C (documents\aqerosoft folder). Same results.

I delete no additional files nor folders. I thought everything was cleaned up running uninstall. Should I?

 

Don't know if it is going to help, but A-330 is running fine.

I will be grateful for any additional advice.

😉

Link to comment
Share on other sites

Sorry for the x's in my folder name.

 

Hardware
--------
CPU Intel(R) Core(TM) i9-9900K CPU @ 3.60GHz
GPU NVIDIA GeForce GTX 1080 Ti (3840 x 2160 x 4294967296 colores)
GPU Driver 460.79
RAM 16GB @ 2133MHz

Microsoft Windows
-----------------
Windows 10 Post April 2020 (2004) Update / Version 10.0.18363 / 64-bit

User Profile and Document Folders
---------------------------------
User Profile Location:
Environment.GetFolderPath =        C:\Users\xxxxx
Volatile Environment\USERPROFILE = C:\Users\xxxxx

Documents Folder:
Environment.GetFolderPath = C:\Users\xxxxx\Documents
Shell Folders\Personal =    C:\Users\xxxxx\Documents


Microsoft .NET Framework 1.0 - 4.0
----------------------------------
.NET Framework DF
.NET Framework 2.0.50727 Service Pack 2
.NET Framework 3.0 Service Pack 2
.NET Framework 3.5 Service Pack 1
.NET Framework 4
.NET Framework 4.0

Microsoft .NET Framework 4.5+
-----------------------------
.NET Framework 4.7.2 or later (only latest version is shown)

Microsoft Flight Simulator (2020)
---------------------------------
No Microsoft Flight Simulator (2020) found!

Microsoft Flight Simulator X & Lockheed Martin Prepar3D
-------------------------------------------------------
Prepar3D v5.x (5.1.12.26829) found at: C:\Program Files\Lockheed Martin\Prepar3D v5\
Prepar3D v4.x not installed
Prepar3D v3.x not installed
FSX Steam Edition not installed
FSX SP2/Acceleration not installed

X-Plane 10 & 11
---------------
X-Plane 11 not installed

X-Plane 10 not installed

Microsoft XAudio2
-----------------
XAudio2_9.dll found: 10.0.18362.650 (WinBuild.160101.0800)
XAudio2_8.dll found: 10.0.18362.1 (WinBuild.160101.0800)
XAudio2_7.dll found: 9.29 (DXSDK_JUN10.100602-0421)
XAudio2_6.dll found: 9.28 (DXSDK_FEB10.100204-0932)
XAudio2_5.dll found: 9.27 (DXSDK_AUG09.090904-1620)
XAudio2_4.dll found: 9.26 (DXSDK_MAR09.090316-1354)
XAudio2_3.dll found: 9.25 (DXSDK_NOV08.081027-0939)
XAudio2_2.dll found: 9.24 (DXSDK_AUG08.080731-0600)
XAudio2_1.dll found: 9.23 (DXSDK_JUN08.080530-1349)
XAudio2_0.dll found: 9.22 (DXSDK_MAR08.080305-1539)


Simconnect, SDKs and Visual C++ Redistributables
------------------------------------------------
Microsoft ESP SimConnect Client v1.0.20.0 - (Version Data: 1.0.20.0)
Microsoft Flight Simulator SimConnect Client v10.0.60905.0 - (Version Data: 10.0.60905.0)
Microsoft Flight Simulator SimConnect Client v10.0.61242.0 - (Version Data: 10.0.61242.0)
Microsoft Flight Simulator SimConnect Client v10.0.61259.0 - (Version Data: 10.0.61259.0)
Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.56336.0)
Microsoft Visual C++ 2005 Redistributable - (Version Data: 8.0.61001.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.17 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x64 9.0.30729.6161 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.17 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2008 Redistributable - x86 9.0.30729.6161 - (Version Data: 9.0.30729.0)
Microsoft Visual C++ 2010  x64 Redistributable - 10.0.30319 - (Version Data: 10.0.30319.0)
Microsoft Visual C++ 2010  x86 Redistributable - 10.0.40219 - (Version Data: 10.0.40219.0)
Microsoft Visual C++ 2012 x64 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x64 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x86 Additional Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2012 x86 Minimum Runtime - 11.0.61030 - (Version Data: 11.0.61030.0)
Microsoft Visual C++ 2013 x64 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x64 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x86 Additional Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2013 x86 Minimum Runtime - 12.0.21005 - (Version Data: 12.0.21005.0)
Microsoft Visual C++ 2019 X64 Additional Runtime - 14.27.29016 - (Version Data: 14.27.29016.0)
Microsoft Visual C++ 2019 X64 Minimum Runtime - 14.27.29016 - (Version Data: 14.27.29016.0)
Microsoft Visual C++ 2019 X86 Additional Runtime - 14.27.29016 - (Version Data: 14.27.29016.0)
Microsoft Visual C++ 2019 X86 Minimum Runtime - 14.27.29016 - (Version Data: 14.27.29016.0)
Prepar3D v5 Content - (Version Data: 5.0.21.0)
Prepar3D v5 Professional Client - (Version Data: 5.1.12.0)
Prepar3D v5 Scenery - (Version Data: 5.0.21.0)

Link to comment
Share on other sites

  • Aerosoft

Thanks for that. I had a quick look and everything seems to be well and good with your support files.

Right now you are the only user experiencing this issue as far as we know and we are unable to recreate this issue. So not really sure what it could be that's causing this unfortunately.

Link to comment
Share on other sites

Well, @masterhawk, I appreciate your comment about Prepar3d folder. But I ever had no issue with this. My aircraft or scenery are not under this folder, what is a very different thing. Anyway, I am sure I can successfully deal with windows folder user rights 😉. Thanks.

 

@SecondatorI have got additional problems related to this one. As I couldn't install 1.4.0.1, I am not able to check if that solves the reallight issue with P3Dv5, as overhead lights are not working properly, either (I won't talk about it here, it has another topic).

 

Please, do understand my point. I can wait while contributing by my side to solve this one, but not forgetting about it, for an endless time. Also, I understand support is not an easy task sometimes. But I expected a little bit more from Aerosoft support. I am a proud Aerosoft A320 user from a long time, and I wouldn't want to change that. Please, consider I really don't know if I am the only user experiencing this glitch, or the only one who has reported it.

 

So, can I do something to help? Is there anything you can tell me to do? Things to check? Tips to install?

Looking forward to hearing from you.

Thanks in advance for your kind support 😉

 

Link to comment
Share on other sites

  • Aerosoft

IBE1133,

If only we had some clue what could be causing this kind of behaviour on your system. Unfortunately we have no idea right now and other users are not experiencing similar issues. Unfortunately it looks like there could be something wrong with your system that is causing but it's nearly impossible for us to really say what. If it was more widespread issue with more users seeing and reporting it we could be more certain that it's an issue from our side with our product but since right now you are the only user that we know of experiencing this issue we really don't know much about it. I know that this answer will not help you much in this case and trust me if we had any better idea what could be causing this, we would let you know.

We are preparing a new experimental update for the smaller busses to be released soon. Perhaps, once the update is out, if you try to do one more clean installation following the reinstallation procedure given here and then applying the update, it will finally work. 

Link to comment
Share on other sites

just to keep you updated:

Uninstalled A-320

Uninstalled P3D v5

Installed from setup (not only client), last P3D v5 version (HF1). Installation path was, anyway, C:\Prepar3dv5

Installed FSUIPC v6.0.11

Installed A-320 to 1.4.0

Updated to 1.4.2 via ASUpdater

... and got the issue again. No flight controls, no aircraft state, etc...

 

Uninstalling and installing A320 again to 1.4.0...

 

May you all have a very merry Christmas!

😉

Link to comment
Share on other sites

  • 1 month later...

I guess it is too much time for a single answer. At present day, I can fly my Aerosoft A-330 like a charm, even with thrumaster throttle support (attathrottle!), but there is no news about the A-320. No progress, no news since december. Well, is there no option for us? Maybe, ask for a refund and going for another bus? Certainly, I rather prefer not, but if I am pushed... Anyway my question still is unanswered. And it seems it won't be answered anymore.

I told you before, I can understand it is not an easy task, but, at least, I really excepted some kind of support from aerosoft.

Please, to put an end to this question, which is your solution (technical, commercial, whatever) for this support issue?

Thanks in advance,

Regards, Luis 😉 

Link to comment
Share on other sites

  • 3 weeks later...

Well, I was not expecting a solution at first try, as I am aware of the difficulties to solve some software problems. It is not an easy thing.

But customer support should be!

It is only about to answer your customers when they ask you for support in good manners.

Should I ask for a refund?

Thanks

 

 

Link to comment
Share on other sites

On 16.12.2020 at 12:07, masterhawk sagte:

Only thing I notice:

You shouldn’t install any sim related in the c:\program files folder. That’s a special by windows protected folder and often cause any kind of problems.

 

 

No he is not. I have the same problem.

Link to comment
Share on other sites

  • Deputy Sheriffs
On 2/21/2021 at 6:10 PM, IBE1133 said:

I guess it is too much time for a single answer. At present day, I can fly my Aerosoft A-330 like a charm, even with thrumaster throttle support (attathrottle!), but there is no news about the A-320. No progress, no news since december. Well, is there no option for us? Maybe, ask for a refund and going for another bus? Certainly, I rather prefer not, but if I am pushed... Anyway my question still is unanswered. And it seems it won't be answered anymore.

I told you before, I can understand it is not an easy task, but, at least, I really excepted some kind of support from aerosoft.

Please, to put an end to this question, which is your solution (technical, commercial, whatever) for this support issue?

Thanks in advance,

Regards, Luis 😉 

Hi, a update for the smaller busses is in preparation. Maybe it will help you.

Bit it’s nothing special adressimg your issue.

As you have already tried a fresh P3D install, we have just no idea what’s going on, why you have this problem and why the A330 not.

 

I only have the idea, that there might be one bad windows or  runtime file. A function used in A320 not in A330.

 

What might help is to run in command window with admin rights:

sfc /scannow

 

That will check and repair windows files.

Link to comment
Share on other sites

Hi, Bob,

Thanks for your advice. Maybe the update is not intented for this issue, but you never know. Sometimes software development gives you solutions not expected (bad or good), I do know very well.

Additonal info: Recently, I have updated Windows 10 to a new version (20H2). Issue still stands. Anyway, I executed SFC just in case. 100% checked, no integrity issue found (I will save you to check the screenshot, as it is in spanish).

Again, thanks

 

 

 

 

Link to comment
Share on other sites

HI... I have the latest update  1.4.2.1, also.. 

What looks like the hydraulics does "not work".. .the doors opens half and the cargo doors are inactive. 
The aircraft is off, so I switched on the electric pump and 2950 psi.. 

The door panel says open and cargo doors are not open.

 

All the best..

Jens

I have P3Dv5.1

Link to comment
Share on other sites

  • 2 weeks later...

Update: New A-320 install from scratch. Uninstall via control panel, and deleted any file related still in the disk. Windows registry "as is", untoucjed manually by me. Again same issues when updated to last versión.

Nothing remarkable in log files. Maybe I don't know exactly what to search. Did I mention that Crew Oxyg is off on start?

Any idea about next update schedule (not a particular day... days? Weeks?)

Thanks 

Link to comment
Share on other sites

Finally! Almost solved!

I have made a last attempt, installing my airbus A320 from scratch. This time, instead of installing in drive D (where I am used to have my addons placed, my A330 is there), I installed it into drive C. To my surprise, my A320 is now updated to last version and it is almost working. :-).

 

Conclusion: Seems that update procedure for A320 does not work when the aircraft is installed in a drive different from C. It is not the case for A330, updates have been working succesfully. May I expect a confirmation from your side?

So please, take this one into account when building next update for A320 (or, at least, check it please). I'd prefer to have my add-ons installed in drive D, unless there is a string reason.

 

But I said that it was "almost" working. Everything goes actually well, except for TCA throttle support. I have enabled it in A320 configurator. Remember that it works flawlessly for my A330, so axis and keys assignments are supposed to be ok. Any problem having A330 in drive D and A320 in drive C, regarding TCA throttle support?

Well, you have got more experience than me with TCA, so please, any advice?

🙂

Link to comment
Share on other sites

Unfortunated coincidence. I have check it is not a question about the installation drive (or not only). After looking within the files, and after cleaning folders and registry, I have seen something bizarre/strange:

This is a relevant piece of ASC.log.txt, coming from v1.400:

 

Aircraft loaded (Req)
Panel Folder: C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\SimObjects\Airplanes\Aerosoft A320 CFM Professional\panel\asc.cfg
Add-on.xml Path: C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Professional\add-on.xml
Add-on.xml not found at this location
Add-ons.cfg Path: C:\ProgramData\Lockheed Martin\Prepar3D v5\add-ons.cfg
Add-on.xml Path from Add-ons.cfg: C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\add-on.xml
Path from add-on.xml (addoncfg == true): C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\add-on.xml
WavDir Path: C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\SimObjects\Airplanes\Aerosoft A320-A321 Professional Base\Sound_ASC
Loading System sounds
System sounds loaded
Loading Custom sounds
Custom sounds loaded

 

First, I don't know where is the process obtaining Add-on.xml path from, because it goes to "C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Professional\add-on.xml", that's not the case. Fortunately, it makes another try (from add-ons.cfg), this time to the right folder: "C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\add-on.xml"

It is not clear for me who is telling the process that wrong path. It has consecuences, because this Add-on is reflected in different add-ons.cfg (programdata and use3r folders) than other ones.

 

Well, that leads to a right execution in P3Dv5, over v1.400, with its known limitations.

 

Next try was to update the bus thru ASUpdater. Of course, the issue still is there with 1.412.

If we look into a equivalent piece of ASC.log.txt after installation, we can find (many times, as it retries loading the plane several times:

 

Aircraft loaded (Req)
Panel Folder: C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\SimObjects\Airplanes\Aerosoft A320 CFM Professional\panel\asc.cfg
Aircraft loaded (Req)
Panel Folder: C:\Users\luis\Documents\Prepar3D v5 Add-ons\Aerosoft A320-A321 Pro V5\SimObjects\Airplanes\Aerosoft A320 CFM Professional\panel\asc.cfg
Add-on.xml Path: C:\Users\luis\Documents\Prepar3D v4 Add-ons\Aerosoft A320-A321 Professional\add-on.xml
Add-on.xml not found at this location
Add-ons.cfg Path: C:\ProgramData\Lockheed Martin\Prepar3D v4\add-ons.cfg
Add-on.xml not found at this location
Add-ons.cfg Path: C:\Users\luis\AppData\Roaming\Lockheed Martin\Prepar3D v4\add-ons.cfg
Add-on.xml not found on this PC!

 

Suddenly it goes to Prepar3d v4 folders to get the add-ons.cfg files. Of course, no need to tell you that there is no v4 folders in my pc, and I am almost sure that there is no registry entry for v4 (I say "almost" because I only can read text for humans, no hex or ID codes.

 

Anyway, in spite of not been found, the A320 appears in Prepar3D, issue included, indeed.

 

Maybe following the process that writes into this file (ASC.log.txt) can help. Please find attached two copies of this file, after v1.400 installation and 1.412 update.

Any explanation? Can it be related to the issue I am experiencing?

Please take a look into this, at least, let us know how this things are happening.

Thanks in advance.

 

ASC.log - v1.400.txt ASC.log - v1.412.txt

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...