Have you opened a ticket with HiFi? it installed and worked fine right away for me. Although I did have 2.5 still installed but later deleted it.

 

Vic

Were the good folks at Hifi able to shed any light on this?

It does work.  I have the newest beta on a client PC, and it works fine. However, I will say that ASN has been and still is the most finicky program in terms of connecting to P3D.  I had to spend hours updating security and sharing settings for every single file and folder shared across the pcs, in addition to making firewall exceptions and AV exceptions for everything, otherwise I would randmonly get the cannot control ambient conditions error. 

I'm done I have spent hours on this its not on my end - Jeroen have done what you posted just before you posted nothing works

Do you have a SimConnect.xml in the %APPDATA%\Lockheed Martin\Prepar3D v3 folder?

 

I had to manually put one there.

Other than that it worked just fine.

I'm done I have spent hours on this its not on my end - Jeroen have done what you posted just before you posted nothing works

 

Sorry Richard, but it is something in your end. A lot of people, me included, are running ASN on v3 with no problems whatsoever....

Thanks Guys got it working man that was painful - this is what I did followed Jeroens directions just install the full installer and last patch not the installer patch - which I did before but didnt work

 

Now this is what I think made the difference - the connect installer was routing to program files 86 lockheed martin folder and it was looking for your new p3d v3 folder so I went to the lockheed 86 folder and deleted it before continuing then routed installer to my p3d v3 folder and it worked - key here was to delete that folder before hitting next as I did route to my main p3d v3 folder before but didnt work so tried this and it did - does not make sense but worked

I can't make any sense of your description what the problem was, but hey, who cares LOL Glad you've got it working now! Sometimes software can be a real pain indeed...

I can't make any sense of your description what the problem was, but hey, who cares LOL Glad you've got it working now! Sometimes software can be a real pain indeed...

 

In a nutshell there was a leftover p3d v2 folder in programdata folder and asn was confused

What a nightmare this ASN update is, I went from p3d2.4 to v3 and spent hours going dizzy with granting permisions and different errors at different times. I still really don't understand how i got it working but J van E  advice looks similar to what i did if not exactly the same.

 

Tis the problem with flight simming....an expectation from developers that everyone is advanced techno nerds that could do it all blindfolded.

 

ASN forum didn't really shed light on what must be a common glitch.....is everyone scared to ask?

 

So fustrating

with granting permisions and different errors at different times. I still really don't understand how i got it working but J van E  advice looks similar to what i did if not exactly the same.

 

If you got al kinds of permission problems: did you install ASN into the default Program Files folder? I never ever install anything there if I have the option. Try installing ASN outside of it.

 

If my method looks similar there is a chance it's not the same... :wink: Also take into account what Richard just posted about some v2 leftovers. I installed ASN the way I did on a fresly installed OS so that might also have helped preventing problems. Not saying you should reinstall your OS :wink: but make sure there are no leftovers from P3D and also ASN itself.

 

Sorry, it dawned upon me you've got it working already LOL

 

Anyway, yes, it seems simmers are expected to have (quite) a bit more knowledge about computers and OS's than gamers...

Odd, I didn't have any issues with ASN, super simple just ran the patches.

 

My environment (Windows 7 64bit with both V2.5 and V3.0 installed):

1.  ASN on a remote PC (not flight sim PC - "Rob-AMD-PC")

2.  Make sure my drive mappings are correct on remote PC (pointing to V3 folders in my case \\Rob-5960X-pc\d\Lockheed Martin\Prepar3D V3 and \\Rob-5960X-pc\c\Users\Rob\AppData\Roaming\Lockheed Martin\Prepar3D V3

3.  Install the ASN patch (ASNext_P3D_Update_B5751)

4.  Uninstalled AS_Connect_P3D_Install on my main FS PC (5960X)

5.  Copied over the new AS_Connect_P3D_Install from my remote PC

6.  Installed AS_Connect_P3D_Install from my FS PC (5960X)

7.  Continued with rest of B5751 update patch

 

Repeated steps 3-7 for B5756 Update patch - all good.

 

To be fair, Flight Simmer don't need much PC knowledge when installing P3D ... they however might need some PC knowledge when installing add-ons and how 3rd party devs accomplish this varies greatly from 3rd party product to 3rd party product.

 

Glad you got is sorted Rich, but have NO IDEA what you were doing, suspect perhaps you were over complicating the matter? or was it a Win10 issue?

 

Cheers, Rob.

I'm where Rich was before 'it suddenly worked'.  Exhausted every option, and i mean every, that I can think of.  Grrrrrrrrrrrrr..........

Thanks Rob no it was an installer glitch not my fault - but I figured it out and hope for a better installer for from ASN which they will for sure

To clear things up and not having to read thru all of this - this is the short and sweet of it maybe it will help others

 

Got it working but an official v3 installer would be welcomed - installer put files in a legacy v2 folder which it shouldn't have as I directed it to v3 folder also had to delete that legacy folder for it to work - thanks