I was not aware of historical weather either, but then I never fly real world commercial routes, or use real world airlines, or even use weather at all!!

19 minutes ago, Christopher Low said:

I was not aware of historical weather either, but then I never fly real world commercial routes, or use real world airlines, or even use weather at all!!

Sacrilege!  🙂  J/K obviously I love we can all use the sims however we please but yep, I needed it "explained" to me too.  I've had AS in Live Weather Mode since the day I installed and first started using it...  

I really like the PMDG colours (including the green P3D band at the top of the tailfin), and I have often wondered how many other flight simmers use them.

Edited February 15, 20224 yr by Christopher Low

On 2/13/2022 at 1:11 PM, Bobsk8 said:

We will see which sim is still  around in two years. 

Well hopefully Prepar3d V6 or maybe even V7 by then.

Here I still am using my server + client pc with MSFS and Prosim.

To have my home cockpit hardware working 100% I should build a P3D server and use my current MSFS pc’s as outside view clients using WidevieW.

The issue that I have is that WidevieW does not operate the external lights in the other sim. A P3D server with MSFS clients will not have correct working external lights…..

Hopefully that might change one day 🤗 

12 minutes ago, GSalden said:

Here I still am using my server + client pc with MSFS and Prosim.

To have my home cockpit hardware working 100% I should build a P3D server and use my current MSFS pc’s as outside view clients using WidevieW.

The issue that I have is that WidevieW does not operate the external lights in the other sim. A P3D server with MSFS clients will not have correct working external lights…..

Hopefully that might change one day 🤗 

I used to have that problem with just P3D host + client, for aircraft whose lighting systems were non-standard. And other issues of not syncing systems that had to sync to be functional on the client like custom nose wheel steering (it had a directional taxi light affected by the nose wheel angle). So ultimately I wrote a program that runs alongside Wideview and syncs up changes in LVARs or FSUIPC offsets across multiple clients. It works reasonably well but still needs more work if it's going to be a complete product. And I haven't even tried to test it with an MSFS client yet, but in theory since FSUIPC7 works on MSFS, it *ought* to work.

2 hours ago, neilhewitt said:

I used to have that problem with just P3D host + client, for aircraft whose lighting systems were non-standard. And other issues of not syncing systems that had to sync to be functional on the client like custom nose wheel steering (it had a directional taxi light affected by the nose wheel angle). So ultimately I wrote a program that runs alongside Wideview and syncs up changes in LVARs or FSUIPC offsets across multiple clients. It works reasonably well but still needs more work if it's going to be a complete product. And I haven't even tried to test it with an MSFS client yet, but in theory since FSUIPC7 works on MSFS, it *ought* to work.

In the Prosim forums there are LUA scripts to combine a FSX/P3D server with FSX/P3D clients.

https://forum.prosim-ar.com/viewtopic.php?f=12&t=13682&hilit=WidevieW+lights

That is working great with my P3D - P3D setup.

However, using MSFS - MSFS It does not work even tough the variables should be the same.

It appears that WidevieW check the lights on the server for default aircraft only. Prosim has its own values.

Result : when I switch on external lights on the server the lights go on the client but they stay enabled, even when I disable them on the server ….

Reacion from Luciano Napolitano :

Here a reaction of Luciano from WidevieW:

“The problem with the lights, is because wideview server overwrites the *local* (client) light status continuously, as the status of lights are sent together with aircraft position (even if you deactivate the spot plane / animation option).

So the only way, would be to operate the lights only on server (by pressing L or using your cockpit hardware) but this normally works only with default Simconnect (MS) lights.

In particular, I synchronize the Simconnect variables below:
"LIGHT LANDING"
"LIGHT TAXI"

And, if spot plane/animation is activate, I synchronize also the variables below:
"LIGHT STROBE"
"LIGHT PANEL"
"LIGHT BEACON"
"LIGHT NAV"
"LIGHT LOGO"
"LIGHT WING"
"LIGHT RECOGNITION"
"LIGHT CABIN"

So...... if you could find a way to properly write on server "LIGHT LANDING" and "LIGHT TAXI" when the hardware panels are operated, you should be fine, as wideview will catch them and send to all the clients. 
I don't know if the drivers or the software you are using, lets to set Simconnect variables according (alternatively, you may also try with FSUIPC offsets, I think). “

regards,

Gerard

Edited February 17, 20224 yr by GSalden