Simple Joystick Crash (4.26)
Page 1 of 1

Author:  Abex [ Mon Sep 08, 2014 8:31 pm ]
Post subject:  Simple Joystick Crash (4.26)

Whenever I attempt to open the 'Simple Joystick' window RobotC Crashes.
RobotC is version 4.26, building to a Cortex with the latest Master and RobotC firmwares (CORTEX_V4_22.bin & VEX_Cortex_1026.hex, respectivly)
This happens regardless of code pushed to the Cortex, either a blank template or code that polls getPCJoystickSettings. This has been also tested on multiple computers, both with Windows 8.1.
Attempting to open the 'Simple Joystick' window causes RobotC to exit without an error message, leaving Windows to prompt the user with a "Application has stopped working" error. This can be triggered either by pressing the button in the Debugger Windows menu or with a #pragma DebuggerWindows("joystickSimple"). This issue did not exist as of RobotC 4.10

Author:  JohnWatson [ Tue Sep 09, 2014 12:47 pm ]
Post subject:  Re: Simple Joystick Crash (4.26)

Please post a sample of your code using the [code] tags as this will help with the debugging process. Also, what type of joystick are you using for the joystick control? Are you using a VEXNet Joystick Controller or a USB-based controller (such as a Logitech F310 controller)?

Thank you in advance!

Author:  Abex [ Tue Sep 09, 2014 1:10 pm ]
Post subject:  Re: Simple Joystick Crash (4.26)

As I stated in my post this issue occurs regardless of code pushed, including:
task main() {}

The controller I am using is a Logitech F310 mascaraing as Dual Action, according to the Joystick Configuration Utility.

Author:  JohnWatson [ Thu Sep 11, 2014 11:11 am ]
Post subject:  Re: Simple Joystick Crash (4.26)

Thank you for this information. We have been able to duplicate this issue and should have a fix available for the next release.

Author:  RobolinkStudent [ Thu Sep 25, 2014 9:00 pm ]
Post subject:  Re: Simple Joystick Crash (4.26)

I have experienced this exact problem as well. Is there any work around in the current version of RobotC?

Author:  tfriez [ Thu Oct 09, 2014 3:16 pm ]
Post subject:  Re: Simple Joystick Crash (4.26)

This is a known issue unfortunately for the VEX Cortex/IQ platforms. We have a fix available for our next release, which we are in the final stages of preparation to release. We hope to have the build released by the end of this week/monday at the latest.


Author:  afriesen [ Sun Oct 12, 2014 11:57 pm ]
Post subject:  Re: Simple Joystick Crash (4.26)

Having joystick problems as well with NXT.

The competition joystick debug window shows that the joystick is working.

Not able to read any joystick information in any program. As far as I can tell, the entire joystick struct is zero'd out and never changes.

Communication between the PC and NXT brick is good, both USB and BT. Other programs run.

Following simple program never indicates a button press. joy1_Buttons is always 0 in the debug stream.

#pragma debuggerWindows("joystickGame");

#include "JoystickDriver.c"

task main()
while (true)

writeDebugStreamLine("%d", joystick.joy1_Buttons);


Author:  BurningLights [ Tue Oct 14, 2014 12:03 am ]
Post subject:  Re: Simple Joystick Crash (4.26)

The game joystick window can be a pretty tricky animal to get to work right. I would recommend that if you only need one joystick, you use the simple joystick window instead. Just replace "joystickGame" with "joystickSimple".

Author:  BurningLights [ Thu Oct 16, 2014 11:28 am ]
Post subject:  Re: Simple Joystick Crash (4.26)

Maybe you could try this code for your tankControl function:
tankControl(joystick.joy1_x2, joystick.joy1_x1, 10);

from the ROBOTC online help.

Also, I'm not sure if you need to call startJoystickControl() before the joysticks work. This command is in the ROBOTC 3 help, but doesn't seem to appear anywhere in the 4 help.

Page 1 of 1 All times are UTC - 5 hours [ DST ]
Powered by phpBB © 2000, 2002, 2005, 2007 phpBB Group