Pete Dowson

Well, that's part of a normal FSUIPC log showing it running well and NOT crashing FSX, at least yesterday from 19:15 to 22:30 hours your system time. That's over three hours running with no problems. If FSUIPC is running okay and FSX is not crashing, then you don't have an FSUIPC problem. If something changed since last night, perhaps you can remember what you changed after 22:30 hours? Why did you remove the top few lines which at least confirm the version? Please don't do that next time. Anyway, if you want help with the problem you originally reported, assuming it still happens, I'd need to see the Install log, which you can recognise because it includes the word "Install" in the name! But maybe you can also provide a history of the changes you've made since 22:30 last night? I'm sure that could identify the culprit more quickly. And have you tried reinstalling FSUIPC as I suggested? Regards Pete

First, I need to know the FSUIPC version number. I always need that. If it isn't at least 4.60 please update. There's also a later version still in the Updates Announcement here. This sort of error is rare, but it is invariably caused by a known bug in the Trust checking mechanism in FSX's SimConnect module. The crash actually occurs before FSUIPC is even loaded. Have you added anything else recently? If so it may just be down to the ordering of DLL's being loaded by SimConnect, in which can merely re-installing FSUIPC might fix it. If installing 4.60 doesn't help, show me the FSUIPC installer log (from the FSX Modules folder), and we'll go from there. Regards Pete

Yes, when you have more than one assignment to a button, you cannot edit it in the options -- it would get too confusing and error prone since that dialogue can only handle one assignment and I didn't want to make it more complex for the 99.9% of uses and users. Could you enable Button logging and try using the button. that should tell us what is happening. I'm not able to try it here at present -- at least not till tomorrow. [LATER] Ok, it is "tomorrow" now, and I've tried it, at least in FS9. The default 737 uses parameters 1, 14 and 15 for that control, and using those values instead of your 0, 5, 6, 7 works fine. I think the parameter values come from this list: 0=None, 1=All, 2=Left, 3=Right, 4=LeftAux, 5=RightAux, 6=Centre, 7=Centre2, 8=Centre3, 9=External1, 10=External2, 11=Right Tip, 12=Left Tip, 14=Crossfeed LtoR, 15=Crossfeed RtoL so your selection should choose Off, Right Aux, Centre and Centre2, in turn. I have to ask, does that A2A P47 really have such an odd collection of fuel tanks? I think, possibly, that this is where you have things wrong? Or maybe the designers have simply re-used these Microsoft allocations differently? Either way, there's nothing else wrong with the parameters. Regards Pete

Yes. It involves editing the INI file. First, in FSUIPC, assign the button to "Offset byte cyclic increment". Set the offset field to x66C0 (a user offset, freely usable -- there's a range of them, from 66C0 to 66FF), and the parameter field to 1/n where n is the number of choices you want, less one. For instance a 4-way choice would be 1/3. This command simply changes that offset by 1 every time you press it., cycling back to 0 after it reaches the maximum, 3 in this example. Now OK out of FSUIPC options and load up the INI file in a normal text editor (e.g. Notepad -- not Wordpad). Find the line in the [buttons] section defining the action you just set (search for that '66C0' part). The line will be in the form n=Pjoy,btn,Cx510066C0,x00030001 Now you have to add a line for each action, in the form: m=B66C0=x Pjoy,btn,Ccontrol,0 m is incremented, it is a line number. x goes from 0 to 3, 4 lines for 4 choices "control" is the control number for the action you want -- look this up in the List of FS controls document installed by FSUIPC. For more explanation please see the Advanced User's guide. Regards Pete

Yes it is certainly possible. Simply find the Network Properties for your local area connection, On the General tab you'll see a list of items. Scroll down and find the "Internet Protocol (TCP/IP)" entry. Select it, then click Properties. Change the "Obtain an IP address automatically" to "Use the following IP address". Enter your fixed IP address. The mask will be 255 255 255 0. Enter the IP address of your router (which will be fixed -- it's the one you use to set it up etc, presumably 192.168.0.1 as that isn't in your range) as "default gateway" and also as "preferred DNS server". You don't need an alternate one. The router will still also provide a DHCP service so any visiting notebook PCs and so on can be connected without a specific IP address, and the router will avoid assigning them any IP addresses already specifically in use. Regards Pete

Show me, please. You provide nothing for me to see. If the path shown for "EXE Path" in the Install log is still showing wrong, then the Registry is still wrong. FSUIPC's Installer doesn't invent paths, it simply reads them from the Registry. Not a good idea. But with FS9 it isn't a big job to fix it. You just need to get the Registry corrected. In all cases I've seen, the fixer program does that okay. However, if there was NO registry entry for EXE Path, then FSUIPC's Installer would ask you to point to FS9.EXE, and it would correct the Registry for you too. Your problem appears to be that you do have a Registry entry, and it is wrong. Can you use the registry editor, Regedit? If so, please check the entry (I gave details before), and correct it manually. Regards Pete

Well, that's not really using FSUIPC to advantage, but it is something to do with the VRInsight driver (SerialFP2) sending FS keystrokes for some things -- that usually depends on the aircraft loaded and so on. If that's all you want to use, that's fine. but you cannot easily program keystrokes to produce other keystrokes. The problem is that they all go through Windows message queues looking the same, so, for example, a "Shift + X" programmed to sent a "Ctrl + F5" could end up looking like "Ctrl+Shift+X+F5", depending on the timing and gap between KEYDOWN and KEYUP messages. FSUIPC contains many facilities and one of those is the ability to read joystick buttons, switches and knobs. Many years back that was extended to explicitly support EPIC controllers, then, also a few years back, GoFlight modules and PFC serially-connected devices, and then, just this year, VRInsight devices. Unfortunately, because VRInsight devices use a serial port and have a lot of complex interactions to maintain the displays, it gets more complex for those than for the others I mentioned. Although a VRI device CAN be controlled completely by FSUIPC, it requires some plug-in programming, using Lua, to program the displays. That's obviously not for everyone, so another method had to be devised. Without special low-level driver/monitor type software, serial ports cannot be shared between different programs. So the solution arrived at to allow VRI buttons to be programmed in FSUIPC whilst still allowing SerialFP2 to handle the displays was to employ an existing low-level driver to intercept the serial port on FSUIPC's behalf. The recommended one is VSPE, as you've now read. Whether you want to use VSPE and thereby extend FSUIPC's capabilities for your MCP Combi is up to you. It really depends on how ambitious you are in using it for assorted FS add-ons. But it isn't too hard, I hope. AndyDigital over in the VRI Forum can help for sure. He was the one who got me supporting VRI devices in the first place! ;-) Regards Pete

It is usually either a poorly written Installer, which assumes no one else in the world uses the DLL.XML file and so just obliterates the rest, or a product supplied with a ready-made DLL.XML file which you are supposed to use to help edit one you have already, on the false assumption that everyone is competent to do that. As Andy says, if you show us the file we can tell you how to fix it. If you cannot find a way to attach it, you can load it into an ordinary text editor, like Notepad (not Wordpad), then cut and paste it all into a message here. Regards Pete

Don't change the Port number. And you don't need both ServerName and IPAddress -- one translates into the other. It is still best simply to put you computers into the same workgroup, then everything is automatic. Otherwise only two entries are needed -- ServerName OR ServerIPAddr, and Protocol. Please do NOT mess with anything else! If you've added all sorts of changes I suggest you delete the INI file and start again! Yes, as I said, the default workgroup names are different. Windows doesn't allow Broadcasts to PCs in different workgroups, so that prevents WideServer telling WideClient where it is.

Sorry, I've no idea now -- last time it was compiled was many years ago. I only know it was a Microsoft compiler. However, you will see that I supply the source for the library, so you can simply either recompile it yourself or actually build the code into your application, your choice. Regards Pete

Well it appears you failed to point the registry repairer to the correct place for FS9, because it set the parameter thus: EXE Path="F:\Program Files" which is evidently NOT where FS9.EXE is. It looks like you only pointed the repairer to the directory in which the FS directory was. Try again, or edit the Registry manually to correct the parameter "EXE Path" in the Key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft Games\Flight Simulator\9.0. Regards Pete

Well that address, the one which Windows says matches the name you gave, appears to belong to advancedsearch.virginmedia.com, as I found by using an IP search on-line. Here are the details: I don't know if you are on Virgin Media, but it sort of looks like it. I've always found it best to use fixed IP addresses for all my PCs. I have many, and they all get IP addresses assigned by me. It is also more efficient as it stops each and every PC doing a search request every second or so. That used to be one of the causes of stutters in FS -- I've always recommended using fixed IP addresses on local networks. I think it's usually something to do with security masking on routers, but it could be elsewhere I suppose. It's happened a few times over the years. Folks do sort it out, I think, but no one ever seems to come back and explain what did it now how to fix it. Maybe they all use fixed IP addresses as I recommend. Regards Pete

Sorry, I really don't have anything to do with the sales end. SimMarket do all of that. Have you been to your account there to see if the Registration Key has already been posted? I don't think they send anything back by post. Did you supply an email address? Normally, for all purchases on SimMarket you go back later to retrieve your Key. Nothing else happens as far as I know. I've bought quite a lot of stuff over the years and it's always been like that to my knowledge. If there's nothing, maybe it simply takes a lot longer my snail mail, depending where you posted it. I don't know how you can check except to raise a Problem Ticket on the SimMarket website. Have you done that? I really can't even check anything for you as you hid behind a pseudonym here instead of using your real one. BTW do you realise you are adding to a thread which is on a completely different subject? You really should have started your own! Regards Pete

There's only one button marked "mode" and it is inoperative until one of the radio selector buttons is pressed. Once it is operating it sends a different code depending on which radio is selected. All 5 possible values it sends are detected in FSUIPC (when configured correctly) and are therefore individually programmable. So the answeer is "yes". However, this was a recent addition, after 3.98 and 4.60 was released. In those versions the radio section was not programmable. I added it later, in versions available in the Updates Announcement here, as described in the details there, thus: It is always worth looking through the Announcements from time to time as they do tell you these things. You mean the Radio section's Mode button, I think. That's the only one on the MCP Combi. The "Key Presses" Tab in FSUIPC is for detecting key presses, not Buttons. To detect buttons and switches you need to select the Buttons and Switches tab. That is why they are named that way. ;-) If you don't see any of the VRI buttons there, then you've not followed the instructions to enable FSUIPC to see these devices. Please check the documentation. It is all explained there. The facilities were included in the 3.98/4.60 versions and updated since, as already explained. Regards Pete

It evidently was not"incorrect terminology", but perhaps a misunderstanding of what a mouse macro is. So, you are not using FSUIPC's VRInsight button programming facilities? You are using VRInsight's "SerialFP2" to produce keypresses from the device? Okay, but that is a complex process compared to programming the buttons and switches on the VRInsight devices. I spent as lot of time adding VRInsight support. Because, as I said, it is not an FS function at all -- it is not simulated. You probably cannot use a mouse macro, unless the Ivap screen is a proper Gauge written using the C/C++ Gauge SDK. Did you try? That's the only way to find out. Far better would be to use FSUIPC's button programming facilities to assign the correct keystroke. Two questions: 1. if you are programming a mouse macro to operate a hot-spot on a gauge, why would you be pressing F5? Where does F5 come in when using a mouse? 2. F5 is, by default, assigned to "flaps up" in FS. If F5 causes FS to hang you have something seriously wrong in your installation. Are you sure this is what you really mean? You should be able to do all you want and more by using the new VRInsight facilities added in recent FSUIPC releases. You will find the topic dealt with in an Appendix in the Advanced User's guide. It is listed in the contents. Regards Pete

I know. You are repeating yourself. :? I think one of those two times you edited the file made a mistake deleting -- or you deleted whilst FS was still running, which could possibly cause problems too. There again you appear to be quoting that incorrectly, which led me completely astray in the first place. In the file it is not [Profile.]1= but [Profile.] 1= precisely as if it would otherwise have been [Profile.Concorde] 1=Concorde before you deleted the Concorde parts. Not with my explanation, no, not really. If you really still think there's a bug and you can reproduce it, please give exact steps -- keystroke by keystroke -- and without things like presenting "[Profile.]1=" when the "1=" is a new line. If it is possible to derive such a strange result without user error I'll need to reproduce it to fix it. Regards Pete

And here's the clue: Your two PCs are probably in separate workgroups. Please please please do read at least a little bit of the documentation, especially when nothing works. "If all else fails read the manual", remember? The part you need to read is entitled "Configure your network", and immediately follows the Installation section. There's even a big red note there pleading with you to at least read a bit of it! Yes, and WideClient would also automatically connect if it knew where the server was. XP and Win7 use different default workgroups. Broadcasts don't work across different workgroups. As the User Guide says, you either have to put them in the same group, or edit the INI file to tell the Client about the Server. You'd have been off the ground much quicker if you'd spent just a couple of minutes browsing the User guide, espcially the highlighted section. Pete

If there is it'll be in the documentation for the IVAP software, probably some keypress or one you can choose. Then you'd assign it to a button or switch in FSUIPC. There's no built-in facility because FS itself doesn't simulate it and each on-line program does it differently. With Squawkbox 3 there was an offset in FSUIPC which would control it. In Squawkbox 4 there's nothing, which is the one reason why I, as an FSX user, don't fly on-line. Unfortunately the Squawkbox developers seem to have given up development because I've been asking for this to be corrected for two years now, to no avail. :-( A mouse macro? Why on Earth do you need to use a mouse macro? Why not just assign the Key combination, Ctrl+F5, in the FSUIPC Keys tab? What is the mouse macro doing? When would you hit the F5 key in a mouse macro? I think you must have your FSUIPC terminology mixed up? And just pressing F5 actually HANGS FS? Phew. It can't be FS itself, better report that to the IVAP folks. Regards Pete

Okay. In fact the line wasn't as you quoted, the one I couldn't unsderstand. The wrong lines are: [Axes.] [Profile.] 1= To me it looks exactly as if you deleted just the "Concorde" name before you retried, instead of the complete section, thus leaving those partial lines. I cannot think of any other possible explanation! The reason it was okay in the Calibration tab (and would have been in the Keys and Buttons tabs) is that you only had Axes defined before. Anyway, in the next release I shall ignore or even delete such entries, even though I don't think they'll ever happen naturally. Regards Pete

The log and the INI file you show here have no sign of any odd Profile behaviour, so did all that disappear? You said so I was really looking for this odd line. Could it be that somehow that file became corrupted before the problem occurred? Obviously something more than the Profile name is missing as there should never be that "1=" immediately after the "]", and a null name may well match any aircraft. I can improve the code to detect the omission of the name and delete or ignore that line, and I will do so, but first I'd like to find out how it arose. If you think you could reproduce it, please do, after making a safe copy of your INI. Please write down step-by-step how to do it so I can try here. If I can reproduce it I can fix it. The entry in your current INI, as shown here, looks fine: [Profile.Concorde] 1=Concorde (Capt) BAUF OAF Regards Pete

No. What version of FSUIPC? If earlier than 3.98 or 4.60, please update first. Then can you show me an FSUIPC4 log, please, with that plant being loaded/used, and also your INI file. You can paste them into a message here. Just select them after pasting and use the "code" button to encapsulate them for scrolling and selection. Regards Pete

As far as I know, that offset hasn't been useful since FS2000 or FS98. The flight plan contains the Latitude and Longitude, doesn't it? All you need to do is check that the aircraft is on the ground, and that its position is within reasonable distance (2 or 3 nm maybe?) of the airport.Lat/Lon. If the flight plan was loaded in FS then you might get more information from the offsets for the GPS, 6080 onwards. But I'm not really sure about many of those. Regards Pete

That's a bit out of date, and not supported. 4.60 is current, with a later update in the Updates Announcenemt in this forum. Strange. After updating to 4.60 or later, can you show me an FSUIPC4 log, please, with the Concorde being loaded/used, and your INI file. You can paste them into a message here. Just select them after pasting and use the "code" button to encapsulate them for scrolling and selection. Regards Pete

Okay, so it's your hand you take off, not your foot! ;-) Similarly, give a little twist one way, press centre "SET", a little twist the other way, press centre "SET". You need to give it a range of values which will encompass all those you might see when taking your hand off and letting it centralise itslef. Pete

Yes, Unicode is a wide character coding format, 16 bits per character, with zero in the high 8 bits for normal ASCII-compatible characters. FS uses straight 8-bit ISO-extended ASCII internally. Regards Pete