Kensei

Yeah, that's what I have done now with those two buttons I mentioned. To clarify: the TQ6 actually has 6 levers which are connected to a pot-meter (that's what it's called right?) and 4 axis that are dummy axis (thise 4 axis 'share' the same 'opening' in the TQ6 where the 4 actual (pot-metered) axis reside), meaning...you can moven them like an axis, but in fact...they don't have any pot-meter attached to those axis. They only have a button hooked up to the axis so one can use those buttons (4 per dummy axis) when moving that (dummy) axis down untill it makes contact with the actual throttle axis. I insert a picture of the TQ6 so you get an idea of the layout of it. Actually, I do have another GF item (the T8) but I can't get it to work with the Ariane 737 (I posted a question about that not too long ago), but..I can get rid of the gfdev.dll in this particular case. OK, I leave that at your desgression Thanks Pete. I hope I clarified things for you. Regards

Hi Pete, I've seen in the forum that you've gotten a lot of questions regarding a reverse. I've read them all (i think I have anyway). Basically there're two options: program a lever and link it via FUIPCS Direct to a trust reverse. The other option is cvreating a "dead-zone" on the throttle axis and make the lowest possible setting the thrust range (as is done with many CH products). Well..I have a GF TQ6. You may remember that one 'cause it does have 'wannabe" thrustreverse levers which, actually, only are there only to activate a button. Now..I've the reverselevers working, but am not really sure if I've gotten the correct way. Let me explain: When activating the buttons of a thrustreverse (I only use 2 of the 4 axis for the throttle and ofcourse also two reverse axis (which aren't real axis as I've explained)). When checking FSUIPC I see the following happening when pressing the button: The button start with 2,2 in the Buttons/Switches TAB of FSUIPC, but than changes automatically to 169,2 (even though the button is still pressed). The other thrustreversebutton starts with 2,3, but changes to 169,3 while the button is still pressed. This is something FSUIPC has no control over, so it's something that originates in the controller of the GF. The fsuipc.ini file shows this: 0=R169,2,C65966,0 1=R169,3,C65971,0 My actual question is this: The thrustreverse works by pulling the levers back and thereby activating the button. FSUIPC detects the 169,2 and 169,3 and activates both left and right trustreverse (since I linked that particular action to the 169,2 and 169,3 buttons). However...when I want the reverser to get back to normal (no thrust reverse), I have to move the throttles forward a bit. I hope you understand what I mean here. What I really would like to have is the option to push the reverse levers back to their "up" position (eg no thrust activated) without moving the throttle levers. However...I don't see any option that would give me that. The only thing I can think of would be: is it possible to make a timed action after pressing a button? So I press a button, an action is done, but only during a certain amount of time (like...30seconds or so). You know what really is weird? Goflights own software somehow can do this: I activate the thrust reverse, the reverser is activated untill I move the lever back. But that doesn't compute...the button is, by itself, switching from R2,2 to R169,2. I know this all might sound weird, but I tried my best to explain. If you need more info I'd be happy to provide it. FSUIPC 4.573 is being used on FSX.

Hi Pete, Well..as to Ultimate Traffic X...it was just that it was the latstest thing I installed on my rig...and it was also responsible for my full harddrive. After de-installation I reagined about 8-9GB. And after starting FSX up, it was complaining about a missing scenery; area169 (which corresponded with Ultimate Traffix X. I just deleted that entry out of the scenery.cfg.UltTrafficX is AI as you probably know, So possibly it did indeed have a actigate.dll...I'm not sure.

Hi Pete, I seem to have fixed this error myself, but am not too sure what triggered it (although I have my suspicions). 1. The FSX drive was full and had only 700Kb of free disk space :oops: . I can imagine that the logging of FSUIPC or it's own internal mechanism triggerd an error -> disk full or something like that. 2. I had Ultimate Traffix X installed too (which accounted for the full hard drive), but even after de-installing it, this error reappered..until I deleted the appropriate area out of the scenery.cfg. Then the error didn't return anymore. Point of this message is at least let you and the members know that such a message can occur and maybe why it did occur in the first place. I'm sure it has noting to do with FSUIPC. Regards,

Sorry, my bad. I won't send anything :) I might try a Lua and if that fails...then the mouse will also be an option :D

Hi Pete, Thanks for your quick answer. During the time that I posted my question and you posting your answer I've been busy reading the first 9 pages of this forum to get a better overall idea on how things can be made to work, especially the Lua items (quite interesting stuff btw). I'm unsure when it was that you had contact with Ariane, but I guess that not much has changed with them (just knowing that access to their forum is taking >1month by now is a :x ) Anyways...as to your questions regarding my posting: I can live with the ghost image of the flaps since it only happens when I leave the FSUIPC...which I won't access during flight. As to the keys to operatie buttons/switches etc... I might give it a try with offsets, but...frankly...I won't get my hopes up. Oh..and I tried the default 737 from FSX...which didn't show the mouse macro screen as well. I'll try again later, and if if it still won't work, I'll post the logfiles. If I run into any issues, I'll post the appropiate loggings too (I've noticed that you've requested those from a lot of members here...and should make it easier to troubleshoot...I understand)

Hi Pete, Thanks for your reply. I've been trying to get things started yesterdayevening, but unfortunatly have been running in some unforseen issues which I can't really explain. Info up front: Running FSX Acceleration on WIN7 x64 with 8GB RAM. Sceneryrelated things: REX, GEX2, UTX, Xclass landclass files, Radarcontact. Using FSUIPC for FSX with Wideview (wideview not actually used) v4.573 (upgraded v4.3 to 4.5 to 4.573) I have the Ariane 737-800 X2 (bought December last year) and have been trying this weekend to get things working with my GF stuff (TQ6 throttle and an 8 switch T8). Using a registered FSUIPC 4.573 (that's the latest version). I don't know whats wrong but I experience the following troubles: 1. Can't create mousemacro's. This doesn't work in any plane, so it's not Ariane related. I have been creating mousemacro's in the past (last year with the PMDG MD-11). I'm missing the pop-up that usually comes after starting a mousemacro recording and clicking any switch, button...whatever. I guess (if memory serves me well) that I'm doing it still the correct way (I'm typing this by memory so if it's not 100% accurate, that's the reason): Click Create Mouse Macro, give it any name, so I choose "Ariane738", click OK, click OK in FSCUIPC to return to the cockpit. I click the Logolight switch and expect the popup from the mouse macro, but...it doesn't show. I re-open FSUIPC and can select to end the mouse macro creation (so it's actually running, but not showing I guess). EDIT: just read this reply (viewtopic.php?f=54&t=78335#p477609). Maybe Ariane is using a different way for their cockpit. Do you happen te have any knowledge in what Ariane's using Pete (even though that's not your job to know :) ) 2. Just as another user I read about on this forum, I have the same issues with "ghost moves" (viewtopic.php?f=54&t=77942&p=475049&hilit=ghost#p475049). I setup my TQ6 with the Spoilers, the two throttles (2 axis, one for each throttle) and a flapaxis. Flaps are set at UP (flaps 0), I enter FSUIPC, I go to the tabs Calibration (I think it's called that way), I change NOTHING, close FSUIPC and my flaps are going all the way down..by itself! I used the DIview you mentioned to that other user. I see no change on that during that ghost move (sliders remain exactly where they were before the ghostmove occured. I tried the "dontresetaxis=yes" in the fsuipc.ini but to no avail. I even deleted the fsuipc.ini file and let a new one be created, but even that didn't help. I thought that maybe it had to do with the Goflight software, so I de-installed it and put the GFdev.dll from your Goodies page on this forum in the ...\Modules directory of FSX, but that didn't help either. Powersettings to the USB devices are standaard (no powersaving activated there) As you can imagine..I'm a bit at a loss here. I hope I gave you enough information to get an overall picture of what's going on. If you need more info, please let me know. I can only do debugging and so during the evenings mind you. Regards, Eric

Hi all, Maybe this is a question in the "DOH'' category...if so I apologize. I've bought FSUIPC for FSX some time ago and had been 'playing' around with it, but on a very small basis. Now I'm planning on doing more with it and had a question regarding payware planes that only ship with a 3d cockpit (the PMDG JS4100, the Ariane 737 and the oncomming PMDG 737NGX). Will the default FSUIPC work with 3D cockpits ONLY when creating mousemacro's or is it neccesary to use the LUA method? Should it matter that I'm using a TrackIR when creating mousemacro's? Thanks for the help. Now I'll start reading the PDF for the flap detents :D

sorry that i didn't react sooner...my pc crashed so i'm re-installing everything which will take some time. I'll report back later....maybe the LUA will work at once then :D

Correct, nothing works. I'm gonna try your tips tomorrow when I've got more time, and will check the logfile.

Well...just my luck :cry: I can't seem to get this to work. I own the PMDG JS4100. I have an official FSUIPC v 4.53(which is the latest). I use the VRinsight MCP-Combi with SerialFP2 v2.520 and a Goflight T8. I can get the HDG, ALT bugs working, but none of the items listed here react in the SIM. I used Richard Cooke's and your LUA an MACRO and linked it to my FSUIPC but nothing works. Screenshot: My J41.LUA file: -- LEFT Fuel Pump SWITCH TOGGLE if ipcPARAM == 1 then LFuel = ipc.readLvar("L:LeftStbyFuelPump") if LFuel == 1 then ipc.writeLvar("L:LeftStbyFuelPump", 0) ipc.control(66587, 8027) elseif LFuel == 0 then ipc.writeLvar("L:LeftStbyFuelPump", 1) ipc.control(66587, 8028) end -- RIGHT Fuel Pump SWITCH TOGGLE elseif ipcPARAM == 2 then RFuel = ipc.readLvar("L:RightStbyFuelPump") if RFuel == 1 then ipc.writeLvar("L:RightStbyFuelPump",0) ipc.control(66587, 8027) elseif RFuel == 0 then ipc.writeLvar("L:RightStbyFuelPump", 1) ipc.control(66587, 8028) end -- GROUND POWER SWITCH TOGGLE elseif ipcPARAM == 3 then GPwr = ipc.readLvar("L:GndPowerSwitch") if GPwr == 1 then ipc.writeLvar("L:GndPowerSwitch", 0) ipc.control(66587, 8028) elseif GPwr == 0 then ipc.writeLvar("L:GndPowerSwitch", 1) ipc.control(66587, 8027) end -- Warning Panel Mute SWITCH TOGGLE elseif ipcPARAM == 4 then WarnMute = ipc.readLvar("L:CapMuted") if WarnMute == 1 then ipc.writeLvar("L:CapMuted", 0) ipc.control(66587, 8027) ipc.writeLvar("L:CapMuteSwitch", 0) ipc.control(66587, 8027) elseif WarnMute == 0 then ipc.writeLvar("L:CapMuted", 1) ipc.writeLvar("L:CapMuteSwitch", 1) ipc.control(66587, 8027) end -- LEFT CABIN FLOW SWITCH TOGGLE elseif ipcPARAM == 5 then LCabFlw = ipc.readLvar("L:CabinFlowControl") if LCabFlw== 6 then ipc.writeLvar("L:CabinFlowControl", 0) ipc.control(66587, 8027) elseif LCabFlw == 0 then ipc.writeLvar("L:CabinFlowControl", 6) ipc.control(66587, 8027) end -- RIGHT CABIN FLOW SWITCH TOGGLE elseif ipcPARAM == 6 then RCabFlw = ipc.readLvar("L:FDeckFlowControl") if RCabFlw== 6 then ipc.writeLvar("L:FDeckFlowControl", 0) ipc.control(66587, 8027) elseif RCabFlw == 0 then ipc.writeLvar("L:FDeckFlowControl", 6) ipc.control(66587, 8027) end -- START MASTER KNOB LEFT GROUND elseif ipcPARAM == 7 then LStart = ipc.readLvar("L:StartMasterKnob") if LStart > 0 then ipc.writeLvar("L:StartMasterKnob",0) ipc.control(66587, 8028) elseif LStart == 0 then end -- START MASTER KNOB RIGHT GROUND elseif ipcPARAM == 8 then LStart = ipc.readLvar("L:StartMasterKnob") if LStart < 2 then ipc.writeLvar("L:StartMasterKnob",2) ipc.control(66587, 8028) elseif LStart == 2 then end -- NAV LIGHTS TOGGLE elseif ipcPARAM == 9 then NavLt = ipc.readLvar("L:NavLightSwitch") if NavLt < 2 then ipc.writeLvar("L:NavLightSwitch", 2) ipc.control(66587, 8027) elseif NavLt == 2 then ipc.writeLvar("L:NavLightSwitch", 1) ipc.control(66587, 8028) end -- NAV LIGHTS/TAIL FLOODS TOGGLE elseif ipcPARAM == 10 then NavLt = ipc.readLvar("L:NavLightSwitch") if NavLt > 0 then ipc.writeLvar("L:NavLightSwitch", 0) ipc.control(66587, 8027) elseif NavLt == 0 then ipc.writeLvar("L:NavLightSwitch", 1) ipc.control(66587, 8028) end -- SEAT BELT switch TOGGLE elseif ipcPARAM == 11 then sblt = ipc.readLvar("L:FastenSeatbeltSigns") if sblt == 1 then ipc.writeLvar("L:FastenSeatbeltSigns", 0) ipc.control(66587, 8028) ipc.control(66587, 74) elseif sblt == 0 then ipc.writeLvar("L:FastenSeatbeltSigns", 1) ipc.control(66587, 8027) ipc.control(66587, 74) end -- NO SMOKING SWITCH TOGGLE elseif ipcPARAM == 12 then nsmk = ipc.readLvar("L:NoSmokingSigns") if nsmk == 1 then ipc.writeLvar("L:NoSmokingSigns", 0) ipc.control(66587, 8028) ipc.control(66587, 74) elseif nsmk == 0 then ipc.writeLvar("L:NoSmokingSigns", 1) ipc.control(66587, 8027) ipc.control(66587, 74) end -- Left Windshield Antiice off elseif ipcPARAM == 13 then LWS = ipc.readLvar("L:LeftWSAntice") if LWS == 2 then ipc.writeLvar("L:LeftWSAntice",1) ipc.control(66587,8027) elseif LWS == 1 then ipc.writeLvar("L:LeftWSAntice", 2) ipc.control(66587,8028) end -- Right Windshield Antiice off elseif ipcPARAM == 14 then RWS = ipc.readLvar("L:RightWSAntice") if RWS == 1 then ipc.writeLvar("L:RightWSAntice",0) ipc.control(66587,8027) elseif RWS == 0 then ipc.writeLvar("L:RightWSAntice", 1) ipc.control(66587,8028) end -- Left Air Data off elseif ipcPARAM == 15 then LAD = ipc.readLvar("L:LeftAirData") if LAD == 1 then ipc.writeLvar("L:LeftAirData",0) ipc.control(66587,8027) elseif LAD == 0 then ipc.writeLvar("L:LeftAirData", 1) ipc.control(66587,8028) end -- Right Air Data off elseif ipcPARAM == 16 then RAD = ipc.readLvar("L:RightAirData") if RAD == 1 then ipc.writeLvar("L:RightAirData",0) ipc.control(66587,8027) elseif RAD == 0 then ipc.writeLvar("L:RightAirData", 1) ipc.control(66587,8028) end -- DC PowersourceKnob UP elseif ipcPARAM == 17 then DCP = ipc.readLvar("L:DCPowerSourceKnob") if DCP < 3 then ipc.writeLvar("L:DCPowerSourceKnob", DCP+1) ipc.control(66587, 8039) elseif DCP == 3 then end -- DC PowersourceKnob DOWN elseif ipcPARAM == 18 then DCP = ipc.readLvar("L:DCPowerSourceKnob") if DCP > 0 then ipc.writeLvar("L:DCPowerSourceKnob", DCP-1) ipc.control(66587, 8039) elseif DCP ==0 then end -- PROP SYNC SWITCH TOGGLE if ipcPARAM == 19 then PSync = ipc.readLvar("L:PropSync") if PSync == 1 then ipc.writeLvar("L:PropSync", 0) ipc.control(66587, 8027) elseif PSync== 0 then ipc.writeLvar("L:PropSync", 1) ipc.control(66587, 8028) end -- CCT Auto Cycle Switch elseif ipcPARAM == 20 then ipc.writeLvar("L:AutoAnticeCycle", 2) ipc.control(66587, 8028) ipc.sleep(200) ipc.writeLvar("L:AutoAnticeCycle", 1) ipc.control(66587, 8027) end and my JS41 Macro: [Macros] 1=L:GrndSpoilersSwitch=TOG 2=Left feather 2.1=C66587, 1420 2.2=C66587, 8029 3=right feather 3.1=C66587, 1421 3.2=C66587, 8029 4=LNAV Zoom + 4.1=C66587, 4940 4.2=C66587, 8031 5=LNAV Zoom - 5.1=C66587, 4930 5.2=C66587, 8031 6=AP_HDG plus 6.1=C66587, 26902 6.2=C66587, 8031 7=AP_HDG minus 7.1=C66587, 26901 7.2=C66587, 8031 8=AP_HDG press 8.1=C66587, 2691 8.2=C66587, 8031 9=AP_Alt plus 9.1=C66587, 3921 9.2=C66587, 8031 10=AP_Alt minus 10.1=C66587, 3920 10.2=C66587, 8031 11=AP_CRS plus 11.1=C66587, 26702 11.2=C66587, 8031 12=AP_CRS minus 12.1=C66587, 26701 12.2=C66587, 8031 13=AP_CRS press 13.1=C66587, 2672 13.2=C66587, 8031 14=AP_IAS plus 14.1=C66587, 26802 14.2=C66587, 8031 15=AP_IAS minus 15.1=C66587, 26801 15.2=C66587, 8031 16=AP_IAS press 16.1=C66587, 2681 16.2=C66587, 8031 17=AP_ALT 17.1=C66587, 281 17.2=C66587, 8031 18=AP_ALTarm 18.1=C66587, 282 18.2=C66587, 8031 19=AP_VS 19.1=C66587, 283 19.2=C66587, 8031 20=AP_IAS 20.1=C66587, 284 20.2=C66587, 8031 21=AP_HDG 21.1=C66587, 277 21.2=C66587, 8031 22=AP_NAV 22.1=C66587, 278 22.2=C66587, 8031 23=AP_APPR 23.1=C66587, 279 23.2=C66587, 8031 24=AP_BC 24.1=C66587, 280 24.2=C66587, 8031 25=EFIS1_Full/Map 25.1=C66587, 214 25.2=C66587, 8038 26=EFIS1_TCAS 26.1=C66587, 215 26.2=C66587, 8038 27=EFIS1_GSPD/TTG 27.1=C66587, 217 27.2=C66587, 8038 28=EFIS1_ET 28.1=C66587, 218 28.2=C66587, 8038 29=EFIS1_V/L 29.1=C66587, 21901 29.2=C66587, 8038 30=EFIS1_LNAV 30.1=C66587, 21910 30.2=C66587, 8038 31=FMS_Enter 31.1=C66587, 3610 31.2=C66587, 8030 32=FMS_DirectTo 32.1=C66587, 3220 32.2=C66587, 8030 33=FMS_Prev 33.1=C66587, 3200 33.2=C66587, 8030 34=FMS_Next 34.1=C66587, 3210 34.2=C66587, 8030 35=FMS_NAV 35.1=C66587, 3470 35.2=C66587, 8030 36=FMS_VNAV 36.1=C66587, 3480 36.2=C66587, 8030 37=FMS_FPL 37.1=C66587, 3500 37.2=C66587, 8030 38=FMS_Plan 38.1=C66587, 3540 38.2=C66587, 8030 39=FMS_HDG 39.1=C66587, 3550 39.2=C66587, 8030 40=FMS_Tune 40.1=C66587, 3560 40.2=C66587, 8030 41=FMS_Back 41.1=C66587, 3460 41.2=C66587, 8030 This switch should toggle the CCT, but i don't see nothing happening. What might be wrong here? Any help would be appreciated!