John Dowson
-
Posts
13,697 -
Joined
-
Last visited
-
Days Won
288
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
8 hours ago, ark1320 said:
If a TOD time is entered successfully, a TOD event.timer() is started which, as I understand it, will automatically cancel the data entry event timer.
Yes, thats the case. Only one timer per lua plug-in.
8 hours ago, ark1320 said:I wanted to ask if I am correct that rerunning a running script automatically cancels all the events in the first instance of the script?
Yes, as re-running a script kills the thread in which the original was running.
John
-
10 hours ago, asessa said:
Ok, so i have to use to light on the decel lights , right?
Well, I added them for you to try this - the AUTOBRAKES ACTIVE flag at offset 0x0C46 sounds like what you are after, but I haven't checked if this is populated in the A320.
Both offsets are read-only. -
5 minutes ago, asessa said:
Wich values can i expted to have this offsets?
They are bools, so 1 or 0.
-
On 12/18/2020 at 11:40 AM, John Dowson said:
There is an AUTOBRAKES ACTIVE simulator variable, but it looks like this isn't exposed via SimConnect at the moment. I'll check it to see if its available (in case its just missing from the SimConnect documentation) and if so I will add it and let you know. In the mean-time, you could see if the standard brake indicator offset 0x32F9 show anything for Autobrakes..
There is also a simvar LIGHT BRAKE ON which is available via SimConnect, which is True if the light brake is on, but this may be for toe brakes. I'll add it anyway so you can check.It may take me a few days to get around to this though.
@asessa Sorry for the delay. I have now added
0x0C46 1Byte AUTOBRAKES ACTIVE
0x0C47 1Byte LIGHT BRAKE ON
in the attached version, v7.04e. They are both recognised (i.e. do not give simconnect errors), but I haven't verified the values - I'll leave that to you!John
-
1
-
-
11 minutes ago, MarkStallen said:
I will check to see if it's still working with the vanilla A320.
Yes, please do. I have had various reports of offsets/controls not working when using the FBW mod.
-
Maybe @Thomas Richter can explain why this value isn't in the -1 to +1 range, or what the actual complete range is so, that I can calibrate to an integer range of -16383 to +16383?
-
Btw, I have noticed that offset 0x0BF8 is already reserved for 'Unlimited visibility value', so in the next release I have moved this value to offset 0x0C10. You can still test with the dll posted above in the original offset position.
John
-
1 hour ago, MarkStallen said:
The offsets for the APP en LOC function on the A320 don't work anymore ?
DEC 65806 parameter 0
DEC 65723 parameter 0
Sorry, but what is APP en LOC? What is DEC?
Control 65806 is AP_APR_HOLD_ON
Control 65723 is AP_LOC_HOLDAnd what do you mean by anymore? And what have you changed since whatever it was was working?
In summary, please provide more information as to what your problem is, and attach any files that I may need to investigate, which initially would be
- your FSUIPC7.ini
- your FSUIPC.log file, generated when experiencing your issueJohn
-
1 hour ago, MarkStallen said:
Auto Brake Hi is working with this, Lo and Med not?
If the control is being sent (check by activating Event logging) and it isn't having the desired affect for a particular aircraft (or all aircraft for which it applies), then you need to report to Asobo via zendesk. I only add the controls provided by the SDK, if they are don't work then thats usually an FS issue.
John
-
1 hour ago, ark1320 said:
My understanding is you use event.timer(500, "mytimer") to call this function every 500 ms (milliseconds) to check if data has been entered within the allowed time period of 3600000 ms or 60 minutes, and if not all events are cancelled. My question is, if in a request for data application we were to set the allowed time for data entry to a much smaller time, say 5 minutes (300000 ms) could we just use a 5 minute interval, e.g. event.timer(300000, "mytimer')? What I'm asking is why check repeatedly if data has been entered instead of just checking once at the end of the total allowed data entry time?
Sure. It is what it is as I based the script on an existing script and I didn't modify the timer interval. You can just set it to your time-out value, not decrease the timer and cancel both timers and exit the script when the timer function is called, as indicated by Pete's comment:
40 minutes ago, Pete Dowson said:So check at the sort of period you would allow for the reply to be entered, whether long or short.
41 minutes ago, Pete Dowson said:And terminate as soon as done
This is already implemented on the event.key() function for the return/enter key.
John
-
1
-
-
55 minutes ago, karlo922 said:
Regarding the 32 button limit - will this be solved when you go for xInput ?(I saw this on you "ToDo" List for future updates to cover Xbox One controllers)
No, as that will be for xbox one and 360 controllers ONLY, as they do not support DirectInput (very well...).
DirectInput can support up to 128 buttons anyway, and I will also look into supporting more buttons (at least to 64, hopefully to 128) via UI assignments at some point for DirectInput devices. Unfortunately, I am spending at least 80% of my time at the moment covering support, which leaves me hardly any time for fixing bugs, let alone adding/improving current functionality. Hopefully this will change at some point.....John
-
1
-
-
1 hour ago, karlo922 said:
unfortunately I cannot use FSUPIC alone as I have those 128 buttons.
But this is easily handled by adding an additional lua. For example, see the lua scrips in the last comment in this post (derived from HidDemo.lua), that provide access to the buttons in the new Honeycomb devices that are > 32:
However, if you are happy with your solution, then go ahead with that. I just want to emphasize that your issue was not caused by FSUIPC.
There are also various solutions around the 32 button limit, from lua files to using the vJoyOffsets utility, or this utility (written for StreamDeck, to provide virtual button functionality for that device, but I'm sure easily adapted):I have not heard of any "slow response" reports when using any of these.
John
-
On 12/29/2020 at 5:06 PM, karlo922 said:
Even when setting poll rate = 100.
The default is 10 (i.e. every 10ms). So by setting this to 100, you are actually slowing things down.
It was probably the ButtonRepeat rate you wanted to adjust.17 minutes ago, karlo922 said:I do not know why it's not correctly working with LINDA/FSUIPC.
Me neither. If you took Linda out of the equation, then we could look into it, but if using Linda then you really need their support.
But as long as your happy with this 'different tool' (a name would be helpful for other users!), I will consider this closed.John
-
3 minutes ago, GBOULANGER said:
Thanks for this information. I will read with attention and give you a feed back
My installation was done as "Admin" and FSX.exe run as Admin also.
1 to 5 and 10 & 11 checked
i'm going to read the vol7 and check 12
i will be back to you after
There's not much I can do with this. I think you would be better off supplying any feedback/questions to the Aerosoft forums.
As I said, I don't have that aircraft or quadrant, or even FSX/FSX-SE or FSUIPC4! But still, let me know how you get on and I can still take a look at your logs/ini once you have revised your set-up from the Aerosoft advice.John
-
On 12/23/2020 at 11:52 AM, John Dowson said:
I think it should really continue and cancel all registered events for that function.
I'll update this at some point, most probably for the next release (FSUIPC6 & 7 only though).This has now been implemented in FSUIPC6/7 and will be included in the next release of those products.
John
-
1
-
-
1 minute ago, Jlandry5555 said:
OK, I guess I cannot request a refund for the 25 Euros I spent on FSUIPC7 at SimFlight GmbH?
No, I'm sorry. I cannot authorise a refund in such situations as you nowhave a key for FSUIPC7. The requirements for FSUIPC7 are clearly stated as for MSFS only. And we also provide the free version for you to test before purchase.
John
-
Found this on the Aerosoft forums (https://forum.aerosoft.com/index.php?/topic/112537-throttle-problems/) that may help (especially item 6):
QuoteGuys,
I'm very sorry not to have responded... I had some things come up that took me away from my computer.
The primary reason for throttle jumping as your describing is either the joystick software or calibration. It can also be the deadzone and sensativity settings in your flight sim software.
1. Be sure you are running FSX with SP1 and SP2 (Service Packs), or FSX Acceleration, or FSX Steam (FSX.SE).
2. Ensure UAC (User Account Control) is disabled or set to the lowest possible setting.
3. Open your Main FSX Folder and Right Click on the "FSX,exe" icon, select "Properties" and then click on the "Compatibility" tab and check to ensure that "Run this program as an administrator" is checked. This setting should be the second to last setting checkbox), and it's difficult to see if the setting is greyed out (if it's greyed out then it's likely set via the "Change settings for all users", which is the last Check Box Item under the "Compatibility" tab.
4. Let's also be sure that "Auto Rudder" is turned off in FSX as this could be causing a problem with the FBW (Fly By Wire) programming.
5. Be sure you installed the Airbus correctly. Having customers install properly has fixes a great many problems, including throttle issues. If you wish to reinstall, follow the procedure HERE. The standard procedure for INITIAL installation of flight simulation related software is to have your Antivirus turned off, User Account Control Disabled, then Right Click the installer and select RUN AS ADMINISTRATOR. If you are REINSTALLING the Airbus then please follow THIS procedure.
6. Be sure you setup the throttle exactly as shown in the Throttle Section of the Airbus documentation (Vol7-Thrust Lever Setup).
7. Test your joystick using either the Joystick software or Windows Game Controllers and looking at the axis graph see if you're experiencing the same "jumps" instead of a smooth signal on the graph. If your throttle is jumping, you have a noisy joystick (probably a Potentiometer) and you should contact the manufacturer for a solution.
8. If none of the another helped, try removing the dead zone and reducing sensitivity in your flight sim software. You may need to find the right mix of the two for your joystick.
9. Though Aerosoft does not recommend using FSUIPC for setting up the throttle, you may benefit from doing so if your joystick is noisy. You'll need the Registered Version of FSUIPC, then follow the FSUIPC setup procedure in Vol7-Thrust Lever Setup .
10. When starting the Airbus, select the "ACRFT STATE" on the Copilot MCDU and select "TAKE-OFF STATE", after which please fully program the FMS for your test flight. This will veriffy that allow systems are up and Auto Throttle and V-Speeds are programmed for the flight.
11. Check / verify that the inverted AXIS setting in the Airbus Configurator. Please also note there are TWO CONFIGURATORS if one has both the A320/A321 and the A318/A319 installed so one needs to ensure they are using the applicable Configurator.
12. In FSX, remove ALL AXIS assignments, then close FSX, followed by restarting FSX, and then reassign your joystick AXIS. Let's note something here: If you don't normally receive the "FSX Failed to Close Normally" message, and recently saw that message (popup window) when you ended FSX, then there is a good possibility that some of all of your Joystick settings got dumped and auto configured. This occurs from time to time in FSX and FSX:SE (never been able to figure out how or why) and one has to either use a backup copy of the control settings OR re-program the Joystick settings. Because this happens from time time (even after months and months of not happening) I recommend that users back up their control settings file. The file name is "Standard" and it's located at: C:\Users\[YOUR USERNAME]\AppData\Roaming\Microsoft\FSX\Controls folder. Note that the "AppData" folder is a HIDDEN folder and as such you'll need to change your Windows Folder Properties to include "Show Hidden Files and Folders"
If you're still having problems after doing the above you either have a bad joystick, bad joystick driver, or you need to carefully follow the outlined procedures.
Finally, a short video or screen shots showing the problem you're having would be very helpful.
Please let me know how you make out.
John
-
@GBOULANGER Hi Guy, welcome to the forum. Your problem seems to be the same as the OPs. Its interesting that you are both using FSUIPC4...I wonder if this is just a problem with the FSX/FSX-SE version of the Aerosoft Airbuses....
-
8 minutes ago, asessa said:
Uhm ok, so where i should have in MF ?
Sorry, I have no idea how that software works. BUT, they key strings don't (usually) start with KEY_ (only those few you can see). Try searching for the key string name itself. So, for example, to use
#define KEY_ENGINE_MODE_CRANK_SET (KEY_ID_MIN + 1737)
the corresponding key string is 'Engine Mode Crank Set' (in FSUIPC 7 controls lists drop-downs). This would be ENGINE_MODE_CRANK_SET in your MF software.John
-
Here's FSUIPCv7.0.4d containing the event.cancel() fix. I hope to release this version officially in the next day or two: FSUIPC7.exe
John
-
10 minutes ago, asessa said:
Oh i'm sorry, i read is for key press events,
Ok i understand
To clarify, the term 'key strings' refers to the strings available as 'sim events' or controls (basically command instructions), and the key IDs are the internal numbers assigned to those event strings in the sim. They are not related to 'key presses' or keyboard keys - its using the work 'key' in the sense of 'crucial importance'! And to confuse things further, there are also 'key input events' which are the key strings relating to the windows virtual key codes.
John
-
1 minute ago, asessa said:
I downloaded your attached fsuipc but opening mobiflight i cant see these events in the offset list.. maybe i search in the wrong place..
Sorry, I don't understand what you are saying/asking. Those are new events/control, and are not related to offsets. They will be additional controls available from the assignments drop-down menus. If you want to send any available control via an offset, you can use the standard control offset at 0x3110.
John
-
8 minutes ago, asessa said:
Hi Jhon, how can we use keys with fsuipc offsets?
Sorry, what do you mean? To send key presses via offsets?
-
@styves When attaching logs, always attach the full log (zipped if too big), not a continuation log, as there is information that is missing from continuation logs that I need to see (what aircraft you have loaded, for example).
Your log does show that the parameters for your axis controls are all zero, which is very strange . Do you see the in/out numbers changing when you move your throttle with the Axis Assignment tab open in FSUIPC?
Also, did you try moving the throttle in the UI (with the mouse)? What does the FSUIPC4.log show when you do this?
John
FSX CTD
in FSUIPC Support Pete Dowson Modules
Posted
Looks like it 'adds improved recording and replay features to FS' , from here.
You can disable it by editing your dll.xml and changing the <Disabled> entry for that module to True.