r5 made joystick not work?

Wasp · Post by **Wasp** » Tue Nov 17, 2009 2:22 pm

Adam4 wrote:QUOTE (Adam4 @ Nov 17 2009, 09:01 AM) 0.0 causes crashes for some people.

was the 0.0 removed?

after experimenting a little, I discovered the registry settings are:

Large = 11 decimal
Smallest = 31 decimal
Small = 5 decimal

are there values in between that would take effect if we changed these values?...if so...can this be made public so we can edit the registry ourselves?

firestorm · Post by **firestorm** » Fri Nov 20, 2009 1:40 am

guys, i have to stress, it is the update, or the direct x, which is needed to play. did both at same time.

this is a 10 month old laptop used solely for alleg. period. no windows updates were installed, no jave, no nothing.
my switch to mouse will not work, and as i stated earlier, i tried to defaul key map settings, which ive never ever changed anyway.
the js x52 is like 2 months old. whatys the point of plugging it into another computer, when i take my other js (x52 pro) and it responds exactly
the same. windows control panel sees them both fine, and it shows all buttons working on both JS. wife bought me a new one even tho old one was just fiine.
i am not a code guy, nor will i ever be. this new release just ruined alleg for me. period.

Zapper · Post by **Zapper** » Fri Nov 20, 2009 7:30 am

firestorm wrote:QUOTE (firestorm @ Nov 20 2009, 02:40 AM) guys, i have to stress, it is the update, or the direct x, which is needed to play. did both at same time.

this is a 10 month old laptop used solely for alleg. period. no windows updates were installed, no jave, no nothing.
my switch to mouse will not work, and as i stated earlier, i tried to defaul key map settings, which ive never ever changed anyway.
the js x52 is like 2 months old. whatys the point of plugging it into another computer, when i take my other js (x52 pro) and it responds exactly
the same. windows control panel sees them both fine, and it shows all buttons working on both JS. wife bought me a new one even tho old one was just fiine.
i am not a code guy, nor will i ever be. this new release just ruined alleg for me. period.

Well... Either you post the template or you go and make a post about your problem(this can involve harsh talk and name calling), You need to post the DirectInput.log into a

Code: Select all

 in the new post, the file is located in the folder with the alleg .exe.

Either way is a help others help you process..

Zap

Cortex · Post by **Cortex** » Fri Nov 20, 2009 9:58 am

firestorm wrote:QUOTE (firestorm @ Nov 20 2009, 02:40 AM) guys, i have to stress, it is the update, or the direct x, which is needed to play. did both at same time.
[...]
i am not a code guy, nor will i ever be. this new release just ruined alleg for me. period.

You'll have to be patient. There was a beta out for three months that you could have tested and reported the problem, then you wouldn't have to wait now. We're doing what we can, but I have to remind you that you could have most likely avoided this situation by spending half an hour to confirm that your system still works on R5 -- *before* we release it. We're not doing these betas to show off, you know...

Other than that, what Zapper said.

Storm Strike · Post by **Storm Strike** » Sat Nov 21, 2009 5:29 pm

My X52 throttle base isn't working any more either. I'm not using the joystick base, I'm using my old Sidewinder 3D Pro, but still using the X52 throttle base for throttle, zoom, sidethrusts, targeting, etc. Worked fine up until the R5 and directx updates. Updated the Saitek drivers and profile editor, but didn't help. WinXP64.

Post by **FreeBeer** » Sat Nov 21, 2009 5:35 pm

Storm Strike,

Please start your own topic. It keeps things cleaner for folks to be able to debug the issues. Use the template where appropriate. I expect they'll need to see your DirectInput.log file. Post that, too, in a

Code: Select all

firestorm · Post by **firestorm** » Sat Nov 21, 2009 6:51 pm

well, beta times were wednesdays, and i work harder than most. i never am home in time for betas.
whatever...
this is a setp forward at least, firstly people were telling me it was something i did unrealted to alleg.
i have already informed my squad i will not be playing anytime soon, if ever.
choi.

firestorm · Post by **firestorm** » Sun Nov 22, 2009 7:45 pm

try as i might, no mouse for sure either.

launched game w/o js.

notjarvis · Post by **notjarvis** » Sun Nov 22, 2009 7:53 pm

Fire - have you tried uninstalling the saitek drivers? see if it's the driver that's causing the issue?

Edit: removed snarkiness

firestorm · Post by **firestorm** » Sun Nov 22, 2009 11:10 pm

i removed the software and removed the device from the hardware manager, and
no change.