AndyCYXU

Hi I wanted to assign a button on my yoke to control HUD display in PMDG.. so when i opened console adn i click in the area to drop/retract it i get something like that 3347813 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3347844 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3347875 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3347906 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3348813 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97901 (0x00017e6d) ROTOR_BRAKE 3348875 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97904 (0x00017e70) ROTOR_BRAKE 3352453 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3352485 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3352516 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3352547 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3352578 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3352906 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3353750 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97901 (0x00017e6d) ROTOR_BRAKE 3353844 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97904 (0x00017e70) ROTOR_BRAKE 3356938 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3356969 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3357000 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 97903 is just moving mouse on the screen but when I click to deploy or retract HUD it gives me the lines in bold.. ? tying to set up custom control doesn't really do much more like it gives me error anytime i press it 3303844 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3303875 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3303906 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3311063 Exception 1 "ERROR", Ref 5969, Index param 2 on TransmitClientEvent, object=0, id=97901 (????), data=1 3314610 Exception 1 "ERROR", Ref 5971, Index param 2 on TransmitClientEvent, object=0, id=97901 (????), data=1 ....... 3336828 Exception 1 "ERROR", Ref 5996, Index param 2 on TransmitClientEvent, object=0, id=97901 (????), data=2 3337094 Exception 1 "ERROR", Ref 5997, Index param 2 on TransmitClientEvent, object=0, id=97901 (????), data=2 3340172 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3340203 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3340235 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE 3340266 *** EVENT: Cntrl= 66587 (0x0001041b), Param= 97903 (0x00017e6f) ROTOR_BRAKE What can I do with that info? any help appreciated Thanks

Yes Fabio I did press the Record Button, I figured it out when i successfully once recorder the take off video wiht option "start Above 1000" set i will try later with another aircraft i was using A320 FBW... idk I understand it might not record flap positions and other detail info but regular recording works fine with it IDK maybe FCR doesnt know when I descent and cross the 1000 ft

yes i know and it doesnt do anything.. ONCE ONCE ONLY it recorder take off i set it to record once above 1000 and it worked as soon as i crossed 1000 it started to record, but i tried several time to record once descending i set it up to 1000 as well landed and nothing no recording was made

well i do have an issue any idea why ? even key assignment doesnt work i assigned R to record it is not assigned to anything else and it doesn't work I replied to your message heard nothing since

any clue how?

There are settings in options that do not seem to work for example setting, Automatically Record Below XXXX i enter there 1000 and nothing happened, it did not start recording. I was testing the feature many times and it seems the way to do it is set the option, then start recording (press red button) then once it detects I am above/below XXXX altitude it will actually start recording. Only once using record ABOVE setting it worked as advertised. Is this project dead or do you intend on providing some updates and support? Thanks

None of the key assignments work from options to start recording using button on your joystick or key press.. ?

How can I use it in VR ? 1. VR support FlightControlReplay can be used also in all VR Environments via key mapping AND for Windows Mixed Reality Headset. You can also run FlightControlReplay directly into the cockpit and you can see FCR User Interface for full use! I am understand when you refer to "...via key mapping..." I am suppose to assign some keys for Record/Play etc... in the options menu.. so keep program open on desktop then in VR i press joystick button or key on keyboard and that is suppose to start recording? 2. VR support FlightControlReplay can be used also in all VR Environments via key mapping AND for Windows Mixed Reality Headset. You can also run FlightControlReplay directly into the cockpit and you can see FCR User Interface for full use! Secondly how do I bring this FCR window into VR? I am using ReverbG2 with WMR but I have no clue how to bring it inside the cockpit, I know how to bring entire desktop inside the cockpit but to my understanding it seems like I should be able to open just the FCR and have it there in my VR cockpit as a stand alone window... how do I do that ? Thanks

Ok great! Thank you Pete it's the first time I ever really used the console yet I have been flying with fsuip since FSX lol, Anyhow great to know that this is common occurrence seen previously and not necessarily affecting stability of somewhat unstable MSFS .... Pun intended, 😄

Hi, I recently run a console while the sim is running and I have come over very strange issue with some of the aircraft here is my recent flight console log. What I am referring to is this: 41109 7764 *** EVENT: Cntrl= 66280 (0x000102e8), Param= 0 (0x00000000) RADIO_COMMNAV1_TEST_TOGGLE 41109 7764 *** EVENT: Cntrl= 66281 (0x000102e9), Param= 0 (0x00000000) RADIO_COMMNAV2_TEST_TOGGLE ... the above event is spamming consistently through the entire flight in this case I am using Cessna 172 SP NOTE: not all aircraft do that, some do other commands which they spam the console with all the time.. the other was Beechcraft 350i this one was spamming console with these some Starter_fuel_set and Starter_Fuel_set_2 (sorry i deleted this aircraft and the logs, so i don't recall exactly the event, I think it might have started to cause my MSFS to CTD, i tried reinstalling the aircraft same thing, I have (had) no mods for this King 350. So i tried unhooking all my devices (yokes, throttle even keyboards, yup) also check to see if there are any assignments to these events in FSUIP and/or MSFS, No there are none. so it seems MSFS is sending these by itself... why beats me...? I do not know if this is FSUIPC issue or MSFS issue, obviously without FSUIP i have no idea if these events being spammed into the console, hence there will be no console LOL So yeah I was wondering if anyone has any suggestions maybe you would be willing to check on Beechcraft King 350i does it spam these command in your console? Again NOT ALL AIRCRAFT do that nonsense... most behave normally there is nothing going on in the console unless i actually do something (press button, switch knob etc). I really think this could be causing sim to crash, maybe worth to report to Microsoft.. NOTE: I had to delete a lot of from this file to make it 20kb... there are as you can see about 3 million events.. out of these 3 million probably 2.8 million was pure spam from the 41109 7764 *** EVENT: Cntrl= 66280 (0x000102e8), Param= 0 (0x00000000) RADIO_COMMNAV1_TEST_TOGGLE 41109 7764 *** EVENT: Cntrl= 66281 (0x000102e9), Param= 0 (0x00000000) RADIO_COMMNAV2_TEST_TOGGLE Other you may see there they are legit for example press key UP or DOWN that is me moving around the cockpit and if you keep key pressed it will generate these events so these are fine. It seem like for the problematic ones a key is stuck BUT !!! I have no key assigned to these events (i don't even know what they are really ??COMMNAV2_TEST_TOGGLE???) again i checked all my key assignments in MSFS and FSUIP nothing like that, disconnected all my yokes, throttles and keyboards to ensure there is nothing that could be sending this event from my hardware.. adn nothing hlped this is still showing like a key that is stuck of sort or something wrong with MSFS. Ok Thanks for any help and suggestions as to why this might happen would be appreciated to put this mystery to bed. Andy FSUIPC7e.log