den4

Wideview is a means of putting different (usually virtual cockpit) views on multiple PCs and you would need to have everything duplicated on each PC for it to work properly. I used it years ago when I ran FSX but it was such a PITA to keep everything on all 4 PCs identical that I eventually gave up using it. I have gone down the line of having 2 graphics card, 2 Triple Head 2 Go units, one attached each graphics card, with 3 screens attached to each TH2G. I then run P3D and XP11 in windowed mode and stretch it out across all the 6 monitors to give panoramic views. Frame rates are not killed by doing this like using multiple view widows of P3D would. I don't know anything about PMDG, can you run the instruments on a second PC? Just noticed this is an old thread, did you solve the problem?

Many thanks Pete, renaming them in the ini file did the trick. I saw the msg about registry fixed but didn't twig as to what it meant, thinking it had cured any problem. FYI I do have joy letters assigned. This is the first time I've had any problem like this and hadn't seen the FAQ thread you mentioned. Have a nice Christmas break.

I have been using a generic usb joystiuck for some time. It supplies me with a dozen switch connections that I can use. Recently I've added a scond one to my simpit, but FSUIPC does not see it when i try to allocate controls to it. They are both seen by fsuipc as shown by the entries in the log file, both have different GUIDs, but the second one will not show up in the Buttons page when I try to use it. Pressing any button on it with the button page open results in the page remaining blank in the buttom reference window. It is visible in the Windows game controller app and the red lights light up whin I operate the switches. I can program them in X-Plane 1 with no problem. However I cannot allocate them in FSUIPC. Using P3D v4.3 and FSUIPC 5.15. Any suggestions? . FSUIPC5.log

Which version of FSUIPC5 are you using? If it is not the latest then update it using the link in the Download Links subforum.

Thanks both for your help, now working correctly.

Thanks Pete It isn't a toggle, just a button. I'd seen that in the documentation. But I'd totally misunderstood the point about the 16 bit though, I thought that was there because it was a 16 bit offset.. Still got a lot to learn! I'll have another go tomorrow.

Mario, thank you for that it has removed the error message now. Unfortunately it still doesn't do what I want it to do. It sets the button colour to red regardless of the value in the offset. Seems my logic is wrong somewhere as well! Den

Can someone help please? I've been trying all afternoon to get the following simple script to work : - function Magsoff(off,val) if val = 0 then ipc.setbtncol(7, 255, 0, 0)--toggle to red else ipc.setbtncol(7, 224, 224, 224)--toggle to grey end end event.offsetmask(0x0892, 16, "UW", "Magsoff") Each time I try I get an error in the log There is a "then" near to the "=" sign, so what am I doing wrong? I haven't got much hair left to tear out these days!

Are they seen in the Windows Devices application? If not there may be a fault in the unit.