Pete Dowson

I've already told you that I have never had the problem being discussed, but it seems, from that thread in FAQ, that others who have were successful in fixing it following Marcel's advice. I gave you my theory as to why Windows does mark the DLL in this way. There is nothing more I can do about it. It isn't FSUIPC4 which is failing, but it is due to another crash you've had in FSX. If you are worried, just make a backup first. See https://www.windowscentral.com/how-backup-entire-registry-windows-10. i can't explain it better. I've frequently edited the Registry, and in more critical areas than simple "compatibility flags" which is all that part is recording. Except for the strange way it marks a library to be Ignored in this way, Windows Compatibility settings are controlled in the program properties (right-click on the EXE file of the program, select Properties then Compatibility). Pete

And have you actually read the "other" places where this is reported? Seems not. I assume you are trying the Beta (i.e. "test") version of FSX-SE released very recently? If so, haven't you read how a special version of FSUIPC has been released just to satisfy those who want to participate in that test? Details are also pinned at the top of this forum and also in the Download Links subforum! There is no installer for the Beta version of FSX-SE. Just a temporary replacement FSUIPC4.DLL. You really need a proper non-Beta release of FSX-SE installed first. That said, the existing installer for 4.974 worked fine here after a completely fresh install of the Beta FSX-SE. Before this week i long ago removed alltraces of FSX and FSX-SE!

At first reading it seems a pretty easy option to add, yes. I'll take a look at the code. John's away at present but I'm sure he would also be favourable towards this, possibly for the next release of FSUIPC5 (for which we can't currently give a date). Pete

I have made available a version of FSUIPC4 which will work with the recently released FSX-SE update, build 63003,. this version of FSUIP4 will work as normal of other FSX, FSX-SE and P3D versions, but with FSX-SE 63003 some of the facilities haven't been enabled (the ones needing complex hacks into the FSX-SE code innards). These: are the missing parts: * Wind smoothing (only used in conjnction with external weather apps) * Friction table access * Mouse macros * SimConnect text diversion * AI Traffic deletion (eg for ZAP facility and traffic limiting) * Reading and changing traffic settings by program You need to install FSUIPC 4.975, available in the Download Links subforum and also on FSUIPC.com. Please also read the IMPORTANT notes included in the downloaded ZIP file. Pete .

That's what I read. Except it's "ADMIN" not "ASMIN". See: 1) Open regedit 2) Goto the key HKEY_CURRENT_USER\Software\Microsoft\Windows NT\CurrentVersion\AppCompatFlags\Layers 3) Delete the key "C:\\Games\\FSX\\fsx.exe"="$~ RUNASADMIN IgnoreFreeLibrary<FSUIPC4.dll>" If the key does not exist or does not end with the “IgnoreFreeLibrary<FSUIPC4.dll>” then you have a different problem than described here… 4) If you would like to run FSX as an administrator you need to activate that again as you removed that in step 3. Why not just follow those instructions? I've never had this problem (which is usually caused by a bad scenery or texture file) so I have never had to do this. The reason FSUIPC4 gets marked down to not be loaded is because it's usually the last thing running when FSX crashes. By the time FSUIPC4 gets notified and tries to tidy up its assorted threads, everything else has closed. (This could happen also to any other SimConnect client DLL with multiple threads, but FSUIPC is the only common one). Pete

No idea. It's evidently a function of the software used for the Forum. There are quite a few Forums on which I find this problem. I think you need to put the image on another webite and put the link here using the "Link" selection just above the edit area (like two chain links). I think there are some free sites for hosting images for just such a purpose. Personally, for support requests, I prefer text to images. I often fin it difficult to work out exactly what it is the poster wants me to see. For Windows error reports you can get all the text details in its Event Viewer. Pete

Okay folks. download FSUIPC 4.974c. Unzip the DLL and put it into your FSX-SE build 63003 Modules folder. See if this works well enough for you. Please let me know. Pete

Please see this, the first topic in the FAQ subforum: https://forum.simflight.com/topic/73518-possible-solution-for-fsuipc-access-violation/

I assume you are only doing this temporarily, "to help Microsoft"? Seems a step backwards, an especially big one from P3D4 as it is today! Pete

Yes, all those things will be fine. Interception of SimConnect text displays and menus and display windows for transmission to another program, eg. WideClient. i use the facility to get these displays on a screen in my cockpit rather than annoyingly on the scenery view outside. I'll get a Test version of FSUIPC4 built early this week. Pete

I've had a quick look, and it seems many things have moved around -- probably through re-compilation. I normally try to work out where they've moved to by comparing with the previous version. however, I removed FSX-SE (and Steam) long ago, after development stopped. So: a question for those participating in this Microsoft Beta version of FSX-SE: are you only needing FSUIPC to support joystick assignments, calibrations, etc? Or are you also needing full support of things like mouse macros, and SimConnect text diversion? If the former i can just stop it doing all the hacks into FSX innards. This won't remove most of the capabilities, only these: * Wind smoothing (only used in conjnction with external weather apps) * Friction table access * Mouse macros * SimConnect text diversion * AI Traffic deletion (eg for ZAP facility and traffic limiting) * Reading and changing traffic settings by program I can provide a version with these limitations very quickly. What do you think? Otherwise it will be a while. Pete

Okay, thanks -- downloading overnight. Not sure when can do it, but i'll take a quck look soon. if it is only a matter of updating sone addresses it should be quick enough. Well, they don't look very significant, but there you go. Only the weather part seems a bit more signiificant, but then I thought snyone who wanted decent weather used an addon like Active Sky. 9I always have). Pete

Being curious about this FSX-SE update, I installed Steam again, and registered with my account, as used when I was developing for FSX-SE before its demise. But even then I cannot find a way to even install FSX-SE again, let along update to a Beta. If you can tell me how to get it again then I might be able to see how easy it would be to adapt to it, assuming it is worthwhile. Pete

How strange! Unfortunately I no longer have Steam installed, nor have I an easy development environment for FSUIPC4, having frozen that code a while ago and moved onto a 64-bit environment (for P3D4 of course). Please let me know whether these bug fixes are worth the update. If it looks like enough folks will move to it I will try to find time to go back to 32-bit with Steam and FSX-SE. But it won't be for a week or two. Pete

Are you assigning these is FSUIPC? If so you could try increasing the scan rate. This parameter controls that: [Buttons] PollInterval=25 That value, which is in milliseconds, can be reduced. 25 gives up to 20 presses and their releases per second. In the end, though, these events do gve rise to messages flying about within the simulator, and the processing of those will depend on other factors too. Sometimes (usually0 they get queued, but that depends. What is often done for rotary encoders is to differentiate between turning a knob quickly and slowly. GoFlight do that within there own drivers for modules like the RP48. It can be done for others too, by prograam or even by having a Lua plug-in to process the incoming button press indications and acting differently depending on the interrval between. Pete .

Those values are accelerations, not pitch values, so there'll be zero in a constant speed pitch change. FSUIPC is onlt passing on the values supplied by the simulator. Please refer to their documentation for more details. They are SimConnect Variables and will all be catalogued in the SimConnect SDK. Sorry, how you actually operate a motion system is beyond me. I think you might need to visit one or more of the cockpit building forums if you want advice on that. there are also books on the subject. The one called "Flight Simulation" in the Cambridge Aerospace Series, by JM Rolfe and KJ Staples has a whole chapter on the subject. There are others. Pete

The 6 in 6DOF relates to the six axes of movement -- X Y Z and also roll pitch and yaw. All those values are together as you see in successive offsets. You would need just to scale those accelerations to meet the needs of whatever your motion system needs. I don't know, but think the G force experienced would be determined by those accelerations, so I;m not sure that is also needed as a 7th factor. Pete

In that case you are NOT actually calibrating, as calibration produces outputs from -16383 to +16383 no matter what the input values are. i think you are reading the "IN" values. Check in Axis assignment. What numbers does that show? Have you bothered to calibrate in Windows first. you should do, because that gets the Registry sorted. That can be quite normal. Before calibration in FSUIPC just check the "REV" checkbox. That is what it is for. it is short for "REVerse". But calibrate in game controllers first, because otherwise the range of changes you are getting is woefully short. In FSUIPC, follow the numbered steps in the User Guide for calibration. Don't skimp on this! Pete

Just install and register. You can have FSUIPC registered on any number of computers provided they are all for your personal use. Pete

What is that supposed to mean? Are you objecting to me trying to explain things? I do it as clearly as i can! If you don't like me trying to help I won't answer any more! I work as hard as i can to support my software as well as i can! Zero. It mens the ASCII string is terminated by a zero. Intel stores numbers in memory with the least significant part first, hence the apparent reversal treating them as single bytes. I did not assume it at all, hence the "sorrt IF" part. the IF is a conditional. I felt as if I wasn't explaining things well enough. Anyway, that's it from me. It seems obvious that you don't like my way of tryting to help, nor my English for that matter. Bye,

Thanks. it would be worth you describing the problem, especially reproducing it using P3d's own facilities rather than FSUIPC, on the L-M support forum. Pete

GFDEv64 is available, like most of our software, in the Download Links subforum here (see the subforums list at the top!). Just open the Download Links subforum and see the thread called "updated modules". Do NOT get any software from old posts in the Forum. they could be old versions, or test versions, and unsupported! Incidentally all the current software is always also available on the new official Dowson page. petedowson.info Pete

John is on holiday at present, but answering for him he means he won't be putting together the next supportable Release of FSUIPC until sometime in December. Meanwhile interim test updates might be made available to those willing to check things out and return reports on the results. Pete

Pardon? What are you asking? Pete

It's because it's actually a negative number (parameters are signed because they often need to be, eg, for yoke positions, throttles with reverse, vertical speed, etc). Try putting - in front, otherwise FSUIPC thinks it is positive and that's the "nearest", binary-wise. Or try entering x80000000. That might work. FSUIPC is doing nothing more than sending the control number with the parameter. It cannot interfere with this. It is probably just the matter of the negative parameter. With parameters you can always enter them in hex by preceding the value with an x. Saves trying to get more complex decimal sequences correct in cases like the PMDG mouse codes. Pete