Is it possible to configure it as Right CDU ?

5 hours ago, raam123 said:

Is it possible to configure it as Right CDU ?

"configure" - no.

You would have to make a copy of the index.html and replace all the variables and events in it with those for the right hand CDU.

This is not difficult to do, but still a fair bit of work. I was hoping that one of the more talented web developers on flightsim.to would provide a more professional CDU, like they did for the 737...

A new version of the Web FMC has been uploaded, it includes all three CDUs now.

Edited July 14, 20241 yr by Lorby_SI

On 7/14/2024 at 8:21 AM, Lorby_SI said:

"configure" - no.

You would have to make a copy of the index.html and replace all the variables and events in it with those for the right hand CDU.

This is not difficult to do, but still a fair bit of work. I was hoping that one of the more talented web developers on flightsim.to would provide a more professional CDU, like they did for the 737...

A new version of the Web FMC has been uploaded, it includes all three CDUs now.

Thank you 🙂

@Lorby_SI is there any way to map these events to a physical controller? screenshot - https://ctrlv.link/wRXU

I am trying to map the CDU to a button box.
Thanks!

 

Edited July 21, 20241 yr by Sammyyouarewreckingthecar

8 hours ago, Sammyyouarewreckingthecar said:

@Lorby_SI is there any way to map these events to a physical controller? screenshot - https://ctrlv.link/wRXU

I am trying to map the CDU to a button box.
Thanks!

 

Sorry, but I'm not sure that I understand the question?

They are just normal K: events, you can map them the same way as you assign everything else - as a "Button" in AAO. You may have to use the PDMG Mouse codes for the assigned value though, with the 777 many of them don't seem to work with the default "1".
For example, for the LSK L1 on the left CDU you would assign
Key Down: #69960 value: 5368709121
Key Up: #69960 value: 131072
The PMDG mouse codes are in the AAO manual, chapter about PMDG planes.

Or use the ROTOR_BRAKE codes like I did with the WebFMC. They seem to work better für the MSFS models from PMDG.
Download the WebFMC, pull out the folder for the 777 and check the "left.html" file with a text editor. Right at the beginning there are all the button definitions.
For example, just starting at the top, for the LSK L1 on the left CDU you would assign
Key Down: ROTOR_BRAKE value: 32801
Key Up: ROTOR_BRAKE value: 32804

etc.

Edited July 21, 20241 yr by Lorby_SI

@Lorby_SI thanks ,not sure what I was doing wrong but I have managed to map all the CDU keys to hardware now. 

I have a question - could you look at the FMC/COMM key, it is only registering a key press and not release. Its the only one behaving that way... any ideas why?

Thanks for yours help!

4 hours ago, Sammyyouarewreckingthecar said:

I have a question - could you look at the FMC/COMM key, it is only registering a key press and not release. Its the only one behaving that way... any ideas why

What do you mean by "doesn't register? Register how and where? Can you provide screenshots? Are you using the K event or ROTOR_ BRAKE code?

In any case, there is nothing to look at for me. There is no special code for the PMDG user events in the app, AAO simply takes your value and your event ID, and sends them to the sim. If one of them doesn't behave like you think it should, you would have to ask PMDG about it. 

@Lorby_SI I clearly dont know what I am talking about. Sorry for the silly questions.

I have mapped the FMC/COMM to a physical button https://ctrlv.link/4ZIb

When I use this mapping to click the FMC/COMM - the button remains pushed (doesnt release). https://ctrlv.link/PrZq you can see FMC/COMM pushed in. I have similar mapping for all the CDU buttons (INIT, RTE, DEP/ARR, etc...) they all work as expected, "click and release".

"Are you using the K event or ROTOR_ BRAKE code?" - I am not sure
"If one of them doesn't behave like you think it should, you would have to ask PMDG about it. " - understood, will try their forums. 

 

4 hours ago, Sammyyouarewreckingthecar said:

I have mapped the FMC/COMM to a physical button https://ctrlv.link/4ZIb

You have to supply both down and up events. Just sending "1" as a value does not always work with the MSFS 777, as you found out. 0 and 1 often mean "off" and "on" with the custom events.

 This is as per PMDGs SDK documentation, Packages\Community\pmdg-aircraft-77w\Documentation\SDK\PMDG_777_MSFS_SDK.pdf page 13 "numerical parameter":

Quote

All values below 8192 are treated as a numeric position to which the item being controlled should be placed.

 

There are two options how to assign these buttons:

1. ROTOR_BRAKE

PMDG themselves do not use their SDK events in the behavior code, they call the ROTOR_BRAKE event with different numerical codes. For the left FMC/COMM that would be

347101 for key down

347104 for key up.

Meaning, you select the event "ROTOR_BRAKE" in the boxes for both key down and key up and then enter the numbers above in the little numerical boxes to the right. Doubleclick the box then you can enter the number. Or use the mouse wheel (left half of the box - big changes, right half - small changes)

The ROTOR_BRAKE codes for the FMC are all in the html-file that comes with the WebFMC (left.html). Be mindful that the javascript method always sends both down and up events (xxxx1 then xxxx4)

2. Custom Event

With the custom events you should be using the PMDG Mouse event values, those are listed in the AAO manual, in the chapter that describes how to use PMDG aircraft in AAO.

In this case, with #73103 the values are

536870912 for key down (left mouse button down)

131072 for key up (left mouse button up)

(Edit: maybe it would also work using 1 for down and 0 for the up event. The FMC/COMM seems to be a later addition to already existing code, as it works differently to the others)

Edited July 28, 20241 yr by Lorby_SI

Thanks alot @Lorby_SI
 

Rotor_brake is a new one for me, it sorted it out. I had a bit of a play around and realized i could get the same result with this: https://ctrlv.link/fe3O

Thanks alot for your help!