All Activity

Ok, thanks for the update. And thanks for the kind words. Also, please note that these forums are now closed for new support requests, and will be removed at the end of the year. For any further issues, support id available on the FSUIPC website (fsuipc.com). Please see Regards, John

John, apologies for not responding sooner. After trying a number of checks to ensure that I had all of the necessary files etc. loaded and correctly installed where they should be, I realized that strange things were happening in other areas of my computer. So I eventually took my machine in for testing and had to replace the AIO for my processor. The pump was not working properly and thus the temperatures were extremely high even at low loads. I now believe that the high temps for the processor were the significant cause of my problems. I have had the computer back for about three weeks now and things are stable. FSUIPC was and still is working perfectly after recalibrating some axis. Thank you for your patient support throughout. I have been a devoted user of FSUIPC for a very long time (decades) and do not want to be without it. It makes my flight sim experiences a pleasant and very satisfying pastime.

First, please not that these forums are soon closing and will be unavailable by the end of the year. Please use the new support forums - see This has been reported many, many times... As I tell everyone, for any and all installation and registration issues you should read the provided documentation before posting, namely the Installation and Registration guide. For all new installations, you will need to install the latest combined VC++ redistributables (for both x86 and x64) from Microsoft. Please see the documentation. If you had read this topic you would have also found the same advice, and also in one of the hundreds of others reporting this issue. I am closing this topic now, For any other issue, please use the new support forums. John

Hi, After a machine upgrade, I have the same problem. I have copy/pasted the details exactly as given but am getting the details not-verified error. Can you please help?

Hi John Thank you very much, that worked throttle works as it should I appreciate all your help on this topic Best wishes Rhys

The usual value range for an axis is -16384 to +16383. The value range for the axis you are using (as show in the log is -16306 to 3000. So the minimum value (-16306) is ok, resulting in a max thrust (as your axis is reversed) of 88,76%. But the max value (3000) will only result in a minimum thrust value if around 41%. You can try two things: 1. Try calibrating your axis in windows game controllers to see if you can get the full range for the axis values. 2. If you cannot get the full range of values, just calibrate the script to the range of values your axis produces. So with a range of 16306 to 3000., in the lua script change: newValue = (16384 - value) / 327.6 to newValue = (3000 - value) / 193.06

Hi Log file now shows changes. As per the last post I removed [Auto..Bell UH-1C] section but nothing showed up in the log so I reinstated it I did get data Cheers Rhys FSUIPC4.ini FSUIPC4.log

Your log shows only one value being logged from your axis. I have no idea why your axis is not updating offset 66D0 when it is being moved. We need to determine why your axis is not writing its value to that offset. For the time being, can you stop that lua from running - just remove it from you [Auto] or profilw-specific [Auto..Bell UH-1C] section, whichever one you are using. then add offset monitoring to offset 66D0 using the right-hand side of FSUIPC's logging tab, as S32. Then load your aircraft and movr your throttle slowly from idle to full throttle and then back again, exit and attach both your log and ini files. Strange that this was previously working correctly, but just reversed. They are probably fine and look to be using FSUIPC-added controls or custom controls. They looked strange to me as there was no comment generated, but maybe FSUIPC4 does not auto-generate comments for such controls, like it does in other versions. I have not used FSUIPC5 / FSX for many years now and forget the differences in this compared to later versions. John

Hi John Ok here is the latest log file. This one does show throttle axis value and Lvar value which I hope is what you are after Cheers Rhys FSUIPC4.log

Offset logging is done via the right-hand side of the FSUIPC logging tab. However, you don't actually need that as the lua script logging is sufficient, as that will log any offsetchanges. Please also remove the comment characters from the other ipc.log statement:

Hi John Thank you for your help and please forgive me if I am making things frustrating for you which is not my intention. Between my dyslexia and a ADHD I am as frustrated with figuring this out as you are as I try to implement your instructions here is the Lua script with the ipc,log uncomment out but I just not sure in the text where to add the offset logging for offset 66D0 local ThrottleOffset = 0x66D0 function throttleControl(offset, value) -- Calibrate value from range -16384 - +16384 to 0-100 -- NB if the lvar range is fifferent, change this, e.g. if the range is 0-1, use -- newValue = (value + 16384) / 32768 newValue = (16384 - value) / 327.68 ipc.log("Throttle axis value is " .. value .. " resulting in lvar value " .. newValue) -- send value to lvar ipc.writeLvar("L:UH1_THROTTLE", newValue) end event.offset(ThrottleOffset, "SD", "throttleControl") --ipc.log("Milviz Bell uh1 redux ThrottleCollective-handling lua now running") Regards Rhys

No, you did not set the correct logging., You have activated lua debug logging - I did not request this and it is not needed, please remove this. As I said, you just need to uncomment the 'ipc.log' line entry in the BellUH1Throttle.lua file. You also did not add the offset logging, and the log file shows no movement in the throttle (or the lua debug logging is not showing this). You also forcibly closed the log and started a new one. Please don't do this. Please set the logging as requested and show me those files again. Please exit FSX/FSUIPC before attaching logs, and do not request a new log file.. John

Hi Here are the two files, hopefully I have captured the correct data for you I know you mentioned invalid button assignments in the dodsim -{}- They are assigned and work. I wonder if it is the event file that I am using that the buttons don't show up like the in Milviz MD530 and the Bell U-1C. Cheers Rhys FSUIPC4.1.log FSUIPC4.ini

Activate the logging in the lua script (remove comment characters from 'ipc.log' line) and add offset logging for offset 66D0, then test and show me your FSUIPC4.log & FSUIPC4.ini files. For the test, first move the throttle from idle to full and back again, and then exit FSX/FSUIPC4 before attaching the files. John

Hi John Started from scratch again. I didn't realize that I only need to set the offset Dword to the first drop down box I cleared the second drop down box so the throttle now moves in the correct direction but I won't rotate back to idle Rhys

.Ok, thats interesting. So they are not 'scoped lvars' then.. Thanks for the update. I will make a note of this and take a look at the ProSimSDK.dll when I get time. Thats good to know, thanks. I also saw this on using ProSim with MobiFlight and FSUIPC (which may be useful): https://www.mobiflight.com/en/tutorials/aircraft-guides/prosim737.html John

Hi John, thanks again for your kind help. Meanwhile it turned out that all these variables used by Prosim are proprietary - they provide an SDK to work with these variables which means that there is an extra ProSimSDK.dll which can be used when writing own code in C# for example. Obviously only MobiFlight is currently doing this in their current beta, so with Mobiflight I am able to read and write those Prosim variables. Still struggling with writing Boolean values or reading String values, but these bugs are currently fixed by MobiFlight - obviously the Prosim support within MobiFlight has just been introduced recently. With that I can shift values back and forth in offsets and then work with these offsets in the Lua script. Best regards Stefan

Please do this. You need to: 1. Correct your aircraft profile names, as advised 2. You have a lot of general button assignments to your Macro Bell_UH1C - shouldn't these be in your .Bell UH1c profile? 3. You seemed to have assigned your axis to update offset 66D0 twice: Why is this? 4. You are starting your BellUH1Throttle lua script in the [Auto] section, so it will run with all aircraft. As this is specific to the Bell UH1, you should start it in a profile specific [Auto.Bell UH1c] section. 5. You seem to have assignments to non-exisiing macros: But it looks like the lua isn't running for some reason. Are you sure it is in your FSUIPC4 installation / modules folder?

Hi John Only just got back to the simulator after adding a Leo Bodnar button box and reconnecting all my switches and axis I deleted my ini file and started from scratch. For some reason the Lua is not working here is the ini file and log file. Trying to tidy up my aircraft profiles as you have pointed out Cheers Rhys FSUIPC4.ini FSUIPC4.log

These forums will soon be closing, and are already closed for new topics. Please see the following announcement: John / FSUIPC

These forums will soon be closing, and are already closed for new topics. Please see the following announcement: John / FSUIPC

In case this happens for anyone else, if you click the copy icon from inside the app, it always copies the whole line but that also includes the “Name:”, Email:” and “Key:” part as well so there a number of characters need to be manually deleted meaning some are being missed. Thankfully I found my original email…. and what was going on.

This depends on how you select the key to copy it. If you just double-click it, it may not select the entire key due to the mix of letters and numbers. It is up to you to make sure that you are copying the entire key string - I am not going to provide details on how to copy and paste correctly...! However, I will add a comment to make sure that the entire 12 characters of the key are copied/pasted. Anyway, glad its working and thanks for responding with what your issue actually was. Regards, John

John I apologize to you for raising this issue. You were correct, it was user error. In my defense however, i was copying the key from the Simmarket app which as it turns out misses the last 4 characters of the Key....

There is no 'password' - your FSUIPC7 license contains 3 parts: name, email/address & key. If you have already registered your license, the details will be in your FSUIPC7.key file. Otherwise, the license details can be retrieved from: 1. the purchase email you received from SimMarket 2. Your SimMarket account If you have issues accessing your SimMarket account, you need to resolve this with SimMarket, not here. I am just a vendor on SimMarket and cannot assist with SimMarket issues. John