Dave March
-
Posts
64 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Dave March
-
-
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 -
46 minutes ago, John Dowson said:
I guess I could automatically open the window if an update is available - I can look into adding this for the next release.
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 suggestThank 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> -
-
Just had a user complaining about a couple of missing airports, LECK and LEMQ
I checked the various output files produced by MakeRwys 5.13 for MSFS and discovered the following:-
LECK and LEMQ are NOT in Runways.csv, R5 or F5. But they are referenced in Runways.txt, Runways.xml, T5 and G5
I couldn't see anything obvious as to why this should be and would appreciate your thoughts/comments
Thank you
-
I'm using Live traffic, there are no settings other than on/off... at least I think that's correct... I can't use offline AI because it cause CTD's every time,
-
Hi John
Thanks for the update. The minimal testing I've done so far looks good. Unfortunately I never seem to experience a lot of live AI traffic at the best of times. I'll obviously keep running with it and let you know if there are any issues.
-
Excellent news 👍
-
Thank you John... we're getting closer at least.
-
Hi John,
Just been checking the AI Traffic tables and notice the 'From/To' data is now being populated correctly but the 'State' element is not. When I first raised this last November I know you said you reported it on Zendesk so Asobo may well think this has now been addressed fully. I'm more than happy to report this but thought you might wish to follow it up.
Dave
-
Thanks John... I didn't think there was much that could be done... at least I know the formats I'm likely to get so can work around it
-
With reference to an old post...
... and apologies if this has been readdressed since (but I couldn't find anything more) but today I thought I was having another senior moment. The offset 0x3C00 was once again only showing the path from \Simobjects and not the full path. So I restarted FS and tried again and this time 0x3C00 was now showing the full path. What the heck? Hitting Escape and returning to the main menu I changed aircraft and hit Fly Now, once at the departure airport I tried 0x3C00 again and whoa!!!! Only showing the path from \SimObjects.
I recall last year when we were discussing this I thought Asobo were changing things on a daily basis because this reared its ugly head quite a few times but now I can recreate it.
Don't know if this helps at all
Dave
-
Thanks for the link John
-
Just thought I'd post my findings as it may help someone some time if they experience the same issue.
1. Install FSUIPC7 7.0.4 (everything's great and FSUIPC7 starts with FS2020)
2. Install Honeycomb's Light Fix
3. FSUIPC7 no longer runs with FS2020
4. Lights on Honeycomb Bravo still not working!
5. After some head scratching I checked the EXE.XML file to find the Honeycomb installer doesn't append to the existing file but merely overwrites it. Not only that but the file it output was not complete and had some XML tags missing, hence the lights not working.
6. Re-install FSUIPC7 and make a safe copy of the EXE.XML file.
7. Add the Honeycomb entry to the XML file
8. FSUIPC7 starts with FS2020 and the lights on the Honeycomb Bravo work too!
I have reported this to Honeycomb support
Hotkey issue
in FSUIPC7 MSFS
Posted
Thank you John