Got to tinkering around with Spad.next and messed things up. I wasn’t content, once I got the Saitek radio panel working, to just leave all else alone and somehow caused this to happen. If I start pressing around, it crashes to desktop.
Short of maybe doing a complete reinstall, any ideas as to what I may have done. I unistalled Spad and the bridge, and deleted stuff in the wgs folder. Still no good. I can fly as things are (I’m so tired of tinkering and tweaking), but I hate to leave something broken unfixed.
Are you under the SU2 beta v1.4.10.0 ?, if so it is a known issue: SU2 1.4.10 breaks control bindings!
Yes. But, this is the first I’ve heard that rolling back kills all the assignments.
So you rolled back from the SU2 beta to SU1? If so that is concerning.
Sorry for posting on this problem, since I see it has already been well documented.
I did make an effort to find previous posts, but I believe I wasn’t wording the inquiry well enough.
Switching the filter to “assigned” did bring them back, but I didn’t look beyond that. I figure since the bindings obviously are still there and working, I will leave well enough alone.
Yes, best to not touch until a forthcoming SU2 beta fixes that.
I rolled back back to su1. I had ti back up my controls and then restore them to get everything back. The profiles you made are just not visible but are still there. Used the tool on flightsim.to to backup and restore
