
John Dowson
Members-
Posts
13,332 -
Joined
-
Last visited
-
Days Won
273
Everything posted by John Dowson
-
You can use: Cheers, John
-
Only if the spoilers don't fully deploy when the lever is in the up position, as I said... Yes. Once you have set the multiplier, you can calculate the addition parameter so that full deflection (lever up) of 16383 gives 16383 once both the scale multiplier (m) and addition (a) have been applied, so (16383 * m) + a = 16383 a = 16383 - (16383 * m) Make the changes with FSUIPC open and the axis assignment panel showing. When you have saved your changes, click the Reload all assignments button to reload the changes.
-
It gets read at various points, but not when you press a button. You can also force a reload by pressing one of the reload buttons in the assignment panels. Sorry but I don't understand this....what do you mean by "value"? There is no value associated with a button press. A repeating button will just send button press events until the release is sent. You can have multiple assignments to set the view mode based upon the current view mode, using offset conditions (see Advanced User guide) on offset 0x8320 (current view mode). If there are multiple assignments to a button or key press, then they are executed in index number order. There is only logging - for example, logging for Buttons & Keys will show you which assignments are executed, as well as those not executed due to compound button conditions or offset conditions on an assignment. Not sure what you mean....there are no "modifier keys" for button and switch assignments. Again, there are no "modifier keys" for button and switch assignments. Not directly, but you can achieve this using flags or offsets. You would set a button flag (one for a button/device that you are not using) on the key press, and clear it on key release. Then, on the button assignment, you would use a compound button condition on the state of the flag. Alternatively, you could write a value (1) to a spare FSUIPC offset on the key press, and clear the value (0) on key release, and use an offset condition on the button assignment to check the value of the offset. John
-
FSUIPC Screen missing while running Prepar3d V5
John Dowson replied to Yatzar's topic in FSUIPC Support Pete Dowson Modules
The FSUIPC window is most probably being positioned off-screen. To correct this, remove the ini parameter Window from the [General] section of your FSUIPC6.ini file, which is what holds the main window size and position. Do this before you start P3D/FSUIPC. John -
Yes. I had noticed this but hoped it was temporary... I will either include the image or use/upload one to a more permanent location...depending on copyright.... Thanks for reporting. Regards, John
-
You can first try just decreasing the addition parameter, e.g. CZ,256,F,66382,0,0,0,*0.6428227,+5200 -{ TO SIM: AXIS_SPOILER_SET }- This will send a lower value when the lever is in the down position, but the higher value sent when the lever is in the up position will also be reduced, and so the spoilers may not be fully deployed when in this position. If this is the case, you will also need to adjust the multiplier, so try: CZ,256,F,66382,0,0,0,*0.65,+5733 -{ TO SIM: AXIS_SPOILER_SET }- or for an even larger range: CZ,256,F,66382,0,0,0,*0.66,+5570 -{ TO SIM: AXIS_SPOILER_SET }- or even CZ,256,F,66382,0,0,0,*0.7,+4915 -{ TO SIM: AXIS_SPOILER_SET }-
-
Can you please see the Advanced User guide on how to use the axis scaling facilities. The axis scaling parameters go on the axis assignment line, not in the calibration section. You need to add profile-specific axis assignments to your 737 profile, then change the spoiler axis assignment to 3=CZ,256,F,66382,0,0,0 ,*0.6428227,+5851 -{ TO SIM: AXIS_SPOILER_SET }- i.e. change the assignment from, 'Send direct to FSUIPC calibration' to 'Send to FS as normal axis' and also delete/remove the spoiler calibration entry.
-
Why do you have a maximum spoiler axis range of only 5851? As we are scaling the axis, best to just remove the calibration - click the Reset button and try again. And check that you have those axis scaling parameters in your ini.., using that should send a value of around -4681 when your throttle is at the lowest position of -16384: (-16384 * 0.6428227) + 5851 = -4681 If you still have issues, please attach your FSUIPC .ini and .log files (not pictures!).
-
creating new macros
John Dowson replied to dragunov2020's topic in FSUIPC Support Pete Dowson Modules
You can have multiple assignments to the same button or key press. Make the first assignment, then open your FSUIPC ini file in an editor. Also open fsuipc and go the button assignment tab. Then comment out the first assignment in your ini by placing a semi-colon (;) after the equals sign (=) on the assignment line and save. Then click the Reload all buttons button in FSUIPC to reload your updated ini. You can now assign the second action to the same button and click Ok. Now reload the ini file in the editor and also open FSUIPC's button assignment window again. In the editor, remove the semi-colon you previously added (to comment-out the assignment) and save the changes, and then click the Reload all buttons button again to reload the ini file. You should now have multiple assignments to the same button. Note that you will only see one assignment in the FSUIPC assignments panel, and it will be grayed-out there. The only way to update/change such assignments is by manually editing the ini file. -
You can use FSUIPC's axis scaling facilities to achieve this, described in page 46 of the Advanced User guide. You want to scale the range -16384 to + 16383 to the range -4681 to +16383, so you would need to use the following scaling parameter: ,*0.6428227,+5851 Just add that to the end of the spoiler axis assignment line in your 737 & CRJ700 profiles.
-
Kuro B787-8 Accessing indexed Lvars via Lua Script
John Dowson replied to Airbuspilot's topic in FSUIPC7 MSFS
I don't know why you say this... I have a long list of user requests and I process and implement them as time permits...unfortunately, most of my time is taken up by support requests, which take priority. I also have an issue with my eyes - I have a genetic degenerative eye disease (Retinitis pigmentosa -RP) so I am certainly willing to improve the visual aspects of the software I provide, but there are only so many hours in a day and I have to prioritise, which doesn't leave me much time. If I could only spend less time on support questions, especially those that could be answered if people actually consulted the documentation I provide and used the resources available before posting questions.... this would save me a lot of time and I would have more time available to implement such features... That is, of course, up to you. SPAD.next is also a great tool - I also use this occasionally. But it doesn't provide the power and control that you can get with FSUIPC, but is generally easier to use for novice users. I don't mark threads as solved - they need to be open if someone has a similar issue that they need to discuss. Regards, John -
use lua script with FSUIPC
John Dowson replied to Pascal Drac's topic in FSUIPC Support Pete Dowson Modules
But why? Yes, that is where they are installed.... unzip/decompress that file, and copy or move the lua file you want to use to your FSUIPC7 installation folder, which is: C:\FSUIPC6 it will then be available in the assignment menus to be started on a key or button press. Or you can start it automatically using the [Auto] or [Auto.xxx] (where xxx is a profile name) in your FSUIPC7.ini file - see the Advanced User guide for details. John PS. Please see the provided FSUIPC Lua Plug-Ins document... -
Your log file does not show anything untoward. I have also just checked here using the FBWA320 (stable version) and do not see any noticeable drop in FPS. If you start MSFS without FSUIPC7 (with the FPS counter window open), load the FBWA320 and wait a few minutes, what does your FPS settle to? If you then start FSUIPC7, again wait a minute or two for everything to load, what does your FPS then settle to with FSUIPC7 running? You can also take a video of this test and show me so that I can see any performance degradation. Can you also try without the FSUIPC7 WASM module running - just (temporarily) move the fsuipc-lvar-module folder out of your MSFS Community folder before you start MSFS. Do you still get the same performance issues without this running? John
-
To get hvars recognised by the WASM and FSUIPC7, you need to use *,hvar files and place them in a specific location. Some *.hvar files are installed by default (for A320, DA40 TDI, DA40-NG, DA62, Skyhawk, TBM) and others are provided in a sub-folder of your FSUIPC7 installation folder called HvarFiles. To use these you must copy/move them to one of the folders where they are recognised, and also make sure that the name if the file is a sub-string of the aircraft name/title. Please see the section Using Hvars in page 47 if the Advanced User guide for details. However, it is far easier to use hvars via calculator code or presets, and they do not need to be made known to FSUIPC with these methods. John
-
Licenses have been sent via PM. John
-
use lua script with FSUIPC
John Dowson replied to Pascal Drac's topic in FSUIPC Support Pete Dowson Modules
Lua scripts, by default, just go in your FSUIPC6 installation folder. Note that you seem to have installed FSUIPC6 under your windows Documents folder: C:\Users\adm_local\Documents\Prepar3D v4 Add-ons\FSUIPC6 This is not a good location, as that is the location of your add-on.xml file that is used by P3D to auto-start FSUIPC6 with P3D. Better to re-install into a non-windows protected folder really - but this is not related to your issue. If you can't see the script in the drop-down (prefixed by Lua, LuaDebug, etc) then it is not in your FSUIPC6 installation folder with a *.lua extension. Check the extension - sometimes people find that a .txt extension has been added... You can do this either using the ipcinit.lua or ipcready.lua files (see the FSUIPC Lua Plug-Ins document for details), or, better, use the [Auto] or profile-specific [Autp.xxx] section in your FSUIPC6.ini file - see the section Automatic running of Macros and Lua plugins on page 41 of the Advanced User guide for details. John -
Voice attack with prosim and FSUIPC
John Dowson replied to Driver170's topic in FSUIPC Support Pete Dowson Modules
Ok, so writing a certain value to an offset can trigger the sound? If so, then you can assign the key press (which will sent from Voice Attack) to write a value to an offset to trigger this using one of the Offset * controls (e.g. Offset Byte Set). It is up to you to determine what value needs to be set to which offset to trigger this - I cannot help with this. Just try this. You will need to know the location of the sound file (*.wav), and then just use the sound,play function to play the file - see the Lua library documentation. Your key press can then just start the lua script that then plays the sound. -
Voice attack with prosim and FSUIPC
John Dowson replied to Driver170's topic in FSUIPC Support Pete Dowson Modules
I am not sure what you want from me...I have already advised on what you should do: Why can you not just do that? And I would like you to answer my questions if you need help. I do not understand ProSim's response as I have no idea what you asked them... ? Approach what? What is wring with my initial suggestion? -
Does this also happen if you use FSUIPC but no FSUIPC clients such as GSX? I think there was another report of GSX causing stutters with some aircraft, so worth checking. If it is another add-on that is using FSUIPC that is causing then then you need to raise with the add-on developer. You need to activate Dev mode first (Options -> General Options -> Developers), then just open the console (Debug -> Console) and see if you can see any excessive message logging, and if so what is causing it. You will see many messages (Errors, Warnings and Messages) - you are looking for anything that is continually logging the same message. You can also show me/attach your FSUIPC7.log file (located in your FSUIPC7 installation folder), but that probably won't show much...please make sure that you exit FSUIPC7 before you attach this. Ah, so you have the MSFS logging console window open. Looks like there are a lot of errors - are they mainly 'Could not find components..' ones? Where are they coming from? It is difficult to see images properly, but your stutters are obviously being caused by the CPU being overloaded (most probably CPU 1). I am pretty this one be caused by FSUIPC, but it could be due to GSX as you are at an airport, so please try without that. John
-
You are using version 7.2.14 which is over 1.5 years old. I did say: Please update. Please also exit FSUIPC7 before attaching any files.
-
Display P3D and MSFS Aircraft Flight Parameters
John Dowson replied to ark1320's topic in User Contributions
You can get the mixture lever position (as a double with 0.0=cutOff, 1.0=full rich) in offsets: 0x3AF0 - engine 1 0x3970 - engine 2 0x3A30 - engine 3 0x38B0 - engine 4 It should be straightforward to add code to read the value from these offsets and display these as well. -
And does the selector that you are using for inc/dec freely rotate? i.e. can you continually rotate it in one direction? Rather than using an offset for each position of the selector, why don't you just use one offset that holds the number of the last position the selector held. You can then read this in the lua script , compare that to the current position (which you can pass in as a parameter), and then decide what to do based upon the difference between these values. So, in the script, you would have the current position c (0-7), and read the previous position p (also 0-7) from an offset, and if (p == (c +1) mod 8 ) or (p ==(c+2) mod 8 ) or (p ==(c+3) mod 8 ) or (p == (c +4) mod 8 ) then decrease else increase then write the current position to the previous position offset, where the positions are 0..7 (for the 8 distinct positions) Doing it this way, you would only need one lua script for each inc/dec function (rather than one per selector position), and it would still work if a position (or two) is jumped.
-
Kuro B787-8 Accessing indexed Lvars via Lua Script
John Dowson replied to Airbuspilot's topic in FSUIPC7 MSFS
I can look into the possibility of allowing the font size to be uncreased, and allow light text on a dark background. I will add this to my to-investigate list, although I have no idea when I will have time to look into this at the moment. Unfortunately all my time is taken up by support these days and I have little time for adding new features. I will not be adding a search function for lvars - you can just list the lvars, open the FSUIPC7.log file in an editor and use the editors search facilities. Not also that the logging console window is light text on a dark background, and lvars are also listed there (it it just a window onto the FSUIPC7.log file), so you can try opening that (Log->Open Console) and using that. John