-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
How to make everything aircraft specific?
Pete Dowson replied to sbclark's topic in FSUIPC Support Pete Dowson Modules
You cannot have two sections with the same name! Each section name has to be completely unique. Only one of those sections will be working. You didn't say you wanted to merge two separate sets of assignments! Sorry, I evidently misunderstood. Ah, so what you posted originally wasn't what you wanted to achieve, as I thought, but what you had already? You'll have to renumber one set and move it into the other. Here, like this: [Keys.F1_Cessna_Mustang1] 1=48,8,66776,0 2=117,10,66784,0 3=117,9,66785,0 4=118,10,66786,0 5=118,9,66787,0 6=119,10,66788,0 7=119,11,66778,0 8=120,11,66780,0 9=119,9,66779,0 10=120,10,66781,0 11=120,9,66782,0 12=121,11,66783,0 13=65,26,66789,0 14=66,26,66790,0 15=67,26,66791,0 16=68,26,66792,0 17=69,26,66793,0 18=70,26,66794,0 19=71,26,66795,0 22=48,10,66777,0 23=73,10,66756,0 25=74,9,66757,0 26=78,9,66758,0 27=112,9,66759,0 28=113,9,66760,0 30=53,26,66750,0 31=54,26,66751,0 32=55,26,66752,0 33=56,26,66753,0 34=57,26,66754,0 35=48,26,66755,0 36=49,24,66749,0 37=50,24,66748,0 Regards Pete -
Problem with multiple joysticks
Pete Dowson replied to flouid's topic in FSUIPC Support Pete Dowson Modules
No, if you mean 3.972 I don't think that's possible. I think you must be still using 3.96. Please show me the FSUIPC.LOG file. Regards Pete -
Problem with multiple joysticks
Pete Dowson replied to flouid's topic in FSUIPC Support Pete Dowson Modules
Fixed a few weeks ago, in the updates available in the Updates Announcement. Best update your FSUIPC4 too, as it can do the same. The safety timeouts were a bit too tight for the Saitek controls. That's only a coincidence. Space lines aren't at all relevant. Regards Pete -
How to make everything aircraft specific?
Pete Dowson replied to sbclark's topic in FSUIPC Support Pete Dowson Modules
Yes, exactly so, if that is the exact aircraft title as shown in the FSUIPC log file. But you might want to also set "ShortAircraftNameOk=Substring" in the [General] section (find the line there and change it). Then you could instead use a name like "Mustang" and have the keys operate all of your Mustangs, if you have more than one paint job, for example. Regards Pete -
I certainly couldn't find any reason for it to be a change I'd made. Here it appeared to start happening when I set FSX to operate in one of the "compatibility modes" rather than default. The problem I found, which only applied here to Windows 7 (I am using 64-bit versions), was that the "joyGetPosEx" scanning was causing Windows to trawl through 10-20 items in the Registry every time it was called. Since it is called frequently, especially in the Buttons options dialogue, it slows things down a bit. But worse, it wasn't closing one of the registry key handles before returning. Watching the number of handles in use (in task manager) I could see it increasing at about 50 per second (default FSUIPC4 scan rate, at 20 mSec intervals = 50 Hz). Using ProcMon I could even see which handle was being left open! Eventually this clobbers things in all sorts of places ... Anyway, in version 4.588 I don't use "joyGetPosEx", and that's fixed it here. Please let me know. I see you too are using Win7 64 -- do you use a compatibility mode for FSX? Regards Pete
-
Yes. Don't delete any you are still using, unless you want to edit all the references too! Regards Pete
-
fsuipc 3.96 pmdg 737/800/900
Pete Dowson replied to SGAMBATERRA's topic in FSUIPC Support Pete Dowson Modules
Please close FS and show me the FSUIPC.LOG file, from the FS modules folder. Regards Pete -
You can delete them if there are no assignments to them. But if the Lua files are still in the Modules folder they will get re-entered into the INI. The reference numbers are used in Button and Key assignments and macro files. If you have no such use, you can delete the entries, but also remove the associated .lua files too. Regards Pete
-
What version of FSUIPC please? I found a problem recently, one which has always been there, but which seems to be exacerbated by running FSX in a "compatibility mode", which I tracked down to a problem in the Windows 7 "joy" API -- which FSUIPC4 still uses for Button scanning. I have fixed it here but the updated version isn't ready for release yet. I'll make it available for download tonight or tomorrow morning. Regards Pete
-
Transition Altitude
Pete Dowson replied to javiercuellar's topic in FSUIPC Support Pete Dowson Modules
Unfortunately FS only has the fixed US TA of 18000. Programs like Radar Contact come supplied with a TA database, but even the one it comes with has a lot defaulting to 18000 simply because no one has ever been through all the charts to get the correct values for every airport in the world. Additionally, it does sometimes change (of course, list as Mag Vars, Runway numbers and ILS frequencies change), and some airports in the world are "flexible" (the charts read "TA by ATC"). Outside North America of course the Transition Level, (the lowest flight level before changing to QNH based altitudes) varies according to the current QNH and is set to provide the proper altitude clearance above the TA. Regards Pete -
Yes, you only had to refer to the Log Lvars.lua plug-in. ;-) If you have no FSUIPC log file than FSUIPC cannot be running. It always makes a log file if it is running. Either you are not running that Lua plug-in, or it is getting an error because you are using an old version of FSUIPC without the facilities. The log would show you if there's an error. Please ALWAYS refer to the log when anything unexpected happens. That is what it is for! You have done it wrong somehow then. since I cannot sit behind you whilst you are doing it, why not do as I asked -- enable Button logging (in the FSUIPC logging tab), then operate your button, and look in the FSUIPC log to see what happened. Show it to me if you do not understand. BTW if you are doing this with FS9 or before, make sure your FSUIPC is up to date (at least 3.96) because the LVar access facilities were only added to FSUIPC3 recently. Mind you, you must surely know you should always be sure to use a supported versiion of FSUIPC before posting here? ;-) Regards Pete
-
You are using it incorrectly then, as it is not a 2 byte number but a 40-byte (max) long string of characters including a zero terminator. That's no use to FSUIPC. The facility at 0D70 requires the name of the macro or Lua plug-in to be run. That is what it is for! It is not a switch. YOU act on the switch, your program sees the switch and writes the macro name to 0D70, as I keep saying. It seems to me you are not referring to the FSUIPC offsets list where this is all documented. Regards Pete
-
Thanks,m but you really never need to paste my own programs here. It was written by me, it is listed in the Lua documentation and it is included in the FSUIPC install. I don't need to see it here! It logs "L:vars", local named variables used by many panels. It logs them in the log, as they change, and on screen. It is useful for investigating whether L:vars would be useful to you. I csnnot possibly know because you supply no more information. What, exactly, did you assign to the button? write down what it is assigned to. If you enable button logging, what does the Log file tell you is happening? Do you know that there are some L:vars to be logged in the panel you are using? Pete
-
No no NO! What is this about "offset assignment"? ARE you writing to offsets from a program, through the FSUIPC interface, or are you merely trying to assign a button to a macro? Assigning buttons is done in FSUIPC's Buttons options tab. The drop downs there will list all of the macros. Writing to offsets from a program is covered in the FSUIPC SDK. Are you writing a program or not? If not what on Earth is all this talk of offsets in the first place? :-( Referring right back you said this: which reads to me as if you have an application and want to write to an offset in such a way that your ATR macro is activated. That is EXACTLY what offset 0D70 is for. Now please explain: where are buttons, drop-downs and ini files involved in this? If your program isn't really using offsets, if it isn't really interfacing to FSUIPC or WideFs, what are we talking about? Pete
-
By putting the parameter, if there is one, into 0D6C and then writing the Macro name to 0D70, exactly as explained in the documentation! Did you not read it? What part of it don't you understand? But that is the encoded form, as used in the FSUIPC INI file for Button or Key assignments. That isn't anything to do with instigating a macro directly via offsets!!! You KNOW an offset can be used to start a Macro -- I told you and you just confirmed! It is 0D70! samples of what? How to write to an offset? Surely, if you are interfacing directly to FSUIPC via offsets you know this already? So all you need to do now is write the macro name to 0D70. The macro name is what you assign to in the dropdowns in FSUIPC -- i.e. ":". What is so hard about all this? Regards Pete
-
Which thread? What does my "2. or 3. Post" mean? There are no posts from me with such meaningless titles! Can't you identify which Lua plug-in you mean? There are very many of them already! I supply quite a few samples with FSUIPC, and there are loads more published in threads here. Unless you can explain what you are talking about or give adequate references I'm afraid I cannot help you! Regards Pete
-
Which Lua plug-in? Sorry, I've no idea which plug-in you are talking about, nor why your thread title is "FSUIPC Hardware Button". Where does a hardware button come into your question? If you mean "can i read the state of a switch on a PMDG panel in a Lua plug-in I might write", the answer is "maybe, if that switch is readable from an FSUIPC offset (doubtful) or from an L:Var (more likely). To see if it changes an L:var value, use the Log Lvars facility in FSUIPC (an assignable control in the drop-downs), or the more extensive Lua plug-in provided to help find out about these things. Regards Pete
-
Sorry, I am not part of SimMarket. Please raise a problem ticket there. I will try to send a message to their management, but it sounds like a problem at your end as things seem to be working as far as I can tell. Can you try it on a different computer at all, just to see if you have a Windows problem? Regards Pete
-
Can this be done with FSUIPC?
Pete Dowson replied to gwplotts's topic in FSUIPC Support Pete Dowson Modules
Yes, that's the keyboard assignment. But you can use that FS control from a button too, it is listed in the FSUIPC assignments dropdown. If your buttons are detectable by Windows and by FS then they are detectable by FSUIPC too, then the answer is yes, as I already answered. Please refer back to my answer. You can assign to the FS control for a toggle operation, but if you want a separate ON and OFF action you can do that too, as I clearly explained. If you bother to ask questions, please do read the answers. I don't see the point in me having to say the same thing over and over. Regards Pete -
Feelthere A320, Fsuipc and Saitek Pro yoke
Pete Dowson replied to juanvm's topic in FSUIPC Support Pete Dowson Modules
Probably due to the timeout. The easy fix was published within a few days of the 3.96 release, a simple parameter change (which could have been guessed at by yourself from the details of 3.96 changes in the History document). Not only that, but the code was fixed a few days later! Please just reinstall 3.96 and apply the update from the Announcement above. You will get no further support for 3.93. I cannot do it. there is no going back, only forward. Bye! Pete -
Yes. WidevieW is totally independent of any of my software. Pete
-
joystick-card question
Pete Dowson replied to crashdog's topic in FSUIPC Support Pete Dowson Modules
I'm not surprised! It would confuse me. The joystick IDs are assigned by Windows. I guess that faced with two absolutely identical connecting bits of hardware it has difficulty maintaining correct assignments. I'm afraid that is all in Windows hands, not mine. With different devices, or same devices with different serial numbers in their USB idents, things are okay. The FSUIPC facilities for using the names of joystick connections are also defeated I assume, as they will both have the same names! Yes, but maybe the USB port scanning isn't quite the same. I don't know. Yes. Even if you assigned joystick letters, there's no way FSUIPC can tell the difference between "IOCa?" and "IOCa?". That's the real problem. Can't you just leave them plugged in all the time? Or do they still swap on different boot-ups? Failing all else I should contact the card makers to see if they can supply chips for the boards with different identity strings. Regards Pete -
FSUIPC, FTG acars and connection to FS
Pete Dowson replied to special20's topic in FSUIPC Support Pete Dowson Modules
Strange. I use Win7 on three systems, and never run either FS9 or FSX "as administrator". Pete -
FSUIPC add-ons crash: IYP, SIOC and FS9 togther
Pete Dowson replied to aweiss09's topic in FSUIPC Support Pete Dowson Modules
Okay, but I'm afraid they don't help. Here's what I replied by email: The SIOC stuff is no use to me. Sorry, I know zero about SIOC. The FSUIPC log shows that FSUIPC was responding normally to commands from whatever was running right up to about 7 seconds before you stopped the test. Not only that but there is nothing specific from IYP. The only commands FSUIPC is seeing are: Repeated "Gen1 off" and "Gen2 off" writes, presumably from PMDG. There are repeated every 60-120 mSecs along with writes to offsets 6296 and 62BD, which are assigned to PMDG, effectively proving that they are the source. There are no other requests at all sent to FSUIPC during the course of this log. The only other requests shown are 200274 *** EVENT: Cntrl= 66070 (0x00010216), Param= 0 (0x00000000) YAW_DAMPER_OFF 200274 *** EVENT: Cntrl= 66070 (0x00010216), Param= 0 (0x00000000) YAW_DAMPER_OFF 200274 *** EVENT: Cntrl= 65958 (0x000101a6), Param= 0 (0x00000000) FUEL_SELECTOR_RIGHT 200274 *** EVENT: Cntrl= 65958 (0x000101a6), Param= 0 (0x00000000) FUEL_SELECTOR_RIGHT 200274 *** EVENT: Cntrl= 66330 (0x0001031a), Param= 0 (0x00000000) DEC_COWL_FLAPS1 which are events detected by FSUIPC but not caused by it nor sent through it. These are on the same period as the FSUIPC writes above, so I think they are from PMDG too. In summary, there is nothing in this log which shows any activity by SIOC or IYP. Are you sure you enabled logging in the right place? The 35secs pause was in what, IYP, or FS froze for 35secs? Again, what paused for 35secs? BTW, Robert Cesar (IYP) says he never saw your post, and asks you to post again in the IYP forum. Regards Pete -
Version 4.07 of FSUIPC is three years out of date and unsupported for most of that time! And the PFC driver is up to version 4.34 at minimum! I cannot possibly support such outdated versions! Please update you installation before asking for Support. As well as the main releases on the Schiratti webpage there are later updates here in the Updates Announcement. The "List of Supported Versions" announcement should always be consulted. You'd also be better off getting FSX properly up to date -- not just SP1 but SP2 also! Pete