| Bug ID |
Description |
| K1 |
Saving Calibration data - toe brake data saved incorrectly in Calibration.ini file. |
| K2 |
Toe brake axes work in wrong direction. This affects digital axis statements assigned to them - important for most sims that don't support analogue brakes and use a keyboard key to generate wheelbrakes. |
| K3 |
Apps have wrong Version numbers on them - caused some confusion in last release. I think it would be sensible to give all exe's and the firmware the same version number for a release version. |
| K4 |
The statements "USE KEYBOARD AZERTY" & "MIX /I ... /O", cause the compiler to report an error with the /O modifier. See this thread. |
| K5 |
The CURVE statement on its own is causing a compiler error. It compiles fine, but just doesn't work. Works fine though on a button statement. See this thread.
|
| K6 |
Long XDEF statements can hang the compiler and long files can affect Foxy's colour highlighting. |
| K7 |
Allow for HxM on X Flag Definitions |
| K8 |
Analogue axes having large deadzones at the ends of their travel. |
| K9 |
Manual Calibration mode: Pressing Apply when there is no calibration.ini file results in X and Y axes not going full range. This impacts severely on several issues:
a) In manual calibration mode, you can't make any changes to axes in the CCP and hit Apply.
b) Similarly there's no point in retrieving the autocalibration data, making changes to the axes and hitting Apply.
c) Similarly if you load up a profile containing good calibration data, and press Apply, then although your axis settings will be applied, your manual calibration data will be incorrect.
.
|
| K10 |
Calibrating from Foxy or its Analyser causes all sorts of failed calibration issues but works fine directly from the CCP. I think to fix this what the CCP should do is just open up itself as normal and show the Startup and Calibration tab. Just showing the calibration routine isn't enough as people might want to save a profile with that data in it and it may be too much work to fix what errors arise when calling this routine only from an external app. |
| K11 |
You cannot load up a profile containing good calibration data, edit the axis settings, save the profile, and use that profile and its calibration data effectively. This is probably linked into bug K9 but I don't know. I would like to think that the calibration data is stored separately from axis data within a profile, and that you can edit the one without affecting the other..
|
| K12 |
USE NULLCHR character isn't working properly. The compiler is generating the character whenever it is seen in a file, instead of generating USB (D00 U00). If the statement isn't present, then the compiler is properly generating USB (D00 U00) whenever it comes across a caret ( ^ ). |
| K13 |
Back to calibration: A USE PROFILE profile (CUSTOM) statement in a joystick file ignores the data in a calibration.ini file. So if you have rubbish manual calibration data in a profile and good data in your calibration.ini file, the ini file will be ignored and downloading a joystick file with the statement in it will result in your stick having rubbish manual calibration data. This also affects downloading profiles from Foxy and CCP's startup options..
|
| K14 |
Statements with many brackets in cause compiler crashes. |
| K15 |
/H statements in axis statements aren't holding down more than one character, DirectX button or logical flag. For example: ANT 2 5 ( /H ({DX1 DX2}) ) ( /H ({DX3 DX4}) ) ^ ( /H ({DX5 DX6}) ) ( /H ({DX5 DX6}) ) but BTN S1 /H ( { DX1 DX2 } ) works fine. The axis statement is treating the /H like it would in a button statement without { } so it's only holding the last character. .
|
| K16 |
Files with lots of REM statements in them will compile fine and then disconnect on download. This is partially the reason behind the "DROP-OUTs + COMPILEd MEMORY USAGE" observations in this thread: http://forums.frugalsworld.com/vbb/showthread.php?t=37370 for the initial download, but doesn't explain why such downloaded files disconnect. |
