I have complained - though my frustration is that if you build a new PC, reinstall your O/S or have to plug the controller into another USB slot than the one it was in when you assigned it, you have to do it all again.
If you keep exactly the same config (hardware) it’s fine. But who does for any length of time? I certainly don’t - though I have been trying to after the last couple of times I had to reassign 6 controllers for 28 aircraft.
Anyway, OT - I do wonder if the BMS config couldn’t be made a lot more user friendly.
How could the software know what you would have assigned, those are files kept in the local OS structure, which either doesnt exist or what you destroy when installing. You can just back them up yourself you know, right?
I do back them up - have done from the start, but that still takes over an hour to reassign the profiles when reinstalling.
What I found was that under several different circumstances, the number in curly brackets after the name of the controller (in the DCS World controller assignments GUI) changes.
I originally thought this was fixed and was the ID of the controller - but I think it is actually the ID of the USB socket, and that’s why it can change (this is guesswork, but can’t see another reason why it would change).
If you have everything the same as before, the assignments will be automatic - you just copy your profile into the new profiles folder and you’re sorted. However, if that number ID has changed, DCS World sees it as a different controller and you get the default assignments - even if you copy in your old profile.
One quicker way is to see what the new IDs are and rename all your profiles to the new one, so they will be recognised and loaded correctly in the various modules, but again, it’s an extra hassle.
I think the IDs in curly brackets are assigned by the operating system. Hence on a different OS installation, same device gets new ID. On the same installation, it will keep the ID no matter which USB port you plug it in to (which is the real benefit from the state before ED and other developers adopted the device ID idea).
Is there a terrain that looks the “best”? Or are they all of similar quality. So far the cities and the water look the worst, just flat sat imagery. Sorry I missed the heyday of BMS, experiencing it for the first time several years too late.
There are some, like Ostsee, that have their cities completely made from 3D objects, and most map objects made in 3D. However, there isn’t anything really that can compete with the modern flight sims. DX7 really shows in BMS, although they made it look as nice as they can, given the limitations.
There are lots of differences but I cannot recall any that apply specifically to your problem. However, the issue I am guessing has to do with the keyfile you are using as default. Check your setup and see if you are using BMS.key or some other. It doesn’t really matter but you do need to be sure which key combo puts the throttle in IDLE and that can be different depending on the *.key. I didn’t have a problem with the F-16 when I upgraded to 4.33 but I DID have the problem when I tried the new F-18. It turned out that I was using ALT-J (I think…its been months since I have run BMS) instead of the current combo.
Okay I’ll check that - thanks. I had actually set the idle detente to a controller key - did that yesterday. I did it for both 4.32 and 4.33, the former is also working fine, but not 4.33 - so I will look at the key files.
I’ve been BMS’in lately, most of the time in Korea EM 1989 (available here: https://www.bmsforum.org/forum/showthread.php?29461-Korea-EM-1989-Update), which is quite fun since it’s a bit easier without all those modern SAMs and weapons systems. But back on topic - The only difference I can think of during start up is that you have to go to TEST page and clear all the BIT errors - but that have nothing to do with the engine starting. The rest is basically the same. I didn’t have any problems at all, I\m using mouse in VC though. When I start JSF I put my throttle mid-way, click on the idle detent (ALT-I by default) move the throttle slightly forward and immediatelly all the way back. It works 100%.