Pete Dowson

Ah, yes. Sorry. I hadn't noticed that. Though, even if that were wrong, your DLL would still be loaded. It would simply have been terminated again quite quickly (i.e. without the init function being called). Since up until FSX I made DLLs work for all versions of FS since FS98, and even including CFS1 and CFS2, I had to set that parameter dynamically, in the DLLmain function, after working out which version of FS had loaded me. Regards Pete

Did you export the ImportTable and Linkage names, as in extern __declspec(dllexport) IMPORTTABLE ImportTable; extern __declspec(dllexport) LINKAGE Linkage; If you don't, FS won't think it's a suitable DLL. Regards Pete

Sounds like either he has tried to register it with bad (pirated) keys -- just delete the FSUIPC.KEY file to fix that. Or possibly it's a signature problem -- all my software is now signed, and if it is corrupted or there's a problem with the signing authority, this will be a symptom. He can right-click on the DLL and check the signature. Most likely he's using winXP before SP2 or any older version of Windows and needs the GlobalSign signature fix applying -- tell him to look at the documentation. In the section on Installation there's a box headed "IMPORTANT: Before updating ...". It tells him about this and what to do. Regards Pete

I don't see why VS2005 isn't usable -- I use it. But sorry, I've no idea about anything to do with C#. Pete

It isn't mandatory, but a good idea if they want better performance, fewer bugs, and any support. No. My game is compatibility. That's what started all this stuff off in the first place. I suppose he's using ages old versions of Project Magenta modules too! :-( Pete

Sorry. Just replace 3.65 with 3.74. I cannot and will not support old versions. Yes, terrible things like bugs being fixed, things working better, support available! ALWAYS use the latest versions! Yes. Tell your user to put his hand in his pocket and pay for an FSUIPC user registration. ;-) Pete

I assume so. Sorry, I'm not really knowledgeable about scenery. But the point of the scenery variable offsets was to allow values to be passed to or from scenery logic. Incidentally, there are no such facilities in FSX at present. I don't know if the scenery variables will be accessible at all in FSX. Regards Pete

Fog is just low visibility. Where you draw the line between fog and mist and mist and haze I don't know. It may be defined for METAR purposes somewhere. Check offset 0F8C, for example. Pete

ECAM = Electronic Centralised Aircraft Monitor, which is more or less equivalent to the EICAS display units for Boeing, I think. The switching of display modes for these in both Boeing and Airbus will be local to the gauge implementations itself. It isn't an inbuilt FS function I'm afraid, so FSUIPC wouldn't know anything about it. For add-on cockpits it is most likely that such functionality is provided in the panel code written by the aircraft maker. He has probably provided mouseclick capabilities for the switching, less likely to have provided keyboard shortcuts, and actually most unlikely to have used any FSUIPC offsets for it. But you'll need to consult the documentation to determine which. For mouse-only programming you might be able to program things using Key2Mouse, a program from Luciano Napolitano, then program the keys via FSUIPC. For keyboard shortcuts you can program those through FSUIPC. For FSUIPC offsets, there are two cases. First they may either be published already, or at least freely available. Second they may be kept secret by the aircraft maker, in order to control the connectivity to his product. So, I suggest a thorough search of the documentation, and if that doesn't help, an inquiry to the author/publisher. I wouldn't help actually stating the name of the product here and in the cockpit-builders forum, as someone may already have dealt with this issue. Regards Pete

What things are specific to Airbus and built into FS? Mostly it's jyst differences in terminology. You tell me what you are looking for. Only if you know what you are looking for. I don't know of anything important missing. You tell me. If the aircraft panel has additional things which are not part of FS but added by the author, then in all likelihood they are only acccessible via whatever means the author has provided -- maybe even only mouse clicks. Why do you think there may be FSUIPC offsets for anything he's added? Does the aircraft even use FSUIPC? Regards Pete

Yes, if you are using FSUIPC offsets for that, or assignments via Buttons/Keys, it will be because the engine starter uses some of the Sim Events, none of which will work for reasons I stated. If you check the FSUIPC4 Offsets Status document, in the 'FSX Write' column you will see "Ok-SimE/Intl". As I said, anything marked SimE for writing won't work because none of the Event names are located. This was fixed since the first SP1 Beta version I provided to FSX Beta testers, via the Beta Newsgroups. This is not what I would call "instability", which is what you said you experienced with 4.09. It is just that many things won't work. I need to know exactly what is "unstable" please. Regards Pete

Not stable? In what way? The only thing which is wrong is that none of the FSX controls (SimEvents) will work -- the table listing them in CONTROLS.DLL moved in Beta2. This affects all button and axis assignments, and calibrations, which simply do not work, and those FSUIPC offsets which are marked as "SimE" in the list for Writing. There's no cause for instability I know of. Please explain what you are finding, and provide some details! :-( As everyone in the Beta test group must surely know, it is a bit too late for Beta3 -- Beta4 came out last night. I invited all Beta testers needing FSUIPC4 updates to contact me by Email. I did Betas for 1, 2, 3 but it is 4 now. Don't you participate in the Groups? Email me. petedowson@btconnect.com. Pete

Good! Thanks for letting me know. Pete

Okay. I've just re-checked this on my Vista PC. It looks like Microsoft have done a stupid thing here. The default installed program "WordPad", which was always fine viewing Word documents in previous versions, is now unable to correctly view Word documents in Vista! In fact it won't even view their latest format "Docx" produced by Word 2007! It looks like they are forcing the change to Adobe's PDF format. I find that quite astounding, that they would reduce support for their own formats and force folks to use an alien one. I can only assume they've now accepted that Adobe have won that "battle" for portable documents! In the next update for FSUIPC4 (4.10) I will only include Acrobat PDF documents, no Microsoft format ones, to get around this. You will need to update to 4.10 in any case after you apply the much-anticipated SP1 update to FSX. Meanwhile, luckily, as you found, I do include the PDF version of the User Guide in the ZIP file itself, so please refer to the Installation and Registration sections in that. Also the READ ME text file can be read by almost anything, including the default NotePad installed with Vista. Regards Pete

Neither sensitivity/null zone sliders nor assignments in FS are at all relevant to FSUIPC's axis assignments. If you elect to send the axis values to FS as normal FS controls it bypasses all of that. In fact you should really disable the FS joystick to be sure of no interference. I find it hard to imagine what you could be doing wrong. What EXACT controls are you actually assigning? Care to show your INI files [Axes] section so I can see? The equivalent to the FS assignments are those called "Axis .... set" in the drop down list. There is also the "direct to FSUIPC" option which uses no FS controls whatsoever. Either will work fine, but the latter would bypass some of the more advanced cockpits which may need them, especially Airbus panels providing fly-by-wire. Regards Pete

Not sure why you needed to do that. I have it enabled on my one and only Vista PC and it doesn't interfere at all. Eryou don't do any of that. You need to download the FSUIPC4.Zip file. Unzip it to anywhere of your choice then run "Install FSUIPC4.exe". There is no "FSUIPC4.EXE". What exact file was that and what did it try to open with? I supply no gibberish files at all! Please tell me what FSUIPC4 file you downloaded and where from. And what version you think you were getting! You are not making any sense I'm afraid. :-( Can't be read by what? Can you tell me what is there? They documentation files are standard Word DOCs or Adobe PDFs, and the is a simple Text "Read Me" which any editor, including the default NotePad, can read. If you mean the Add-OnsFSUIPC options, until you Register you only get the main about/registration page and the Logging taba -- as clearly documented, as as has been the case now for four years. Help to do what? Run as administrator? Just right click on the FSX icon and select "Run As Administrator", exactly as documented! Pete

It may be one of the two possible DirectInput axes which aren't available via Windows Joystick API. In FSUIPC4, for FSX, I managed to change the axis assignment system to use DirectInput, so it does see up to 8 axes and 2 POVs (Hats). but the original Joystick system only supports 6 axes and 1 POV. I'm afraid there is no way I'm able to undertake the work involved to move FSUIPC3 over to use directInput. I only managed it in FSUIPC4 because I had to do a complete re-write of FSUIPC anyway. Incidentally, there was a previous thread about this -- I just did a quick Search (using the Search facility) and came up with it quite quickly. See: http://forums.simflight.com/viewtopic.php?t=52434 The final contribution on that thread does seem to imply that it should be usable in FS assignments. Have you made sure the sensitivity is 100% (slider full right)? You also want the null zone to be zero (full left). Regards Pete

My friend Ray flies Concorde in FS9 a lot, and uses AS I think. I'll ask him when I get a chance. Regards Pete

Thanks! I guess the same settings for GSPout under FS2004 and before should work too! Regards Pete

The problem is I would need you to zero in on the part of the log showing the problem, or else give me precise locations and timings of whatever shifts it is you are seeing. I really won't have time to deal with it until after the upcoming FSX SP! update is released. That does indeed suggest it is a problem of Global vs Local weather settings. Even if we narrowed down the cause, I'm not sure I'd be able to do a lot about it. We are now well into the 4th year of FS9 and this is the first time anyone has mentioned such a problem, so it can't have been very common or important. Let me know what you find out from AS. Regards Pete

I suspect it is more related to pressure settings at different WX stations, possibly not (yet) explicitly set by ASV6, or set by AS but from METAR reports differening in time or with errors. FSUIPC attempts to smooth the settings being sent through from the external program only, it cannot affect those inside FS's own local weather. It does operate on FS's global weather, but that it pretty much redundant in FS9 unless you are in the middle of nowhere. Thinking further, I thought AS had its own smoothing. Doesn't it override FSUIPC settings? Can you check its options please? If you want me to check what is actually happening inside FS, it will need a lot of logging -- Weather logging can be enabled in FSUIPC Logging options, but I can tell you how to add more if necessary. There will be a lot of data to wade though and you will need to be very specific about what exactly you see happening, and where and when, so I can tie this into the weather being supplied by AS and the weather being read from FS. I think in the first instance you should investigate the AS option settings and possible post a query to their Support. Okay? Regards Pete

Thanks for confirming. Pete

I realise that as a virus scanner it is not deliberately blocking TCP/IP communications. But as a virus scanner it is hooking into the TCP/IP stacks in Windows. It seems that SimConnect is very sensitive to how these hooks are placed, or maybe what they do exactly. No, no. From the logs that were supplied it looked like the main problem was SimConnect being blocked, which affected the TCP/IP stacks and thence WideServer, which never managed to send anything to the Client. FSCommander would have been an innocent bystander. It wouldn't have been anywhere near any of that. There must have been something about the way it was set up on dickneuf's system, then, because it seems it definitely clobbered both SimConnect and WideServer (from the logs he supplied by email). I couldn't diagnose what was causing it, but he solved it via NOD32, whether by disabling it or changing some settings I don't know. Regards Pete

Ah, yes. The PM software does has extra options -- they aren't per the aircraft though, I think you'll find. The "callsign" mode is something Enrico added just because the information was there. At least I think that's so -- I have real Boeing 737 and 747 manuals and there's no mode showing any type of ID. Regards Pete

I think he is saying that he cannot set the flight number using the AI creation interface in SimConnect. This is correct when creating non-ATC AI traffic. For traffic with flight plans the Flight Number is actually specified -- in fact as far as I can see it is used to select the plan. I agree with him that there isn't any way around this, unless he decides to use flight plans which, if it can be made to work, is a big job indeed. If you recall, I asked you this question. I don't know what sort of TCAS you are using, but those in Boeing aircraft don't carry any sort of identification. only position, altitude difference (in 100's ft) and an ascending/descending arrow if applicable. I will blank out the false Flight Number which SimConnect supplies from the CFG file. Regards Pete