I have read through the manuals and searched the forums for an answer to this but couldn't come up with anything.

I followed the instructions in the setup guide to have OpusFSX Autostart but it does not work for me. I am sure there is something I have missed but cannot figure it out.

 

I opened the dll file located in C:\"user"'\AppData\Roaming\Microsoft\FSX

 

 

and added the required entries....

 

also note I changed the drive from c to d which is where FSX and Opus are installed

 

Any ideas what I am doing wrong?

Thanks. Tom

Hi Tom

 

That looks OK to me. I assume OpusFSX runs without problem when you run it manually.

 

When it first runs automatically you should be prompted to trust OpusFSX. Have you accepted OpusFSX as a trusted program? You could edit your fsx.cfg file and delete any old trust entries for OpusFSX or see if any exist.

 

Regards

Cheryl

Cheryl,

 

Thanks for the quick response. Yes OpusFSX runs just fine manually. I did run it once before setting up the auto start and trusted the OpusFSX prompts so I will go through the fsx.cfg and delete those and try that.

 

I forgot to mention that I am running TrackIR5. As a side note TIR5 is running perfectly fine within the FSX/Opus environment. So not sure that should be causing an auto start issue.

 

I will post back when I delete those cfg entries and restart FSX.

 

Tom

Hi Tom

 

TrackIR won't effect the OpusFSX auto start but the proper procedure is to run TIR before OpusFSX.

 

Our Getting Started guide describes how to set up TIR to run with OpusFSX.

 

Regards

Cheryl

Oddly enough there are no OpusFSX entries in the Trusted Section of my fsx.cfg file. Neither am I asked to run any from OpusFSX upon FSX start up.

 

(I have FSX on its own partition of my secondary HDD labelled D: drive. but that should not make a difference with any of this as all paths are correct for all software involved.) And as stated above OpusFSX runs great if started manually.

 

Some might say "well if it runs fine manually why bother with auto start." My answer is because it won't when it should and I just can't have that. :huh:

 

Cheryl,

 

I run TrackIR5 on system start up so it is always the first thing loaded up. :wink:

I think you edited the wrong file. It should be in exe.xml file.

 

Cheryl

 

You have edited the wrong file. You have put the statements inside the DLL.xml file which defines what libraries to load. You must edit the EXE.xml file which defines what program's you wish to run on start up.

 

Regards

Stephen

Ok where is this file located? It is not in C:\User\"Me"\AppData\Microsoft\FSX folder

If it is not there you will have to create one. An example is in our Getting Started guide.

 

Cheryl

The plot thickens so off I go.... <_<

 

Be back when I get it fixed

Hi Tom, Cheryl and Stephen,

 

An alternative method to start OpusFSX or any other program for that matter is to add the following entry in your FSUIPC configuration file located in the Modules folder of FSX:

 

[Programs]

Run1=READY,"D:\FSX\Modules\AISmooth.exe"

Run2=READY,"C:\OpusFSX\FSXSERVER.EXE"

etc., i.e., 3rd program to be started after FSX

 

Those entries will cause the listed programs to start after FSX has loaded the flight and also close after FSX is terminated. Should a program fail to close once FSX is terminated, use the following script instead:

 

Run1=READY,CLOSE,"D:\FSX\Modules\AISmooth.exe"

 

Additional information along with more elaborate scenarios are available on page 43 of FSUIPC's Advanced Users' Manual.

 

I use the first example which runs without any itches.

 

Regards,

 

JJ

JJM,

Tried that still isn't auto starting. Here is a screeny of my FSUIPC4 cfg (Registered version)...

 

and this one is from the FSUIPC txt doc

 

 

Well there is obviously something I am not doing quite right here.

***Tried running with just the READY function in FSUIPC.cfg and after the flight loads I hear a system "ding" tone then nothing else happens. Upon closing out and checking the FSUIPC txt doc again there is the ERROR 740 code.

Just follow our Getting Started guide, it is very simple and straight forward, and stop wasting yours and our time trying other non-recommended methods. Just use the standard FSX method of using the standard EXE.xml file like all other packages do. All you need to do is cut and paste the statements to create your own EXE.xml file using Notepad.

 

Stephen

Create an exe. txt document and paste the following:

 

 

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

<SimBase.Document Type='Launch' version='1,0'>

<Descr>Launch</Descr>

<Filename>exe.xml</Filename>

<Disabled>false</Disabled>

<Launch.ManualLoad>False</Launch.ManualLoad>

<Launch.Addon>

<Name>OpusFSX Flight Simulator Server for FSX</Name>

<Disabled>false</Disabled>

<Path>c:\OpusFSX\FSXSERVER.EXE</Path>

</Launch.Addon>

</SimBase.Document>

 

Rename this file to an xml,and place it in the same folder as your FSX.cfg.

 

Make sure the correct path is specified for the FSXSERVER.EXE.

 

Hope this helps.

Starting the OpusFSX Software Automatically with FSX

 

The FSXSERVER program can be started automatically each time FSX is run, simply by editing the content of the standard FSX 'exe.xml' file. The 'exe.xml' file can be found within the standard 'c:\Users\username\AppData\Roaming\Microsoft\FSX\' directory where 'username' identifies your login account name.

 

Edit the FSX 'exe.xml' file using Notepad. Paste the contents of the OpusFSX _ExeXml_Server.txt file at the end of the xml content. You should paste the content in just before the closing </SimBase.Document> statement.

 

For example, after editing the content of the 'exe.xml' file, the content should look something like this,

 

<?xml version='1.0' encoding='Windows-1252'?> <SimBase.Document Type='Launch' version='1,0'> <Descr>Launch</Descr> <Filename>exe.xml</Filename> <Disabled>False</Disabled> <Launch.ManualLoad>False</Launch.ManualLoad> <Launch.Addon>

<Name>OpusFSX Flight Simulator Server for FSX</Name> <Disabled>false</Disabled> <Path>c:\OpusFSX\FSXSERVER.EXE</Path>

</Launch.Addon>

</SimBase.Document>

 

Of course you may already have several Addons listed in the exe.xml file. In which case you will find each Addon specified within a separate <Launch.Addon> .. </Launch.Addon> block.

 

You will need to edit the c:\OpusFSX\FSXSERVER.EXE entry and specify the correct drive location if you have installed it anywhere other than the standard C drive.

 

Stephen

 

Thanks Dimitri

 

Just saw your post as well ... :-)

 

Regards

Stephen

I created the exe.xml file and placed it in the same folder as the fsx.cfg file. Started FSX, accepted FSXSERVER.EXE as trusted and loaded my flight...NOTHING.

 

The only way I can get the Opus FSI Server window or the FSXTRACKIR5.exe window or the addon tab options for Opus is to manually start the program.