Jump to content
The simFlight Network Forums

Prepar3D


Recommended Posts

I've bought Prepard3D and FSUIPC 4.x.

The Prepar3D sim works fine but I can not install the FSUIPC. I did already contact the support form Prepar3D

and they point to the FSUIPC installer. As soon as I start the FSUIPC installer I get following msg:

***************************************************

Installer for FSUIPC4.DLL version 4.60a

Looking in registry for FSX install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\10.0

Parameter"AppPath"

... NOT found! ...

Looking in registry for ESP install path:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"SetupPath"

Not there, so looking in:

HKEY_CURRENT_USER\SOFTWARE\Microsoft\Microsoft ESP\1.0

Parameter"AppPath"

... NOT found! ...

... NOT found! Asking user to find the .EXE instead ...

****************************************************************************

It looks like the isnatller cant find the P3D.exe...

If I point the installer to the Prepar3D folder it will also not work because the isnatller is asking for FSX.exe or ESP.exe.

What do I'm wrong here?

Thank you!

Steffen

Link to comment
Share on other sites

I've bought Prepard3D and FSUIPC 4.x.

The Prepar3D sim works fine but I can not install the FSUIPC. I did already contact the support form Prepar3D

and they point to the FSUIPC installer. As soon as I start the FSUIPC installer I get following msg:

***************************************************

Installer for FSUIPC4.DLL version 4.60a

What do I'm wrong here?

You might not have noticed its date, but Version 4.60a came out long before Prepar3D so it could not possibly recognise it. The first installer and FSUIPC version which copes with Prepar3D is 4.638 which is available in the Download Links subforum here.

Where did the Prepar3D support folks point you to? Surely not the current release version on the Schiratti site?

I am slowly working through the documentation updates which will enable me to put together proper new full releases for the Schiratti site, but meanwhile there are always lots of interim updates posted in the subforums here, where I can control things myself rather than have to ask Enrico each time.

Regards

Pete

Link to comment
Share on other sites

I did enter a few times my registartion key for FSUIPC7 and WIDEFS... The installer says OK, but if I run P3D your window says unregisters version.

Show me the FSUIPC4 log file from the FS Modules folder.

There are separate keys for WideFS and FSUIPC. You need to enter both in the same install, by selecting 'both'.

Why did you enter them "a few times"? Did you make sure to use the correct name and email, to go with the Keys?

There is absolutely no difference in registration for Prepar3D from FSX or ESP. It hasn't changed.

Pete

Link to comment
Share on other sites

Hi Pete,

now everything is running fine, but I have a problem with the WideFS connection...

FSUIPC und WideFS server are running under WIN 7 64bit with Prepar3D..

I can see the FSUIPC menu insde the sim and I have the msg in the P3D program window

"WideServer: waiting for clients"

The WideFS Client is running on a WINXP (SP3 Home Edition) mashine and says waiting for connection..

Both mashines running in the sam network address ramge and same sub net mask. They are in the same workgroup und

the fire wall on both mashines is off....

What do I wrong here??

Many thanks!

Steffen

Link to comment
Share on other sites

Both mashines running in the sam network address ramge and same sub net mask. They are in the same workgroup und

the fire wall on both mashines is off....

What do I wrong here??

If all those things are true -- same workgroup name and no firewalls, then I have no idea. I would need more information. There are three relevant logs -- FSUIPC4.LOG and WideServer.LOG in the P3D modules folder, and WideClient.LOG in the WideClient folder. And can I assume you have not edited the INI files in either?

Please paste logs into a message in this thread. Make sure P3D is closed first, please.

Pete

Link to comment
Share on other sites

Hi Pete,

yes no change in the ini files...

I did remove the e-mail and user name details from the FSUIPC for security reasons..

********* FSUIPC4, Version 4.638 by Pete Dowson *********

Reading options from "C:\Program Files (x86)\Lockheed Martin\Prepar3D\Modules\FSUIPC4.ini"

Trying to connect to SimConnect ESP Orig ...

FSUIPC4 Key is provided

WideFS7 Key is provided

Running inside Prepar3D on Windows 7 (using SimConnect ESP Orig)

Module base=61000000

Wind smoothing fix is fully installed

DebugStatus=255

46 System time = 22/02/2011 10:49:21

1045 FLT UNC path = "\\EVS-PC2\Users\EVS\Documents\Prepar3D Files\"

1045 FS UNC path = "\\EVS-PC2\Lockheed Martin\Prepar3D\"

1404 LogOptions=00000000 00000001

1404 SimConnect_Open succeeded: waiting to check version okay

3151 Running in "Lockheed Martin® Prepar3D®", Version: 1.0.1993.0 (SimConnect: 1.0.21.0)

3572 SimStart Event: Initialising SimConnect data requests

3572 FSUIPC Menu entry added

3619 \\EVS-PC2\Users\EVS\Documents\Prepar3D Files\EDDC TEST START.flt

3619 \\EVS-PC2\Lockheed Martin\Prepar3D\SimObjects\Airplanes\B737_800\Boeing737-800.AIR

20779 System time = 22/02/2011 10:49:42, Simulator time = 12:12:49 (11:12Z)

20779 Aircraft="Boeing 737-800 Paint1"

21980 Advanced Weather Interface Enabled

1679335 Sim stopped: average frame rate for last 1657 secs = 22.4 fps

1687072 System time = 22/02/2011 11:17:28, Simulator time = 12:40:27 (11:40Z)

1687072 *** FSUIPC log file being closed

Average frame rate for running time of 1657 secs = 22.4 fps

Memory managed: 395 Allocs, 395 Freed

********* FSUIPC Log file closed ***********

********* WideServer.DLL Log [version 7.638] *********

Blocksize guide = 4096 (double allowed)

Date (dmy): 22/02/11, Time 10:49:25.038: Server name is EVS-PC2

15226 Initialising TCP/IP server

15226 Initialising IPX/SPX server

15226 IPX/SPX socket() failed [Error=10044] Socket type not supported

15226 Failed to start IPX/SPX Server

15226 Initialising UDP/IP server

16209 Broadcasting service every 1000 mSecs

1681067 Closing down now ...

Memory managed: Offset records: 395 alloc, 394 free

Read buffer usage: 0 alloc, 0 free, max in session: 0

Write buffer usage: 0 alloc, 0 free, max in session: 0

Throughput maximum achieved: 0 frames/sec, 0 bytes/sec

Throughput average achieved for complete session: 0 frames/sec, 0 bytes/sec

********* Log file closed *********

********* WideClient Log [version 6.841] Class=FS98MAIN *********

Date (dmy): 22/02/11, Time 11:03:00.250: Client name is ASE-NOTEBOOK

219 LUA: "C:\Wide FS\Initial.LUA": not found

250 Attempting to connect now

1250 Trying to locate server: Need details from Server Broadcast

1250 Failed to connect: waiting to try again

3250 Attempting to connect now

4547 ****** End of session performance summary ******

4547 Total time connected = 0 seconds

4547 Reception maximum: 0 frames/sec, 0 bytes/sec

4547 Transmission maximum: 0 frames/sec, 0 bytes/sec

4547 Max receive buffer = 0, Max send depth = 0, Send frames lost = 0

4547 ********* Log file closed (Buffers: MaxUsed 0, Alloc 0 Freed 0 Refused 0) *********

I hope you can find the problem!

Many thanks Steffen

Link to comment
Share on other sites

yes no change in the ini files...

Well, you may need to change the Widecliemt.INI file. Look:

********* WideServer.DLL Log [version 7.638] *********

...

16209 Broadcasting service every 1000 mSecs

********* WideClient Log [version 6.841] Class=FS98MAIN *********

1250 Trying to locate server: Need details from Server Broadcast

1250 Failed to connect: waiting to try again

Seems that the broadcasts from the server are not reaching the Client. This can only be due to one of three things:

1. The two PCs are in different workgroups. The names need to be the same. XP and Vista/Win7 have different default workgroup names -- but you said you'd fixed that?

2. One of the operating systems involved doesn't support broadcasting (Win95/98/Me, maybe original XP before SP1).

3. The broadcasting and listening ports are blocked by firewalls (9002 is the default port used by WideFS for this).

You don't HAVE to let them connect automatically by broadcasts. Please see the User Guide -- you can supply the ServerName, or ServerIPAddr, and Protocol parameters to Wideclient, and it will then not wait for a never-arriving broadcast.

Regards

Pete

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Loading...
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use. Guidelines Privacy Policy We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.