jpreou

I have had clarification from Stephen at Opus that they do indeed 'read' simconnect. With the joystick disabled, no simconnect event occurs and therefore does not get sent/see by Opus. I will see whether I can assign a keystroke, then capture the joystick button with FSUIPC and send the keystroke instead. If it works, I'll let you know. Cheers

Thanks Pete, perhaps I'll check in with Opus. In Opus, you open the main window, then click the "Shortcuts" button and then you can assign a joystick button to some common functions. I'm not sure how Opus reads the button press; whether it 'intercepts' P3D or reads directly. I'll ask them, but I suspect it intercepts because if I disable controllers in P3D the buttons don't work, and if I re-enable then they do, so some how they are related. I wondered about a mouse macro since the update weather is available from an add-on menu directly in P3D, but on re-reading that section last night I understood it related to gauges and not general mouse ops. Never mind; though I have found something else I can use a mouse macro for, so that was handy! If I find an answer from Opus, I'll post here. Cheers.

Hi there, have looked through the manual and not sure how to achieve this. Maybe a mouse script/macro? Previously I had two buttons on my Logitech joystick mapped in Opus to update dynamic weather and change Opus camera. I've had a few issues with P3Dv2 and controllers, so I'm now using FSUIPC exclusively and have 'disabled' controllers in P3Dv2. I'm not sure how to re-map those functions for Opus since I don't know how to send commands to Opus, or whether Opus 'intercepts' commands to P3D. The update weather commend, at least, is available from drop-down menus ... I don't think the change camera view is. Anyone out there know how to proceed with this? Cheers -- Jeff

Thanks Pete. Another user suggested this also in another post. I Google'd and found you original post confirming, so went ahead and changed it. All good. Apologies for not coming back to update this post. Cheers.

Hi Thomas, thanks for that: I google'd it and found PeteD's original post. I'll see if that does it for me. Cheers

I'm making slow progress; found that I need to actually set SPAD to send a virtual button rather than offset for the master battery switch. Not quite what I am after as the plane in use doesn't always match the switch position, but I'm a little closer. At the moment I'm using the Toggle Master Battery type in FSUIPC. I tried the offsite type mentioned in another post, but that didn't work. In a second post I've been advised this is a known P3Dv2 bug that LM will likely fix, so perhaps I may need to just wait a little. Sorry about that second post: didn't know they needed moderator approval before appearing and thought this post had gone astray! Cheers

Ahh, cool. I've seen mention of a v2.05 soon, followed by a v2.1 Hope it isn't too far away. Hope I won't need to re-install and re-configure stuff. Once I get all the controls sorted I'll think about add-ons; until then, it's all vanilla (and boring too!) Thanks for the heads up.

P3Dv2, SPAD drivers for Saitek and latest FSUIPC4 registered. Seems most switches on the multi-panel work ok except the battery (default Carenado Bonanza). Worked out to config SAPD to send virtual button to FSUIPC for the battery switch and selected button 0 (off) and 1 (on). Selecting Toggle Master Battery works, but can sometimes be reversed depending on the position of the switch. Tried to do same by using offset (x1302, from memory; might have been x1304) found in another post, but this didn't work. New to P3D and SPAD *and* FSUIPC. Would prefer the switch in the aircraft to always match what the Saitek is configured to. Cheers

Just installed P3Dv2 Installed SPAD 0.51 (no Saitek software or drivers) Installed latest FSUIPC Still working through testing everything. Most functions of the multi-panel seem to work except the battery switch (default Carenado Bonanza). In looking to resolve this, notice FSUIPC does not detect switches on the switch panel. I think this may also affect the multi panel as the throttle auto-arm switch is not detected (though the flap lever works). SPAD recognises it is connected to FSUIPC, the aircraft detected and P3D. New to all these programs and would like assistance to determine why FSUIPC / SPAD don't appear to be jiving. Cheers