David Cox

Pete, Thanks for the mindaugas link - looks really promising - similar to an EPIC board but a fraction of the price !!!. Also, thanks for the explanation on the buttons/sections - I understand now !. Also, your advice on controls vs. keys - I'll change them wherever I can. The 3 presses a second measurement was done by me watcing how fast the MCP guage in my FS panel updated over a 10 second period - I haven't looked at this in the Event log yet - I'll do that and let you know the results in a day or two David

Pete, many thanks for your input on this. I think my confusion was not about whether an aircraft section had precedence over the general [buttons] section but more about the fact that I had four/five actions for one button but wanted to put some in the aircraft section and some in the [buttons] section - I didn't find anything in your guides that expalined that all actions for a single button have to go in one section Thanks for the additional info on the Button repeat rate - that may fix the problem - I'll try it later - by the way, I was getting 3 presses a second when I programmed the MCP speed scroll the other day Bye for now David

Pete - sorry I think I gave you some bum text - I have just tested with the following entries in FSUIPC.INI [buttons] 1=U0,34,C66147,0 0=P0,34,C65676,0 *2=CR(F-0,10)(F-0,11)0,0,K190,8 *3=CP(F+0,10)(F-0,11)0,0,C65752,0 ** [buttons.PMDG 737-700] 0=P0,38,C65680,0 1=U0,38,C66147,0 *4=CP(F+0,10)(F+0,11)0,0,K52,9 *5=CP(F-0,10)(F+0,11)0,0,K51,9 *6=CP(F-0,10)(F+0,11)0,0,K50,9 1) The U parameter now appears to be working in all scenarios both with the 737 PMDG loaded and any other FS2004 default plane - that is how I interpret the above code so please ignore this one unless I get back to you at later date. I think I must have ended up with som corruption in my previous set-up. 2) The problem relating to button 0,0 still exists - I show the correct lines from the INI file above (marked *). Basically, if I include all these five lines in one section [buttons] they all work fine. If I split them as above then all lines work EXCEPT **(I am using two joystick buttons as to act as SHIFT keys thus giving me four possible actions for each button). I have switched on Event logging and cannot find any reference to the control (65752 -parking brakes) in this case. I hope this gives you more to go on - as far as I can tell all five lines should work for button 0,0 even though they are in two separate sections. 3) Thanks for your suggestion on the speed scroll issue - I'll try it when you release the next version in a couple of days David

Pete - thanks for your prompt response and feedback on the MCP hardware. To answer your questions, all of the examples I gave were when the PMDG aircraft was loaded - I have not yet tried it with one of FS2004s default planes. By using this : [buttons] 24=CR(F-0,10)(F-0,11)0,0,K190,8 25=CP(F+0,10)(F-0,11)0,0,C65752,0 26=CP(F+0,10)(F+0,11)0,0,K52,9 27=CP(F-0,10)(F+0,11)0,0,K51,9 28=CP(F-0,10)(F+0,11)0,0,K50,9 [buttons.PMDG 737-700] 0=CP(F+0,10)(F+0,11)0,0,K52,9 1=CP(F-0,10)(F+0,11)0,0,K51,9 2=CP(F-0,10)(F+0,11)0,0,K50,9 I was trying to acheive a situation where 24 to 28 would be used by all aircraft in FS2004 including PMDG 737 if it was loaded. Entries 0 to 2 are designed to only work with PMDG 737 and this is how it works except that line 28 doesn't function (the idea was to use button 0,0 for 4 different tasks depending on the position of two shift buttons). Is this how it should work the way I have programmed it ? I will do some more tests on this and the U parameter and get back to you. Thanks for your input on the speed scroll issue - I presume there is no way to have FSUPIC start using one control on a button and after say 5 seconds switch to another one ? David

Pete - OK, I've done some fiddling so here is the latest position. 1) I am using FSUIPC 3.45 - I deleted the FSUIPC.INI file as I had been makes lots of tweaks especially in the Technical page. I let it create the file from scratch and started again - the only changes I am now making are to the [buttons] section, otherwise I have a virgin file. I have now got the U command working after carrying out the above - I got rid of a specific section for my PMDG 737, all entries are now under a [buttons] heading only. I think using a heading for the PMDG 737 may have something to do with it as I have noticed something else - if I use the following code under my [buttons] heading everything works fine : 24=CR(F-0,10)(F-0,11)0,0,K190,8 25=CP(F+0,10)(F-0,11)0,0,C65752,0 26=CP(F+0,10)(F+0,11)0,0,K52,9 27=CP(F-0,10)(F+0,11)0,0,K51,9 28=CP(F-0,10)(F+0,11)0,0,K50,9 However, if I do this : [buttons] 24=CR(F-0,10)(F-0,11)0,0,K190,8 25=CP(F+0,10)(F-0,11)0,0,C65752,0 26=CP(F+0,10)(F+0,11)0,0,K52,9 27=CP(F-0,10)(F+0,11)0,0,K51,9 28=CP(F-0,10)(F+0,11)0,0,K50,9 [buttons.PMDG 737-700] 0=CP(F+0,10)(F+0,11)0,0,K52,9 1=CP(F-0,10)(F+0,11)0,0,K51,9 2=CP(F-0,10)(F+0,11)0,0,K50,9 In this case, all entries work EXCEPT line 28 ! (and the U parameter didn't work under the [buttons.PMDG 737-700] section either. Is it not possible to have conditional arguments for the same buttons in two different sections ? 2) Can I bother you with another couple of questions as I am new to this stuff : I am short on normal single push buttons on my Saitek Evo joystick and would really like to use some of them to increase and decrease the speed in the PM MCP speed window. You provide four controls to do this, one set increases/decreases by 1, the other set increases by 10. I thought the best way to do this would be to use the set that increases by 1 (otherwise I would need both to set precise speeds) but when I use the control with the R parameter for single increments/decrements it takes too long (probably only 3 second). Is there a wy to increase this or can think of another solution that involves one button to increase and another to decrease (I was wondering if some form of timer can be used to start using the single control and after so many seconds switch to the x10 control until the key is released ?) 3) I am thinking of buying some cockpit gear (EFIS panel, MCP etc) but am not sure which ones to get. I see Go-Flight, Aerosoft and CPFlight/Engravity. Have you any views on which set-up is best for FS2004/PM/FSUIPC from a compatibility ease of installation/programming point of view. Your input is much appreciated David

Pete - sorry, been away for the weekend Parameters in use are as follows : [buttons.PMDG 737-700] 1=U0,34,C65674,0 0=P0,34,C65676,0 2=P0,0,C65676,0 3=U0,0,C65674,0 As you can see, I have tried the same thing with two different buttons but the button release parameter "u" does not appear to work on my Win 2000 Pro/FS2004 system. Right view is activated but on release it stays that way. I have also used a second very simple joystick - same result. Many thanks for your help on this one David

Thanks Pete, I'e tried that - the problem doen't seem to be with the View Reset/Forward command but with the "U" (key release) parameter itself - anything I program using this parameter doesn't seem to work - any idea why ? Many thanks David

Pete, Many thanks for your reply 1) I tried your suggestion and have come across a problem - when I select "View Reset" as a key release command (either through the "Buttons" interface or manually using the "U" parameter) nothing happens - I noticed this earlier when testing the commands before I started programming - the release option doesn't appear to work on my system (I have tried two different joysticks - same problem). Any suggestions as to why it's not working ? 2) Is it possible for me to keep the FS view functions working whilst using the POV hat for other functions using my shift keys - I have tried this but the FS view functions always work at the same time as my new shifted function via FSUPIC ? Many thanks David

Hi Pete - hope you are well I have been busy programming FSUIPC/FS2004 to work with my new Saitek Evo joystick (I am programming a lot of it manually in the INI file so I can use osme buttons forSHIFT functions - this gives me 4 times the amount of usable buttons). To achive this I have deleted the standard FS2004 joystick POV mapping and have programmed each POV direction as above, however, two things don't function as they do if I let FS2004 handle it via the joystick mapping, namely : 1) If I move directly from left view to left forward view I always briefly see the straight ahead view first (same with other directions) and 2) In virtual cockpit, the infinite virtual scrolling effect doesn't work (it just shifts from view to view as in cockpit view). My code so far is : 10=R0,38,K100,8 11=R0,34,K102,8 12=R0,36,K98,8 13=R0,33,K105,8 14=R0,39,K103,8 15=R0,35,K99,8 16=R0,37,K97,8 17=R0,32,K38,10 Any help you can give will be appreciated many thanks David

Pete, Thanks for your advice - I've now switched to TCP/IP (from IPX) and I no longer get any error messages in the log files for your modules - I think this points to a problem with the IPX drivers on my system - do you agree ? It's a shame because Project Magenta seems to update more smoothly from FS2004 when I use IPX. Anyway, the V-speed problem still exists so it's obviously nothing to do with your modules Many thanks David

Hi Pete - long time no speak. I wonder if you can help - I'm using the latest versions of FSUIPC and WideFS with Project Magenta and I'm getting problems with the V-Speeds updating from the CDU to the PFD (they don't stay in sync when I lower flaps - they lag behind but the pattern varies). I have checked the logs on your software components and the only one with error messages is the Wideclient one (see attached). Have you any idea what is wrong here ?. Many thanks David Cox ********* WideClient.DLL Log [version 6.101] Class=FS98MAIN ********* Date (dmy): 28/12/03, Time 16:47:49.484: Client name is XEON 312 Attempting to connect now 6875 Error on client pre-Connection Select() [Error=10051] Network is unreachable 6890 Ready to try connection again 6937 Attempting to connect now 94922 Connection made okay! 105172 Connection closed by server! 105187 Ready to try connection again 105218 Attempting to connect now 105234 Connection made okay! 264218 New Client Application: "CDUDemo" (Id=1108) 372015 New Client Application: "MCPDemo" (Id=776) 431953 New Client Application: "GCDemo" (Id=432) 2095515 WRITESTATEDATA received with bad data size! 2095515 1500 ReadLocal: Offset=2F03DD4, Size=1A10 2658422 1813 ReadLocal: Offset=2F03DD4, Size=2310 3852234 3516 ReadLocal: Offset=2F03DD4, Size=3610 4121281 1750 ReadLocal: Offset=2F03DD4, Size=3A10 5358359 Connection closed by server! 5358375 Ready to try connection again 5358422 Attempting to connect now 5493453 Connection made okay! 5578781 WRITESTATEDATA received with bad data size! 5578781 94 ReadLocal: Offset=60000000, Size=4747 5793422 Connection closed by server! 5793422 Ready to try connection again 5793453 Attempting to connect now 7230109 Connection made okay! 7241453 New Client Application: "cdu" (Id=692) 7349359 New Client Application: "MCP" (Id=752) 7369250 GetRecv() missed block? Sequence 3283 jumped to 3285 7369843 New Client Application: "pfd" (Id=672) 10142437 Connection closed by server! 10142468 Ready to try connection again 10142484 Attempting to connect now