I'd just installed the previous version and have been working with that. I'll pause and install the newest version.

FIXED!

When I re-installed the gauges just to be certain I had the latest version, I forgot to re-edit the RealityXP.GNS.ini file...

Everything except the V and C knobs is working properly now. I'll tackle them in the morning and hopefully this will allow me to compile a new installer for the team to run through for a final sanity check.

Edited March 26, 20188 yr by n4gix
Edited to revise information content.

It works the same with 430 and 530, so long as you enable "Use Simulator GPS Commands" for each. Can you cross check this is the case?

I'm wondering but wouldn't it be the same events you'd use in modeldef.xml should you setup any default GPS with 3D Bezel, since these are the standard SDK GPS events?!?

The only difference is that you can now use the parameter/argument as a modifier for GPS#1/#2, and for Press/Release actions.

The advantage is that customers interacting with the 3D bezel won't loose any event, regardless of the input speed, especially true when turning the knobs with the mouse wheel for example.

In fact I use the same "default" for my very own XML GNS530/430 units and they work quite well. They are nowhere near as 'nice' as the Trainer based ones of course.

For my 2nd 530/430 units however I used the G1000_MFD and G1000_PFD events. ;)

And yes, I've triple-checked that the "Use Simulator GPS Commands" are set for all units.

I am up to date version wise. The desktop shortcut to the manual is a nice touch.

16 hours ago, n4gix said:

Everything except the V and C knobs is working properly now.

Is the GPS_BUTTON1 solved now?

 

Turning the C and V knobs requires:

23 hours ago, RXP said:

For these last 2, Command Modifiers Exceptions p15 explains further how to control them:

The following commands support "press-release" events only:
 KEY_GPS_POWER_BUTTON, KEY_GPS_ACTIVATE_BUTTON
To command knob rotation, use the 'press and hold’ modifier (value 2) as 'TURN LEFT’ (CCW) and the 'release’ modifier (value 4) as 'TURN RIGHT’ (CW): 

3 hours ago, RXP said:

Is the GPS_BUTTON1 solved now?

Yes it is working just fine. I do note however that the CLR button on the 430_2 unit will not "declutter" the screen at all in the VC, but works fine in the popup window.

<MouseFlags>LeftSingle+LeftRelease+DownRepeat</MouseFlags>
	<CallbackCode>
	(M:Event) 'LeftSingle' scmp 0 == if{ 10 (>K:GPS_CLEAR_BUTTON_DOWN) }
	(M:Event) 'LeftRelease' scmp 0 == if{ 12 (>K:GPS_CLEAR_BUTTON_UP) }
	</CallbackCode>

Great for GPS_BUTTON1

as for 'declutter' it is because you are using wrong events with wrong modifiers.

Either you send an event named 'down' and you don't need a modifier (except for GPS#1#2)

0 (>K:GPS_CLEAR_BUTTON_DOWN)
0 (>K:GPS_CLEAR_BUTTON_UP)

or

You just use GPS_CLEAR_BUTTON with the press and hold, or the release modifiers.

2 (>K:GPS_CLEAR_BUTTON)
4 (>K:GPS_CLEAR_BUTTON)

 

NB: all buttons support press and hold and release modifiers correctly, which makes it super easy to program:

"mouse left single"  -> press and hold (modifier = 2)
"mouse left release" -> release (modifier = 4)

 

 

This works for GNS430_2. Thanks for your kind assistance:

	<PartInfo>
	<Name>RXP_GPS2_CLEAR_BUTTON</Name>
	<MouseRect>
	<Cursor>Hand</Cursor>
	<TooltipText>CLEAR</TooltipText>
	<MouseFlags>LeftSingle+LeftRelease+DownRepeat</MouseFlags>
	<CallbackCode>
	(M:Event) 'LeftSingle' scmp 0 == if{ 10 (>K:GPS_CLEAR_BUTTON) }
	(M:Event) 'LeftRelease' scmp 0 == if{ 12 (>K:GPS_CLEAR_BUTTON) }
	</CallbackCode>
	</MouseRect>
	</PartInfo>
	

This sounds great.

In the end, would you mind posting the final modeldef.xml section for the GNS #1 and GNS #2 so that I can help you spot any remaining issue if any, and or provide any tip if any as well?

Absolutely! In fact I was planning to send you a complete RXP_GNS_modeldef.xml file. There's absolutely no reason why any other developer should have to reinvent the wheel...

That is very kind of you, thank you. It is not that hard either though, just standard FS SDK events! I'm glad it is all working fine for you, and this shall allow you to reuse this as-is for the default XML GPS as well!