• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Patch ADE 1.78/9 From 32Bit to 64Bit

Please see post #8 in this thread. It is not currently solved but the workaround is to turn off the ADE connection to the sim. I believe that it will then work.
Hello.

Sorry Jon, I dont understand what you mean by turning off the ADE connection to the sim. ADE works fine, it just doesn't connect to the sim. Is there a way to make it work like you say?
 
Sorry - you can decide whether ADE automatically tries to connect (and with this bug generate the message) or not

1633097980112.png


Uncheck Auto Connect and save ADE. This means the user needs to manually try to make a connection.
 
Sorry - you can decide whether ADE automatically tries to connect (and with this bug generate the message) or not

View attachment 77291

Uncheck Auto Connect and save ADE. This means the user needs to manually try to make a connection.
Oh, ok, I see what you mean. I get the posted error message when I manually select connect. I don't use the Auto Connect feature.
 
OK - then that's a bug we can't fix so far
 
Jon:
This might be the version of the FSUIPCClient.dll you are using. Yours is dated 2015. There was an update in 2018 that added support for among other things, 64bit.
I have not tried this with your latest 64bit patch process yet, however using the new dll with the unpatched version of ade 179.7475 fails with a version conflict, so a recompile/build of ADE with the new fsuipcclient might be required. Just a thought.....

 
The batch file returns a corflags : error CF001 in response to every command in the batch.
The google answer is the OS cannnot modify the exe file. Running as admin returns a longer string of errors.

Troubleshooting, I had ADEv1.79.7475 installed in Program Files (x86) so I moved the installation to my c: root directory. Same batch errors result.

Not sure what to try next. Batch response:
Code:
C:\ADEv5>corflags "Airport Design Editor.exe" /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>FOR %I in (*.dll) DO corflags %I /FORCE /32BITREQ- /32BITPREF-

C:\ADEv5>corflags ADE_GroundPolys.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags AeroWizard.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags AMS.Profile.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags AMS.TextBox.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags ASToFra.Coordinates.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags ASToFra.ErrorHandler.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags ASToFra.EventLog.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags ASToFra.FSUtils.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags ASToFra.Interfaces.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.

corflags : error CF001 : Could not open file for writing

C:\ADEv5>corflags ASToFra.MapRenderer.dll /FORCE /32BITREQ- /32BITPREF-
Microsoft (R) .NET Framework CorFlags Conversion Tool.  Version  4.8.3928.0
Copyright (c) Microsoft Corporation.  All rights reserved.
 
UPDATE: Solved. Running the batch as admin was a no go, but changing the corflags.exe attributes for all users to admin did the trick. Confirmed the conversion to 64 bit. Thanks..
 
Please see post #8 in this thread. It is not currently solved but the workaround is to turn off the ADE connection to the sim. I believe that it will then work.
Please see post #8 in this thread. It is not currently solved but the workaround is to turn off the ADE connection to the sim. I believe that it will then work.

Hi Jon, sent you a message on the missing jetways.
 
Hey fellas, any breakthroughs on getting 64bit version of ADE to work? I got a couple airports are that are pretty memory intensive and this could really help out. But the failing to connect to the sim is too valuable to do away with.
 
Hello:

To the extent I have tested this so far, one must use the "Connect" feature with the original *.exe in a separate session.

If I use the patched *.exe, although I can add a background image to the ADE workspace, after I exit, the project loses that image. :alert:

But while the patched *.exe is used, the added background image can be very large (...while it lasts).

I suppose we need to try exporting a ADE Project Backup before the crash occurs, so we can toggle between projects and patched *.exe's ?

GaryGB
 
OK, thanks for the quick update. Sounds a bit too complicated, I'll just keep the 32bit version for the time being.

Regards
 
The patch works for using 64Bit but a price is that this does not convert FSUIPC. FSUIPC is used to connect ADE to the Sim and this does not work in 64Bit mode. Otherwise everything appears to work.
 
The patch works for using 64Bit but a price is that this does not convert FSUIPC. FSUIPC is used to connect ADE to the Sim and this does not work in 64Bit mode. Otherwise everything appears to work.

Hi there.

I have a 64bit version of FSUIPC. Using version 5.157, which is a 64bit version according to the FSUIPC website. It has been superseded by version 6, which I will try out.

So unless I misunderstood you, I don't think that FSUIPC is what is causing the problem.

Regards
 
Hello:

To the extent I have tested this so far, one must use the "Connect" feature with the original *.exe in a separate session.

If I use the patched *.exe, although I can add a background image to the ADE workspace, after I exit, the project loses that image. :alert:

But while the patched *.exe is used, the added background image can be very large (...while it lasts).

I suppose we need to try exporting a ADE Project Backup before the crash occurs, so we can toggle between projects and patched *.exe's ?

GaryGB

So this might be an option since I don't use the connect to sim feature all the time. Can you explain how you are able to have both versions installed?

If I understand you correctly, I patch my 1.78 version to 64 bit. Then I retain a backup of the 32bit "Airport Design Editor.exe", keep that in the same ADE folder and I can now switch back and forth between 32bit and 64bit by clicking on the appropriate ADE.exe file?

Thanks for any help

Regards
 
No. Many of the files used are also switched to 64Bit. Keep a 32 bit (unpatched) installation of ADE and make sure you have separate shortcuts for each. If you need to use the connection with the sim via FSUIPC then open your project in the unpatched installation. Patching has no effect on the formats of ADE projects so they should be editable by the patched or unpatched installations without issue
 
Back
Top