• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

FSX WideFS open protocol?

Messages
6
Country
spain
Hi folks,

I don't know if this is the right place to ask this question, but I tried to find out by myself in google and no answers there.

I know WideFS as a Client->Server software that allows you to connect to your FSUIPC remotely, but I don't understand why the protocol it's that close. I mean, Imagine that I want to develop something on my small & unexpensive linux box (let's say, raspberry pi) that connects to my fsuipc to get information about the flight to (for example) create some of the flight instrumentals using those amazing (and again unexpensive) small tft's. I can't, and it's just because the WideFS protocol seems to be so f***ng closed. Do I have any alternative to make this real? my only option is have a full (and expensive) computer to achieve this?

:D I will apreciate any thoughts about the issue, because I'm a little bit lost.
 
If you only plan to use it in combination with FSX you could try Simconnect instead of WideFS/FSUIPC.
 
It should be possible with FSUIPC/WideFS however you always need something to fetch/send the data to FSUIPC which can be either C/vb.net/... then it should work :)
 
Since it's not Open Source or freeware, but rather a commercial solution, I'm not surprised that it's pretty tightly controlled. ;)
 
Thanks for the answers,

I agree with n4gix, it's not an open solution but I still don't understand why the protocol it's not open. I mean, You can have a closed and expensive solution and provide an open protocol make your solution even better. I'm pretty sure that Dawson wants to sell a lot of FSUIPC and WIDEFS's but under my point of view, close the WIDEFS protocol only makes it less attractive, and opening the protocol will not degrade his product because in the and (and does not matter if the protocol it's open) you will always need to buy WIDEFS if you want your linux box talking with FSUIPC.

I will start a new project using Simconnect and a small (and open) piece of software (c# or something like that) on my windows FSX box with an open protocol, maybe HTTP REST to connect ANY device to a remote FSX. From a cell phone to a linux box.

Imagine a web page on your mobile phone showing information of the flight coming from the FSX via Simconnect...

I'm not sure if it's better use Simconnect or FSUIPC but since I'm a little bit angry with mr Dawson, I don't want to make something that help him selling more FSUIPC (anyway, problably anybody interested on this have their own copy of FSUIPC).

Do you thing that this could be interesting?

Thanks for the answers
 
It's Dowson ;) and, of course, it is up to each one of us to decide whether we make our work open source or not. Even a lot of freeware is not open source :)

Also I would not personally assume that I understand at all what Pete wants from his software................
 
scruffyduck I don't complain about the non opensource software, I complain about the closed and undocumented protocols... That's the point that personally I don't undersand.
 
I'm not sure if it's better use Simconnect or FSUIPC but since I'm a little bit angry with mr Dawson, I don't want to make something that help him selling more FSUIPC (anyway, problably anybody interested on this have their own copy of FSUIPC).

I'm afraid you don't know anything about FSUIPC. This dll allows one to send/receive information to/from FS9/FSX.

WideFS is a totally different product not created by Pete Dowson.
 
I don't want to make something that help him selling more FSUIPC

I guess you do not know that most users of FSUIPC do not need to pay for it, nor that without the work Pete has done the FSX community would be much the poorer. FSUIPC is probably the most important third party tool there is for FS. Without it many third party tools that we take for granted would not work. Most of the developers I know would be delighted if they could enhance the reputation of FSUIPC by using it.
 
Golf-HotelDelta,

As far as I know WideFS it's a product intended to make able to connect to FSUIPC from a remote computer.


Code:
          COMPUTER 1                 COMPUTER 2
               FSX
              /\   |
               |   \/
             FSUIPC            FLIGHT PANNEL (by ex)
              /\   |                  /\   |
               |   \/                  |   \/ 
             WIDEFS  <----- LAN -----> WIDEFS

Isn't this right?

And I get this from WideFS User Guide :

--------------
WideFS User Guide
A network application interface for Microsoft Flight Simulator by Pete Dowson, 11h February 2012
--------------

:D Maybe you're the one that don't know anything about WIDEFS or maybe Pete Dawson it's lying us... Or maybe I'm half crazy and living in a parallel dimension.

I don't want to be rude, but your answer seems a little bit of it.
 
scruffyduck,

I guess you do not know that most users of FSUIPC do not need to pay for it, nor that without the work Pete has done the FSX community would be much the poorer.

So you're telling me that when a company like Saitek develop something like (let's say) rudder peddals and include FSUIPC (I don't know exactly if it's a real case) mr Pete receives nothing for it??? Let me doubt it.

FSUIPC is probably the most important third party tool there is for FS. Without it many third party tools that we take for granted would not work. Most of the developers I know would be delighted if they could enhance the reputation of FSUIPC by using it.

I agree with this, but still don't understand some things, that's all...
 
I believe this thread has gone far enough off topic and starting to get personal.

I think we have established the answer to the original question concerning whether or not a protocol is open sourced or not. Whether it is or not is in the hands of the developer.
 
I agree with you and apologies because that's not my intention, I got a little bit angry with the Golf-HotelDelta answer.

Thanks for the answer.
 
Pete Dowson explained some time ago the purpose of WideFS


This is NOT a program for linking several copies of Flight Simulator, nor will it allow scenery or cockpit views on multiple PCs. It is purely for running EXTERNAL applications on a separate PC whilst still communicating with FS as if on the same PC. For such applications to work through WideFS they need to access Flight Simulator through the interface provided and defined by SUIPC (or originally, for FS98 programs, FS6IPC).
[My emphasis]

I assume that still applies?
 
WideFS is a totally different product not created by Pete Dowson.
There was (is?) another product that was often confused with Pete's WideFS client-server utility, but I'll admit that over the past dozen years since I last thought about it I can't remember what it was called or who the author was... :scratchch

That's one of the unavoidable side-effects of age unfortunately; poor memory... :o

Ah-ha! I found it: Wideview by Luciano Napolitana

Wideview
With the Wideview software it is possible to expand the number of outside view monitors without loosing performance, by deviding the load over more then one PC. Wideview is a set of gauges where you have one server and as many clients as you want. The aircraft panels have to be on the server PC. The clients are only used for outside views. MS FS needs to be installed on all PC's and these PC's should be connected by a wireless LAN or ethernet network.

Wideview grabs from FS running on the server PC data like position and attitude (pitch, bank, roll) of the aircraft and broadcast this to all clients. FS on the clients, working in 'slew' mode, uses this to produce the outside views. Wideview can als forward weatherdata from the server the the client PC's
This software is developed by Luciano Napolitana and for more information or downloading a trial version you can go to his webpages at http://www.wideview.it/
See: http://home.wxs.nl/~jarkest/fs/fsnetworking.html for the source of the above quote.
 
Last edited:
Back
Top