NAX

This worked PERFECT. Bare in mind the Parameter needed to be 89+512, not 82+512. Thanks for exellent and prompte implementation!

I'll let you think about it. Sorry for not getting the part with Key press. I actually tried that first without result, then I went to Buttons and only assigned Y to get the line in the .ini, then adding the <SHIFT> value after K89. I'll look for your release and read carefully about the added functionality. Have a nice weekend

adding the line: 1=PH,28,K89,512,8 When trying the button in FSUIPC it turnes up as rctrl+y. Cannot get it to work with the 512 command. It acts like the 128 shift-command

I only get to assign it as Y, but I might type the wrong syntax. Adding +512 after 89 will not stick when ini is saved, so i only get 89 working. Reading advanced manuals now to try to sort it out. EDIT: it's a comma, not a plus... okidoki

Thanks John. Will test within a few hours and report

TaDaaa!!! Excellent news John! Will sure make handeling classics apps together with msfs in VR a lot easier. Thanks and have a nice day

To be able to change between vPilot and sim, I need to press Win+Y. Tried assigning it as a buttom press, but FSUIPS do not seem to detect the Win button at all. I cannot find a way to change the WMR shortcut to something else, so I'm kinda stuck and out of ideas. Any help appriciated

Have to correct myself. Basically nose wheel steering in the new 737 pmdg does not react to tiller axis assigned and calibrated in fsuipc. after deleting axis assigned as tiller in fsuipc and then asigning it in msfs, it works.

Hi all All software updated. Assigning tiller and setting it up in fsuipc does not give me functioning tiller ingame. For rudder and yoke axis is ok for all planes when assigned only in fsuipc. tiller, or nose wheel steering, only work when assigning in ingame settings. Two problem follows after doing this as my rudder are home built and axis not perfectly set around value 0. Problem 1 is that rudder hang in more or less full right rudder whenever using rudder after using tiller. Kicking the rudder once more set it zero again if tiller is also 0. problem 2 is that when i taxi and using tiller (keeping my foot away from rudder) i have to keep moving the axis, jiggering the tiller, to keep it from just sink back to 0. It seems that fsuipc dont write to the correct value in the sim? If i coul keep it only assigned in fsuipc like rudder and yoke, that would be the best for me. hope i described the problem understandable

We'll get there. This is just a temp setback and as FSUIPC seems to work like a charm, we know we soon will have all our gear up and running within.... weeks? Months? hopefully not years

Wilco Thanks Thomas

Hi there Both Sioc nd Prosim MCP connect to the model via fsuipc as i understand, at least these modules freeze when WideClient crash. Also CDUs fall out due to changes in COM or/and USB states. I thought about it a great deal while searching for a solution yesterday, and I think I could be on to something regarding my two networks on both machines. I have a LAN for the fs-stuff with static IPs 10.0.0.x, where 10.0.0.1 is the server/P3D PC. I run Wide client on two other comuters, but the problem is only on my client running all the Prosim modules, 10.0.0.3. Both these computers also have a wlan for connecting to internet and this scope is 192.168.1.x. The client pc is set up to run all needed modules automatically, and I usually turn on both computers then enter the cockpit. What happens then, is that WiceClient is up and running long before I have started a flight. It will listen for the server response trying to connect 10.0.0.1 many times then connect to the 192.168.1.20 instead. WideClient had no serverIP in the config, only trying to connect to the server called P3D1, and nevermind wich IP. I edited the .ini for WC and entered the Server IP line on the top with 10.0.0.1, and had a flight afterwards without error. It became quite late, so I need to do another test today, starting both computers and let them go through a standard automatic startup to see if the problem is surely gone. So far I suspect the two network instances and a non ip config was to blame. Fingers crossed.

sry... i just found the manual... Will look at logs and try to sort it out before asking you again, and hopefully report what caused it :) IF you immediately do have a clue of what causing my crashes, let me know...

Hi there I run a full cockpit with two computers in network, P3D on PC1 and Prosim737 stuff on PC2 (in general). Every time I run my setup, WideClient will crash sooner or later during a flight. I can then restart WC and most times it will then be stable for the rest of the evening, although is may also crash several times more. When restarting WC I usually get all components except CDUs up and running again. I have sort of learned to live with it, but it is quite irritating. Is there a way for my to find the cause of this and try to eliminate it? Can I run WideClient in debug mode or anything?