HTR and FSUIPC 4.971 - Joystick readings

[G2Novice]

Hi

I have a problem with my joystick setup that appears to have been fixed with an earlier patch, but I can't seem solve it and have come to this forum for help.

I'm currently using 4.971 (Registered) FSUIPC and HTR 1.5.   The simple problem is that with my throttle fully down, HTR reads 50%. This appears to have been fixed with a patch which is no longer downloadable? In FSUIPC the in and out readings are 16213 and -16213 but HTR only reports from 50% to 100%. According to forums this was fixed with a patch ?

Interestingly I downloaded HTR 1.62 and although the throttle works, the pedals have a different problem. FSUIPC reads 16380 to -16380 with a centre of zero,  however, only the left pedal actually registers on HTR. It goes from 0 to 100% e.g. from centre to full left pedal. The right pedal does nothing.   In HTR 1.5 the pedals read 50% i.e. in the centre and the left and right pedals operate as expected.

I'd be grateful for any advice?

Thanks in advance.

 

 

[Pete Dowson]

2 hours ago, G2Novice said:

I'm currently using 4.971 (Registered) FSUIPC and HTR 1.5. 

What's HTR 1.5?

2 hours ago, G2Novice said:

The simple problem is that with my throttle fully down, HTR reads 50%.

If HTR perhaps a Saitek product? Because their installer has a notable flaw in that it often seems to install data in the Windows Registry which causes this. You should really post on the Saitek support forum, because it is high time it was fixed and users advised.

Meanwhile just see the very first thread in the FAQ subforum.

Pete

 

[G2Novice]

Hi Pete

Thanks for the prompt reply. Apologies for not being clearer. HTR is the Helicopter Total Realism physics library by Fred Naar over at Hovercontrol.com

I've read the FAQ, I'm using a heli-kit from heli-kit.com and that doesn't appear to be the problem, FSUIPC reads the full range -16380 to 16380.

I noticed on a forum that when flying the R22 in fsx/p3d using HTR with FSUIPC there were similar problems and you released a patch - something to do with offsets? It appears the Bell 206 works like a charm but the R22 starts at 50%?  

Here's the post reference http://www.hovercontrol.com/cgi-bin/ib3/ikonboard.cgi?act=ST;f=53;t=20488

Would it be possible to download the earlier version with that patch to test it please?

Thanks in advance.

Edited October 24, 2017 by G2Novice

[Pete Dowson]

1 hour ago, G2Novice said:

Thanks for the prompt reply. Apologies for not being clearer. HTR is the Helicopter Total Realism physics library by Fred Naar over at Hovercontrol.com

I've read the FAQ, I'm using a heli-kit from heli-kit.com and that doesn't appear to be the problem, FSUIPC reads the full range -16380 to 16380.

In that case it will be the calibration. Maybe you have half of the range dedicated as a reverse range, and shoould be setting the "No Reverse Renge" option?

1 hour ago, G2Novice said:

I noticed on a forum that when flying the R22 in fsx/p3d using HTR with FSUIPC there were similar problems and you released a patch - something to do with offsets? It appears the Bell 206 works like a charm but the R22 starts at 50%?  

The post reference you gave actually refers to something which was obviously nothing to do with me, and you need to read it again. The "patch" to which you refer was evidently a replacement to your HTR ptrogram to make it process an offset correctly. If you read it all properly you will see that there was apparently an error in an early version of FSUIPC which, instead of being pointed out to me at the time it was discovered, was used in the faulty condition by the HTR programmer. So when I actually fixed FSUIPC his software was wrong.

I've no other information and no way of knowing what the original bug was now. I think you really should obtain the correct working version of HTR. 

Nevertheless, using the History document (which you also have for reference in your FSUIPC Documents folder), I looked through the "fixes" list for version 4.80, the first major version after the 4.745 to which that post refers, and found this (number 3 in the "Bugs Fixed" list on page 24):

3. Fixed offsets 332E–3336, and 3412, 3416, 3418 to provide the axis values is the correct range, calibrated if so
subjected. For clarification, for throttles the correct range is 0-16k for forward thrust, with negative values
providing reverse. These values are then suitable for application directly to the FS control offsets, as documented.
These offsets have been wrong for a long time, often providing the incorrect range (-16k to +16k). Therefore, in
case this bug fix messes up any programs which have assumed the offsets were behaving correctly, and made their
own "fix" already, a parameter in the [General] section of the FSUIPC.INI file is available to force these back to
their old (wrong) behaviour: just set "AxesWrongRange=Yes".
Note that this was mostly fixed by version 4.743, but a further correction was applied in 4.745

Take note of the red parts. Could that be your answer?

Pete