John Dowson
-
Posts
11,232 -
Joined
-
Last visited
-
Days Won
220
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by John Dowson
-
-
12 hours ago, Fragtality said:
Should work now (with FSUIPC7 7.3.9h installed!)
Note that 7.3.9i has now been released, hopefully fixing the axis calibration issues. No change in the WAPI/WAPID though, so PilotsDeck 0.7.3 should still be fine, but I recommend updating to this latest release. I will publish this as the official 7.3.9 tomorrow (probably....!).
John
-
28 minutes ago, Chad P said:
- no Nosewheel / tiller steering with steering set and the FBW A320 neo (but this has never worked with fsuipc, Asobo added the tiller axis in SU 9 and I remember writing with you, that you can not add it at the moment
Yes - they added to the Nosewheel steering event internally and have not exposed this via SimConnect yet as far as I know, but I will check this. The Steering Set was working for some aircraft (the last time I checked), but not all - probably not for the ones that have switched to the new nosewheel event. Anyway, I will check this but probably not until I have released 7.3.9 as I need to get that out asap really.
Do you have reversers working?
Later: it may be possible to use a preset for the Nosewheel steering axis and assign to that, if I know what the event is actually called...I may look into this in the next few days...
-
Yep. there is not really much use of the *.hvar files any more unless you want to use them in macros. They are helpful to see what hvars are available though - but then you need this file provided so someone has to create this file in the first place.
Note also that you can call presets from lua using ipc.writeSTR to offset 0x7C50. I am planning to add an ipc.preset or ipc.executePreset lua function to make this easier.
Cheers,
John
-
Two things:
1. Lvar and hvar handling is broken in the current released version 7.3.8 since SU10. You need to update to the latest beta release 7.3.9i, available from
2. Hvars are only known to FSUIPC if you have provided them in a *.hvar file, named accordingly so loaded with the aircraft. This is described in the WASM section of the Advanced User guide. Please review section. Only a few such files are provided by FSUIPC out-of-the-box, and I generate these quite some time ago and so are probably not up to date (i.e. may not contain all known hvars).
However, there is no problem activating hvars or setting lvars using calculator code, and doing so by-passes the need for FSUIPC7 to know about them.
If you want to use a *.hvar file though, if you create a new one or update any existing one, if you could share that with me I can add it to the installer so that it can be used by others.
Regards,
John
-
There have been a lot of posts on this subject...with the 7.3.9i release I hope most of these issues are fixed. As far as I am aware, I still need to check the following:
- reversers in the PMDG 737
- Steering Set and Nosewheel Steering
If I have missed anything that needs to be checked, please let me know - but AFTER you have tested with 7.3.9i please, and, as always, please specify aircraft being used and attach your FSUIPC7.ini and FSUIPC7.log files.Thank you all for your patience with this matter,
John
-
1 hour ago, John Dowson said:
AXIS_LEFT_BRAKE_LINEAR_SET is not available via simconnect (and so FSUIPC) as far as I am aware - I tried adding this but get a NAME URECOGNIZED response with this, so it was removed. How are you assigning to that event?
I have re-checked this and get the same:
Quote8641 Exception 7 "NAME_UNRECOGNIZED", Ref 4192, Index param 2 on MapClientEventToSimEvent for "AXIS_LEFT_BRAKE_LINEAR_SET", id=67298 [0x106E2]
8641 Exception 7 "NAME_UNRECOGNIZED", Ref 4194, Index param 2 on MapClientEventToSimEvent for "AXIS_RIGHT_BRAKE_LINEAR_SET", id=67299 [0x106E3]I therefore don't see how these events can be used except through MSFS assignments at the moment. I will report this to Asobo.
John
-
Could you all try the attached version please, 7.3.9i. In this version, I have prevented any axis assigned to 'send to FS as normal axis' being diverted to FSUIPC's calibration facilities.
Any issues, please supply a brief description of the issue,, specify the aircraft or aircrafts that you are using that give the issue, and attach both your FSUIPC7.ini and FSUIPC7.log files.
I would like to release an official version today, although I doubt I will have time to completely update the documentation...
John
NB. Full installer from the Announcements page also updated, but the only change is the FSUIPC7.exe posted here.
-
33 minutes ago, Elad said:
yes this what i meant just wanna know if it known issue, thanks
Yes, of course it is....that is what this whole thread is about!
-
1 minute ago, Elad said:
with clean INI Axis throttle X set is working everything is stopped when trying calibrate
Sorry, but what does this mean? If you mean that assigning using 'send to FS as normal axis' without calibrating is working, but when you calibrate it isn't, then that is the known issue - you cannot currently calibrate any axis if NOT assigned using 'send direct to FSUIPC calibration.
Otherwise, can you please supply more details and also attach your FSUIPC7.ini and FSUIPC7.log files.
John
-
12 minutes ago, Agniparvata said:
It is the toe-brakes that do not work.
Seemingly
AXIS_LEFT_BRAKE_SET does not work anymore but AXIS_LEFT_BRAKE_LINEAR_SET does.Toe brakes are working here with
AXIS_LEFT_BRAKE_SET and for other people:3 hours ago, amicodepla said:Hi John today I used C172 with toe breaks, follwing your advises and the brakes work, using fsuipc's rev calibration. The *-1 was written for problem that I had with parking brakes 737 pmdg, but now I no longer have this problem.
AXIS_LEFT_BRAKE_LINEAR_SET is not available via simconnect (and so FSUIPC) as far as I am aware - I tried adding this but get a NAME URECOGNIZED response with this, so it was removed. How are you assigning to that event? -
23 minutes ago, Agniparvata said:
Furthermore, if John doesn't mind it, I'd have a remark on "policy".
John has repeatedly declared that he was reluctant to deal with problems during the long beta period of SU-10, although many users had already reported similar problems.
The LONG beta period was a good opportunity to find out, if the Asobo changes were INTENTIONAL or were simply BUGS.Now it suddenly turns out that the changes are intentional, but John has not paid any attention to this over the long beta period, which lasted almost THREE MONTHS.
It is not a good practice to wait for the release version and THEN trying to find out that there are changes, changes that touch the very basic functionality - like brakes.Now our sims, home cockpits, setups, whatever, are simply unusable due to the delay of dealing with intentional changes, that is a tiny bit unacceptable from the users point of view.
Betas are released to deal with changes BEFORE the release and that is exactly what other 3rd party developers did, and that is what the single FSUIPC developing "team" should have done.It is way too late trying to find out solutions, now, when due to the MS policy, there is no way to turn back to the previous version, a version that everything worked fine in this regard.
Just my 2 cents, but FSUIPC7 is a popular and very useful add-on, thus it would have deserved more attention if after the release our basic functionalities remained the same, or rather we need enter another wait-cycle, when possible solutions are experimented out.
It was nothing else but a waste of time, for both parties involved. Spe3cially so, that half of the millions of MSFS users have already used the free beta for long periods.I know that I should have tested FSUIPC during the beta period, but unfortunately it was/is just not possible at the moment. I have to support the current released version of MSFS, that is the priority. I also support FSUIPC for FSX, P3Dv4 & P3Dv5 (as well as any P3Dv5 betas available, although I cannot obviously discuss this or even confirm if there is one or not). And I also support the various other free utilities and drivers that I provide.
Support, especially for MSFS. is taking up 90% of my time and is leaving little time for development, let alone anything else I have just not had the time to set-up a dual system where I can investigate the beta as well as provide support for the released version, as there are various tricks/hacks you have to perform to be able to run both systems on the same PC. And I currently just don't have the disk space to run multiple copies of MSFS.
This is certainly something that I am planning to do, but I just need the time to look into this and re-organise my hard disks or purchase new ones. I will certainly be doing this once the SU10 issues have been resolved.
John
-
@Cloud8.5 You have you mixture1 axis assigned to 'send to FS as normal control' but have calibrated:
Mixture1=-10130,8192,8192,16247/32
Remove that line.
I don't know why the throttle assignment is giving errors - can you try in another/default aircraft.2 hours ago, Cloud8.5 said:And normally the new version of FSUIPC7 (7.3.9h) [installed yesterday] should work with the SU10, but it doesn’t.
No! That has fixed some issues, but not all - I am still working on it. However, I don't think I can do much at the moment except report these issues to Asobo and remove al calibration except when sending direct to FSUIPC calbration. Anyway, I will update and release a new beta at some point....
3 hours ago, Chad P said:perhaps I am using profiles without knowing it 🙂
You were sort-of using profiles but not correctly, which is responsible for some of your issues (i.e. axes disappearing).
3 hours ago, Chad P said:I want to have the same settings in every aircraft at the moment, I am just flying the FBW A320 and the Fenix A320. For the FBW A320 I need the LUA Script to start a flight for my VA, because I need to release the parking brake to start a flight.
If you need a lua script started just for one aircraft, then you need a profile for that aircraft.
3 hours ago, Chad P said:The Steering Set don't work via FSUIPC.
I will check this.
2 hours ago, Chad P said:the lua script for the parking brake stopped working with the latest fsuipc updates.
No. This was due to your dodgy ini. Please post your latest ini and I will correct it for you.
@tango3000Did you remove any calibration for axes assigned with 'send to FS as normal axis'? If not, do that and try again, otherwise please show me/attach your FSUIPC7.ini and FSUIPC7.log files.
17 minutes ago, Agniparvata said:I fail to understand why the parking brakes seem to work, whereas toe-brakes do not.
But you said these are now working...
17 minutes ago, Agniparvata said:And how is it that known 3rd party add-ons, which employ the brakes via SimConnect, do work without ANY changes, but FSUIPC does not, even if it is supposedly also does that by using SimConnect.
This is related to how FSUIPC can calibrate events received from the sim using event masking which seems to have broken in the SU10 update. I guess the other 3-rf party add-ins don't do this, and calibrate before sending to the sim, as FSUIPC does using the 'send direct to FSUIPC calibration', which IS still working.
I will reply to your other points in a separate comment....
John
-
Yes - Byte x 2 means two single bytes, each byte containing a boolean (1/0) value. You would normally read each byte separately.
On 9/25/2022 at 3:34 AM, iperwaiz1122 said:Regarding the blue annunciators, as they have blue and white states, the offsets file does not seem to have offsets for two different states. For example, "6469 1 BYTE FUEL_annunXFEED_VALVE_OPEN" this cross feed valve annunciator only has one offset while it should have two states as white and blue. Does this mean that PMDG NGx does not support dual states for the blue annunciators?
That offset holds three states, as specified in the document:
0: CLOSED
1: OPEN (dim)
2: IN TRANSIT
(highlighted)Other byte offsets also hold multiple states - check the Notes column in the PMDG Offset mapping document.
It is a 1 byte value, but not a boolean - a single byte can hold up to 256 values (usually 0-255 when unsigned but -128 to +127 if signed).
John
-
You really need to post your FSUIPC7.ini and FSUIPC7.log files if you have such problems.
However, there are currently many issues since the SY10 update. There is a beta available that fixes some of these issues, but not all, available here:
There are still some issues with axes assignments. At the moment, if you have assigned an axis using 'Send to FS as normal axis' and have also calibrated in FSUIPC, then this causes errors. For such axis assignments, you have remove/delete the calibration.
John
-
No need to post logs if its working...
-
1
-
-
FSUIPC is not compatible with any version of XPlane - you need XPUIPC which is from a different developer.
John
-
Did you try setting the FSUIPC7.exe compatibility property setting 'Run this program as administrator' ?
-
@Cloud8.5 Your files show that you are using an old and unsupported version of FSUIPC7 - 7.3.6. The current released version is 7.3.8, and the latest beta with the SU10 fixes is 7.3.9h. Please update to the latest beta (available from the Announcements sub-forum) and try again, then post if you have issues.
John
-
35 minutes ago, John Dowson said:
Checked this and none of the toe brake assignments seem to be working with the C172.
Sorry, made the same mistake again - had the parking brake set! The toe brakes work both when assigned to send direct to fsuipc calibration and calibrated, and also when assigned as send to fs without calibration.
There is one strange thing with your toe brake assignments:
Quote3=CX,256,D,7,0,0,0,*-1 -{ DIRECT: LeftBrake }-
4=CY,256,D,8,0,0,0,*-1 -{ DIRECT: RightBrake }-You are scaling with '*-1' to reverse. But, as you are assigning to FSUIPC7 calibration, you shouldn't do this - you should reverse in the calibration panel. Can you remove those '*-1' and calibrate to reverse instead and try again. Also, check that the parking brake is released!
-
54 minutes ago, John Dowson said:1 hour ago, amicodepla said:
I tried the latest beta with C172 default. The toe brakes in my situation do not work with calibration.
I will check this as well....
Checked this and none of the toe brake assignments seem to be working with the C172. I can also check if directly updating the Brake Left/Right Position has any effect...
Id it possible to apply the toe brakes in the VC with the mouse? Would be helpful if that was possible (so that I can monitor values), but doesn't seem so...
-
2 hours ago, John Dowson said:
I see you are also using the A320ParkBrake.lua - is that working for you? I ask as I have had reports that this is no linger working, but have not had time to look into this yet...
Checked this now and still working fine...
-
16 minutes ago, Berzerker said:
I only tested in the 800, but I would be absolutely floored if the systems didn't work identically enough to detect issues for both products
Yes, should be the same...but you could possibly have been using the DC-6...! As I say, always better to specify the aircraft, as well as the provider.
-
1 hour ago, Berzerker said:
Reversers are not, also direct to FSUIPC, with or without calibration. With those, I seem to get a slight amount of reverse action, allowing idle reverse, but no movement after that.
Ok, I will check this in the PMDG - presume you mean the 737-700? Better to specify the exact aircraft to avoid confusion. Anyway, I only have the 737-700 from PMDG, and don't have the Fenix, so will check in that.
45 minutes ago, amicodepla said:I tried the latest beta with C172 default. The toe brakes in my situation do not work with calibration.
I will check this as well....
John
-
1 hour ago, Chad P said:
I never had created an aircraft profile like the one for the fbw A320, I don't use this feature. Perhaps it's just an error by myself inserting the lua plugin for the parking brake for the FBW A320 without knowledge 🙂
Now I am confused....are you saying that you are not using profiles? Thats fine if you only fly one aircraft, but is really needed, especially in MSFS, if using various aircraft.
You have now set the profile aircraft name to 'FBW' - this will not catch the FBW aircraft as that string is not in the name, and so your general assignments that will be used. And as the A320ParkBrake.lua is only started in the profile, it won't be started.
Do you want to use profiles or not? I really suggest you do, if you have any intention of using any other aircraft with FSUIPC7. Decide on that, and then we can correct your FSUIPC7.ini accordingly.
John
Sorry, missed this:
1 hour ago, Chad P said:is there an option to set the nosewheel steering axis from MSFS to FSUIPC? I can't find it here.
I think only the Steering Set axis is exposed via SimConnect, but will check....
HVAR not working in LUA but same calculator code works
in FSUIPC7 MSFS
Posted
Ah, ok. I can add them - there are already those hvars but with '_1' and '_2' appended.