Jump to content

Archived

This topic is now archived and is closed to further replies.

smpetty

Prepar3D v2

Recommended Posts

I am having problems with OpusFSX v3.36.1 and Prepar3D v2. Running OpusFSX causes Prepar3D v2 to crash at the new FSX-like startup screen. It happens whether I run OpusFSX before or after running Prepar3D. I have uninstalled and reinstalled OpusFSX, checked that the dll and exe files in the OpusFSX folder all have the same date, made sure that I have only one installation of OpusFSX, downloaded the Prepar3D v2 SDK and copied the Simconnect.xml file from the SDK to my User/Appdata/Roaming/Lockheed Martin/Prepar3D v2 folder (the same folder where the Prepar3D.cfg file resides), and disabled update weather at startup all to no avail. Earlier today before the crashes, I was able to get it working once or twice in P3D v2 but my external camera views all showed a skeleton of my aircraft (the stock Maule). Now it crashes every time.

 

I have had OpusFSX running beautifully with Prepar3D v1.4 for many months and have become dependent on Opus for great weather and great views. Please help!

 

Thanks,

 

Scott

Share this post


Link to post
Share on other sites

You must install the P3D V2 SimConnect software so that is compatible with the v2 software.

 

The skeleton view is because the Cameras.CFG file is not being amended and the Opus [CameraDefinition.999] is missing at the start of the file. You could copy the definition from your FSX Cameras.CFG or old V1 P3D one for now.

 

I will post a new beta very soon to accommodate the new 'Prepar3D v2' folder name.

 

Stephen

Share this post


Link to post
Share on other sites

 

 


You must install the P3D V2 SimConnect software so that is compatible with the v2 software.

 

To install the P3D V2 SimConnect software, do I edit the SimConnect.xml file that came in the P3D V2 SDK and put that file in the same folder as my Prepar3D.cfg (for P3D V2) file?  If so, what entries do I put in for Address (my computer's IP address?) and Port?

 

Thanks,

Scott

Share this post


Link to post
Share on other sites

I think you need to install the SimConnect.msi for the v2 P3D. I believe this version is backward compatible with the older SimConnects but is needed for compatibility with P3D v2. I will be carrying out further tests with P3D v2 very soon (now that I have repaired my P3D PC when its HDD crashed), but most users are reporting installing the v2 SimConnect is working fine.

 

I will also be posting a new beta or release soon correcting the Live Camera external view problem. The current software is looking of the Cameras.CFG file in the Perpar3D folder which is now called 'Prepar3D v2'. This CFG file has the [CameraDefinition.999] inserted at the top for the Opus External Aircraft view.

 

Stephen

Share this post


Link to post
Share on other sites

Stephen -

 

What values should I use for port and address in the SimConnect.xml file?  There is no SimConnect.msi file that I can find in the P3D V2 SDK or anywhere on the Lockheed Martin site.

 

Thanks,

 

Scott

Share this post


Link to post
Share on other sites

Just install the P3D V2 SDK then, that should include it. But I haven't done it myself. The xml file will be the same as FSX running on a single PC. You could Google it or wait until I can post my FSX one. I believe I may have already posted my FSX one in another topic ... P3D V2 Demo Mode or something similar.

 

Stephen

 

Here's my SimConnect.xml for FSX ...

 

<?xml version="1.0" encoding="Windows-1252"?>

<SimBase.Document Type="SimConnect" version="1,0">

<Descr>SimConnect</Descr>

<Filename>SimConnect.xml</Filename>

<Disabled>False</Disabled>

<SimConnect.Comm>

<Disabled>False</Disabled>

<Protocol>Auto</Protocol>

<Scope>local</Scope>

<Address></Address>

<MaxClients>64</MaxClients>

<Port></Port>

<MaxRecvSize>4096</MaxRecvSize>

<DisableNagle>False</DisableNagle>

</SimConnect.Comm>

</SimBase.Document>

 

But I believe you must install the P3D V2 SimConnect for compatibility.

 

Stephen

Share this post


Link to post
Share on other sites

There is no P3D simconnect,msi and all needed files are installed during the installation. There should also be no need to have the simconnect.xml in your apps folder unlles your running a client server setup. LM explains in the SDK learning center why P3D doesnt use the msi. If your missing required simconnect files, a repair may solve the problem. Now if your using a client computer things are more complicated. If Opus supplies a simconnect.msi, you can try running that. It should be in the Opus installation folder.

 

Now, there is an issue/bug with the new P3DV2 startup screen causing CTD's that may be you problem all along and have nothing to do with Opus or simconnect.

Share this post


Link to post
Share on other sites

 

 


There should also be no need to have the simconnect.xml in your apps folder unlles your running a client server setup.

 

I'm not running a client server setup... just a simple one computer installation

 

 

 


Now, there is an issue/bug with the new P3DV2 startup screen causing CTD's that may be you problem all along and have nothing to do with Opus or simconnect.

 

As long as I don't run OpusFSX, the new P3DV2 startup screen works well and I have no problems.  As soon as OpusFSX runs, the startup screen crashes to the desktop.

 

 


If your missing required simconnect files, a repair may solve the problem.

 

I guess that's all that I can do to try and get OpusFSX and P3DV2 working?  I'll try running the P3DV2 installer again and repair what I have.

 

Thanks for your help Rendi,

 

Scott

Share this post


Link to post
Share on other sites

OpusFSX is an external program that connects to P3D in an identical fashion, in fact that software has no knowledge of what sim it is connecting to. P3D simply accepts the connection at the other end. Hence OpusFSX cannot influence P3D in the manner you are hinting at. The problem is within P3D, just because the problem doesn't manifest itself until some external program like the Opus FSXSERVER program tries to connect with SimConnect matters not.

 

In other words just because P3D only crashes when Opus connects counts for nothing. Opus cannot influence or cause P3D to crash, I couldn't do that even if I wanted to, that's all down to just the fragility if P3D V2 with respect to its SimConnect handling.

 

Stephen

 

Many people are running OpusFSX with P3D V2. It is P3D that is the new unknown here. Opus connects via SimConnect and this connection is totally independent of the sim type. Opus connects in an identical fashion no matter what sim or version of sim software is running at the other end. My advice would be to reinstall SimConnect using our supplied msi. But please, it is the P3D V2 software that is the new unknown here. Everything from the SimConnect link onward including all the external and independent Addons trying to connect to the sim have not changed here, only the P3D V2 code.

 

Stephen

Share this post


Link to post
Share on other sites

OpusFSX is an external program that connects to P3D in an identical fashion, in fact that software has no knowledge of what sim it is connecting to. P3D simply accepts the connection at the other end. Hence OpusFSX cannot influence P3D in the manner you are hinting at. The problem is within P3D, just because the problem doesn't manifest itself until some external program like the Opus FSXSERVER program tries to connect with SimConnect matters not.

 

In other words just because P3D only crashes when Opus connects counts for nothing. Opus cannot influence or cause P3D to crash, I couldn't do that even if I wanted to, that's all down to just the fragility if P3D V2 with respect to its SimConnect handling.

 

Stephen

 

Many people are running OpusFSX with P3D V2. It is P3D that is the new unknown here. Opus connects via SimConnect and this connection is totally independent of the sim type. Opus connects in an identical fashion no matter what sim or version of sim software is running at the other end. My advice would be to reinstall SimConnect using our supplied msi. But please, it is the P3D V2 software that is the new unknown here. Everything from the SimConnect link onward including all the external and independent Addons trying to connect to the sim have not changed here, only the P3D V2 code.

 

Stephen

 

Understood - realize that I never meant to "hint" that OpusFSX was the culprit and P3D V2 the victim.  I just want my simulator working with Opus.  I have used Opus since it was released on both FSX and P3D V1.4 and I have become dependent on the camera and weather Opus provides. 

 

 

I have had OpusFSX running beautifully with Prepar3D v1.4 for many months and have become dependent on Opus for great weather and great views.

 

That was me at the beginning of this thread... obviously I'm not an angry Opus customer... I was just asking for help from the experts.

 

You must install the P3D V2 SimConnect software so that is compatible with the v2 software.

 

I think you need to install the SimConnect.msi for the v2 P3D

 

Just install the P3D V2 SDK then, that should include it

 

I followed your advice, installed the SDK, could not find SimConnect.msi in the SDK or on the LM web site (because it doesn't exist), and asked for clarification.  I never cast aspersions at Opus software, so please calm down.  I am still where I started - Opus and P3D V2 don't work together on my rig.  Is there anything else that I can try?  Any log files or testing that I might be able to do on my end that would shed light on this issue?

 

Scott 

Share this post


Link to post
Share on other sites

Yes, install SimConnect using the msi in your OpusFSX folder.

 

The only reported problems have been overcome by creating a SimConnect.xml file (see above) and installing SimConnect.

 

Stephen

Share this post


Link to post
Share on other sites

I installed SimConnect using the msi in my OpusFSX folder and I created a SimConnect.xml file and put it in the Users/Appdata/Roaming/Lockheed Martin/Prepar3d v2/ folder.  P3DV2 still crashes when Opus is running.  I monitored the Spy window and here is what it showed (please see attached files)...

 

Scott


if Opus is run BEFORE P3Dv2 it will run OK every time, it has to load always before P3D.

 

In my case, P3DV2 crashes if I run Opus before or after P3DV2.

Share this post


Link to post
Share on other sites

Your SimConnect link is clearly not working correctly hence all the errors reported in the Spy window. The connections seem to be made but the SimConnect request are just failing. I will try and see what the error code means by I am now wondering if there is a V2 SimConnect that you must install. I cannot advise you much on this one. I will try and find out myself about installing a correct SimConnect.

 

Stephen

Share this post


Link to post
Share on other sites

You can test your simconnect functionality  by putting the simconnect.ini in your simms document folder, make sure console is set to 1. Open the Simm, you should get a console window, simconnect diagnostic output if simconnect is communicating.

Share this post


Link to post
Share on other sites

Your SimConnect link is clearly not working correctly hence all the errors reported in the Spy window. The connections seem to be made but the SimConnect request are just failing. I will try and see what the error code means by I am now wondering if there is a V2 SimConnect that you must install. I cannot advise you much on this one. I will try and find out myself about installing a correct SimConnect.

 

Stephen

 

Thank you Stephen!

 

Scott

You can test your simconnect functionality  by putting the simconnect.ini in your simms document folder, make sure console is set to 1. Open the Simm, you should get a console window, simconnect diagnostic output if simconnect is communicating.

 

I will try that - thanks Rendi

Share this post


Link to post
Share on other sites

Now that we are back in the office and my machine is repaired all I can do is download and install the V2 software then let you know what we find and what files we have installed.

 

Stephen

Share this post


Link to post
Share on other sites

 

We are downloading P3D V2 now, we only have medium speed Internet though so I won't be able to install until tomorrow.

 

Stephen :-)

Share this post


Link to post
Share on other sites

We are downloading P3D V2 now, we only have medium speed Internet though so I won't be able to install until tomorrow.

 

Stephen :-)

 

Thanks again Stephen, I really appreciate your help.

 

Scott

Share this post


Link to post
Share on other sites

Installing Prepar3d Version 2 ....

 

I have installed and carried out a quick test of OpusFSX with the new Prepar3d v2 software with no problems.

 

Procedure,

 

To install onto my dedicated E drive in folder 'E:\Prepar3D v2',

 

1. I first recorded all purchase and licensing details into a c:\Prepar3D folder.

 

2. I downloaded the Install Instructions and v2 installation zip file into my c:\Prepar3D folder.

 

3. I extracted all installation files into a sub-folder of c:\Prepar3D.

 

4. I navigated to the extracted files and ran the Prepar3D.msi installation file (not the Setup.exe program).

 

5. After installation and activating the license I paused the simulator and configured all Prepar3D setting, starting off with a target frame rate of 40 fps (just for test).

 

6. I ran the FSXSERVER program (latest release version 3.37.2, to be posted later today). The FSXSERVER program was working fine with FSX previously, opened the Configure dialog, changed the simulator type to Prepar3D and identified the 'E:\Prepar3D v2' installation folder.

 

7. I restarted the FSXSERVER program opened Spy and ensured it connected OK via SimConnect which it did. I got the initial FSUIPC4 errors since I do not have FSUIPC4 installed for P3D v2 yet.

 

8. I relocated the aircraft to EGNX then with my Spy window open and the Upper Atmosphere weather report opened I set my Destination to EGKK, cruise altitude to 8000 feet and Updated the weather. I followed the GRIB and METAR downloads in the Spy and Weather report windows. The weather loaded without problem and the Lower/Upper wind and temp data appeared in the report. Both Local and Destination reports were correct.

 

9. I opened the Cameras dialog to ensure all CFG files had been modified. Restarted both Prepar3D and the FSXSERVER program and tested some camera editing and displays. All worked fine.

 

At all times I manually ran the FSXSERVER program from its desktop icon AFTER first running and initialising Prepar3D v2.

 

I did not need to create a SimConnect.xml file in the Prepar3D.CFG folder nor did I need to do anything to obtain a good SimConnect connection although my FSXSERVER program had been working perfectly well with FSX, which is installed on my dedicated F drive.

 

I did NOT install 'Prepar3D v2' in Program Files, I always install FSX and Prepar3D into its own named folder. For example, my Prepar3D is installed in E:\Prepar3D v2 and my FSX is installed in F:\FSX. Only files that the simulators need to access share the dedicated SSD.

 

Stephen :smile:

Share this post


Link to post
Share on other sites

Thanks Stephen.  

 

I will uninstall and reinstall P3Dv2 (although I followed the same procedure that you outline above) and upgrade to the new Opus version 3.37.2 and will let you know if it works.  

 

Scott

Share this post


Link to post
Share on other sites

Do you already have a working system with FSX ? If not then I would advise installing SimConnect using our msi BEFORE installing P3D v2 using its msi file.

 

I had absolutely no problems and didn't need to do anything other than the above procedure. Note, after opening the Cameras dialog, resulting in amending the CFG files for the first time, you must restart both the sim and the FSXSERVER program.

 

I would also recommend a complete uninstall of P3D before installing v2.

 

Stephen

 

Also I did not install any other Addons for P3D v2. I only ran the Prepar3D.msi file with no other P3D product installed on the computer, which only had my working FSX system.

 

Stephen

 

I did add the HIGHMEMFIX statement to the Prepar3D.CFG file.

 

I also had Custom Weather set, 100 mile cloud draw distance, detailed and fairly dense clouds, and volumetric fog enabled in both Opus and P3D.

 

Stephen

Share this post


Link to post
Share on other sites

Quick update -

 

I can run P3D v2 and OpusFSX together with no crashes as long as I let P3D v2 go straight into the flight.  If I let P3D v2 bring up the FSX-like new startup screen (where you can pick weather, aircraft, time and location before starting the flight), P3D v2 will crash to the desktop in seconds whether I run Opus before or after P3D v2.  

 

Seems odd.  Any thoughts Stephen?

 

Also I wanted to ask about my camera views.  I made a copy of my P3D v1.4 P3DSERVER.CAM file.  I still have P3D v1.4 installed and will primarily use it until the P3D v2 has some of the kinks worked out.  Anyway I ran P3D v2 using the same P3DSERVER.CAM file that I created in P3D v1.4, I opened the camera dialog in Opus after everything was loaded to let it update the file, closed all, and re-ran all.  The skeleton airframe issue on outside views is resolved, but my viewpoint is shifted 50 or so yards in front of the aircraft on all external views.  All internal views work perfectly as in P3D v1.4.  Is there any way to fix/shift the external views other than editing those views for each aircraft?  Did I do something wrong?

 

Thanks,

 

Scott

Share this post


Link to post
Share on other sites

×
×
  • Create New...