Strange... ship is behaving on it's own... (cargo, silent running, lights...)

I've noticed after a long absence weird things.

Only after I returned my exploration data to the current CG, I have started to experience strange things:
- Cargo hold is opening without my input.
- Lights are activating without my input.
- Silent running is activating without my input.

I'm using a X55 hotas with some macros, only Silent runing is macroed. The funny thing is that Silent running is macroed to a ticked-button that sends "N" continously to windows. When it activated, it was only for a milisecond.

It is really strange. I first though that my bluetooth keyboard (in another room) was being pressed, but I double checked and it was powered off.

This strange behaviour only happens inside coriolis stations (atm).

:tinfoil... I had some exploration data from those closed sectors on 2.1. I came from Veil to Pleiades to Witch Head and I had that exploration data on my ship banks. I went just near Betelgeuse pre 2.1 in order to experience with VR the Vive suposed bugfixes on 2.1 and once 2.1 was launched I just went to Betelgeuse and back to the bubble.

Anyone is experiencing this issues?

(Though I have voice attack installed it's not activated, I still need to configure it)
 
google x55 ghost keypresses.

its a pita and mine did it all the time on my old PC untill i started using my usb 3.0 ports.

i have not tried changing ports on my new pc.
 
This happened to me with my X-55. Once on plugged the X-55 into an powered USB the problem went away...

It is not the case, it's in a powered port from the mainboard (ASUS Maximun Hero VIII), not any kind of hub, and has never *never* failed before...
I will switch to another port or to a dedicated port on a powered (4moles) internal PCI USB 3 card. Thanks for the sugestion.

Have you tried asking the ships computer if it would mind opening the cargo bay doors?

That's why I carefully stated that VO is not active. I've a 19m/o baby and I need to play quiet... :sigh:
 
You should do what Obsidian suggested, may help the problem.

: Puts on tinfoil hat :

Take a good look around your ship, in all those dark places.

Make sure there are no strange computer programs present on your computer, like Hal or something :) .

Also, if highway to hell starts playing over the ships intercom, run, get out out of there!
 
Last edited:
Yes, it is a ghosting problem caused by insufficient power supply.

Either plug the joysticks into the 3.0 USB on the MB (On the back of the case, not the ones on the front of the PC) or buy a USB hub with power supply (they're cheap)

edit. so many ninjas!
 
Last edited:
Open Notepad (if you're on PC), make sure the cursor has input focus (click in the notepad window), and walk away for awhile.

with the exception of CTRL, SHIFT & other invisible characters, notepad will show what your _collective_ set of devices (which produce keystrokes) are outputting - on their own.

it's also a good tool to try your fixes / definitions.

-Slick
 
Thanks to all the suggestions.

I had never experienced this before, I have not changed the USB ports nor anything similar.

The only difference in my setup now is that I have a Vive linkbox plugged in (the Vive itself is not pluged to the linkbox), but this is on a dedicated PCI USB3.0 card so *should* (ehem, windows...) not affect the X55 ports (the same ports used the last 6 months)

I have double checked and I have no keyboard mapings on lights nor cargo (only silent running and the panels) so it's not ghost keypress but ghost button press on the X55. This only happens with controls mapped to the top / left buttons on the throttle and the silent runnig button (for me is the toggle button on the throtle, just above the two dpads).

I will discard the thargoids then. Meh... would have been funny if it was intended heh
 
so it's not ghost keypress but ghost button press on the X55.

erm this is exactly what people mean when they say ghost key presses.

As i understand it the X55 demands more power than it is supposed to for the usb2 protocol and as such some mobos struggle to deliver its requirements.

the other possibility is it is the wiring throttle loom issue also which the X55 suffers from, and i also had this problem with my old X55. you better hope this is not your problem however is this is new throttle time :(

(the wires crack and buttons stop working when your throttle is in certain positions, but further more, sometimes you get random buttons on the throttle firing off, presumably because sometimes the bare wires (bear because the plastic has come off) cross talk with each other.

PS I have a 6 month old myself - or will be on weds anyway... so i feel your pain ;)
 
Last edited:
It is not the case, it's in a powered port from the mainboard (ASUS Maximun Hero VIII), not any kind of hub, and has never *never* failed before...
I will switch to another port or to a dedicated port on a powered (4moles) internal PCI USB 3 card. Thanks for the sugestion.



That's why I carefully stated that VO is not active. I've a 19m/o baby and I need to play quiet... :sigh:

I think Nerwan was making an amusing reference to a scene in '2001 A Space Odyssey'. Or, at least, I found it amusing! :)
 
Thanks to all the suggestions.

I had never experienced this before, I have not changed the USB ports nor anything similar.

The only difference in my setup now is that I have a Vive linkbox plugged in (the Vive itself is not pluged to the linkbox), but this is on a dedicated PCI USB3.0 card so *should* (ehem, windows...) not affect the X55 ports (the same ports used the last 6 months)

I have double checked and I have no keyboard mapings on lights nor cargo (only silent running and the panels) so it's not ghost keypress but ghost button press on the X55. This only happens with controls mapped to the top / left buttons on the throttle and the silent runnig button (for me is the toggle button on the throtle, just above the two dpads).

I will discard the thargoids then. Meh... would have been funny if it was intended heh

The wiring masksmakes sense... That's why only happens at stations.

I will contact support then. Thanks!
 
Back
Top Bottom