Opening an FDS instrument window by double-clicking an instrument with a modulation rate of one thousand or greater causes the value to change back to 1, because the comma separating the thousands gets interpreted as a decimal point. Perhaps this isn't an issue on systems set to a different language where the separator is a space (I haven't tested this), but I'd wager a lot of users live in an area or speak a language that's problematic.
EDIT: Apparently, this was reported by rainwarrior before. My bad for making a new thread. The problem still exists, however... Is it bad doctor?
I should take this opportunity to ask for an option to swap Z (C-low) and Y (A-high) for "qwertz" keyboard users because yes, a different language setting does solve the problem but it also messes with . - , and stuff like that (0 is also gone from my keyboard then)
The latest beta was supposed to contain a workaround for this issue, but that only works when space is used as separator. I didn't realize this was different for different countries. Anyway I found a way to entirely disable the thousand separator so that should solve the problem.
