Thanks for the feedback. I forgot about being able to refuel; so used to saying rearm/refuel in the same sentence. IFF isn’t a big issue for me personally, don’t know why I put it at the top. My top two things would probably be being able to mark things with the HMCS and some sort of GUI overhaul.
Posts made by Fuzzysham
-
RE: Ff you could have one thing in the next update it would be…
-
RE: Ff you could have one thing in the next update it would be…
Once they added the ability to modify the order in which controllers are detected, that fixed a huge headache for me. Using my Warthog with TARGET was a pain to reorder controllers in Windows every time I rebooted. That was my single biggest complaint with BMS. Huge props for finally taking care of that.
With that said I’d still like to see some additions. Yes, I know this isn’t just one thing.
- Some basic form of IFF. It’s mildly irritating when AWACS says it is hostile only to be my own guy. I’m not looking for full IFF but some basic form.
- Ability to mark points using the HMCS. Being able to look at something and mark it would be so useful.
- Moving map display.
- Ability to rearm and refuel.
- Complete rework of the GUI. It’s low resolution and seems just overall old and outdated and could use a 21st century update. I did read a post a long time ago one here saying it wasn’t possible but I have faith in the BMS team to figure out a solution.
- Integration with Weapons Delivery Planner (and other useful tools).
- Dedicated multiplayer exe. I don’t really play multiplayer but I could see this being useful for people who do.
- 3D RWR audio https://www.terma.com/defense/airborne-audio-solutions/3d-audio-and-radio-separation/
- ALE-50 towed decoy. I read about this in Viper Pilot and seems like a useful addition.
-
RE: Weapon Delivery Planner released
Any chance we can get WDP to work with the latest Battle for Balkans campaign? I’m not at my of right now so I can’t recall what errors I get, I just know it doesn’t work. I play it in single player.
-
RE: Begging for some help from the BMS GODS!
Joy IDs has never worked for me. It sure would be nice if it did. Here is the way I get the controller order setup correctly. It is cumbersome at first but then you just get used to it. I’m running Windows 10 x64.
1. Open Device Manager
2. In a separate window Browse to Devices and Printers (you should see all your controllers and other things)
3. Right click and remove the device you want to be listed first; you right click and remove in Devices and Printers
4. Alt-tab over to Device Manager and right click in the white space and click scan for hardware changes; it will then re-add your device to the bottom of the controller list in Windows
5. Repeat this for each device…For me I have the HOTAS Warthog (stick and throttle), two MFD’s, MFG Crosswind’s and the Logitech G13. Every device is out of order whenever I reboot so if I want to get it in the correct order I will remove the joystick first, re-add and then remove the throttle, re-add, MFD 1, re-add, MFD 2 re-add, MFG Crosswind’s, re-add, G13, re-add. After I do that everything is in the correct order. If you do it enough it becomes second nature.
With all that said, if you can get Joy IDs to work then it would be much easier.
-
RE: Which Windows version are you using?
Windows 10. I’ve had fewer problems using BMS on Windows 10 than any other version of Windows (7, 8, 8.1).
-
RE: Iff you could have one thing in the next update it would be. (Archive)
Never heared about that! … I do not think so … IRL we just adjust the volume (one weaker one louder) and that’s it.
I just learned today this is real and even cooler than I thought. It would be awesome to implement this into BMS.
Further reading on it.
http://termanorthamerica.com/defense/airborne-audio-solutions/3d-audio-and-radio-separation/
-
RE: Iff you could have one thing in the next update it would be. (Archive)
“one” thing I didn’t see in this thread yet - joystick usability discussed elsewhere: option to smooth axis (for those spikey days) and identifying joysticks by id rather than order (for profile stability/exchange)
This.
I spend so much time reordering my controllers to be in the right order after a computer restart. It has become so bad that I dread rebooting my computer. It reminds me of the Falcon 3.0 days when I was 10 years old and had to do a selective startup into Windows to get it to work; I memorized each item back then. The reordering of controllers is such a pain.
It would also be nice to have an updated interface if at all possible. Running a monitor at 2560x1440 makes the main Window quite small.
Having Weapons Delivery Planner built into BMS would be a huge bonus. Maybe even expand the capability of it to include full mission planning.
Obviously updating the avionics to enhance the realism is great. However, there are some older parts of BMS that could use some updating to bring the sim as a whole up to date.
-
RE: Mouse Cursor Speed in 3D Cockpit
In the bms config file in beta settings:
set g_fMouseSensitivity 1.0 // 3D mouse sensitivity multiplier
I have no idea if this could help or if it works, I’ll leave that up to you as I have not messed with it
This works. I always felt the mouse was too slow in cockpit. I set mine to 2.5 and it seems about right now.
-
RE: Morphine's Profile
I also have Obutto and FSSB3. Works really well to have the FSSB3 anchored to the A-10 Obutto kit. I ditched the MFDs and G-13 and went 100% touchscreen with Helios.
Can you do me a favor and PM me a pic of your Obutto setup? I need ideas so I’m prepared next Tuesday when it arrives.
-
RE: Morphine's Profile
I actually figured it out. I went into the TARGET GUI and enabled the LED’s on the throttle via the checkboxes and then your script worked correctly. With that said, I don’t use the LED’s now. I use a hybrid of your script. I bought the TUSBA for the Cougar throttle so I can use it without the Cougar stick and I use the switches on the Warthog throttle with the FSSB R3 for the Warthog stick plus the MFD’s and your G-13 profile. Then, next week I have the Obutto cockpit coming so that will shuffle it all up. Without your script though, I would be SOL.
Re-ordering controllers in Windows is a huge pain still and there is no fix.
-
RE: Morphine's Profile
Challenge Accepted!
This is also something I’ve wanted to do for a while as well. Add the code below to the TARGET Script and the 1st (Top) LED will come on once you are in the deadzone and the remaining lights will come on once you leave the deadzone and activate the AB. In your controller setup screen set the AB detent when the first light is on and you will be good to go.
Add the code below between the following two lines in the TARGET Script:
SetShiftButton(&Joystick, S3);////////////////// AXIS CONTROLS //////////////////////////////
////////////////// LED CONTROLS ////////////////////////////// //initialize LED status all "OFF" ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1)); //set LED 1 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2)); //set LED 2 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3)); //set LED 3 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4)); //set LED 4 OFF ActKey(PULSE+KEYON+LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)); //set LED 5 OFF //LED Throttle Position Indicator; LED 1 - MIL Power; LED 1-5 AB KeyAxis(&Throttle, THR_LEFT, 0, AXMAP2( LIST( 0, 65, 75 ), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED1), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED1), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT-LED5)), CHAIN( LED(&Throttle, LED_ONOFF, LED_CURRENT+LED2), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED3), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED4), D(), LED(&Throttle, LED_ONOFF, LED_CURRENT+LED5)) ));
If you’ve changed the deadzone to something other than 65 - 75, you will need to adjust the vaules in the text “AXMAP2( LIST( 0, 65, 75 )” accordingly.
Well it has been at least eight months since I’ve played BMS because after I upgraded to Windows 8.1 I didn’t feel like going through setting up all my controls again. However, everything worked pretty much perfectly this time. This new code with the LED’s though is messing up things. If I utilize this code it causes my stick and throttle to become unresponsive once I hit the deadzone. If I don’t go into the deadzone with the throttle then everything continues to work. I copied and pasted the code exactly from here. Is the last long line supposed to be broken up into separate lines or something? Thanks for the help.
-
RE: Morphine's Profile
Fuzzysham sent me a PM with a problem he is having that I think others are also having. I’ve posted his PM here and my response so all can address their similar issue.
Unfortunately, your device is being recognized as the 4th DirectX device attached (when TARGET is running) rather than the 1st. First thing I would try is to unplug all other USB Game devices, reboot, and then plug your WH Joystick directly into a Motherboard USB port (the ones on the back of your computer near your Ethernet port, etc.) and not to any external USB hub or other front or back USB ports on your computer (as these are also considered hubs). Reboot your computer and do the same with the WH Throttle putting it right next to the Joystick. Reboot again. Now add your other devices to any other USB ports and one last reboot. Now if you got lucky, this may have re-ordered your devices so that the WH Joystick is now Device 0 and the Throttle is Device 1. You can see what the Device order is by going to using DxDiag.exe. To start DxDiag, go to your Start Menu and in the Search box at the bottom, type DxDiag and it should appear in the list above and you can launch it. The last tab called INPUT will list all your DirectX (DirectInput) devices attached. Under the column CONTROLLER ID, it will list the ID number and thus the order they appear to games (remember ID# 0 is the first device and so on). So if our trick worked above, the Joystick is ID# 0 and the Throttle is ID# 1. When the TARGET script is run the Thrustmaster Combined device should now get Controller ID# 0 in DxDiag.
If that didn’t work then you will need to edit the Warthog_DX.key file (with Notepad++) and the TARGET script (with Script Editor). In the keyfile you only need to edit the Joystick mappings. I’ve attached a spreadsheet that shows how the numbers are calculated. Since your Thrustmaster combined device is Device #4 then you need to add 128 to every number from 0-32. For example:
TG1 (Win DX1 = BMS DX0)
SimTriggerFirstDetent 0 -1 -2 0 0x0 0
Would be changed to:
TG1 (Win DX1 = BMS DX0)
SimTriggerFirstDetent 128 -1 -2 0 0x0 0
Same for the shifted layer buttons as well:
TG1 (Win DX1 = BMS DX0+256 = BMS DX256)
SimDoNothing 256 -1 -2 0 0x0 0
Would be changed to:
TG1 (Win DX1 = BMS DX0+256 = BMS DX256)
SimDoNothing 384 -1 -2 0 0x0 0
In the TARGET script, anywhere there is a DX# button, you will also need to add 128 to that number. For example:
//Paddle/S4
MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX4, 500));Would be changed to:
//Paddle/S4
MapKey(&Joystick, S4, TEMPO(PULSE+F12, DX132, 500));If you have other DirectX devices like the TM MFD’s attached you will probably have the same problem and have to edit the key file to fix their numbers as well using the same process. However, you may need to experiment with the numbering as when you run TARGET the MFD’s don’t move to DirectX ID 1 & 2 in DxDiag, but that is how the game sees them and how the keyfile controls them. You may also need to experiment with your numbering for your DirectX devices as it may also have some differences in how the game sees it versus how DxDiag reports it. A quick test is to go into the Controller Setup screen in the game (with TARGET script running) and push the first trigger button on the Joystick (just to the first detent) and see what the game reports that button number to be (e.g. 128 ). The same can be done with the MFD’s but use the upper far left button. You will then you will know where to start your numbering for each device.
Hope that helps and good luck.
I appreciate the detailed response. That really helped a lot. I knew in theory what had to be done but didn’t know the best way to go about it. Your spreadsheet was very useful. I have used your profile before, last May-ish. It worked flawlessly before. Since then, I have gotten three ten port USB hubs that are full plus all the 12+ ports on my mobo and upgraded to Windows 8 and an FSSB R3 for the Warthog. Makes sense that it did not go so smooth this time for me. I was using the Cougar throttle with the FSSB R3 Warthog but the Cougar throttle is just not cutting it anymore. Yours definitely is the best profile.
I spent from 9am to about 6pm trying to get this to work, as I had nothing better to do today. First it was editing the key file but then the shifting wasn’t working then it was re-ordering the USB inputs, among other things. I finally got it working and now I’m gonna pass out from the mental strain of so many numbers. Ultimately, I did it by re-ordering all the inputs. I actually found the easiest way was to right click and remove a device in “Devices and Printers”. Once I got the stick and throttle working, the MFD’s were not in the correct order so I kept removing and letting it re-add itself until it finally put itself in the right place. Now I know the easier way. I am terrified to reboot my computer for fear of screwing it up again. I can’t even imagine how borked the controls for DCS are now.
Thanks for helping me get it working again.
-
RE: Morphine's Profile
Very nice Fuzz…. And I’m jealous of your FSSB. I’m hoping the RealSimulator guys do a version for the Hog Joystick.
I really hope they make one for the Warthog as well. The Cougar’s base doesn’t have enough surface area to stay in place using higher resistance. It really needs to be attached to a base like the Warthog’s. Right now I use a 25 pound weight on the front of the Cougar to keep it in place. Quite annoying. The FSSB does rock though.
-
RE: Morphine's Profile
Just wanted to say thanks for the profiles and the setup ideas and tips. The G13 for an ICP/DED is an especially good idea and works out wonderfully. Also, I am able to use the FSSB with the Warthog throttle. I wouldn’t have been able to setup my controls without your help and profiles. See my setup below inspired by yours (mainly the G13).
-
RE: Morphine's Profile
Thanks for the help. To be honest I don’t know a thing about how to edit the key files, script editing and DX shifts. I’ve looked at the key files and I see lots of numbers like 0x0001 or whatever. I haven’t figured out what all that is attributed to. The scripting as well is foreign to me. I’m not asking for an in depth explanation, I’ll read up on it all. Thanks for setting me on the right path though.
I sometimes put my Warthog stick on the FSSB. I like the feel better and the push of the CMS button. I was trying to get Thrustmaster/Guiliemot to sell me just the Warthog stick. As we all know, they don’t do that. I’m going to keep asking over the months until they say yes
-
RE: Morphine's Profile
This is a great profile, thanks for it. I had some trouble tweaking it and I’m not even sure I did it right. I recently bought a used Cougar and already had a Warthog. I just wanted the Cougar for the throttle. I recently decided to upgrade the Cougar to the FSSB. It’s awesome. Anyways, the Cougar throttle sucks, the pots continually spike and the antenna elevation has no center detent. I couldn’t take it. So I attempted to use my Warthog throttle with the FSSB modded Cougar stick using this profile. Yeah, that didn’t work so well. I think I got it working now, except for the push of the CMS button for the jammer. Also, on occasion, the throttle base buttons don’t work as intended in the profile, not sure what’s up with that.
What is the “ideal” way to tweak this profile for it to work with the Cougar stick and the Warthog throttle? Thanks.