
gfd
Members-
Posts
171 -
Joined
-
Last visited
Everything posted by gfd
-
I decided on using the KeySend option. It works very well. I am having trouble running scripts in WideClient. I don't want to comment further until I have exhausted my efforts to find a solution. If necessary, at that time, I'll create a new post regarding the scripts in WideClient.
-
I assigned the rest of the unassigned and things were again scrambled after the location of the updated button. Perhaps FSUIPC doesn't know or care about the wideclient buttons. That's OK. Took about 20 minutes to fix. I think in future, I will assign all buttons on a page, even if unused. That way, I will not have to deal with the unintended reassignment. Just having the button screen available is worth the time taken to realign the assignments. Graham
-
Thanks for the reply Den. The screen starts minimized and then I maximize the window for use. No issues before I activated the button item described below. Sorry for the sketchy description in my initial post. I have corrected the situation and so cannot give you exact examples. I have setup a LUA file to assign the button screen virtual buttons. I used parameters to assign the various lua items in the script: Custom_AXE.lua...parameter 1, etc. if ipcPARAM == 1 then <do something> end My setup for buttons is copied below. Please note button 9 which now has 4B"JETWAY" assigned to it. Before I programmed the button, it was the same as 18= is now; just a number with an equal sign. I assigned button 9 and then opened FSX and started to prepare the cockpit in the aircraft. At that point 2/3 of the assigments in FSUIPC had shifted and I had to reassign them. Example: button 1 was Custom_AXE.lua, parameter 1 (assigned in FSUIPC button tab). After assigning button 9, button 1 became Custom_AXE.lua parameter 9 (assigned in FSUIPC button tab). That is probably not exactly what happened, but it is the jist of it. [buttonScreen] Size=10,6 Title1="Airbus X" Colour2=52,115,90 ;toggle not set dark green Colour3=153,247,171 ;toggle set light green Colour4=52,115,90 ;dark green for buttons Colour5=200,200,200 ;grey for goto ===========Page 1 Airbus X=========== 0=4B"ADIRS 1\rOFF" 1=4Br"ADIRS 1\rNAV" 2=Tr"CABIN\rLIGHTS" 3=T"NAV LOGO" 4=Tr"BEACON" 5=Tb"BATTERY 1" 6=Trb"BATTERY 2" 7=Tr"FUEL PUMP\rLEFT 1" 8=T"YELLOW ELEC\rHYD PUMP" 9=4B"JETWAY" 10=4B"ADIRS 2\rOFF" 11=4Br"ADIRS 2\rNAV" 12=Tr"PANEL\rLIGHTS" 13=T"STROBE" 14=Tr"WING" 15=Tbr"EXTERNAL\rPOWER" 16=Tr"APU\rMASTER" 17=Tr"FUEL PUMP\rLEFT 2" 18= 19= 20=4Bb"ADIRS 3\rOFF" 21=4Bbr"ADIRS 3\rNAV" 22=Tr"NO\rSMOKING" 23= 24=Tr"RUNWAY\rTURNOFF" 25=Tb"APU\rBLEED" 26=Tbr"APU\rSTART" 27=Tr"FUEL PUMP\rCENTRE 1" 28= 29= 30=4B"CAPT WIPER\rOFF" 31=4Br"FO WIPER\rOFF" 32=Tr"SEATBELTS" 33=4B"LANDING\rRETRACT" 34=4Br"NOSE\rOFF" 35=Tb"EXTERNAL POWER\rCONNECTION" 36=Tbr"EXTERNAL GPU\rCONNECTION" 37=Tr"FUEL PUMP\rCENTRE 2" 38= 39= 40=4B"CAPT WIPER\rSLOW" 41=4Br"FO WIPER\rSLOW 42=Tr"EMERGENCY\rARM" 43=4B"LANDING\rOFF" 44=4Br"NOSE\rTAXI" 45=Tb"WHEEL\rCHOCKS" 46=Tbr"TRAFFIC\rCONES" 47=Tr"FUEL PUMP\rRIGHT 1" 48=T"ENGINE\rANTI ICE" 49=Tb"PROBE WINDOW\rHEAT" 50=4B"CAPT WIPER\rFAST" 51=4Br"FO WIPER\rFAST" 52=Tr"ANN LIGHTS\rTEST" 53=4B"LANDING\rON" 54=4Br"NOSE\rTAKEOFF" 55=4Br"GSX" 56=4Br"PRO ATC X" 57=Tr"FUEL PUMP\rRIGHT 2" 58=Tr"WING\rANTI ICE" 59=5G60"NEXT PAGE" Thanks again for looking in on this, Graham
-
Greetings I have set up my button screen and I must say I am pleased with the result. I do have an issue: I left a number of buttons blank inside the screen. I then setup one of those buttons with a control. When I next opened FSX, the buttons were mostly mismatched with the original controls. I had to realign most of the buttons with the correct controls. I'd like to know what I did wrong, so that when I setup the remaining unassigned buttons, I don't have to realign again (if possible). My guess is, that given I didn't setup the buttons originally, with no assignment, I created the problem at that point. Any advice is appreciated. Thanks Graham
-
Thanks Paul I thought about it a bit after my first reply. You are of course right. I was looking for a complicated solution to what should be a simple problem. It seems I either autorun a lua file when WideClient opens (event option) or use sendkey in FSUIPC and have WideClient run a script when it receives the appropriate key code. Thank you very much for setting me straight. I'll fool around with these options and hopefully come up with a solution. Thanks again, Graham
-
Well thanks for the reply Paul. When I saw Wideclient only, I assumed that was advisory. OK, at the risk of getting in over my head, would it go something like this: -ensure copy of ipc library in Wideclient folder on networked machine -write script which would change colour of button in question also in Wideclient folder -setup function in client script to take 2 arguments (button number and colour numbers) -call script on client machine, in script on FSX machine If this is the right idea, how do I go about calling a script on a differnt machine? If I'm out in left field somewhere, can you give me a rough sketch or point me somewhere I can get the required information? Thanks again for looking into this, Graham
-
Greetings I am working my way through programming the WideFS virtual buttons. I am quite impressed with the result. Currently, WideClient is on my non-FSX networked machine. The lua script I am writing is on the FSX machine. I noticed in the ipc library, that there is a function called ipc.setbtncol. That could be quite useful in allowing me to show non-toggle buttons as on or off. I attempted to add that function to a code block I was writing to change the state of a control in Airbus X. The form of the function was ipc.setbtncol(buttonNumber, r, g, b). I'm sure the function parameter data (button number and the colour numbers) were correct. However, when I activated the control using the virtual button in WideClient, on the networked machine; I got an error message in the log window on the FSX machine. It suggested the function was referring to a nil value. As stated above, the LUA script to manipulate the controls is on the FSX machine. The virtual button screen is on the networked machine. Forgive the long drawn out explanation. Can anybody help me to understand if what I am trying to do is possible? If so, what am I doing wrong? Thanks Graham
-
Greetings I have set up a button screen in WideFS on a networked machine. Communication with FSX is there. The buttons are seen by FSUIPC and I have programmed a couple of controls in Airbus X Extended. So far, so good. My problem is with buttons designated as toggles. When I press the button, the colour changes, as I imagine it should. But when I set up the button to toggle a control in FSUIPC, something a bit strange happens. It requires 2 presses of the button to change the state of the control. 2 presses on and 2 presses off. At first, I thought it was the nature of the Airbus X L:Vars. So I programmed a toggle button to turn the parking brake on and off. Airbus X uses the FSX control for the parking brake. I got the same result as if I did with the Airbus X L:Var. When I set up the button as just a button, the control behaved as I thought it should. 1 press on and 1 press off. There is obviously something wrong with my understanding of the nature of the toggle button for the button screen. Furthermore, it is probably something so basic, that I'll feel like a bit of an idiot when I realize what it is. The lua script for the action in question is below: --External Power Toggle if ipcPARAM == 3 then LVarSet = "L:AB_OVH_ELECEXT" intValue = 0 if ipc.readLvar(LVarSet) == 0 then intValue = 1 end ipc.writeLvar(LVarSet, intValue) ipc.writeLvar("L:SmallOverheadPushButtons", 1) end I understand that Pete is away on vacation. If anyone can help me out with this in the meantime, it would be most appreciated. Thanks, Graham EDIT: To any and all that read this post. I did a search (after my post...duh) and saw another post that provided the answer. Please forgive the inconvenience. Graham
-
Thanks for the reply. I'll post on LINDA and see what develops. You know, I find it rather interesting that this should be an issue at all. Why don't addon developers just use standard FSX controls and where it is not feasible, publish the custom controls so that mere mortals, like myself, can program our controllers in FSUIPC. This last sentence is obviously from an uninformed civilian. Thanks again Graham
-
Thanks for the reply. Ive already asked on their forum. However, I didn't ask the right question. It seems to me that it would be win/win if LINDA supported your buttons. Would you object to my referencing the fact you think it's feasible/desirable? It may spark greater interest at their end. Of course if you can do it at your end (perhaps that's not what you were inferring) that would be awesome. In the 6 years I've been playing with planes, I find that your product has been rock solid, as has been your support. I agree that pulling apart someone else's effort is tricky and often leads to failure. Also, even if successful, defeats a good purpose. Thanks again Graham
-
Greetings. Iam using wideclient and have programmed the button screen. Thank you for developing that. Unfortunately, LINDA doesn't recognise the button screen. That's understandable. However, LINDA has the plug-ins for mostof my add on aircraft. It seems I will have to develop my own routines to make available to FSUIPC for the addon aircraft. I am certainly not asking for lessons, but if you could point me in the right direction, I'll get to work. I'm guessing you have included documentation. I'm just not sure where to start. Thanks Graham
-
Pete Dowson is the man!
gfd replied to robert mcdonald's topic in FSUIPC Support Pete Dowson Modules
I hesitate to add to this topic as I believe Pete is wary of over-zealous boosterism. I come from a different angle. I am very new to this. I have found my hobby. I don't even want to think of VATSIM (with greatest respect for rob), VOR, ILS, etc; at this stage. FSUIPC was my first software purchase after FSX. It has allowed me to optimize my controllers in a way that permits me to to spend my time learning to fly the aircraft as opposed to remembering which key combination turns on the coffee pot. It is conceivable that I would have found FSX to be more like a Rube Goldberg machine than a simulator, without FSUIPC. In time, I will move on to the finer points of this obsession, with further help of this utility; at which time I am sure to express my thanks for FSUIPC 9.458f :) Until then, I'd like to thank Pete for getting me started. Graham Derreck -
Happy new year. Hope you enjoyed your vacation. I got the new G940. I also had the same issue as described above. It seems that there are 2 different calibration routines for controllers. One calibrates the joystick using the mini X Y hat. The other calibrates the joystick using the actual handle. After finding and using the latter, the X Y axes on the joystick reported values that were correct.
-
Hi Robert, I have the registered version installed. Here is where the docs are: ...\<FSX root folder>\Modules\Documentation\FSUIPC Documents. Is that what you're after?
-
Thanks for the reply. Assigned in FSUIPC. Sent to FSUIPC for calibration. Calibrated in FSUIPC. Version 4.7.4.9. I have a return authorization for the G940. We'll see how the new one works. Thanks for your help and thanks for FSUIPC. Graham
-
Seasons greetings Peter I am working my way up the learning curve with FSX, in no small part because of FSUIPC. I am learning how to calibrate my controllers in FSUIPC. Once you get the hang of it, the amount of control one can exercise is excellent. One thing I noticed was that the G940 joystick hits its maximums about half way into the throw in both the X and Y axes. Now you didn't make the controller. I dare say if you did, I wouldn't have to be writing this. The joystick's calibration page calibrates only the hat. Perhaps that is meant to calibrate the main stick. Anyway, I digress. Is there a work around in FSUIPC to compensate for this? I have calibrated the joystick in FSUIPC to accommodate different aircraft. But in order to do so, I have to narrow the centre zone and flatten the slope. Now perhaps joysticks are designed to hit their maximum values early into the throw. If that is the case, I won't bother myself, or you, further. Thanks for the help.
-
Thanks for the replies. I'm a rookie, but I'll get better.
-
Greetings I am new to flight simulation and I must say using FSUIPC has certainly flattened the learning curve from a setup point of view. Learning how to fly right, well that is something else. I am in the process of setting up my G940 to work with Flight Simulator X. I have the Acceleration addon. My question is regarding the autopilot. I was able to map changes to altitude, vertical speed and max bank to 2 of my trim wheels. I can use buttons to toggle the various functions (on...off). I would like to assign heading and course to the trim wheels using FSUIPC's feature to segment an axis. Excellent idea, by the way. I can't seem to find a command that would increase or decrease the compass headings on the dials. I noticed in the user manual that there is a command to incr/decr the heading bug fast (1024 and 125), but I imagine I'd want to have a more graduated change. After hours of searching the options and reading through the manuals, I am flummoxed. The answer is probably beating me on the head, but I can't see it. Can you point me in the right direction so I can finish setting up my Autopilot controls? I realize I can use a mouse to move those dials, but I have TrackIR and I get dizzy trying to stay steady with the mouse. Besides, I got a controller to avoid the use of the mouse and keyboard. By the way, I do have another question: I would like to thank you for profiles. I noticed that FSUIPC does not extend to many payware aircraft. Fair enough. You can't be everything to everyone. If I use a payware plane and it has its own logic for, say the autopilot, I can create a profile for the aircraft. That's good. Now, let's say this plane uses Ctrl + M (fictitious) to turn on the autopilot and there is already a command using that key combination for something in a default plane. If I set up this profile and assign this keyboard command to a button, will it conflict, or will the command in the profile override the default (for the payware plane) and play nice? I would like to say that I am impressed with the software. Before I bought the registered version, I didn't realize that a number of addons use the freeware version of the application to talk to FSX. But even had I known, I would have paid for the product. It has added a lot of flexibility and saved me a lot of time in setting up. Just doing that and reading the manuals, has been an excellent early learning experience. Sorry for the novel here. Any help will be appreciated. Graham