have SL pay atention to an specific joystick and not other

when using PPJoy to emulate joystics, with GlovePIE to controlt he virtual joystick, with a Wiimote installed on the system (this is on WInXP), SL will either not read any joysticks, or will read the Wiimote, that doesn't return any data in the standart format for joysticks (needs a program that can understand the "language" the Wiimote speaks, in this case, I'm using GlovePIE)

my question is, how can I have SL read another joystick without uninstallign any of the joysticks I have instaled right now?

(it once read perfectly my MS Sidewinder, but that was in a period I didn't had the Wiimote installed, so the Sidewinder was the first Joystick on the list on Window's Control Panel)

BUMPIDY-BUM!

please, can someone help me figure out how to have SL read the joysticks I want it to read? the way it is now it is either reading what isn't meant to be read, or isn't reading anything at all

is there a "input devices Linden", or office hours about input devices or somthing? or is there somewhere I can read info on how to troubleshoot and setup my SL to read joysticks?

Using windows, have you selected the Glove as the default input device?

Assuming you have a Game Profile programme with the Glove, you should be able to asign the Axis that apply to the SL Client interface. Save the profile and asign that to SecondLife.exe so it loads eachtime you load SL.

I don't have any gloves, GlovePIE is a program that can read aswell emulate several types of input devices, I use it to convert Wiimote data into joystick data, for that purpose it uses a program called PPJoy, that can deal with parallel port joysticks (hence the name) aswell work as a virtual joystick, propperly coded programs and games see it as just another joystick on the system



ps:btw, on the latest RC i could confirm it is trying to read the non-operational "Bluetooth HID keyboard" the system installs when i connect my Wiimote

I assume the parallel port doubles up as a GamePort?. If so, have you altered the EEP/ECP settings in the Bios? Those settings are to make the port bi-directional, which unless you are using force feedback, may confuse the controlling programme. Most modern controllers use a Dedicated GamePort, which also doubles as a Midi Port from a soundboard.
You may also find there is a IRQ conflict. With the limited amount of IRQ (Interupts to CPU clock cycles for system timings), many are stacked. Use system properties to what IRQ your PPJoy is asigned to, and what is sharing it. Reasigning IRQ's isn't easy, as you can simply move the problem elsewhere.

I don't think it is like that, joysticks that are connected thru the parallel port aren't recognized by most programs and such like normal joysticks, that is the reason for the necessity of programs like PPJoy

I haven't touched any BIOS setting, and I'm not using any paralell port joysticks

you read the part I said I'm using PPJoy to create a virtual joystick right?

SL did read my MS Sidewinder joystick when I didn't had the stuff thatget installed when you first connect a Wiimote on the system

and lots of games and program can see and read all the joysticks I have on my system without a glitch, so the problem is most likelly on SL

SL's client outputs to the OS and uses the API calls, it's been that way since conception, hence why we do not have a prolifercation of drivers for every programme we install covering every printer made (Old DOS), only the drivers for the hardware. The OS interprets the programmes API call comand and interfaces the hardware through its own native drivers. I would suggest it's the hardware/drivers and not SL's Client.

The reasoning for that is simple, the output from SL's Client through the OS works fine for the intended purposes, i.e. joysticks, gamepads etc. All of which work in Analogue and not digital, as the interface is Analogue. Have you the option to switch to an Analogue Device either via Hardware, or through the Drivers?

With USB devices this is taken care of via the drivers.

I have 3 diferent types of joysticks on my system, gameport, USB and virtual, none of those are read by my SL, on the latest RC it states which Joystick it is reading (not sure if it would list more than one when working propperlly), and it isn't any of those, it is reading only the one that isn't a joystick at all, the Bluetooth HID keyboard that is installed as a sideeffect of connecting a Wiimote to your computer, but that doesn't behave like a keyboard like the name might sugest nor as a joystick as it's presence on the game device options control panel thingy could imply

I'm not familiar with the devices you are talking about. The only things I can think of are...

Either

A IRQ conflict and/or, the device trying to connect to a COM port.

The drivers are only DirectX compatible.

Drivers incompatible with XP.

The device is digital and will not respond or be seen (handshake), by the analogue output API calls from the Client to the installed drivers.

games and other programs recognize the joysticks properlly, the issue isn't the joysticks

and btw, you're not familiar with USB nor gameport joysticks?! 0.o

I am, many years ago I used to write DOS drivers for gameports, even extending the 8th bit in some ports..... I am just not familiar with the particular equipment you are using... I'll go silent and let someone who does know your particular equipment add to this thread.

I see

anyway, the issue isn't the equipaments, is how SL is handling their presence, they work just fine on other programs and games

When you blame SL and not the equipment, the one thing you have overlooked, is SL is a OpenGL platform and not a DirectX platform. The vast majority of 'games' over the past 10 years are DirectX and the GC etc, manufacturers have been writting their drivers for that platform. It is doubtful OpenGL will go beyond version 2.

One last ditch effort to assist you with this issue, try install the latest version of .NET Framework (version 3). You can get that from Microsoft http://www.microsoft.com/downloads/details.aspx?FamilyID=10CC340B-F857-4A14-83F5-25634C3BF043&displaylang=en
That will update the Windows platform with the latest OpenGL runtime libraries.

isn't openGL just for graphics?

No, OpenGL is a platform. Net Framework is the API between the OS and the programme, supplying runtime libraries.

ok, I installed the latest version and still no change :/

Did you check for IRQ conflicts with it all loaded? Even IRQ sharing (which is very common) can cause a problem. The introduction of Windows XP and other non-DOS OS's, overlay IRQ's removing the limitations of only having a few available. If your intermedetry programmes are working at low level, they maybe trying to reasign the IRQ.

Are the drivers for the hardware, XP compliant and upto date?

One last ditch effort to assist you, have you tried a simple joystick to make sure that the FlyCam option works with your system configuration?

how do I check that?


I would think so, but I'm not sure, where do I check for that?







when it was only one joystick installed on the system SL read the right one, my guess is this might be an issue that happens when more than a single joystick is present on the system


(remembering that other programs and games do recognize all the joysticks without issues)

You can install this software for hardware/software information at quite a low level http://www.sisoftware.co.uk/

Check with your hardware vendor for the latest drivers.

'when it was only one joystick installed on the system SL read the right one, my guess is this might be an issue that happens when more than a single joystick is present on the system
(remembering that other programs and games do recognize all the joysticks without issues)'

This maybe the issue, SL's client cannot recognise more than one device, 'other' programmes may, as they are probably dual control compatible, or DirectX platforms.