-
Posts
38,265 -
Joined
-
Days Won
170
Content Type
Profiles
Forums
Events
Gallery
Downloads
Everything posted by Pete Dowson
-
FSUIPC stops working while flying
Pete Dowson replied to Hong's topic in FSUIPC Support Pete Dowson Modules
Okay, so the logs I asked for should be very useful. FSX can only use up to just over 3Gb memory -- it is a 32-bit program, not 64, so cannot take advantage of your 8Gb. Hoever, there's another use of memory external to FSX and that is for TCP/IP buffers, used by SimConnect. And those can certainly clog up the rest. However, that would affect EFB too so it is unlikely. Certainly there are known issues with FSX when it gets near filling its 3Gb -- corruptions occur, as noted in the G3D.DLL crash threads in the AVSIM FSX Forum. The corruptions occur before FSX flags "out of memory", so it is certainly a possibility, Did the Simconnect INI file you put into the Flight Simulator X Files folder look exactly like this: [SimConnect] level=Verbose console=No file=path to FSX\Modules\SimConnect%01u.Log file_max_index=9[/CODE] If so then, yes, each time you start FSX again it should make a new log, till it gets to 9 then is starts overwriting the oder ones. But just go by the date and time of the log. Don't worry too much. Regards Pete -
Okay. So the crash is occurring between Initialise #1 and #2. The only process done there is reading the INI file and trying to sort it out.into sections for indexing. Did you do the test I requested with the INI file removed, so a new one would be made? Did you do the test with the KEY files removed? Okay. And as I surmised, you do have a [General] section added at the end because of that !1=. You need to completely delete the first [General] section including the !1= Worse, and probably the cause of the problem, there is more corruption later on: First, the [buttons] section has errors. There are duplicate line numbers: All these: 69=P101,8,K8,9 70=P101,9,K13,9 71=P101,10,C65908,0 72=P101,11,C65909,0 73=P101,12,C65910,0 74=P101,13,C65911,0 75=P101,14,C65912,0 76=P101,15,C65913,0 77=P174,7,K49,8 78=P174,6,C65876,0 79=P101,16,K13,9 80=P101,17,K8,9 81=R0,0,C65588,0 82=P149,31,C65892,0 83=P149,28,C65893,0 and these: Only one of these sets will actually operate. Not sure which (it depends how Windows works in such cases). 69=P174,9,K82,15 70=P174,8,K82,15 71=P174,14,K49,15 72=P174,15,K49,15 73=P174,13,K50,15 74=P174,12,K50,15 75=P174,19,K51,15 76=P174,18,K51,15 77=P174,16,K52,15 78=P174,17,K52,15 79=P174,22,K85,8 80=P174,23,K85,8 81=P174,21,K85,12 82=P174,20,K85,12 83=P174,3,K89,11 Then there's a spurious [ character at the end of that Buttons section: [ Maybe these are the only errors, maybe though there are some in the parts you are not showing me. ALL sections are read initially so that an index of the sections present can be built. Removing some because they "may not be relevant" only obscures what might be happening. As to how this corruption occurred, I can only hazard a guess that you had some other crash whilst the INI file was being re-written one time. Or maybe a power failure or a disc glitch.. Why it doesn't appear to affect 3.991 but does 3.998 I do not know, but I'll find out. But I might need the complete INI file. Please, before "fixing" it, Zip it up and send it to me at petedowson AT btconnect DOT com. [LATER] Yes, I do need the whole file, please -- I can't make it crash with the above extract. I've a feeling it's something more than the relatively minor corruption above. Thanks, Pete
-
Duplicating keyboard Functions With Mouse
Pete Dowson replied to wb2002's topic in FSUIPC Support Pete Dowson Modules
No, it is't possible in FSUIPC at present. What "forward and back" controls do you mean? Left and right arrow buttons do what, exactly? Are you Slewing? Is it possible in FS? I only added some mouse "look" functions to FSUIPC because FS disables its own mouse look facility if you disable joystick controllers (which seems weird to me, but still ...) and I was trying to restore that facility for those using FSUIPC exclusively for axis and button assignments. BTW what are "mouse wheel's side-to-side switches"? It sounds like you want the mouse to be treated as a type of joystick insofar as all button-type inputs are assignable like buttons? If that so? If I went that far then shouldn't mouse movement be X and Y axes for assignment as well? Regards Pete -
Okay. download 3.999a here: FSUIPC3999a.zip Run Debugview, the run FS9 with 3.999a in the Modules folder. When it crashes, go to the Debugview screen, and save the log as, for example, debugview.log (File menu, save As). Then you can load it into and editor and paste it here. After that I may need to add more such stuff into the area it identifies and repeat the process. Thanks! Regards Pete
-
I know -- it just shouldn't be there and the fact that it was SHOULD have meant that a complete new [General] section was generated at the end of the INI file. I expect it is there (so removing that 1= gives you two such sections, which will make things confusing in the future!). The problem I have is insufficient information, and your editing much of the INI file before pasting didn't help. Both the joystick list and sound list are read before logging starts, for example. I've examined the initialisation code and I cannot spot which part it might be -- since 3.991 in April last year there were 12 interim releases before 3.998 in September. Some of those might have needed small initialisation changes, but I'm not spotting them at present. So I'm making a special version which logs some locating information, helping narrow it down further. Because logging isn't enabled in this short period, I'm sending the data to Microsoft's "DebugView" program, which you will need to download and install, please, from here: http://technet.micro...ernals/bb896647 It's a small program with no installer. Just put it into some convenient folder and double-click it to run it. I'll tell you more when I have the special version ready. Regards Pete
-
Ah ... that's a useful fact in itself. One of the first things FSUIPC does when it is loaded is create the Log file. The fact that it isn't being created at all limits the area I need to examine somewhat. Hmm. Very little if anything will have changed between 3.991 and 3.998 in the small parts of code between loading and log file creation. But I'll go through that area with a fine tooth comb and see what I can identify. I may need you to conduct more tess, because there's no problems here on several different systems, and no other reports. That !1= before [General] worries me. Did you put that there? Section headings should only be [<name>], nothing else. The !1= ... construct makes that a position-retained comment line, making the rest of that section ignored. FSUIPC would create a new default [General] section. Just in case there's something in the INI file causing the problem, could you save your copy out of the way, remove it from the Modules folder altogether, so letting FSUIPC 3.999 make a new one, please? Then see if FS loads okay. Another useful test would be to temporarily remove your FSUIPC.KEY file, to make it appear unregistered. See if 3.999 works then. Unfortunately you seem to have removed other sections too. There should at least be a section listing your joystick devices and your sound cards. Both may be relevant. Regards Pete
-
Wideclient 6.94 on old win 2k mashine
Pete Dowson replied to ab_a320's topic in FSUIPC Support Pete Dowson Modules
You posted your support query into the FAQ subforum. I moved it to the Support Forum for you. Sorry, I cannot support anything earlier than XP. Too much has changed and it would be a nightmare trying to make WideClient cope with older as well as newer versions of Windows. You will be fine staying with WideClient 6.78 provided you do not need to use any of the newer facilities like Lua plug-ins or BroadcastMode. Regards Pete -
Ah, a completely different matter, then. Versions 3.98 and 3.99 are a lot older than all of those! That's more than a mere "element of language"! ;-) I am definitely getting the same problem with both of the latest versions. Okay, so that is the log from a working version. I need to see the log from 3.999 please. That might be useful, once I know whereabouts (i.e. at what stage) the crash is occurring. Hopefully the log from 3.999 will help there. Please also paste in your FSUIPC.INI file, in case the problem is related to some parameter therein. Regards Pete
-
Cant Get FSUIPC Registered
Pete Dowson replied to Harpee's topic in FSUIPC Support Pete Dowson Modules
So you DID right-click on the EXE and select "run as" then "administrator", as instructed? In your earlier message you seemed to be saying that since you were the administrator in administrator mode you assumed you could just execute it by just double-clicking. That was the assumption I was pointing out was not so good. Never mind, you got it working. Let's move on. Pete -
FSUIPC stops working while flying
Pete Dowson replied to Hong's topic in FSUIPC Support Pete Dowson Modules
Isn't a working FSUIPC needed, then, for that aircraft? I thought it was using FSUIPC. How did you complete the flight -- changing aircraft? I think it is necessary. We need to understand what is happening to cause this problem, and maybe it is related to something the aircraft does (or you request it to do) at that stage of flight -- after all you seem to be implying it is always happening at cruise level -- immediately you are in cruise mode? What actually happens then which is different, what action are you taking after which it (immediately?) 'stops' working. It was 2:20 when you replied but I'd gone to bed half an hour before. ;-) Regards Pete -
Cant Get FSUIPC Registered
Pete Dowson replied to Harpee's topic in FSUIPC Support Pete Dowson Modules
You surely don't need to be a computer guru to follow instructions! Best to never simply assume. Pete -
FSUIPC stops working while flying
Pete Dowson replied to Hong's topic in FSUIPC Support Pete Dowson Modules
Okay. It still insn't clear then whether it is really FSUIPC, or the aircraft, ot SimConnect which is "stopping working". And if you tried to close FS immediately, how could you tell that EFB was still getting good data about your aircraft position and the AI Traffic? It's importannt to know this because if that stops receiving too is points more towards SimConnect. Nothing new in the Log. Still have that strnage .PLN being loaded with no name. I think now you need to do some serious logging. First, set the Simconnect.INI file to ake a SimConnect log file. You'll find instructions for that in the FAQ subforum (see FSX HELP: Logging SimConnect). Then run FSX. Before you get to cruise or whatever it is which appears to cause the problem, go into fSUIPC options and check the "IPC Writes" optin. Nothing else, just that. Okay out. Carry on till you are sure its stopped. ZIP up the SimConnect log file and the FSUIPC4.LOG file (do NOT paste them here, they'll be huge), and send as an email attachment to petedowson AT btconnect DOT com. (Convert that to an email address first of course). Are you dealing with Eaglesoft support on this as well, BTW, for the Citation? I may need them to work on this. Regards Pete -
Cant Get FSUIPC Registered
Pete Dowson replied to Harpee's topic in FSUIPC Support Pete Dowson Modules
You need to state the version number of FSUIPC., and I need to see the Install log and the FSUIPC log, both of which are found in the FS Modules folder. It sounds like you've not followed the instructions properly and run the Installer "as administrator. But paste those two files into a message here and I'll check. You've seriously contradicted yourself there. The FSX.EXE must be in C:\FSX is that's where you installed it. The Application Data place is where FSX puts its CFG files and other stuff, data which can be changed -- it isn't allowed to change things in its own folders by strict Microsoft rules. If there's nothing in your C:\Documents and Settings\Desktop\Application Data\Microsoft\FSX folder you've got something serioisly wrong. If you've ever run FSX it would have generated several files there, including all of the FSX setting in FSX.CFG, and the DLL.XML file without which FSUIPC4 would never even get loaded. Why did you try running some registry fix program anyway? Regards Pete -
Aerosoft EFIS, MCP and EICAS
Pete Dowson replied to cavaricooper's topic in FSUIPC Support Pete Dowson Modules
There are four main documents, not counting the Histories. The User Guides for FSUIPC3 and FSUIPC4, and the Advanced User guides for both too. I did a search on "Aerosoft" in the FSUIPC4 user guide and found some very very ol stuff in there on virtual button programming which uses the Aerosoft MCP facilities as an example. That was done many years ago. The virtual buttons are used a great deal these days for all sorts of things and have direct support in the Lua library too, but i've got no recollection at all about any of the old Aerosoft stuff and don't know of anyone using those facilities in that way. You'd need the original documentation from Aerosoft for that, I guess. Sorry, I don't know LINDA at all. Best ask in their Forum. Regards Pete -
FSX Metar content
Pete Dowson replied to verredoavec1paille's topic in FSUIPC Support Pete Dowson Modules
Have you got it now? Else I can help -- I'd have to look up see jhow i decoded it in FSUIPC. Regards Pete -
FSX Metar content
Pete Dowson replied to verredoavec1paille's topic in FSUIPC Support Pete Dowson Modules
The format is an "extended" one devised by Microsoft and documented in the SimConnect SDK. That's what you need to refer to in order to fully decode it. Annoyingly the Write format isn't identical to the Read format, either. I think two different people wrote the two parts of the code! Regards Pete -
I've no idea wehy you keep doing that. I advised you not to last time! Only "helps"? Or fixes it? If it fixes it then your reverer axes are jittering and sending values when they shouldn't. you need to park them where they cannot interfere, at one end of the travel, in an area calibrated RELIABLY as 'dead' zone. Well, it is certainly the FSUIPC log file, but you've not enabled Axis logging as I suggested so that we could see what was happening. Therefore it is of no interest at all. Regards Pete
-
Just looked at FS9, and the keys are the same. Where's the challenge? Save the file, assign the key. Job done. I think FS remembers the playback length from last time you used it, so just preset it to what you want. The only use of editing the numbers via Lua would be if you wanted a different button for different lengths. Pete
-
Sorry, there's no need. I understand exactly what the question is. And I can indeed help you with the solution But whilst I have someone who is "new to FSUIPC" and who is so severely misunderstanding my documentation, I would like to understand how the misunderstanding arose so I can improve the documentation. I see now that you are unwilling to do this by reading my analysis and answering questions. I assume you just want the answer on a plate without having to understand it at all? I am not so keen on that because it means you and others don't learn anything and makes me have to do it over again, for everything. Far better, don't you see, for me to understand what needs changing in the documentation?That would benefit everyone and allow me to get on with life. One way to do that is to find out how to explain it all to you, as a 'beginner' as you say. Unfortunately so far, despite the fact that I've been spending a lot of time trying to break it down for you, you seem to want to ignore it all. So it is getting frustrating. I've been wasting my time? The answer, assuming each click on the rotary sends "press" and "release" alternately: 1=P1,0,K119,10 2=CP(F+15,0)1,0,K119,10 3=U1,0,K119,10 4=CP(F+15,0)U1,0,K119,10 5=P1,1,K114,10 6=CP(F+15,0)P1,1,K114,10 7=U1,1,K114,10 8=CP(F+15,0)U1,1,K114,10 9=P1,5,C1005,3840 The answer assuming each click sends both "press" and "release": 1=P1,0,K119,10 2=CP(F+15,0)1,0,K119,10 3=P1,1,K114,10 4=CP(F+15,0)P1,1,K114,10 5=P1,5,C1005,3840 Now please don't come back with more questions unless you are bt then willing to answer mine too. Please consider Forum use as a two-way process. Deal? Regards Pete
-
No, mouse macros are macros generated to directly activate buttons or switches on an aircraft panel which normally need a mouse click to operate. They only work when the panel or gauge is written in a special way, and they have nothing to do with any other FS functions. I'm afraid there are no control functions to do what you want apart from those involving visiting the menu entries. You could, however, use a Lua plug-in to operate that menu for you pretty smoothly. Try this (this is for FSX. Not sure if the key presses needed are the same in FS9 -- you'd need to check): ipc.keypressplus(79,16,4) --Send ALT+O for Options menu, focus to FS ipc.keypressplus(82,8) -- Send R to select the Replay dialogue ipc.keypressplus(13,8,8) -- Send Enter to confirm and exit back to FS, returning focus [/CODE] Save this to your FS Modules folder as, say, Playback.lua, then load up FS, go to FSUIPC's button assignments and assign your push switch to "lua playback". You could easily extend the above to preset the numbers in the dialogue. Just more keypresses before that last one sending Enter. You'd need to send the numbers, and Tabs between each field and to get the focus back to the OK button for the Enter to work. KeyPress codes are listed in the Advanced User's guide, around page 23 or so (I'm looking at an older one). Regards Pete
-
Flaps on Saitek Quadrant
Pete Dowson replied to philldant's topic in FSUIPC Support Pete Dowson Modules
Yes, REV, when needed, always should be done BEFORE calibration, else all the settings need re-doing. FSUIPC's calibrations facility started out only calibrating axes already assigned in FS. In fact the recommendation was to assign in FS, get them worrking as best as you can, before THEN going into FSUIPC and doing it a little more precisely. That way it is FS which does the REVersing when needed -- in fact it also has a "reverse" checkbox or similar. The facilities to assign axes in FSUIPC instead came about much later, really to suit those needing different devices for different aircraft types, but also to allow some additional axes to be made assignable (like reversers and steering tillers). FSUIPC's calibration still works with both ways of assigning. Then there's the hardware differences. It didn't use to be quite so predictable which axes needed reversing, and sometimes it's a matter of taste -- but generally these do, for different reasons: 1. Toe brakes on rudder pedals: for some reason manufacturers insist on having the max value sent with the brakes off, and the minimum when fully depressed. 2. Spoiler / speed brakes -- because "off" is fully forward, the opposite of Throttles 3. Flaps, because fully up is full forward. With any axis is is best to check first. If the numbers are increasing is a counter intuitive way when just watching the input on the Calibration screen, REVerse. Regards Pete -
I assume you are really trying to say that you simply want two keypresses for fast, but only one for slow? But the above gives two for a "Press" ("down" or "On"), P, and one for "Release" ("Up" or "Off") U. I don't know how your rotary works, but most give alternate presses and releases as you turn them. So how would that work with the above? You'd get alternately two clicks then one click wouldn't you? If not when do the press and release signals occur? You've got me very worried now! :-( How did you derive the above from anything I wrote? In the first place they obviously have no effect whatsoever on the lines which actually send the keypresses, the ones beforehand, because you've put no conditions whatsoever on those keypressing lines. They are completely unconditional, so they'll just operate regardless of anything else. Isn't that obvious? If not, please tell me why not. Because somehow otherwise I'm failing to explain even the very basics. I'd really like to understand how i am failing so badly. Onto the lines with the conditions. Let's just pull apart one of those lines to see what it means: 7=CP(F+1,5)(+1,1)1,0,C1005,256 CP says "this will be Confitional on a Press of a button" Conditions are those parts in () parentheses: (F+1,5) says "only obey this line if the Flag associated with button 1,5 is set" (+1,1) says "only obey this line is button 1,1 is currently pressed" 1,0 is the button which when pressed actually makes FSUIPC look at this line: it is the activating or active button C1005,256 says "when all these things are true, toggle the Flag associated with button 1,0" because 256 = (1 x 256) + 0 So, working backwards, those four lines are only looked at when button 1,0 is "pressed" -- this is, I think one of the rotary directions, right? Even if it is pressed, the line is only excecuted if button 1,1 is also "pressd" -- isn't that the other direction? Both pressed together? Even if both those were true, the line is only executed is the Flag for Button 1,5 is set. Since button 1,5 isn't even assigned to anything, that will never be true. Even if all those things were true, all the line does is toggle the Flag for Button 1,0, which isn't even used in the first place. Please please, tell me how you arrived at this from anything i wrote. If you can get so muddled from what i wrote it seriously needs re-writing. It has stood unchanged now for over 10 years, but maybe everyone else gives up? Please help me. Regards Pete
-
3.99 is not the newest one. Please install 3.999. If you still get problems I need to see both the Install log and the FSUIPC log, both from the FS modules folder. You can paste the contents here. Also provide more information on what this "CTD" is. If there's no error details on screen, look in the Windows error log. But you just said that both old ones, 3.98 and 3.99 (both very old now) crashed on you. FSUIPC's settings are saved in your INI file which is not touched by installation or re-installation. Without logs and information I really can't help. Please update to the currently supported version and supply logs and error data. Regards Pete
-
No, there's no change in keys. Your FSUIPC4 key lasts forever, and would an FSUIPC3 key, but only for those separate products. So make sure you are using the right one. The name and email you enter must also be exactly correctly, exactly as you originally used, not any new email address or change in name spelling. Regards Pete