• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

key event codes + ace.exe tool in FSX XML gauges

Yeah, I do most of the work in a text editor as well, but I think ACE does have its uses, especially for visualizing the positions of elements and click-zones.

I finally did a complete re-install — this time also on a non-protected location (I'm running Win7-64bit), and now everything works fine.
So either the installer, or me myself, did something wrong during the first install.
I don't get any false error messages anymore, and I even now see a brand new section that was never there before (the "Control Palette" group).
I haven't figured out yet what it actually does, but I'm a lot happier with my Ace now already... ;)
 
I use Visual Studio's XML Editor and have FSX open on my second monitor. After making an edit, switch focus to FSX, hit Ctrl-Shift-R and reload the aircraft...

...instant update that allows me to use FSX for a "visual design/validation tool." :D
 
I frequently find I run out of space even on two monitors. Gmax and FSX on one, reference material and XML on another. And then I have to find room for GIMP, ACES, Firefox...

Sometimes I wish I had four monitors, never mind three!:)
 
When I really need more space, I use my 42" HDTV/HDMI monitor. I can have six windows open at the same time on it, and a seventh on the 22" left side monitor.
 
B21 said:
I have a couple of lines in my gauge intended to trigger key events, i.e.

1 (>K:KOHLSMAN_DEC)

This gives an error in the ace.exe tool:

Error: Invalid key event specified in XML: "KOHLSMAN_DEC"

The same error occurs for all other values of key event code I've tried also, so I don't think it's peculiar to KOHLSMAN_DEC.

My source XML actually contains "1 (>K:KOHLSMAN_DEC)" and I don't think the error has anything to do with the greater-than sign.

Have I done something obviously wrong?

thanks,
B21
Click to expand...

Hi, yes those will throw an error but I'm not sure why. Errors may crop up since you can code other simulator gauges with ACE. Most of the time those key event id's go along with a mouse click. If you look at the MouseClick element you will see KeyEvent as one of the items you can select. You need to only specify KOHLSMAN_DEC in the element. An event with the > sign puts an amount for a key set variable like KEY_THROTTLE_SET. So tune a value with one item and set with a key style of item.


<MouseArea id="IncreaseKholsman">
<FloatPosition>135.000,52.000</FloatPosition>
<Size>15,15</Size>
<CursorType>Hand</CursorType>
<MouseClick id="MouseClick">
<KeyEvent>KOHLSMAN_INC</KeyEvent> <----- KeyEvent
<ClickType>LeftSingle</ClickType>
<ClickRepeat>True</ClickRepeat>
</MouseClick>
</MouseArea>
 
You must log in or register to reply here.
Back
Top