Dave March

Thank you John

Thank you, I'll pass that on and get whatever infor I can for you

Hi John, I've just tried this myself with the latest FSUIPC and can confirm I have no problems at all. I have now posted on our support forum asking for further information (as you requested). Whether or not that will be forthcoming I don't know as they are using the previous version... we'll see

Thank you John... I'll run some tests myself tomorrow and if I can recreate it I'll send the logs. I'll also try to get more info from the users reporting the issue.

Hi John, I have some users who are experiencing hotkey issues again with the latest version of FSUIPC (7.4.9), where FSUIPC simply doesn't seem to be detecting them. They've all reverted back to the previous version (7.4.8) and the problem is now resolved resolved

All good now... sorry for the false alarm

Hold fire on this one... I suspect the issue is I'm using a very old version of FSUIPC (7.2.6). How the heck I installed that after the MSFS rebuild I don't know. Anyway, just about to check again with the latest version.

Morning John, Following a reinstall of MSFS (long story) I am now unable to send a control event via my program to the PMDG 737, which worked flawlessly before. So I bypassed my prog and setup an event in FSUIPC to change the MCP altitude. I notice an exception error in the log and wondered if you could shed some light on what might be the cause. 596453 EV_KEYDOWN received: 0x59 (Y) 596453 KEYDOWN: VK=89, Waiting=0, Repeat=N, Shifts=0 596453 FS Control Sent: Ctrl=84137, Param=20000 <84137> 596453 .. This key is programmed in FSUIPC7 'Keys' options 596485 Exception 1 "ERROR", Ref 4628, Index param 2 on TransmitClientEvent, object=0, id=84137 (????), data=20000

That would be excellent John... I hardly ever have to open the IPC7 window so an auto prompt would be great. Thank you for looking at this, much appreciated

Wow, brilliant. So that window should pop up when FSUIPC starts or the message is only displayed when you hit Alt+F ? Not by my FS pc right now so unable to try... it's certainly not the former for me so I will check what you suggest Thank s for the reply

Good morning John, I was wondering if you've ever considered implementing an update's prompt when a new version of FSUIPC7 is available? I was certainly caught out this week and was still running ver 7.3.24 (I know, I know). I had some users reporting a problem with my prog no longer being able to pause the sim. Obviously it wasn't something I could recreate and then checked for a later version and also spotted the change list item 'update to pause indication offset 0x0264 and pause control offset 0x0262'. So all is now well and fixed at my end. Just thought I'd ask the question.

Ah ha, thank you so much... now you mention it I do remember seeing that at some point. Much appreciated

Okay Pete, thank you very much for taking the time to look into this. Dave

Here you go... <ICAO id="LECK"> <ICAOName></ICAOName> <Country></Country> <City></City> <File>\\?\F:\FS2020\Official\OneStore\fs-base-genericairports\scenery\0502\APX46170.bgl</File> <SceneryName>fs-base-genericairports scenery 0502</SceneryName> <Longitude>-3.934329</Longitude> <Latitude>39.693424</Latitude> <Altitude>2367.43</Altitude> <MagVar>0.000</MagVar> </ICAO> <ICAO id="LEMQ"> <ICAOName></ICAOName> <Country></Country> <City></City> <File>\\?\F:\FS2020\Official\OneStore\fs-base-genericairports\scenery\0502\APX46170.bgl</File> <SceneryName>fs-base-genericairports scenery 0502</SceneryName> <Longitude>-3.874286</Longitude> <Latitude>39.898067</Latitude> <Altitude>1602.32</Altitude> <MagVar>0.000</MagVar> </ICAO>

Hi Pete, Yes they are default airports in MSFS Please see attached Runways_Extract.zip