Pete Dowson

So whatever crashed FS in the first place is consistent and crashes it again. You'd need to go to an earlier saved flight and avoid whatever it is wrong with your scenery or other addons. So, there's something wrong with them? No, there is no problem. All Autosave does is make the call to FS's flight Save function, the very same function as you can instigate by pressing ";" or going into the menu,. There is no difference. There is nothing in the AutoSave function itself which is saving anything at all, it is just standard FS. Therefore there is nothing to go wrong with AutoSave. If the files FS makes cause FS to crash again then it would be the same if you saved the flight yourself and reloaded it. You need to fix the cause of the problem, not the saved flights which on reload are merely restoring the conditions in which you crash again. If it is only those two aircraft which give you problems thenn either they are corrupt or a buggy. Try reinstalling, or go to their respective support forums to see if there are already solutions or updates. Regards Pete

Everything FSUIPC can do it does, everything the PMDG 737NGX can do it does. I've no way of answering such a question in any other way. If you have specific questions about FSUIPC4 which are not answered in the documentation I can answer them here. For PMDG questions you will be better off in the PMDG forum unless others can jump in here, because I don't use any PMDG aircraft, and none of my hardware is standard (a PFC 737NG cockpit using Project Magenta). Regards Pete

4.80 is superseded. There's also a later WideClient. See the Download Links subforum. And? Sorry, I'm confused. The "ShutDownHotkey" sends a shutdown notification. What's that got to do with starting apps? No. why? There's a delay in the starting up of WideServer in the Server end, which is there deliberately to ensure everything is correct. Then there's an initial delay when Wideclient connects for it to get al the base information established. The latter may be shorter if you use UDP protocol and the BroadcastOnly method (using more up to date versions than yours), but that is probably only true when there are several clients -- it allows them al to get up to date at the same time using the same frames. I have 8 clients and it is much more efficient that way. But on a single client it probably wouldn't make any difference. What is the problem you want to solve? 30 seconds at the start of each day? I don't understand. I don't know why you supplied the INI file if you've not changed it? Logs would be more appropriate if you thought there was a problem, and it is easer really to simply paste them into your messages. Regards Pete

Temperatures are SIGNED values -- they have to be, of course! 65353 is the unsigned interpretation of -183 (i.e. -0.715 degrees).. You must always treat numbers in the correct way or you will be bound to get wrong answers! In a 16-bit word, signed values go from -32768 to +32767, unsigned from 0 to 65535. There is no such value as 65353 in a 16-bit signed word. Pete

Sorry, what exactly do you mean by this? What are you seeing? What says "FSX isd unable to connect to FSUIPC"? Isn't there an FSUIPC4 log file? If so please show that. If not, then FSUIPC4 never actually got loaded and what you are seeing is a Simconnect 'trust' bug. Please, for this, see the FAQ subforum, the thread entitled "FSX fails to run after FSUIPC4 first installed". BTW the Install log you showed does not terminate correctly. Have you abbreviated it? You said it says things are OK, but that message should also show in the log, but it does not. Regards Pete

Well, I don't know about that, but please just use the logging facilities to check? I can't really help without information. Surely you can understand that? I certainly haven't changed anything in this area in any recent updates, that's all i can say. Maybe some new bug has crept in somehow? Please just check what is going on and let me know. There are surely enough tools you can use to check this? If you don't know how to use the Logging or FSInterrogate, let me know. Regards Pete

No, there is absolutely no problem having both on the same PC, even on the same drive. They do not interfere with each other in any way whatsoever. The problem I *think* you ar decribing (though I can't be sure without the answers to my earlier questions) is a well-known one which occurs with Saitek devices and is easily fixed by a registry change. I don't have the details to hand. Please search or check the Saitek forum. Pete

Sound? The offsets mentioned have not changed. Use logging to check. Pete

Sorry, please clarify. What do you mean by "axis number"? Axes are actually lettered -- X, Y, Z, R, U, V for instance. Do you mean the value being seen? And by "one position" do you mean the number didn't change? If so, that appears to clash with your next line: Do you mean there are no values between? If so then I think you are suffering from a bug in the way the Saitek installs, one which is fixed by a Registry change. It isn't anything to do with FSUIPC itself, and has been reported and fixed many times. Either do a search here or, better, refer to Saitek's support forum. Regards Pete

Looks like a bug. The value '0' is actually being used as a flag to say there's no limit set -- i.e. same as omitting it. I'll need to figure a way around this. Sorry. Look out for an update over the next few days. Probably Monday. Regards Pete

Okay. The latest version (4.828) now has an "OOMcheck=Yes" entry in the INI, so you can turn it off if you like by changing that to 'No'. Pete

Two things there. FSUIPC is not crashing, nor is it causing FSX to crash. FSUIPC is closing BEFORE FSX is crashing -- this part: is only ever output on a normal close. Yes, because FSX is closing normally, no crash at all. WHY it is doing this is another matter, but I find it highly suspicious that FSUIPC never actually gets connected to SimConnect: This surely indicates an FSX installation error -- or are you really trying to use the original buggy release of FSX? If so you should most certainly update with both the SP! and SP2 updates. Please check the FSUIPC4 Install log, also in the Modules folder. If there are any SimConnect problems they would show in that. Regards Pete

Where are you getting 99840 from? Try adding them again. 66932+390 = 67322 not 99840! If you can't add it yourself use a calculator. FSUIPC doesn't provide a calculator for you. Regards Pete

The FSUIPC patch to G3D patches the FSX code, in that DLL. It doesn't do anything with sceneries. It is just a crash avoidance, not a scenery fix. And it only works with one specific G3D crash -- luckily the one which appears to be most common (though I've only ever had it once). So, no, if FSUIPC is installed, that's it. Any further G3D crashes you get are not the specific one which is patched. Pete

Without any other inforamtion and no one else with any such problems I cannot really help. can you tell me what the crash actually looks like -- any mesage? Any information about it in the Windows error log? Also check in the Modules folder for the FSUIPC4.LOG file which will show how far it got. The usual reason for an early crash is a corrupted weather file, (type .WX) being loaded with your default flight. One of the first things FSUIPC does in order to service requests is to read the weather data from SimConnect, and FSX is very poor at checking its files. Try moving the .WX files out of your Documents\Flight Simulator X Files folder. Otherwise I'd need need to have more information. Pete

That is the WideServer LOG as it clearly states. It is also incomplete -- close FS first. The more important file is the WideClient log file, after you've closed WideClient. The Server isn't the part not connecting, it is the Client! you say What update? Regards Pete

Much easier to use the virtual button offsets at 3340. There is room there for 288 separate buttons, all of which are recognised in FSUIPC's options dialogue for assignment. Then just assign as needed. You are finding each time the most complex methods. The virtual buttons facility is made EXACTLY for the purpose of feeding non-Joystick switches into FSUIPC in a way which, to FSUIPC, looks like any other. It is much easier and much more flexible. Try it! Regards Pete

But why go back to such an ancient version? In fact, I don't think 4.27 even supports lettered IDs for devices! The current version is 4.828, the previous version is 4.827 as I said. Pete

Facilities for individually owned and titled Windows for the ipc.display and ipc.linedisplay functions are now included in the latest updates for FSUIPC3 and FSUIPC4. The details are in the updated Lua plug-ins package -- please see the Subforums. The new entry is lua.setowndisplay, and it sets the title, position and size for a Window which is specific to the Lua plugin. The function can be used to retitle and resize/position the Window at any time too. Regards Pete

The offsets lists for FSUIPC3 and FSUIPC4 are included in the FSUIPC SDK -- see the usual main download site, or the "Useful additional programs" thread in the Download Links subforum. The Lua "ipc.readXXX" and "ipc.writeXXX" functions are described in the Lua library documents, installed already in your FSUIPC Documents subfolder. The types of values like "SD = Signed Dword" can usually be easily deduced from the offsets list -- it is either explicitly stated, or easily deduced from the size (1, 2, 4, or 8 bytes) and type of data. There's a useful note about numbers in the FAQ subforum. Regards Pete

Why are you messing about in the INI file? Use the FSUIPC options dialogue, assign to one of the Offset controls, enter the offset and the parameter. You can set a value, inc or dec (cyclically with a limit if you want), or set / cear / toggle individual bits! Whatever you need! Why do I make things easy if everyone wants to do it some complicated way? :-( Regards Pete

No, if anything performance is improved with 4.80 as several areas have been streamlined. The OOM check isn't currently optional, but i am going to make it so, so you could check with that switched off. However, all that does is read from Windows the amount of available and used process memory once every 10 seconds approx, so i don't really see how that could have such an effect. The recent versions are of course reading PMDG 737NGX data is it is enalbed in the latter's INI file It is only doing this when SimConnect notifies it of a change, of course, but when flying such changes will be frequent. I don't think this will afftect anything noticeably though, it is a single block of memory of less than 512 bytes. Logging is negligible (take a look) unless you've enabled some options. But definitely check the log in any case. One thing that can clobber performance is a SimConnect problem which causes FSUIPC to continually try to reconnect. Those events are logged. Regards Pete

FSUIPC sees all of the KeyCodes listed in the documentation, including the different codes for the numpad normally to the right of the main keyboard. I don't know of any separate numpad that doesn't simply duplicate the same pad as that on most keyboards, and there are no other keycodes listed by Windows for such. If you can't make it work, enable keys logging in FSUIPC, try the keys and show me the log. Regards Pete

Well of course it will do if the buttons numbers refer to the wrong device. How did the letter assignments get changed? The whole point of letter assignments is to keep the same assignments no matter what! You will notice in your new INI that A=Saitek Pro Flight Rudder Pedals and all your buttons are assigned to A, the pedals! Just swap the As and B's over in the [JoyNames] section. Only 4 lines to change, one character in each. I cannot support such old versions - that is years old! Current is 4.827 with interim update 4.828 due out later today. Pete

A direct line, great circle? OR what? You need the Latitude and Longitude of both places and do some complex spherical trigonometry. Google the web for the formulae. Regards Pete