
John Dowson
Members-
Posts
13,304 -
Joined
-
Last visited
-
Days Won
271
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by John Dowson
-
Could you send me or attach the update files (presumably FSUIPCuser64.lib, UIPCHello.c and UIPChello64.exe) and I will include them in the next release. Saves me some time having to look into this...thanks. John
-
I turned off on-line services (weather and AI traffic) and after doing this I can set the zulu hours and minutes in offsets 0x023B and 0x023C. Setting the hours seems to work (i.e. it goes from day to night in the sim) but the offset gets reset but the sim stays in night for some reason, And, as with offsets 0x0238 and 0x0239, setting the hours resets the minutes, and setting the minutes resets the hours. Very strange...! This works as expected in MSFS2020 (where setting zulu time also updates local time and vica versa), so its definitely an issue with MSFS2024. I will report to Asobo.
-
Also offsets 0x0238 and 0x0239 (which use the CLOCK_HOURS_SET and CLOCK_MINUTES_SET events) also have issues in MSFS2024 whereas they work ok in MSFS2020. I can set the hour, and it seems to work. However, when I then set the minutes, the hours go back to its original value, but the minutes are updated. In fact, setting one seems to reset the other (back to zulu values), and the zulu times are also not updated.
-
Really? That is interesting - how are you setting the local minutes? I have checked offsets 0x023B and 0x023C and writing to those in MSFS2024 doesn't change the hours/minutes, as reported here. I have also tried switching to use the CLOCK_HOURS_SET and CLOCK_MINUTES_SET events (they currently use ZULU_HOURS_SET and ZULU_MINUTES_SET) and they don't work either. Checked in MSFS2020 and they are still working there. There is not much I can do about this at the moment except report to Asobo. I will update the Offset Status document for FSUIPC7 to mark these as read-only for MSFS2024 for the time being. John
-
No - no tengo tiempo para esto, lo siento. Si quieres ayuda, debe hacer lo mismo que todos los demás: explicar su problema y publicar/adjuntar archivos. John
-
FSUIPC 7.5.0 beta : FS24 PMDG Boeing B737 v 3.0.108
John Dowson replied to androl2015's topic in FSUIPC7 MSFS
No, no point. This is nothing to do with FSUIPC if your devices are controlled by the Cpflight plugin. Has that been updated yet for MSFS2024? I only support FSUIPC, not CPFlight. John -
Are you using the latest beta of FSUIPC7 which has added support for MSFS2024? If not, please update to that version. See If using that version, please post any issues in that topic until I release this version officially, and make sure to at least include/attach your FSUIPC7.log file. John
-
FSUIPC 7.5.0 beta : FS24 PMDG Boeing B737 v 3.0.108
John Dowson replied to androl2015's topic in FSUIPC7 MSFS
Yes, as these devices are not assigned in FSUPC, in fact you have no assignments at all, it cannot be anything to do with FSUIPC. Your MCP and Efis are not even detected by FSUIPC. The log file you attached when FSUIPC7 was running and ends after 3-4 seconds and shows nothing. Please ALWAYS exit FSUIPC before attaching any files. John -
¿Puedes decirme cuál es el error? Además, adjunta tu archivo FSUIPC7.log. ¿Estás usando un add-on para el StreamDeck? Si es así, comprueba que se haya actualizado para MSFS2024. Consulta:
-
No need for a screenshot. This sounds like your device has gone to sleep (as the button press is not recognised) - check the USB hub properties in device manager. Otherwise, please show me those files with the logging activated.
-
Both log files look ok and show that FSUIPC7 was running and had not crashed. When this occurs, can you operate in the FSUIPC7 main window? i.e. does Alt+F open the main window, and can you then open the assignments windows and use those? If so, can you see the assignments you have bound to the switch? Is the switch/button recognised? The WASM log looks ok, and shows that that didn't crash. You do have a few reconnection attempts at start-up, although this is nothing to do with the issue you are having, To prevent these, can you please set/update to the following in your FSUIPC7.ini (in the [General] section): DetectToConnectDelayAuto=90 InitialStallTime=45 StartUpTuningDoneVersion=-1 For your issue, can you please activate logging for Buttons & Keys, Events, Extras and WAPI Debug level logging, and the next time this occurs first open FSUIPC7 and the assignments window and press the button (presumably not recognised?), then exit FSUIPC7 and send me/attach your FSUIPC7.log and FSUIPC7.ini files. Then restart FSUIPC7 and try again. Does it now work? Presume so (from what you said), but if not, please then exit MSFS and show me / attach your FSUIPC_WASM.log file. Also please check the power settings on your USB devices and hubs, and make sure Allow the computer to turn off this device to save power (under Power Management) is disabled. Windows has a habit of resetting this setting for some reason... - John
-
Yes, you will need to purchase a license for FSUIPC6 for P3Dv5 (and it is also valid for P3Dv4 and P3Db6). Your WideFS7 key is still valid and this can be used with FSUIPC6. John
-
If you have previously purchased a license for FSUIPC6, then the details of your purchase (including the license key) will be available from your SimMarket account. If you don't have a license, you can purchase one from SimMarket. John
-
The trial license has been updated, now valid until 01/01/2025, John
-
First, there is no point in monitoring such offsets, Monitoring logs the value of the read offset, whereas you write to the write offset (there are separate areas for read and writing), Well, no point in monitoring, and even if you did you should monitor as a FLT64. The parameter/value for all input events is a 64-bit floating point value (double), as it is for lvars, So make sure you write it as such, and not as an S32 (int). Please re-read the documentation.... John
-
No. Please see the FSUIPC7 Offset Status document on how to use the facility at offset 0x7C50: John
-
I am not sure why this would be - I will take a look sometime next week.
-
There are no id numbers associated to Input Events. Each one is identified internally (and by MSFS) by a hash number, but I don't make these available. But to send an Input Event via an offset, you should use offset 0x7C50/0x7C90 not 0x3110/0x3114, and use the input event name, preceded by 'I:'. John
-
FSUIPC Causing Sim Crash (FS2020) On Load-Up
John Dowson replied to CrossHyparu's topic in FSUIPC7 MSFS
Which would confirm that it is not related to FSUIPC, but more of a coincidence that it also happens when FSUIPC is loaded. I think this issue has been reported before, but I can't remember what the issue was caused by, sorry. -
FSUIPC 7.5.0 beta : FS24 PMDG Boeing B737 v 3.0.108
John Dowson replied to androl2015's topic in FSUIPC7 MSFS
Your log shows you didn't install the WASM for MSFS2024, which could be an issue, Anyway, 7.5.0c has been released now with a full installer, so please download and re-install from John -
FSUIPC 7.5.0 beta : FS24 PMDG Boeing B737 v 3.0.108
John Dowson replied to androl2015's topic in FSUIPC7 MSFS
So your MCP and EFIS don't work? In MSFS2020 or MSFS2024, or both? How are the devices assigned? In FSUIPC or elsewhere (e.g. cpflight plugin)? Does FSUIPC even recognise your devices? Was this working in MSFS2020 with 7.4.18? Please clarify what your issue is and why you think this is related to FSUIPC. And please also show me / attach your FSUIPC7.log file as this will at least give me some basic information. -
This normally happens when the DirectAxesToCalibs ini option is set to Yes. Remove that it set it to No. If you need that option set, then you can set it to All (see Advanced User guide for details). If that is not the issue, show me / attach your FSUIPC7.log and FSUIPC7.ini files and I will take a look. However, it may take me a few days to get back to you. John
-
FSUIPC 7.5.0 beta : FS24 PMDG Boeing B737 v 3.0.108
John Dowson replied to androl2015's topic in FSUIPC7 MSFS
Sorry, but I do not understand what your question is. 7.5.0-beta is now available with an installer from the following page: John -
FSUIPC Causing Sim Crash (FS2020) On Load-Up
John Dowson replied to CrossHyparu's topic in FSUIPC7 MSFS
That is very strange, and I don't see how FSUIPC can be doing this. When this happens, can you open FSUIPC7 (Alt + F) and does it work (i.e. can you operate the menus)? Can you exit FSUIPC7? If so, please do that and show me / attach your FSUIPC7.log file. Once exited, foes MSFS then display the ready-to-fly button? When you start MSFS and FSUIPC7 is auto-started (presuming you are using auto-start), can you then exit FSUIPC7 and let MSFS load to the main menu. Then select your aircraft and get to the ready-to-fly stage before starting FSUIPC7. Does it then work? Maybe also worth checking the MSFS console for any messages logged there. You need to turn on Developer mode (in the General options) to see the developer menu bar. This is the support forum for FSUIPC7 and I am the developer.... John -
FSUIPC 7.5.0 beta : FS24 PMDG Boeing B737 v 3.0.108
John Dowson replied to androl2015's topic in FSUIPC7 MSFS
What do you mean? You use PMDG aircraft in MSFS2024 as you would in MSFS2020....