Rich - Did you report that issue to HiFi? Especially the writing to the wrong folder. I'm puzzled as I had both 2.5 and 3.0 installed. I downloaded the update and installed, pointing it to my v3 flder - it worked as expected and I had ASN functioning immediately.

 

Vic

Rich - Did you report that issue to HiFi? Especially the writing to the wrong folder. I'm puzzled as I had both 2.5 and 3.0 installed. I downloaded the update and installed, pointing it to my v3 flder - it worked as expected and I had ASN functioning immediately.

 

Vic

 

Hi Vic - I did report it - It worked fine when I had v2.5 installed but decided to uninstall 2.5 - when I went to install it with just V3 installed thats when the fun started - or should I say no fun

I had some trouble too...I can't rememeber the error but what I did last finally worked. Removed ASN completely....then used full installer (P3dv2 version)....installed that pointing it to the P3d directory. Then right after that, I installed the V3 update... The I started ASN and it ran with no errors or complaints. Its been working fine since.

I had some trouble too...I can't rememeber the error but what I did last finally worked. Removed ASN completely....then used full installer (P3dv2 version)....installed that pointing it to the P3d directory. Then right after that, I installed the V3 update... The I started ASN and it ran with no errors or complaints. Its been working fine since.

 

Hence having 2.5 on your system makes it easy - looking forward to a native v3 installer

Actually, I just have 3.0 installed...I meant the ASN full installer for P3d....which I presume is reall for version 2.5.  But poiting it to 3.0 foler is fine just as long as you don't run it without the 3.0 update....i presume.

Just as a fyi - there was a V3 update released a few days ago - it did not work properly and a new one was released the next day. Anyone who d/l it the first day will be using the wrong version.

 

 

Vic

Unfortunately , I cannot get it to work via LAN to P3Dv3.

I had it working fine with P3Dv2.

 

What I did.

 

Client

1. DL the latest Update for P3Dv3 today and installed it.
2. Pointed to P3D v3 instead of P3D v2
3. Pointed to AppData......Prepar3d v3

Server

1. Uninstalled the v2 Simconnect Installer and installed the new Simconnect installer into v3
2. DLL.XML --> as_btstrp.dll  entry is there
3. SimConnect.xml --> set the IP4 entries to the current Adress ( the same as in v2 )
4. Simconect.cfg --> Set the IP4 Adress ( the same as in v2 )
5. Simconnect.ini is there
6. All folders are Shared.

Note : because I am using Project Magenta the Sharename ( not the shown name ) of the  Prepar3D v3 Files folder is fsplans !  I do not know if that might cause a problem...

 

All suggestions are welcome.

-------------------

 

Finally I could get ASN to connetc to P3Dv3 by uninstalling ASN and strating over from scratch...

All files have the same entries now as when it didn't work.

 

However I get the following Error message :

 

An error message was recived from ASConnect.

Incompatible FSX Steam edition version. This version is designed to be used with FSX SE version.....

 

?????

 

I--------

 

Edit : by in-and reinstalling ASConnect I solved the issue...

 

Sometimes I wonder how you gals/guys are ever able to fly ... hehe

 

NO FSX Steam Edition errors here ... you sure you didn't download and install the FSX/FSX-SE version?

 

EXE.XML should contain this:

  <Launch.Addon>

    <Name>as_btstrp_config_manager</Name>

    <Disabled>False</Disabled>

    <Path>as_srv\as_btstrp_config_manager.exe</Path>

  </Launch.Addon>

 

DLL.XML should contain this:

  <Launch.Addon>

    <Name>as_connect</Name>

    <Disabled>False</Disabled>

    <Path>as_srv\as_btstrp.dll</Path>

  </Launch.Addon>

 

Per my response here: http://www.avsim.com/topic/476347-asn-does-not-work-in-v3/?p=3310303  steps 4 to 6.

 

Cheers, Rob.

 

EDIT: maybe Gerard has me on his ignore list ... hmmm ... wonder if you can add Moderators to ignore list?

maybe Gerard has me on his ignore list ... hmmm ... wonder if you can add Moderators to ignore list?

Not if you're smart. :smile:  And Gerard is smart.

 

I also have had NO issue with ASN. However HiFi works hard to correct ANY anomaly so rest assured they are looking into it.

 

Please open an official ticket rather than just posting your problem. By determining what may be different on *your* system it may help determining the cause of the issues some people are having.

 

Vic

Hi everyone,

There aren't references in our forums or other threads here because this is new.

 

We're looking into this along with a few other minor reported issues and as always have new updates pending.

 

ASN for P3Dv3 is in BETA right now so some issues are expected.  Although in this case without investigating more I'm not sure what the reason for this "complicated procedure" which at the moment we cannot replicate the need for.  The paths defaults in ASN installer and ASConnect installer of course do need to be pointed to the correct paths, and cannot always be trusted to default to the intended path, which at the moment I suspect to be part of the confusion here.  

 

Thanks in advance for posting beta-related bug reports, technical issues or questions to our support forums as requested, and we appreciate your participation in the beta process.

Thanks Damian much appreciated