John Dowson

Hi Eran, first, you posted in the FAQ section. Please post all support requests in the main support forum, not in a sub-forum (unless it relates to the .net client dll). I have moved your post for you. Could you post your .ini, .log an .JoyScan.csv files please (from your Modules folder). Are you running any additional software or drivers for the TPM ? John

Sorry, its ok. The size of the new structure still fits. John

Hi Niberon, do you use (or did you try) the offset area for the CDU screen data? This has also changed, with an additional 3 items (bytes) added to the structure. I'm looking at this now, but it looks like the new structure doesn't fit in the available offsets, so I may have to move these 3 new additional items to a different area. Just wondered if you have used/tested these. John

Depending upon how you are setting this up, you may want to look into using the ini parameter UseAxisControlsForNRZ - see the Advanced User Manual (and/or check the forum).

If you post a support request in any forum other than here, in the main support forum, you will always get a reminder that you have posted in the wrong place. We will find your post (eventually!) and move it, but we ALWAYS let you know your error so that you do not do this again (hopefully!). I usually do this by editing your original post with a larger red text heading telling you that it is moved, and also (usually) mentioning this in the response, but other moderators will handle this differently. No offence is intended, but this occurs very often and gets annoying - its just more unnecessary work for us. We emphasise so you take note and do not do this again.

If you have calibrated, could you go into the FSUIPC logging options and activate Logging for Axis controls. Then activate your left and right brake through its full range (independently). Stop the sim, then post both your .log and .ini files and I'll take a look.

Check your SimMarket account. Its only on sale there, so if you have purchased a license it will be under your account (if you have one!).

Hi Andrew, thanks for reporting back. I could try and reduce some of the delays added, but as these only total a few seconds, it wouldn't reduce the shutdown time by any noticeable amount, so I think I'll leave things as they are. I'll release these changes within the next day or two as v6.0.4 (and remember to update the IPC check version!). Cheers, John

Installing FSUIPC should not affect SODE. You do not provide much information, so its difficult to help! What version of FSUIPC are you installing (FSUIPC5 or FSUIPC6)? Did you read the installation and registration manual? What exactly is your problem? Do you have an installation log? P.S. I deleted your other post on same topic in a different thread P.P.S. And what does the topic of your post mean? Please give your post a suitable title.

Hi Andrew, first apologies, as there was an error with the logging statements, which means that the logging was active even if not enabled, which would affect the timings. Due to this, the test need to be redone. [And was why we were also confused with your logs!] However, as it seems that you are getting consistent results with the CMDRST call disabled (i.e. ini param set to Yes) [but with logging!], I've taken that as another clue and have increased the wait time after this command is sent. So, could you please try the attach dll. Again, no logging please (LogExtras=1 or 0), and try with CMDRST enabled and disabled. Thanks, John FSUIPC6.dll

Hi Andrew, So you changed the logExtras value before closing? Really we wanted to see what happened without this, as the additional logging also affects the timings. Also the tests with ForceTerminateTime don't really mean much at the moment - need to make some adjustments for this to work, but we'll leave this for now. Sorry about that. I'll come back to this if needed... Could you try the attached dll please: I've increased the timings in this one. Please try initially with LogExtras=0 (or 1) and DO NOT CHANGE before closing down. You can try with both the VRIDisableCMDRST set to No and Yes - from your previous results I am hoping this would work with the latter option, but probably not the former. However, if this does work consistently, then we could go with this one. If you still have issues with this, then set the LogExtras to x2005/8197 before closing to get the additional logging, and send the logs (for both VRIDisableCMDRST Yes and No). Cheers, John FSUIPC6.dll P.S. "The log files shows logging ended but the hanging task remained." - but this would indicate a P3D problem, not an FSUIPC one as the log indicates that it (and all associated threads) have closed.... And: "Finally I removed the ForceTerminateTime entry. This time FSUIPC6 terminated correctly with no hanging tasks after a 5-10s delay. This was repeatable." Ah, ok - so this is the test we needed (i.e no logging), so maybe just adding the 10ms delay was enough... Try the new dll anyway and report back. Thanks.

Hi Andrew, could you try the following dll please: FSUIPC6.dll This one has a small delay added to during VRI closing. Could you try this with logExtras=4 please and send the log back to us. You can also try with no extra logging (LogExtras=0 or 1). For some final tests, you can try adding the following parameter to the [General] section of the ini: ForceTerminateTime=<milliseconds> where <milliseconds> is the time it waits before forcing termination. This needs to be long enough for P3D to close down in normal situations (e.g. to rewrite the P3D CFG file if changed). Suggest you try with different values to see what works, maybe starting at 1000ms and going from there. John

Sorry, but does this mean that you have installed and registered ok now? As I said, if you are still having difficulties, I also need your WideFS7 order number if you cannot register that.

Ok, thanks for testing Niberon. I'll release officially this as v6.0.4 in the coming days. John

Ok, thanks for reporting back.

Hi Percy, What do you mean by this? What aircraft are you using? Nothing has changed between FSUIPC5 and 6 with regards to mouse macro functionality. I verified mouse-macro functionality on P3Dv5 with the macros I have/use, and found no issues. Given the above, I'm not sure. I don't think I've seen a switch or button with a drop-down menu - could you elaborate? Thanks, John

Hi Andrew, strange and confusing results...any ideas as to what is causing P3Dv5 to crash? Could you try the following dll please (6.0.3d): FSUIPC6.dll It has additional logging. Start with only the following in your ini: Debug=Please LogExtras=1 Just before you close the session, go into the logging tab and set the extras value to 8197. If you could then generate a log when iy hangs. Thanks, John

Hi Niberon, could you try the attached dll for me please: FSUIPC6.dll If that works, I'll update the documentation and release later in the week. John

Do you have the VRIDisableCMDRST parameter set to Yes in the ini by any chance? I am very surprised that the first dll didn't work (which is actually 6.0.3a but I forgot to update the character string, sorry) as this should be equivalent to FSUIPC5... I'll discuss with Pete to add some logging to try and track down this issue...

Did you click the Register button?

And also please try this one: FSUIPC6.dll The first dll above is compiled against the same Windows SDK as FSUIPC5, so hopefully that one should work. The one attached in this post is compiled against an intermediate SDK. It would be useful to know if this one works or not as well. Thanks.

Just checked and I forgot to update version for IPC in the header. I will correct this in the next release.

Yes, forgot to mention that, sorry - I'll update that topic. John

Hi Andrew, could you try this dll please: FSUIPC6.dll

Your COM ports cannot be opened: 969 VRI port 1 "COM2" failed to open 969 VRI driver port 1 "COM5" failed to open 985 VRI port 2 "COM6" failed to open 985 VRI driver port 2 "COM7" failed to open Is VSPE running? Try adding the logging flags, as suggested: Debug=Please LogExtras=4 You also seem to have two [General] sections in your ini, with the first one prefixed by '!1=n' which will be make that section be ignored. Either delete that whole section, or remove those characters before the section name and also the other [General] section.