PJW

Are you on a wifi connection? If you are would that be a reason for you having a dynamic IP address. I don't know, my knowledge is limited on this. Anyway having checked what your IP address is before you start XP 11 does that get rid of the alert message? I am networked with two computers on ethernet. I can successfully ping each computer. My objective is to run P2ATC on my client computer. My IP address is static but I am still getting this annoying alert message for what reason I do not know. I do not wan't to advance further with my objective until I understand what is causing these alert messages.

I am a newbie to X-Plane 11 and only have about 4 or 5 months experience using it. I'm a bit of an old guy but I still have a lot of patience and want to get to the bottom of these niggling problems. First I have Pilot2ATC successfully installed on the same computer as XP11. By scouring the web I found a download for XPUIPC. The XP11 XPUIPC web page is still not up and running as of date of this post, so this is a problem for many flight simmers in itself. This Plugin is essential to get commuication between the sim and P2ATC working. All the advice given stresses that your IP address needs to be edited into the XPUIPC config file and saved. Then startup your sim and hey presto everything works as it should. Go to your plugins menue and convince yourself XPUIPC is there. OK as I said everything works for me. But! guess what? recently I now have a XPUIPC alert message on start up saying 'Wrong IP address xxx.xxx.x.xx (my IP address not revealed) No NIC with this address found'. (For the uninitiated NIC stands for Network Interface Card). I have searched the forums but always get the same answers as to how to resolve this issue. Which is as per the paragraph above. There might be an issue with Firewall protection. But I am not finding that easy to solve. Any comments would be appreciated.

Please for give. Another silly senior moment. :Doh: Thanks Bryan

Hello Is there any particular reason why all the text information in my main panel is not centred properly in the text window? Is there a remedy? Everything else seems to be working as it should.

Vaughan Thanks. I thought maybe I had slipped up somewhere along the ASE setup path. Good flying Peter

Help Please, I have ASE correctly installed on my client and FSX on server is receiving wx data. The ' start FS' button is greyed out on the ASE main panel. How can I rectify this? Many thanks Peter Wilshire

Thanks Everyone I too have discovered a work around to get FS2 Crew to work free of the SDK error. This assumes FSX has been 2D panel selected by default. If EZdok camera is installed just leave it alone. Then: 1. Select any FSX default aircraft. I use the trike plane. 2. Choose your intended departure airfield and parking area. 3. Load up flight. Ignore the change from 2D to 3D. (This the part that bugged me!) 4. Select you PMDG 737 NGX aircraft. 5. Wait for aircraft to initialise. 6. Activate FS2 Crew and you should be presented with Version 1.3 in the display screen. Thanks for all your help. Truely appreciated.

Rick It was because I had already set 2D as the default panel in FSX that prompted me to post this question. I was puzzled why I always ended up in a 3D panel situation. As you suggested I put a post in the FS2Crew forum and received prompt and reassuing responses from Bryan and others so much so that I am no longer concerned about the brief 2D display since this is apparantly sufficient time for FS2 Crew to initialise correctly in the 3D view. So I now have FS2 Crew starting up correctly. Thanks again for your help.

Hi there, After setting 2D as the default cockpit view in FSX settings/display, I go into freeflight and load any FSX aircraft, the view initially loads up for a second or two into 2D cockpit view and then automatically changes to a 3D cockpit view. I've only just noticed this because I only ever load up a flight with the PMDG 737NGX addon; which is of course primarily designed for 3D cockpit flying. The only culprit I can think of that might be causing this anomaly is the EZdok Camera Addon. I am reluctant to uninstall this because it is vital for getting around the PMDG 3D cockpit. It can be temporalily disabled once FSX is up and running but by then it's too late the horse has bolted as they say. I don't particularly want to fly in a 2D cockpit view, but it is one of the steps the FS2Crew for PMDG 737NGX developers are advising to resolve an installation problem that I and many others are expierincing, namely the 'SDK not initialised' message that greets you when you start up FS2Crew. BTW I do read all manuals avidly on any software installation to make sure I am doing things the right way, but there are times when things are not happening as the book says. That's life so any comments would be appreciated. Thanks.

Thanks Rick I'll do that because I think your right, it will get a better targeted readership. But it I still think it fits in this forum because it's happening within FSX and is not necessarily specific to 3rd party software. Peter Wilshire

Hi there, After setting 2D as the default cockpit view in FSX settings/aircraft, I go into freeflight and load any FSX aircraft, the view initially loads up for a second or two into a 2D cockpit view and then automatically changes to a 3D cockpit view. I've only just noticed this because I only ever load up a flight with the PMDG 737NGX addon; which is of course primarily designed for 3D cockpit view flying. The only culprit I can think of that might be causing this anomoly is the EZdok Camera Addon. I am reluctant to uninstall this addon because it is vital for getting around the PMDG 3D cockpit. It can be temporarily disabled once FSX is up and running but then it's too late the horse has bolted! I don't particularly want to fly in a 2D cockpit view, but it is one of the steps that the FS2Crew for PMDG 737 NGX developers are advising to resolve an installation problem with their product. ('The SDK not initialised') message on FS2Crew start up. Any comment would be appreciated. Peter Wilshire