Raeldor

Hmmm, it's been fairly ok for me so far except for the big black box. But since it's working with 2020 I guess it's obviously ANOTHER 2024 issue. 😞

Works great for me in VR in FS2020, but in FS2024 the frame rate goes to hell in VR depending on where I look. RTX3090. Anyone else having the same issue?

Appreciate the replies, thank you. This is a setting I need to get my force feedback stick to behave properly with trim. I hope this is resolved soon. 2024 has been a massive downgrade for me so far. 😞 Thanks

Does anyone know where this resides now for the included content? I need to modify the elevator_trim_limit, but can't find the file anymore. Thanks!

I don't think that's the problem in this case. It doesn't seem to be assigned anywhere else. Even if it is assigned somewhere else, or even not assigned at all, I should be able to see the controller movement in this screen... The odd thing is, I KNOW it's detecting movement from the axis because if I move it when trying to assign a different device it says 'WRONG DEVICE', so this definitely smells of some kind of bug. EDIT: It seems to be the 'scanning' that's the problem. I can manually assign the control axis and it seems to work. So a bug with scanning?

They all show up and function correctly under 'USB Game Controllers' in Windows. They all show up inside MSFS 2024. But they do not register any buttons/axis changes. When I use the Hardware button to see the graph, the dot is not moving when I move the control.