Pete Dowson

I only just managed to get the released P3D v2 yesterday. The version of FSUIPC4 for P3Dv2 will be released tonight or possibly tomorrow. The first correct support for P3D v2 will be 4.923. Any earlier version will not work correctly and may cause problems and crashes. Regards Pete

You didn't explain you wanted to do that. Of course FSUIPC-connecting applications connect on the PC in which they are rtun. There's no Networking components in Radar Contact or Its Your Plane. They find the local FSUIPC interface and connect to it. I assumked that's what you wanted. Yes, because WideClient provides the same FSUIPC interface and also the needed Ntworking. That's what WideFS is for. It can't do that. FSUIPC contains WideServer, to SERVE WideClients on other PCs. The purpose of WideClient is to interface to FSUIPC on another PC. FSUIPC knows nothing of other FSUIPC's on other PCs. FSUIPC IS FSUIPC and so provides the correct FSUIPC interface to FSUIPC applications. Regards Pete

The Programmers Guide covers all up to FS9. Changes for FSX and later are in the Offsets Status document. It has always been so. Pete

They are not functions available in FS9, and therefore the offsets do not exist on FS9. They are just two of the many additions in FSX and covered accordingly in the FSUIPC4 Offsets Status document installed with FSUIPC4 and also provided in the SDK. Pete

There were three Beta releases of Prepar3D v2 made available BEFORE I went on holiday, and I made specific versions of FSUIPC for each one. Every change by Lockheed-Martin means changes to fSUIPC because it has many hooks into the internals It has always been like this. The specific releases were made to the Beta group only and announced on the private Beta forum. The only P3D v2 announcement on this Forum was that the Installer itself now worked on V2, and that is still true. Just after I left for my holiday the 4th Beta appeared, and I was going to deal with that immediately on my return (yesterday), but then within days of Beta4 the "gold" came out. It took most of yesterday to download it and install it, and I am about to do the conversion now. Please do read what I say in release details a little more carefully. Using anything before 4.923 with the released version of P3Dv2 may well cause unexpected problems because for some actions it will probably be hooking into the wrong place in the P3D code. I do put extra code in place to double check these things, but it is possible for it to cause crashes or other problems nonetheless. I know at least one thing isn't working correctly, and that is Wind Smoothing. There are probably others. Regards Pete

You must update your FSUIPC -- version 4.0 is the original release, over 6 years ago, and cannot be supported. Get up to date please. Most PM controls are provided in the drop-down list, for assignment. But update FSUIPC first. Pete

Moved from "User Contributions" subforum where it was mis-posted: There are only TWO different versions of FSUIPC -- FSUIPC3 for FS9 and earlier and FSUIPC4 for FSX and later. There are not "versions for different programs" (other than FSX v FS9) at all -- how can you possibly read that? There is absolutely no possibility of confusion as the Schiratti site only lists one for FS9 and one for FSX! The latest releases of FSUIPC3 or FSUIPC4 are always available on the Schiratti website, and also here, in Download Links subforum. Install the one appropriate to your version of FS, which I assume you know? If not then I understand your confusion. Use the Help menu in FS to see if it is FS9 (aka FS2004) or FSX! Pete

Yes. All FSUIPC does is call the FSX routine and FS does the saving. The PMDG code will see that happening and save its own stuff too. I'm afraid nothing can be done about that. Maybe you can change some parameter in SB4 to extend its timeout? You should always update to the currently supported version if you want any support. Pete

"Over-sensitive" in the sense that the surface is moving a lot with just a little movement of the axis, or what? If that, then the slope you need is one with a flattened central area. This will make the less-used extremes more sensitive of course, unless you want to completely limit the ability to reach all possible surface angles, in which case you simply use a divisor on the axis assignment in the INI after calibrating without it, or fiddle the calibration figures in the INI file. If you are getting a lot of reaction in the central area with a flattened slope then it sounds more like a joystick axis giving spikes, in which case it is hardware. Try cleaning. Regards Pete

False report. Override it and report it to Norton. In any case the version of FSUIPC for the released version of P3D v2 is not available yet. I was on holiday! I will release it when I've done it, probably before the weekend! Pete

There are still problems because some of the hooks in that version of FSUIPC are not correct for the released version of P3D v2! The version of FSUIPC for the released version of P3D v2 is not available yet. I was on holiday! I will release it when I've done it, probably before the weekend! Pete

The version of FSUIPC for the released version of P3D v2 is not available yet. I was on holiday! I will release it when I've done it, probably before the weekend! Pete

The version of FSUIPC for the released version of P3D v2 is not available yet. I was on holiday! I will release it when I've done it, probably before the weekend! Pete

Sorry, I don't understand. Can you clarify this please? And which version of P3D? I've not released the Version 2 compatible FSUIPC4 yet as it came out whilst I was on holiday. I've just installed V2 and will be working on it in the next day or two. Pete

Yes, you can have FSUIPC installed in any running copy of FSX. There's really no way it knows you are also runnng it on a different PC. Pete

Well, it seems also to answer #1: i.e. edit the INI and add two lines for the same button. You can many assignments to the same button by editing the file. Or you could use macros. If you actually have a flaps lever with notches then obviously you need as many notches as appropriate for the aircraft with the most. For aircraft with less than that you'd simply not use them all. By appropriate notch calibration in FSUIPC you should cover the entire axis spread in any case, so this wouldfn't be a problem. If you don't actually have real notches, or at least marked positions, then there's really no point in calibrating notches at all. Just move the axis to get the correct reading on the flaps indicator. Pete

- Empty Weight (I tried H1330 but It doesnt seems to work..) 1330 is correctly working. Check your code. - Payload (Havent found one yet) Did you try searching on the word "Payload" at all? Not far below 1330 in fact -- 13FC through to 1F7F provides a tbe of all payload stations, including names positions and values. - Fuel (I tried H0AF4 it's giving me a bit diferent value then the right one) As documented, 0AF4 is a value giving the ratio of weight in pounds to capacity in gallons. Please do read what it says. All the fuel data itself can be found easily by searching on the word "fuel" -- see offsets 123E through to 126F. - Gross Weight (I tried H1334 its not working also) As documented that gives the MAX gross weight -- it is fixed per aircraft! PLEASE PLEASE DO READ the document! To compute current gross weight add empty weight, fuel and payload. - Max. allowable fuel (Havent found one..) Again, you aren't looking! The capacilty of each tank is provided in the fule offsets. In fact fuel quantity in each tank is given as a proportion of the capacity, so you'd be reading it in any case! I get the feeling you are not actually using the supplied documentation at all. :-( Regards Pete

I suspect they are right. They should know their code. Maybe other 777 users can help? There are lots of configuration things you can do with FSUIPC for the axes, one might work fine as it did I'm sure for the many 747 and 737NGX users. Pete

I assume you are using this on the Remote PC, as that is obviously where you need it. On the FS PC you are presumably telling GPSout to refer to WideFS? With Eterlogics VSPEmulator.EXE, all I do is click Device then Create, select Pair from the drop down, then Next. Set the COM ports you want (yes, COM1 and COM2 are okay if not otherwise used), then "Finish". The main Windows then shows "COM1 <=> COM2" as "Pair" and "Ready". You can save the connection, giving it a name, and use that name to automatically reload it next time via a shortcut with that name as a parameter on the command line (in the program icon properties). After doing the above, when it says "ready", the Windows Device Manager doesn't show them (I think this is to do with 64-bit OS), but they do appear to work okay. Pete

Use the event system for much greater efficiency: I don't know iFly, but if writing to the CRS offsets changes them, rather than using the INCremental method you are using, then: function copycrs(off, val) ipc.writeUW(0x943E,val) end event.offset(0x9434, "UW", "copycrs") Of course if you are only able to use increments that you will need to do your loop in function "copycrs", but you need not read the value of 0x9434 again as that is supplied as 'val'. Assuming you save this as CopyCrs.lua, just get this running by this in your FSUIPC INI file: [Auto] 1=Lua CopyCrs or, if only for a specific aircraft or profile, [Auto.<profile name>] 1=Lua CopyCrs Pete

Sorry, I know next to nothing about the Helos, though I did think one of those models at least (the Robinson?) was implemented more like a normal prop than a helo and that one always was a problem. Maybe asking in the aircraft design forum on AVSIM might elicit some help. If you know how to operate the collective properly via a normal joystick axis assignment, then enable FSUIPC's axis event logging and see what controls are being used. Then implement your software to either use the same (eg via FSUIPC offset 3110), or the appropriate Engine-related offset which generates those controls. Regards Pete

That function only applies to version FSUIPC3. It has never been implemented in FSUIPC4 (as you can check by reading the User Guide). Why would you need it if you don't even have a PFC module installed? If you mean PFCFSX.DLL, why are you needing to restart it at all? Pete

I've never known AVG to have a false positive virus detection on any ZIP file of mine, but you need to report it, and in any case override it. The current Installer in Download Links subforum is for 4.921f, and there's a 4.921i update also there. Have you tried either of those? As soon as I've done the changes for Prepar3D V2 these will be replaced by 4.923 -- certainly by the weekend. Regards Pete

Answered already. Please don't post the same question twice. Pete

What do you mean by "du switches"? Pete