Han, rethink the position about joy ID and BoS/M

[Potenz]

A few weeks back i asked about if it will be changed the Way BoS/M recognizes the Joystick ID in win 10,

the answer was that not many people uses win10, Well i think is time to rethink that position and prioritize it

as now Win10 x64 has almost 30% of steam users.

 

 

Regs

 

Potz

Edited December 3, 2015 by [AoA]Potenz

[-TBC-AeroAce]

Love the stupidly low Windows 8 scores

 

lol there are 1/2 as many linux users to windows 8.1

 

Also for this to be valid you need to know how many non-steam users there are which i suspect are the majority 

Edited December 3, 2015 by [TBC]AeroACE

[Nil]

I use steam, a lot! (not for this game).. and have a retail version of Win 10 x64 pro?

[No601_Swallow]

And I'd assume that most of us simmers upgrade pretty frequently, given that this particular genre isn't very forgiving in terms of  system requirements.

 

Pershonally, I know mosht if not all of my IT upgradesh ever have been becaush I wanted my shims to run shmoother.... 

[SharpeXB]

From the reports I've seen, that joy# shuffling problem afflicts Windows 8 as well.

[BMA_West]

In win 7 it only happens (on the 2 rigs here) when a new usb appliance added or shuffling of the existing.

You guys mean with 8 & 10 this happens on its own like rebooting?

[Finkeren]

In win 7 it only happens (on the 2 rigs here) when a new usb appliance added or shuffling of the existing.

You guys mean with 8 & 10 this happens on its own like rebooting?

 

I can confirm this. In Win7 it happens when you plug in a new control device.

 

It would be great to have this fixed, even though the fault lies with Windows and not BoS.

[SharpeXB]

You guys mean with 8 & 10 this happens on its own like rebooting?

Right. Sometimes W10 and 8 will change the joy# on its own even if the devices remain connected and no other device is added.

[Jade_Monkey]

Ive only had this issue when unplugging the devices on Win10.

 

It hasnt given me any headaches, maybe a simple reboot once in a couple of months if i have to play other games where the hotas interferes with the keyboard and mouse inputs.

[71st_AH_Mastiff]

This is amicrosoft Windows 10 issue this is why I down graded back to 8.1

[dburne]

Right. Sometimes W10 and 8 will change the joy# on its own even if the devices remain connected and no other device is added.

 

I have never seen that in 8.1...

Been running it for 2 years now.

Edited December 3, 2015 by dburne

[SharpeXB]

I have never seen that in 8.1...

Been running it for 2 years now.

It's hard to figure why this affects some people and not others. If you look at the RoF and CH forums for example you'll see many people having this problem. It affects any game that relies on the generic Windows joy#, like this game, Star Citizen apparently does too. CH even tested this and found the glitch themselves.

[Voidhunger]

Hmm, I have never seen that on win 7-10.

[Livai]

 

 

Potenz' timestamp='1449103433' post='310606'] now Win10 x64 has almost 30% of steam users

 

Nice try if Han say yes to Win10 x64. And next follow will be where is the x64 support?  

 

BTW Games come out with DirectX 12 support next year and more players will move to Win10. 

[Dakpilot]

Apart from 1 instance of throttle reversal way back in early access i have never had any issue with devices 3 axis throttle quadrant and MSFFB 2, never unplugged them and they just functioned as they should

 

(touch wood)

 

This was with Win 7 and now for last couple of months upgrade to Win 10

 

Bos installed on separate SSD from OS (not under default 'Program Files')

 

Cheers Dakpilot

[Finkeren]

Nice try if Han say yes to Win10 x64. And next follow will be where is the x64 support?

Actually, Han has confirmed in the questions thread, that they do plan to move to 64bit, just not this side of BoM release.

 

64bit is coming.

[Quax]

And please add the "swap axis" checkbox to support the FFB2 ! More and more hardware disable the automatic recognition of this old stick. Without the chance to swap axis manually, it will not be usable anymore

 

(DCS did solve the problem that way since years)

[SharpeXB]

I was having that joy# shuffling trouble in Windows 10. They would change almost every time I restarted the PC sometimes they would change when just opening Device Manager. I went through every solution imaginable with no luck including removing and reinstalling all my USB drivers etc. The most sucess I had was with the solution Gramps recommended. Basically restarting the PC until it's set correctly and then locking it in with the Fast Start setting in W10.

 

But now after installing the big November Update (service pack) for Windows 10 the problem seems to have vanished. So there must be a solution which happened there somehow. The big update seems like it replaces many drivers on your machine.

 

Is there anyone still having this problem after the W10 November Update?

 

It would be a very good thing to update the joystick mapping system in BoS to be like other games which recognize the actual device name and not just the joy# because no matter which version of Windows you're using, if you change devices, add or remove one, those joy#s will change. Han did already said they plan to do that.

[71st_AH_Mastiff]

remember adding in 64bit code will at the very least take up to 2 years? no?

[Finkeren]

remember adding in 64bit code will at the very least take up to 2 years? no?

Don't know. But then again, we have no idea how long they have been working on it.

[Potenz]

This is amicrosoft Windows 10 issue this is why I down graded back to 8.1

is not a windows issue, the problem is the game recognizing the joy# and not it vendor identity

[Finkeren]

is not a windows issue, the problem is the game recognizing the joy# and not it vendor identity

The very fact, that we can't assign our own numbers in Windows anymore is utter BS.

[Potenz]

I don't why they never implemented this, even warthunder recognizes periferals by it names