wideFS client problems

[sisoffi]

Hi Pete,

i have this strange problem because when p3d client is used and lanch wideFS it cannot start beacuse

said me that "another program is running". the only program in conflict is Prepar3D. I use OpusFS to syncronize server and client 

and IVAP in multipc.

i close P3d i lanch both Opus and IVAP and with WideClient work perfect! 

 

what can i do to resolve?

 

many thanks,

Simone

[Pete Dowson]

18 minutes ago, sisoffi said:

i have this strange problem because when p3d client is used and lanch wideFS it cannot start beacuse said me that "another program is running". the only program in conflict is Prepar3D.

The whole point of WideClient is to look like FS or P3D, so FSUIPC applications will connect to it rather than to FS or P3D.  You cannot have two programs running both looking like P3D, and that is why you get the error. After all, how would the applications know which to connect to?

If you are only using WideClient for its contained facilities, like button transmission to FSUIPC or keysend actions from FSUIPC, or maybe for Lua plug-ins, then you can do that by setting the "ClassInstance" parameter in the INI file to something other than 0. FSUIPC applications will not be able to use it unless they have a parameter like this too, which most do not, so applications will try to connect to FSUIPC inside the local copy of P3D.

Pete

 

[sisoffi]

i use widefs for the teamspeak button from server to client (taht dont work)

via keysend wide FS.  So:

i lanch p3d and automtaically detect widefs client (server remain in wait for server)

[Pete Dowson]

1 hour ago, sisoffi said:

i use widefs for the teamspeak button from server to client (taht dont work) via keysend wide FS

Just use a non-zero ClassInstance then, as I said. It's only external applications which cannot talk to WideClient with a different ClassInstance.

Pete

 

[sisoffi]

can you please make an example of strings to put inside .ini?

 

thanks

 

 

[Pete Dowson]

24 minutes ago, sisoffi said:

can you please make an example of strings to put inside .ini?

Strings? Sorry, what are you talking about? All I suggested was CHANGING the "ClassInstance" parameter from 0 to 1. There are no "strings" involved in any of that. Where are you getting such ideas from?

Pete

 

[sisoffi]

ok i will try and report.

 

[sisoffi]

Fsuipc.ini :

.......
[WideServer]

ClassInstance=1
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[ClientNames]
1=SIMONE-PC
[Programs]
Run2=READY,CLOSE,C:\IVAO\IvAp v2\ivap_dllhost.exe
Run1=READY,CLOSE,C:\OpusFSI\FSISERVER.EXE

............

 

It's correct?

[Pete Dowson]

31 minutes ago, sisoffi said:

Fsuipc.ini :

.......
[WideServer]

t's correct?

NO!

I've never mentioned "WideServer". The thing on your client PC is called WideClient! The parameter is in the WideClient.INI file! It is the Client PC, not the Server PC where you have the problem, right? Why would you ever think of changing anything on the Server?

There is no "ClassInstance" parameter on the Server, because it is running inside FS. FS IS FS, it isn't WideClient trying to LOOK like FS!!!

Please do read the messages I've been sending here. I do feel I waste my time a lot when I explain things and folks don't read them. Look back, you'll see we are always talking about the client PC, the one where you have the problem. And WideClient is explicitly mentioned.

Pete

 

[sisoffi]

thanks Pete,

I tried to put in wideclient.ini

classistance=1 but when i click to my button yoke in the server to speak with ATC dont work in teamspeak client.

Is correct that p3d server remain in the status "wideserver: waiting for clients" ?

[sisoffi]

[Config]
Servername=SERVER
Protocol=TCP
ServerIPAddr=192.168.0.1
VISIBLE=no
ButtonScanInterval=20
ClassInstance=1
NetworkTiming=5,1
MailslotTiming=2000,1000
PollInterval=2000
Port=8002
ResponseTime=18
ApplicationDelay=0
TCPcoalesce=No
WaitForNewData=500
MaxSendQ=100
OnMaxSendQ=Log
NewSendScanTime=50
Priority=3,1,2
Window=56,349,258,27
Port2=9002

[sisoffi]

; -----------------------------------------------
[User]
Log=Errors+

; ===============================================

Keysend1 = 162.16; means Press left CTRL key
Keysend2 = 162.24; means Release left CTRL key
UseSendInput = Yes;
;

[sisoffi]

some help???

 

 

Fsuipc.ini :

.......
[WideServer]

ClassInstance=1
WideFSenabled=Yes
AdvertiseService=1
Port=8002
Port2=9002

[ClientNames]
1=SIMONE-PC
[Programs]
Run2=READY,CLOSE,C:\IVAO\IvAp v2\ivap_dllhost.exe
Run1=READY,CLOSE,C:\OpusFSI\FSISERVER.EXE

............

 

It's correct?

[Thomas Richter]

Hi,

I've never mentioned "WideServer". The thing on your client PC is called WideClient! The parameter is in the WideClient.INI file!
It is the Client PC, not the Server PC where you have the problem, right? Why would you ever think of changing anything on 
the Server? 

There is no "ClassInstance" parameter on the Server, because it is running inside FS. FS IS FS, it isn't WideClient trying to 
LOOK like FS!!! 

Didn't you read Pete's comment on that?

You still show that you put the ClassInstance=1 parameter into the FSUIPC.ini file [WideServer] section !?

What is anyway the intension to run a WideClient on the FS PC? What you want to control with the WideClient on the FS-PC that sends to FSUIPC on the same PC to send then something over the network to other WideClients?

Maybe best would be to describe first very clear what you want to achieve.

Thomas

[sisoffi]

no Thomas,

i read the Petes' comment and in the wide server.ini there isnt class instance line.

I put the classinstance from 0 to 1 from correct wideclient.ini but the problem remain:

the P3D in server remain in "wait for client" and dont dialogate with client.

I use wideFS for the click open "click to talk" teamspeak install to Client machine.

Ivao in the client is well configured and in the server diallog well.

 

thanks for your help.

[sisoffi]

this is my wideclient.ini

[Config]
Servername=SERVER
Protocol=TCP
ServerIPAddr=192.168.0.1
VISIBLE=no
ButtonScanInterval=20
ClassInstance=1
NetworkTiming=5,1
MailslotTiming=2000,1000
PollInterval=2000
Port=8002
ResponseTime=18
ApplicationDelay=0
TCPcoalesce=No
WaitForNewData=500
MaxSendQ=100
OnMaxSendQ=Log
NewSendScanTime=50
Priority=3,1,2
Window=56,349,258,27
Port2=9002

; -----------------------------------------------
[User]
Log=Errors+

; ===============================================

Keysend1 = 162.16; means Press left CTRL key
Keysend2 = 162.24; means Release left CTRL key
UseSendInput = Yes;
;

[Thomas Richter]

Hi,

why you use both? You use one or the other, preferred would be ServerName=

Servername=SERVER
ServerIPAddr=192.168.0.1

Also it always helps to see the original full files, you can copy and paste the content here, FSUIPC4.ini / FSUIPC4.log / WideClient.ini / WideClient.log

Thomas

[sisoffi]

i havent wideclient.log because is in work in another machine not at home.

if you can help me just with these files, many thanks

FSUIPC4 Install.log

wideclient.ini

FSUIPC4.ini

[Thomas Richter]

In WideClient.ini you use those lines

Keysend1 = 162.16; means Press left CTRL key
Keysend2 = 162.24; means Release left CTRL key

but you use a decimal ( . ) instead of a comma ( , ), so that will not work at all !

It has to be like this

Keysend1 = 162,16; means Press left CTRL key
Keysend2 = 162,24; means Release left CTRL key

The FSUIPC4 Install.log file doesn't help, it would be the FSUIPC4.log file, located in the same folder where you found the FSUIPC4.ini file.

Please update also to latest FSUIPC4.955c , any older version cannot be supported.

From WideClient.ini file remove the line ServerIPAddr=192.168.0.1 and make sure the ServerName is correct.

ServerName=SERVER

Thomas

[sisoffi]

many thanks thomas ,

i will change all like your guide

and will report.

 

[Pete Dowson]

On 6/18/2016 at 9:10 PM, sisoffi said:

the P3D in server remain in "wait for client" and dont dialogate with client.

"waiting for clients" indicates that yje client isn't connecting to the server. with no connection it will never work. It is nothing to do with "ClassInstance". You need to have a working network for any WideFS options to work.

Assuming the Network is connecting okay for other things, then it is probably your Firewall preventing WideClient getting seen on the Server. 

The WideServer.log and WideClient.log files would be the most useful to see what Windows errors are reported when the connection is attempted. The whole point of programs logging thnigs is to help in these situations -- that is why all my programs always make log files.

Pete

 

 

 

[sisoffi]

i tried some test, nothing.

i use both p3d in server and client pc and use Opus to syncronize weather and position.

the only use of widefs is to send to teamspeak a lick from serve to client. 

I dont unse wideclient.exe application because in client is in use P3d, but afer modification suggest nothing

server remain "in ait for client",

control firewall all ok.

the wideclient.ini where need to stay? in the manual said in a folder you can create at your choise, but need to stay inside p3d root?

WideServer0.log

WideServer.log

[Pete Dowson]

6 minutes ago, sisoffi said:

I dont unse wideclient.exe application because in client is in use P3d, but afer modification suggest nothing

Er, really? If you don't use WideClient.exe, then nothing will ever talk to WideServer, so it will always say "Waiting for clients"!!!

7 minutes ago, sisoffi said:

the wideclient.ini where need to stay? in the manual said in a folder you can create at your choise, but need to stay inside p3d root?

The WideCliennt.INI goes in the same folder as WideClient.exe, and that is where the LOG is generated when you run that WideClient.exe. If you don't run WideClient there's no point enabling WideFS in FSUIPC on the Server!

I think you don't understand anything about WideFS! It takes one SERVER, and one or more CLIENTS. With no clients where is no point! There has to be something taslkning to WideServer, and that can only be WideClient!

Please read more about what WideFS s all about in the documentation included in the ZIP package.

Pete

 

[sisoffi]

thanks Pete, was the .exe dont launch.

Now work and is connect to server :)

excsue me for my confusion.

WideClient0.log

[Pete Dowson]

27 minutes ago, sisoffi said:

was the .exe dont launch.

Now work and is connect to server :)

Yes. The EXE wouldn't launch because the ClassInstance=0 parameter makes it pretend to be FSX/P3D, and you can't have two copies of either running at the same time on the same PC. That's why you changed the ClassInstance parameter!

 

However, the Log you attached doesn't show a connection -- it doesn't see a Server named "DISCOVERY_80_SERVER". Are you sure that's a correct name? I think the name is limited to something less, like 11 or 12 characters!

Pete