John Dowson

Hi Diego, first you posted in the 'Download Links' sub-forum. Please do not post there - all new support request should be posted in the main forum (or in the .net client dll, if the request is related to this dll). You have also not provided enough information. What sim are you using? What version of FSUIPC? Which aircraft? If you are using FSUIPC for this, what have you assigned? Please post your ini and log files.

No, as I said, FSUIPC doesn't "return" anything. It populates offsets with the information to be read.

The version comes from the sim via SimConnect. SimConnect is an API.

Just noticed this. Are you saying that your brakes are working ok in this aircraft, and your problem is just with the PMDG aircraft? If thats the case, you could try sending the brake axis to the FS instead of to calibration, as axis calibration in FSUIPC is known to cause issues with PMDG aircraft due to priority levels. If doing this, I think you would then need to scale your axis values as previously indicated so that the sim sees the full range. Again, seeing your full ini would have been useful.

But I have no idea where that comes from - it is coming from the program you are using, not FSUIPC. You need to ask them. FSUIPC does not return anything. It populates offsets with the sim version.

Hi Julius, sorry, but your post is very difficult to understand....google translate by any chance? However, this stands out: This behaviour can be caused by bad registration, i.e. the device is registered in windows registry as digital instead of analogue. You could try the following: - disconnect your device - go to windows device manager rand delete your device there (including any software) - reboot windows - reconnect your device - go to windows Game Controllers and calibrate your device there Once that is done, please try again in FSUIPC. If you require further assistance after performing these steps, please attach your .ini and .log files (as previously requested).

I have no idea what an "interface ID" is. FSUIPC has no such thing.

FSUIPC doesn't send anything. Where are you reading this from? The P3D version number should be available in offset 3124. Offset 3308 will still contain 12 (for P3D 64-bit), as it does for P3Dv4. John

Btw, It would be easier for me to advise if you could post your full ini and the suggested log file: You can try the above (previous post), but it shouldn't be necessary as FSUIPC should scale your axis calibration values from 0-16380 to the full -16384 to + 16383 values anyway. In the brake axis calibration page, what do you see in the in/out values when your toe brakes are in the default position (off)?

The full toe brake axis range is -16384 to + 16383, so with a minumum of 0 in your case your toe brakes will be 50% applied. If you cannot get the full axis range by calibrating (using either windows calibration or any software that comes with your device), then you will need to scale the input axis. There is a section in the Advanced User manual on how to do this, but basically you have to edit the ini to set your brake axis assignment to something like 6=5X,8,D,8,0,0,0, *32.03, -16384 -{ DIRECT: RightBrake }-7=5Y,8,D,7,0,0,0, *32.03, -16384 -{ DIRECT: LeftBrake }- Make this change and then re-calibrate. John P.S. I've corrected the values as I just noticed that your reported range is 0-1023 and not 0-16383, so you need to multiply by 16383/1023 to get 0-16383, then double to get 0-32768, then you subtract 16384 to get the required range of -16384 to + 16384

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.