severniae

Hi John, thanks for the fix and apologies for not attaching my ini - after I saw your first reply I tried removing some old Lua files and then matched the lua identifier in the key command list and it all worked fine after that (although I only have 50 Lua files now instead of several hundred!)

Hi, I have an issue in FSUIPC7, latest version. I use a number of Lua files to control various things on the PMDG DC6 - however my files don't appear to work. I've notced that it is renaming the LUA key presses I've set to the below each time FSUIPC loads - it never used to do this... Please advice apprecaited.. Each one that says 'Preset Control' should be the name of a Lua.. [Keys.Douglas_DC6] 63=N81,10,L70:R,0 -{lctl+Q: Press=Preset Control }- 64=N81,9,L54:R,0 -{lshift+Q: Press=Lua DC6_RPM_24 }- 66=N81,11,L56:R,0 -{lctl+lshift+Q: Press=Lua DC6_RPM_CONTROL }- 78=N69,10,L57:R,0 -{lctl+E: Press=Lua DC6_SOF }- 80=N82,11,L71:R,0 -{lctl+lshift+R: Press=Preset Control }- 88=N84,9,L55:R,0 -{lshift+T: Press=Lua DC6_RPM_26 }- 191=N87,9,L74:R,0 -{lshift+W: Press=Preset Control }- 193=N87,10,L75:R,0 -{lctl+W: Press=Preset Control }- 195=N87,11,L77:R,0 -{lctl+lshift+W: Press=Preset Control }- 197=N82,9,L115:R,0 -{lshift+R: Press=Preset Control }- 214=N85,10,L67:R,0 -{lctl+U: Press=Preset Control }- 216=N85,11,L78:R,0 -{lctl+lshift+U: Press=Preset Control }- 223=N73,9,L84:R,0 -{lshift+I: Press=Preset Control }- 224=N73,10,L83:R,0 -{lctl+I: Press=Preset Control }- 226=N73,11,L85:R,0 -{lctl+lshift+I: Press=Preset Control }- 228=N79,9,L87:R,0 -{lshift+O: Press=Preset Control }- 230=N79,10,L88:R,0 -{lctl+O: Press=Preset Control }- 232=N79,11,L89:R,0 -{lctl+lshift+O: Press=Preset Control }- 236=N76,9,L91:R,0 -{lshift+L: Press=Preset Control }- 238=N76,11,L92:R,0 -{lctl+lshift+L: Press=Preset Control }- 242=N75,9,L54:R,0 -{lshift+K: Press=Lua DC6_RPM_24 }- 245=N75,10,L94:R,0 -{lctl+K: Press=Preset Control }- 249=N74,9,L96:R,0 -{lshift+J: Press=Preset Control }- 251=N74,10,L97:R,0 -{lctl+J: Press=Preset Control }- 253=N74,11,L98:R,0 -{lctl+lshift+J: Press=Preset Control }- 257=N72,9,L100:R,0 -{lshift+H: Press=Preset Control }- 259=N72,10,L102:R,0 -{lctl+H: Press=Preset Control }- 261=N72,11,L103:R,0 -{lctl+lshift+H: Press=Preset Control }- 265=N71,9,L105:R,0 -{lshift+G: Press=Preset Control }- 267=N71,10,L106:R,0 -{lctl+G: Press=Preset Control }- 269=N71,11,L107:R,0 -{lctl+lshift+G: Press=Preset Control }- 273=N77,9,L109:R,0 -{lshift+M: Press=Preset Control }- 275=N77,10,L110:R,0 -{lctl+M: Press=Preset Control }- 277=N77,11,L111:R,0 -{lctl+lshift+M: Press=Preset Control }- 281=N78,10,L113:R,0 -{lctl+N: Press=Preset Control }- 283=N78,9,L101:R,0 -{lshift+N: Press=Preset Control }- 285=N67,9,L59:R,0 -{lshift+C: Press=Lua DC6_WATCHENGINES }- 289=N90,10,L58:R,0 -{lctl+Z: Press=Lua DC6_SON }- 290=N83,9,L112:R,0 -{lshift+S: Press=Preset Control }- 291=N83,10,L79:R,0 -{lctl+S: Press=Preset Control }- 293=N90,9,L72:R,0 -{lshift+Z: Press=Preset Control }- 296=N88,10,L86:R,0 -{lctl+X: Press=Preset Control }- 298=N88,9,L82:R,0 -{lshift+X: Press=Preset Control }- 302=N65,10,L81:R,0 -{lctl+A: Press=Preset Control }- 304=N65,9,L80:R,0 -{lshift+A: Press=Preset Control }- 306=N68,10,L95:R,0 -{lctl+D: Press=Preset Control }- 309=N68,9,L108:R,0 -{lshift+D: Press=Preset Control }- 311=N70,10,L93:R,0 -{lctl+F: Press=Preset Control }- 314=N70,9,L99:R,0 -{lshift+F: Press=Preset Control }- 316=N86,10,L90:R,0 -{lctl+V: Press=Preset Control }- 318=N86,9,L104:R,0 -{lshift+V: Press=Preset Control }-

Hi, I have a strange problem.. I'm finding with some scripts, ones that appear to work fine, randomly...don't.. For example, I have one script that's only function is to call two other scripts - sometimes, when I load this script, it functions, calls the other two scripts in turn and they load fine. Other times, it just exits for apparently no reason before completing its tasks.. the same goes for a few other scripts I am using... Example script: " function CallScripts() ipc.sleep(2000) ipc.runlua("DC6_MP_CONTROL") ipc.sleep(50) ipc.runlua("DC6_RPM_CONTROL") ipc.sleep(1000) end CallScripts() ipc.sleep(250) ipc.exit() " Here is the output for the log - same script ran twice - one time it works, the next not, no change to the scripts between executions...: ********* LUA: "DC6_WATCHENGINES" Log [from FSUIPC version 7.2.1] ********* 1872344 System time = 01/07/2021 00:13:10, Simulator time = 13:15:44 (12:15Z) 1872344 LUA: beginning "C:\FSUIPC7\DC6_WATCHENGINES.lua" 1872344 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:8 1872360 LUA: Global: ipcPARAM = 0 1872391 >>> Thread forced exit (ipc.exit or os.exit) <<< 1872391 System time = 01/07/2021 00:13:10, Simulator time = 13:15:44 (12:15Z) ********* LUA execution terminated: Log Closed ********* ********* LUA: "DC6_WATCHENGINES" Log [from FSUIPC version 7.2.1] ********* 1872469 System time = 01/07/2021 00:13:10, Simulator time = 13:15:45 (12:15Z) 1872469 LUA: beginning "C:\FSUIPC7\DC6_WATCHENGINES.lua" 1872469 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:8 1872469 LUA: Global: ipcPARAM = 0 1872485 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:2 1872500 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:10 1872516 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:4 fn: CallScripts 1872657 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:6 fn: CallScripts 1872797 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:8 fn: CallScripts 1872813 LUA: C:\FSUIPC7\DC6_WATCHENGINES.lua:12 1872828 >>> Thread forced exit (ipc.exit or os.exit) <<< 1872828 System time = 01/07/2021 00:13:11, Simulator time = 13:15:45 (12:15Z) ********* LUA execution terminated: Log Closed *********

Thanks John, very helpful.

Hi, For some aircraft, I have to use the setting THROTTLE1_AXIS_SET_EX1 to control the throttle. The problem appears to be that I can't set a dead zone at the start of the throttle. I understand that I could do this using lua in fsuipc. I have some experience in Lua, I have written some basic scripts to help with automation in the cockpit etc... But I'm not certain of what I should do to execute throttle operation in FSUIPC - nor how to limit the throttle's travel. Would someone mind posting some example code that I may work on as a basis? Thanks in advance, James

Hi, I'm using Prepar3d V5 and I've set a joystick command to increase the simulation rate, and one to decrease. The problem I have is that in VR, I often overshoot the number of times to press decr, and then end up accidentally in half speed wondering what has happened. Is there any way to assign a command to just set the simulation rate to 1? Thanks, James

Right on the money Pete! I edited how much I am moving the throttles and hey presto! They appear to be working as planned. I'm tweaking a little so they don't overrun but so far so good! I will have one issue once I plug the throttles back in - in that using "ipc.writeUW(0x310A, 0xC0C0)" won't work with this script as it would block the throttle settings I'm trying to change. Is there an alternative that would prevent my moving the physical throttles (ch quadrent) from effecting the script in the sim? If so great if not I'll have to get inventive! Cheers, and thanks for all the help! James

Ok so I just did a quick test. Here is the full script I ran.. Here is the log output: And finally here is a log trace with debugging enabled, in case helpful: Hopefully that gives some more information to be working with...

Ok Pete, will do once I get home a bit later on.

Hi All, So I'm trying the quoted below which is an excerpt from a script that I have put together (with help from others), that should read the current manifold pressure value via the gauge in the cockpit, and then either increase or decrease the throttle until the desired manifold pressure is reached. For some reason what I'm expecting to happen, isn't... Just to give a little background on the script: MP is the desired Manifold pressure, in this case '250' represents a manifold pressure, of 25'. PMDG stores the manifold pressure in object 325 (for engine one), so if the gauge was reading 35' - the value in "L:dc6_325_obj" would show as '350' (probably with a lot of decimal places!) var2 is reading the current position of the set throttle. I've set all sorts of display readouts so I can see what the script is seeing as the values. I've found that this value has a range from 0 - 16384. var3 is the control number from the throttle. Through experimentation I've figured that this setting has a range from -16384 for throttle closed, to 16384 for full open. So to try to pass the correct value to set the throttle, I'm having to subtract 16384 and then double the inputted value. I think this is the correct way to do it, but I may be well short of the mark.. What I'm seeing happen, is that when I engage the script the throttle just seems to reduce to 0 and then does nothing... I can't get it to do the gradual increase as it should on the script. If I remove the " * 2 - 16384" from THR_IN then every time the throttle just makes big jumps forward until the throttle is at full power... Should the below script work? or have I fundamentally misunderstood something? Thanks, James

Ok, thanks Pete. Apologies for what must be quite silly questions! Will try your suggestions.

Just as a note - setting the throttle axis does seem to work when set using 'direct' within FSUIPC, it's only if you need to separate the throttles you can't. (see attached images) Are the settings in those images a 'control' or can they be influenced by an offset? Apologies if I'm not hitting the right terms, only really started playing with scripts and these settings over the last few months. Thanks, James EDIT: just tried "ipc.control(65820, 10000)" and it doesn't appear to do anything in the sim.... Though I guess I have missed something,.,

Thanks for the quick reply Pete! I'm quite new to this, how would I get the list of controls? What I'll need for the script to work is the range of the control, and then I can increase or decrease the throttle depending on the manifold pressure readout.. I'm creating an 'alternate' flight engineer - the one PMDG created is great but i'm creating scripts so I can call out and set specific manifold pressures/RPMs!

Hi, I'm trying to use a lua script to do some throttle setting for the PMDG DC-6 but I have a problem. If I set the individual throttles by passing a value to, for instance 0x0924 - nothing happens. This follows the fact that if I set the throttles within FSUIPC configuration itself they don't work, which has been confirmed by PMDG support. However it does work if I set the 'Throttle' to an axis within FSUIPC. I'm trying to see if I can use this 'throttle' axis in my lua script instead of the individual throttles, which isn't ideal for what I'm doing but better than nothing. I just can't find the right offset. I can move the throttles using the axis with 'throttle' set using the FSUIPC configuration, but I just can't figure out an offset to use. Could someone help me? Thanks in advance, James

Thanks for that fast response Pete. I guess it working after is a conincidence - I'll check my load order and see if there is something that I'm doing. To your knowledge are there any known conflicts with ActiveSky 2012/TrackIR5?