Jump to content
The simFlight Network Forums

Start and close Project Magenta MCP with FSUIPC


Recommended Posts

Is it possible to start and close Project Magenta Boeing MCP with FSUIPC!

If yes what must I do ?

Add parameters to FSUIPC.INI, as described in the Advanced User's documentation under the heading "Programs: facilities to load and run additional programs". Have a look, come back if you have any questions.

There's a utility called RunOptions by Jose Oliveira also which may help -- see http://www.schiratti.com/dowson.

Regards,

Pete

Link to comment
Share on other sites

  • 9 years later...

Hello 

 

I have 2 questions on the program start 

 

1-I have managed to start the programs i want but cant get them to close with the kill function,(still working on it)

 

2-Is it possible  over the network via fsuipc to start PM software on other PCs? i am using the easy way (start up file in win7) 

 

kind regards

Link to comment
Share on other sites

I have managed to start the programs i want but cant get them to close with the kill function,(still working on it)

 

CLOSE should work with normal programs, KILL is a bit extreme but needed with some. However, some programs don't create their final window, which FSUIPC needs to detect, for too long after being started. FSUIPC allows a few seconds but it perhaps is sometimes not enough. What programs are you having difficulty with?

 

Is it possible  over the network via fsuipc to start PM software on other PCs? i am using the easy way (start up file in win7) 
 
WideClient can start and close programs automatically, on using a control ("KeySend) from FSUIPC on the host. Just check the WideFS documentation.
 
Pete
Link to comment
Share on other sites

  • 2 weeks later...

Hi 

 

Thanks for the quick reply I was out of town and just got back,

 

I am using Project Magenta,i have tried close1=yes"______" and so of but nothing happen when I close fsx I enter this just below the last run4=

and i close them in the same way but they stay open ,not shore if i have to put the close in a different section.

 

 

i checked the doc and managed to start the programs via wide fs(and not via the win start up file) but still wide fs is in the start up win file what i really what is to be able to have nothing in the start up win file and have all clients and software start after fsx and once closing fsx for them to close, I am working on it but i believe i have missed something.

 

kind regards 

Link to comment
Share on other sites

Hi,

 

WideClient is as the word already says a client and a client needs a server to communicate with. So the server is WideServer, for FSUIPC4 it is included in its dll file, but the client needs to run on the other side.

So the normal and only working setup is that WideClient has to run on the client PC to get the info from WideServer that FS has successfully started. This will be done by having it in Autostart of Windows or starting WideClient manually.

In WideClient you have to start and close programs two options:

1) start programs when WideClient has been started and close when WideClient closes

2)  start programs when FS has successfully started and close when FS closes

Also you need AllowShutdown=...

 

Check page 11 to 14 in WideFS Technical.pdf

Link to comment
Share on other sites

Hi 

 

Thanks for the tip i understand that starting WideFS via the win7 start up and getting the programs to start up via WideFS is good and got it working 

just cant get them to close.

 

Another thing that my sound stupid on my side,I have read the documentation one thing i don't understand is in my config files ti looks like a lot of things are missing

the thing i don't understand is , is that how it is and depending on my needs i go and put the functions i want or is something wrong with my config file.  

 

sorry if its a stupid question.

 

i have attached my fsuipc config and one of my clients WideFS config files Not shore were the problem is

 

 

FSUIPC (FSX MODULES FOLDER)

 

[General]
UpdatedByVersion=4939n
History=OJHJZIMW8UCV0VC844XIY
AxesWrongRange=No
TCASid=Flight
TCASrange=40
AxisCalibration=No
DirectAxesToCalibs=No
ShowMultilineWindow=Yes
SuppressSingleline=No
SuppressMultilineFS=No
AxisIntercepts=No
DontResetAxes=No
InitDelay=0
GetNearestAirports=Yes
OOMcheck=Yes
WeatherReadFactor=2
WeatherRewriteSeconds=1
CustomWeatherModify=No
SimConnectStallTime=1
LuaRerunDelay=66
Console=No
InitDelayDevicesToo=No
NewInterceptTextMenu=No
UseSystemTime=No
UseMidMouseBtn=Yes
MouseWheelMove=No
MouseWheelTrim=No
MouseWheelTrimSpeed=1
JoystickTimeout=20
PollGFTQ6=Yes
BlankDisplays=No
FixControlAccel=No
FixMachSpeedBug=No
DeleteVehiclesForAES=Yes
AutoScanDevices=Yes
VisibilityOptions=No
OneCloudLayer=No
CloudTurbulence=No
CloudIcing=No
GenerateCirrus=No
SuppressCloudTurbulence=No
MaxIce=-4
MinIce=-4
UpperWindGusts=No
SuppressWindTurbulence=No
SuppressWindVariance=No
WindTurbulence=No
TurbulenceRate=1.0,5.0
TurbulenceDivisor=20,20,40,40
SuppressAllGusts=No
MaxSurfaceWind=0
WindLimitLevel=200
WindDiscardLevel=400
WindAjustAltitude=No
WindAjustAltitudeBy=2000
SmoothBySimTime=No
WindSmoothing=No
WindSmoothness=2
WindSmoothAirborneOnly=Yes
PressureSmoothness=0
TemperatureSmoothness=0
DisconnTrimForAP=No
ZeroElevForAPAlt=No
ThrottleSyncAll=No
WhiteMessages=No
ShowPMcontrols=No
SpoilerIncrement=512
MagicBattery=No
RudderSpikeRemoval=No
ElevatorSpikeRemoval=No
AileronSpikeRemoval=No
ReversedElevatorTrim=No
ClockSync=No
ClockSyncMins=5
ClearWeatherDynamics=No
OwnWeatherChanges=No
TimeForSelect=4
LoadFlightMenu=No
LoadPlanMenu=No
PauseAfterCrash=No
BrakeReleaseThreshold=75
SaveDataWithFlights=No
ZapSound=firework
ShortAircraftNameOk=Substring
UseProfiles=Yes
EnableMouseLook=No
DelayedMouseLookZoom=No
FSVersionUsed="Microsoft Flight Simulator X",10.0.61472.0
SimConnectUsed=10.0.61259.0
 
[JoyNames]
AutoAssignLetters=No
0=FDS-FC1
0.GUID={F20C7400-2C01-11E5-8001-444553540000}
 
[WideServer]
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002
 
[user]
AllowShutdown=yes
 
[Axes]
PollInterval=10
RangeRepeatRate=10
 
[Programs]
Run1="C:\Program Files\Project Magenta\pmSounds\pmSounds.exe"
Run2="C:\Program Files\Project Magenta\pmSystems\pmsystems.exe"
Close1=yes"C:\Program Files\Project Magenta\pmSounds\pmSounds.exe"
 
 
[buttons]
PollInterval=25
ButtonRepeat=20,10
 
[AutoSave]
Next=1
Interval=60
Files=10
SaveOnGround=No
AutoSaveEnabled=No
 
[GPSout]
GPSoutEnabled=No
 
[GPSout2]
GPSoutEnabled=No
 
[sounds]
Path=C:\FSX\Sound\
Device1=Primary Sound Driver
Device2=Digital Audio (S/PDIF) (High Definition Audio Device)
Device3=Digital Audio (S/PDIF) (High Definition Audio Device)
 
[ClientNames]
1=CLIENT2-PC
2=CLIENT3-PC
3=CLIENT5-PC
4=CLIENT4-PC
 
 
 
 
And this is the:
 
 
WIDEFS CLIENT
 
 
 
; PLEASE SEE WideFS documentation for parameter details
; =====================================================
 
[Config]
Port=8002
Window=-13,38,820,589
Visible=no
ButtonScanInterval=20
ClassInstance=0
NetworkTiming=5,1
MailslotTiming=2000,1000
PollInterval=2000
Port2=9002
ResponseTime=18
ApplicationDelay=0
TCPcoalesce=No
WaitForNewData=500
MaxSendQ=100
OnMaxSendQ=Log
NewSendScanTime=50
Priority=3,1,2
 
; -----------------------------------------------
[user]
Run1="C:\Program Files\Project Magenta\ABGC\abgc.exe"
Close1=Yes"C:\Program Files\Project Magenta\ABGC\abgc.exe"
 
 
Log=Errors+
Allowshutdown=app
 
; ===============================================
[sounds]
Path=C:\Users\client4\Desktop\WideFS\Sound\
Device1=Primary Sound Driver
 
 
And this the the WIDEFS SEVER
 
; PLEASE SEE the documentation for parameter details
; ==================================================
 
[Config]
Port=8002
 
; -----------------------------------------------
[user]
AllowshutdownShutdown=Yes
Log=Errors+
 
; =================
 
 
it looks very different to the information in the documentation is some could look at it and help out with what i have done wrong.
 
 
kind regards
Link to comment
Share on other sites

[Programs]

Run1="C:\Program Files\Project Magenta\pmSounds\pmSounds.exe"
Run2="C:\Program Files\Project Magenta\pmSystems\pmsystems.exe"
Close1=yes"C:\Program Files\Project Magenta\pmSounds\pmSounds.exe"

 

There is no "Close1=yes"..." parameter supported in FSUIPC. You are evidently not looking up the format of the facilities you want. Please refer to page 45 in the FSUIPC4 Advanced Users document, where you will see the defined formats and options available.

 

You have similar problems in your Wideclient.INI. 

 

[user]
Run1="C:\Program Files\Project Magenta\ABGC\abgc.exe"
Close1=Yes"C:\Program Files\Project Magenta\ABGC\abgc.exe"

 

 

There is no format matching the last line. It is just
Close1=Yes
 
Why not refer to the documentation provided, rather than make it up yourself?
 
Pete
Link to comment
Share on other sites

Thanks for the quick reply i did look at the documentation  but just did not get it right ,

 

so it will have to be something like this:

 

Run1="_____"

Run2=close=yes"________"

 

No no no! You still haven't looked at the documentation! There's no "=yes", just a comma!!! Why not actually look at what it says?

 

Pete

Link to comment
Share on other sites

HI

I read the documentaion and try as it says but still no luck

Run1="(program i want to run)"

Run2=CLOSE,(program i reqested to run)

I tryed KILL too but still dose not close

The program is PM sounds

It start ok but dose not close

My English might not be so good but still dont get it.

Regards

Link to comment
Share on other sites

Run1="(program i want to run)"

Run2=CLOSE,(program i reqested to run)

 

I assume the Run1 program is different to the Run2 program? Earlier you had:

 

Run1="C:\Program Files\Project Magenta\pmSounds\pmSounds.exe"
Run2="C:\Program Files\Project Magenta\pmSystems\pmsystems.exe"
 

So pmSounds then was the first one, not the second.  If that is so, you should be trying:

 

Run1=CLOSE,"C:\Program Files\Project Magenta\pmSounds\pmSounds.exe"
Run2="C:\Program Files\Project Magenta\pmSystems\pmsystems.exe"
 
The "..." around the program name are needed if it contains spaces, as yours does.
 
I run pmSounds like that, with CLOSE, and it works fine, though some older versions of that program didn't close properly, ever.
 
BTW I don't think those programs will like running in "Program Files", because that folder is protected against being written to, and they write their settings and logs there. You'd need to turn UAC off and maybe even run them "as administrator". If you do that you must run FS "as administrator" too. It all gets very complicated. I suggest you move pmSounds and pmSystems to their own folders OUTSIDE of Program Files.
 
Pete
Link to comment
Share on other sites

Hi

Run1 is the same program as run 2 is what i am trying to close,so i am trying to just open it

Run 1="______"

And then close it

Run2=CLOSE,"_______"

I tryed it with "--" but had the same resault

If its only 1 program

I am trynig to get it working and the try on the other clients

Regards

Link to comment
Share on other sites

Hi

Run1 is the same program as run 2 is what i am trying to close,so i am trying to just open it

Run 1="______"

And then close it

Run2=CLOSE,"_______"

 

 

No! No!

 

The start and close is in the one line!!! The CLOSE is an option. All Run lines run the program and optionally CLOSE, KILL or DELAY them! Please please please READ the documentation!

 

Just ONE line per program!!

 

I showed you exactly that in my last message!

 

 

Pete

Link to comment
Share on other sites

Hi

That explains it to me i was thinking

Evey line was a step so

run all programs and the close all programs, so i get it for each progam i want to run and close

Its one line

Run1=CLOSE,"----------"

That it I will try it tomorrow ,it clears every thing know

Let you how it gose thanks alot for the help

Regards

Link to comment
Share on other sites

Hi

I fixed it by the way you explained Run1=CLOSE,"_______"

It works perfict thanks a alot!!!!

I tryed the same thing on the client but got error [267] and softwear will not open dose the clients need somethig diffrent?

Regards

Link to comment
Share on other sites

I tryed the same thing on the client but got error [267] and softwear will not open dose the clients need somethig diffrent?

 

WideFS is DIFFERENT to FSUIPC. The parameters are nothing like the same. PLEASE PLEASE refer to documentation!

 

Pete

Link to comment
Share on other sites

Hi

I got it working just one small thing i dont get from the documentaion,

I want to set it up as when i close FSX for all softwear and pc to shut down,reading the documetation i set it as it says but once i close fsx it dose not close the clients

If when fsx is runnung i press the close widefs application witch comes with wide fs i works all pc close down,

I first set in the wide sever ini witch is in the fsuipc

[user]

Autoshutdown=yes

And then in the client under user i set

Allowshutdown=yes

This way it works with the close widefs application

I also check the widesever0 log and i sed sending close signal to clients (something like that)

I am looking at the documentaion again but dont know were i have gon worng

Regards

Link to comment
Share on other sites

I want to set it up as when i close FSX for all softwear and pc to shut down,reading the documetation i set it as it says but once i close fsx it dose not close the clients

 

Sometimes the problem is that FSX closes before WideFS manages to signal this to the Clients. What I do is assign a keypress (I use Ctrl+Shift+E) to the WideServer "ShutdownHotkey". The parameter is in my FSUIP4.INI file in the [WideServer] section, and looks like this:

 

ShutdownHotkey=69,11

 

This works fine for all my clients. 

 

Pete

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • 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.