Pete Dowson

I think that's mostly done by actually moving the aircraft using the latitude/longitude values, or, easier, by using slewing. Why are you reading 3070 when you've just written it? If the write succeeds you should read back 10. If it doesn't there's no point. so why read it anyway? I don't think you can have any significant affect on these things unless you keep writing them very fast -- because the Simulation engine will overwrite them on the next frame with its next computed value based on things like thrust. Moving things by magic means the magic needs to continuously override reality. I don't know if it "should" work or not. At the very least I would have thought you'd have to loop on that every, say, 20 or 30 mSecs, at least fast enough to beat the simulation rate. One person I do think would know is Herve Sors. Regards Pete

No, it does NOT stop, it simply does everything it should and tells you it is not replacing FSUIPC where it doesn't need to. it is an information message, not an error, and the installer processed normaly. Regards Pete

You can look up Windows system error codes -- google "System Error Codes". Error 267 shows that the path you provide is not correct. ERROR_DIRECTORY The directory name is invalid. 267 (0x10B) What I find odd in the error you are showing is the double sets of quotes "" at each end. Looking closely they look to be different character, in fact. If I try an invalid folder I get: 23244 FSUIPC couldn't run: "E:\FSX\XModules\FSX2.BAT" [Error=267] Single sets of quotes, not double. I think that you are not using a text editor to edit the INI file and the quotes characters you are using are the Unicode different left and right quotes as used in Word Processing. I'm afraid only normal ASCII quotes work. Regards Pete

Where are the axes assigned? FSUIPC's calibration will only see assigned axes. The FSUIPC axis assignments tab should see all axes. did you check there? The file you pasted is the FSUIPC4.INI file. It seems you have Windows hiding filenames from you -- please review the early pages of the FSUIPC User Guide for details of how to stop that. It makes things very awkward. The image you posted shows input values for those two axes you say it isn't reading, so evidently it has read the controls assigned. FSUIPC's calibrations do NOT read joystick axes, they work purely on the controls which FS is using to operate the surfaces. If they are not changing it is because those controls aren't changing. In FSUIPC the only tab which reads axes is the axes tab, where you can assign them. Regards Pete

No. FSUIPC will attempt to run that file when FSUIPC is first started, it won't wait for "Fly Now" -- the "READY" option delays until your sim is "ready to fly". Did you check the log file to see if there was an error finding or running the file? Are you sure the path is correct, because if it cannot find it it cannot run it. Are you sure you did not but Aero.bat into the Modules filder? Pete

There's been no change in any related part of FSUIPC for a long time. Are you talking about assignment or calibration? You need to actually say what you are doing as "configure" doesn't give any details. Please show me your FSUIPC4.INI file, from the Modules folder. Pete

Interesting. Why not use the actual control instead of a keypress which FS then maps to the control -- "Landing lights toggle". Really, problems like this will need reporting to Lockheed-Martin on their Forum. All I will be doing is double-checking and relaying the report, because there's no difference in anything in FSUIPC between FSX, ESP, P3Dv1 and P3Dv2 in any of these areas. The differences are only in areas which need hacking into FS code, not in straight-forward control assignments. Anyway, in checking your report I cannot find an aircraft where both Ctrl+L assignment and the control LANDING LIGHTS TOGGLE don't work to operate the switch correctly, though I can't tell in the P38 because I can't really see much to work it out. Key press assignment in FSUIPC does send the key (as you would have determined had you enabled logging), and does result in the correct FS control (also seen in the Log), the same as Ctrl+L directly on the keyboard does. The Log tells nothing because you did not enable any logging options -- try it yourself with Key/button and Event logging enabled. You can even run in Windowed mode and enable console logging so you can see what is happening in real time. The INI file is not a lot of help without analysing every assignment line because you don't mention which button you assigned. However, whilst you have one specific Acclaim assigned to a Profile, you don't have any P38 assigned anywhere, and the default [buttons] section has no assignment to Ctrl+L. So your test on the P38 at least was void. I don't know why you don't see correct results on the Acclaim unless you were using one not assigned to the profile.. Incidentally, for Profiles you'd be better off changing "ShortAircraftNameOk=No" to ShortAircraftNameOk=Substring and using abbreviations for the aircraft names so all paint jobs etc are included. Regards Pete

First please update to the currently supported version, 4.923. If you still get a problem I will need more details -- the FSUIPC4.LOG file from the FS Modules folder and the Windows crash details from the Windows event viewer. Regards Pete

Ah, sorry. Yes I missed that point. And no, there is no way I know to operate the dock / undock action apart from using the right-click menu. I did search for a way of "fiddling" it through direct Windows messages when developing some of the Lua plug-in facilities butI was not successful. Regards Pete

Yes, verified. It's a P3Dv2 bug and I've reported it. In FSX and P3Dv1 the "ELECTRICAL MASTER BATTERY" variable in SimConnect is both read and write enabled. It should be so in P3Dv2 also, but the write does nothing, not even giving an error like non-writable things do in FSX. I could make a work-around using the control, as i have to with many unwritable values, but that mechanism normally works by detecting the error and acting accordingly. I'd rather see LM fix things than implement work-arounds in FSUIPC, but if nothing is fixed in updates then I'll have to do something myself. Regards Pete

Isn't there a keypress for this. assigned by default in FS? Let me see ... yes, the [ key to open, ] key to close. Logging the resulting events in FSUIPC tells me that these are the FS controls "New view" and "Close view", which you can certainly assign to. Pete

Report this on the Prepar3D Forum. They thought they'd got rid of all those. It isn't specifically realted to FSUIPC and doesn't happen for most users. And can happen with no addons at all. Pete

Well, I can understand the IYP error -- that is because it is looking for the original ClassInstance=0 name. But the error from RC is puzzling, as it implies it connected okay -- else it would get no data at all. Maybe it doesn't even check the connection status, I don't know. sorry. Some developers have facilities in their programs to select the ClassInstance name specifically, but there aren't very many, I know. Pete

No, there is no automatic addition. There's no way FSUIPC can know you are wanting to run that Lua file automatically. YOU have to edit the INI file and add the above section! The use of [Auto] sections to run plug-ins and macros is covered in the Advanced User's guide for FSUIPC. I have no idea if that is a good measure of what it is supposed to do. I thought the changes made were all to do with grip, not rusty wheel bearings -- reducing the tendency to slide sideways in cross wind, for example. But I don't really know much about all this at all. I only provide access to the tables of coefficients. Perhaps you should ask someone over in one of the Forums (AVSIM) where all this was originally discussed? Regards Pete

I've replied by email. Pete

I add those things which are suitable for the memory-mapped offset system, by request. Because the original reason for porting FSUIPC over to FSX (using SimConnect) from FS9 (using only hooks and direct memory references) was for backward compatibility for FS9 applications, the initial coverage needed to be achieved was that subset of SimConnect which was already represented by offsets before FSX. The additions since then have all been by request (just the same way, really, as new entries have been added for each FS version since the initial FS98 coverage). I haven't looked up those specific data values to see if they are suitable, but if you'd like to email me (petedowson@btconnect.com) with a list of those items you require, I'll see what I can do. Regards Pete

Yes, what you've given is correct, except that you need to read the data from the opened device (using com.read or com.readlast). The other HID functions merely decode data already input. The ipc.axis function is easier to use for standard joystick devices. The HID facilities are more general and enable access to additional device types (like GoFlight and Saitek non-joystick devices), and additional axes or buttons on the more advanced joystick types. Regards Pete

Not much more to look up than what I've already told you really! It's just the one line "ClassInstance=0" which needs changing. you just need a text editor like Notepad! I only pointed out that it is mentioned in the documentation so you will know where to look for any more information about WideFS. Pete

The only terms you needed to understand when you went to the Schiratti site to find FSUIPC was "FSX" and "FS9". Those are versions of FS, and there's only one possible FSUIPC download there for each! The subforums to which you refer are just specialised parts of this, the Support Forum, which are permanent repositiories for useful information, not questions about support and subsequent threads which then develop. The main Forum is where all support is done, not in the subforums. I do not know that program and if it does not need a version of FS to run with, then it cannot possibly need FSUIPC, because FSUIPC is an FS module which can only be installed if you have a version of FS to install it into. The versions of programs which may or may not use FSUIPC is nothing whatsoever to do with FSUIPC. The only versions of FSUIPC are the one for FS9 and before and the one for FSX and later. There's no relevance at all to other programs, and especially not ones not related to any version of FS whatsoever. Sorry, none of that is meaningful to me at all. Why should it? Why has Mr. Schiratti got to document anything about programs written and supported by others? That "Dowson" page is just a repositiory of programs by myself written for FS users. If you are an FS user then you should surely know what version of FS you are using! If not all this is really a waste of time. That's your first need -- find out what FS you have got! All versions of FS ("Flight Simulator" in case even that abbreviation mystifies you) are by Microsoft excepting Prepar3D (P3D) which is Lockheed-Martin's later derivative of FSX. That is still actively developed, whilst Microsoft have ceased FS developement. To recap: 1. I have no idea what FSFS Pro 2013 is. If it's a later version of the original FS Flying School then it is an add-on for FS -- probably FSX if it is as new as 2013. 2. The only "versions" relevant to the choice of FSUIPC are the versions of FS (Flight Simulator). You must surely have purchased one such version, otherwse how do you propose using what is presumably an add-on for it? So, find the box which your version of FS came in and see what version it is. If you have actually installed it, then it will probably identify itself pretty clearly when you run it. Regards Pete

Just change it in the INI file, like I said. By default it is 0. Change it to, for example, 1. BTW it is documented in the WideFS documentation. Pete

Yes, it's must be a corrupted P3D install. Pete

It is actually possible to run WideClient on the same PC as FSX. You have to change the ClassInstance number in the WideClient.INI file. Some programs might then connect to it correctly, others might not -- it depends on how they been written. Most would not I fear. If you wanted to try that, please go ahead and let me know. You'll have to remove FSUIPC from the FS Modules folder first, otherwise the interface that presents will clash. Pete

It's okay. Get 4.923, now released. Pete

Version 4.923 was uploaded not long after my last reply. I put a pinned notie up at the top of the Forum. Why do you want to reinstall P3D? Pete

There is no version of FSUIPC for P3D v2 yet. I was on holiday when it was released. Trying to use the currently available versions is not a good idea -- it may crash P3D. I was up to version 4.922 for the Third Beta, before I left on holiday, then Beta 4 and the main release occurred whilst I was away. Most of the hooks are wrong and some code patches too. Even the SIM1 Frictions access is wrong and will probably corrupt parts of P3D code or data. I am in the process of building and uploading version 4.923 now. It will be available shortly. Pete