Saavedra

This mod looks positively mouth-watering, but I´m running into some issues with crashes and the like. I am working on those still, lowering settings here and there. But there is one thing I don´t think lowering settings will help me with: mission start time. I´m afraid that starting a CAS mission at five in the morning on an A-10, when it is pitch-black and I can´t see past my cockpit is... a bit too much of a challenge. Is there any way to change mission start time?

I already do this with SF2, though. Granted, I also use mouse and keyboard at the same time (easy to do when you know what you are going to need when), but the Xbox controller is perfectly functional for SF2.

I haven´t tried it out yet and probably won´t because it would be a pain in the ass to uninstall and install again to test it, but I´ll keep it in mind for next time. Thanks a lot for your reply.

Having a Xbox 360 controller instead of a full-blown HOTAS is the only thing keeping me away from playing this... and yet, it being on Steam for 9,99€ is one hell of a siren call. I may dare go for it despite that limitation. I have heard nothing but good stuff about the game. In fact, it has something that makes me think it may well be better than DCS, which is the whole dynamic campaign deal it has going on. I read somewhere that DCS was about learning to fly aircraft, whereas BMS was about learning to fly fighter aircraft, precisely because DCS feels stale to some people, whereas the dynamic campaign for BMS makes it feel more alive. Those who have played both games here can surely offer a more informed opinion on that than me. And I must say, I am really impressed at how games as old as SF2 and specially Falcon 4.0 still hold themselves up as quality products going a bit beyond being pure entertainment.

After several months without playing SF2, and having upgraded my PC and gotten a new XBOX 360 controller, I decided to get back into the action. However, something weird is going on with the gamepad (yes, I know, but no, I´m not buying a joystick). When I install the game and the window pops up allowing me to play the game immediately, I can go in, configure the buttons, sticks and triggers, and everything works properly. However, when I start the game normally using the exes, the whole thing goes to hell. The sticks don´t work properly (in fact, I lose sensitivity, meaning the plane will only do extremely gentle or extremely hard turns) and the buttons configuration is all sorts of messed up. Just to give you an example: I use the shoulder buttons (L1 and R1) to reduce and increase thrust respectively. Normally, when I press those buttons in the controls configuration, it will name then Button 4 and Button 5. However, with this strange error, it will call them ALT+Button 4 and CTRL+Button 5. Other controller buttons will be named AV PAG and RE PAG (so, keyboard keys... for no reason I can discern), and so on and so forth. I´ve experimented with this a bit already: I have deleted both the game and the folders in /users/ several times and then checked if it was a specific update somehow hurting the original installation. So far, the error is being consistent, and the only exception I can replicate is entering the game through the prompt right after installation. Note that while entering the game through that prompt will let me play properly, every single other time I enter the game (through the exes, as normal), the controller will stop working as it did before, and the buttons will have returned to what they were before I configured anything. Now here is the kicker: the old Trust GTX 28 controller I played the game with all those months ago... it works perfectly fine! In fact, I can plug in both controllers at the same time and the GTX will work while the 360 doesn´t. And bear in mind that my 360 controller has never given me trouble with any other game. I´ve noticed this in the files section: https://combatace.com/files/file/12963-360-controls-for-strike-fighters-2/ So, I assume this is a problem inherent to the 360 controller, and that it can only be fixed through that? Because in that case, I think I´ll be returning to my old GTX. It´s positively old and the control surfaces are not quite as smooth, but hey, if it works...

Look in your controls menu for a key that reads "Last Radio Target". That, as far as I understand it, will designate as target the last entity mentioned in the radio. When an enemy launches a missile at you, using this key will automatically select the launching platform. If the platform in question is a NATO plane launching from afar, and you have no RWR sound, chances are he just launched an AMRAAM at you. It also works with SAMs and MANPADs, so you can discern between IR and radar-guided missiles.

Tanks in the Black Sea Crisis mod will shoot their machineguns at you while engaging their opposite. Infantry in Vietnam Expanded shoot as well (both cases are particularly noticeable if you are flying a helicopter, since you spend more time within their range). I do not remember if infantry can fire RPGs at you, though. I´d swear I´ve seen trails in VEx and Desert Storm.

Some basic tips: 1- Use communications. Tactical control can tell you where the closest bandits are, and you can ask your wingmen to engage them on their own or cover you. 2- Sidewinders are for close shots from the rear. Until the Sidewinder L, most famous for its use in the Falklands, no Sidewinders can lock enemies from the front. Sideshots are tricky and I do not recommend them with any sort of missile. 3- Remember that accomplishing the mission is the most important thing here. If you are engaged in a dogfight after killing your target, why stay around?

Ah, radars that you cannot detect at the appropriate distance for your HARMs. The bane of my life...

Pretty much. You get shot down. Is your pilot killed? Sorry, campaign is over. Is your pilot captured? Hit "Refly", take a screencap of your pilot´s current status, and fly a helicopter mission to see if you can continue flying with that pilot in the future, or if you were unable to recover him/her. Ideally, you would use two transport Hueys escorted by two gunships (Hueys or Cobras). The idea is flying to the point in the map where your aircraft went down (or the closest point on land if your plane went down in the sea), and landing with your transport Huey there. Wait for a few seconds, then take off and return to the closest friendly base or ship. If you lose two choppers/transport choppers on the way in, the mission is aborted (the LZ is too hot). If the transport chopper carrying the captured pilot is shot down with no survivors, the mission is aborted. If you return home with the captured pilot, however, your pilot has been rescued and you can continue the campaign. Say, Stratos, are those troops I see sitting on the edges of the Hueys? And another question: has anyone gotten the doorguns on the Hueys to work?

It occurs to me that we have non-Skunks helicopters in the files section such as Hueys and Cobras. Depending on timeframe and conflict, it would not necessarily be out of the question to postpone pilot retirement until you have tried a CSAR mission. Just hit "refly" and take a screenshot of your pilot before doing a rescue mission. If the CSAR fails, that´s the end-state of your pilot. If the CSAR succeeds, you continue flying. Conflicts like Vietnam and Desert Storm may be considered particularly conducive towards adding this mechanic to Dead is Dead.

Thanks for the replies. As soon as I have some free time, I´ll get to fixing stuff.

Recently, I downloaded Yakarov´s awesome Cobra mod and added it to Vietnam Expanded. I realized that by doing this, I could make combined flights of Cobras and Hueys carrying out CAS missions in South Vietnam. However, when I tried to do it, I found two problems: 1- If I chose to fly the Huey as Army Aviation Unit (nation), I could not choose the Cobra for my wingmen. I switched to USMC, and I could make flights combining these two. However, this led to the next problem. 2- I could set up the mission with one chopper, but then, the weapons they could take would correspond only with that chopper. The other one would be unable to take those weapons. All the stores/pylons would be greyed out. So here is my question: how can I set up things so these two helicopters can use the same weapons? Is this related to the weapons´ nations and can I fix it by simply fiddling around with the ini files? Does this require some other form of heavy editing?

We already have a Falklands/Malvinas campaign, so I´m guessing he means expanded terrain? For example: you cannot use land bases with the optional Vulcan bomber because... well... you would have to take off from an island that is simply too far for the map to include. I´m guessing he wantsa map big enough to make this possible, for example?