wowbagger

Yes, I agree separate issues in separate threads. I would not have posted in here if I didn't think the problems might be related.

I'm not sure if it's related, but binding the range and the wingspan to rotary axes shows similar problems. You can bind them without issue, but the game is only reading a tiny portion of movement in the middle of the axis. So for example as you turn the physical axis from 0-40% nothing happens, then from 40%-60% the wingspan dial goes from 0-max, and then 60-100% nothing more happens. No combination of saturation, curve, and deadzone makes the response more linear across the range.

Agreed. Hope this doesn't go unnoticed.

That sounds good for co-op and multi ... and real world. Have to mess around with the AI wingman and Tacview to see if the respective WCSs both make the same priority assignments.

Ya, why are you so continually caustic? People who like pressing the same sequence of buttons over and over again from rote memory and take pride in doing so must rock back and forth a lot, and lead very empty lives. See? That's not nice or appropriate either. Why do you continue to make snide comments about others and then hide behind "I don't care what others do. I'm just having fun."? Clearly you seem preoccupied with how others use DCS. Live and let live.

That makes no sense whatsoever.

Ya, FFB in the gazelle is a total disaster, with it on it ruins even non-FFB handling. But with curves and tweaks (and FFB banished) it can be fun to fly - whether realistic or not I can't say - but fun, yes for me. However I don't enjoy combat in it. Ka-50 is the module I have owned the longest. Never really got into it because it is so heads down staring at the video screen - ya, I know that's not really a fair or accurate representation. I guess if the campaigns are good enough it could be worth delving deeper.

To get your wingman to fire on a particular target in single player, would you switch to STT and choose attack my target (or whatever the order in DCS is) and then switch back to TWS and choose next target as RIO, so you don't both fire on the same one?

I've come around to enjoy flying the Gazelle, it is fun - but not using it in combat. It is really designed as a two person aircraft and there haven't been enough accommodations in the module to allow me to enjoy doing everything by myself. I have shelved in until they sort out multi-crew. Mi-8 looks like a bus, flies like a bus, has too many people in it - like a bus. Not my cup of rotary tea. Haven't really gotten into the Ka-50 because I mostly fly helos to get away from holding station and staring at in-game video screens. Huey is just fun to fly; simple but challenging. My go to. edit: I'm hoping the Hind will be the best bits of the Ka-50, the Mi-8, and the Huey glued together.

Everyone has their preference. The only difference is I never hear people say "cold starts should be removed from the game, I never use them, so no one else should". I think that mission designers should have final say in how the mission is supposed to be played - even if they are sometimes wrong ;) . Which is what we have now.

No. "I think campaign missions should be cold start" is a point. "Auto start is a cheat which should be removed from the game" is selfish, pointless blather (especially when he means hot start).

Yes, but it would work for those too. They aren't any different from any other mission. Also, I believe Raven One missions are cold starts in the Hornet, so perhaps not every campaign mission for the Hornet is hot start?

I think it's about preference and perception, because I often wonder why some missions aren't hot start, especially when they are designed to teach something else specific (ie, why waste all the time on starting the jet when you are trying to practice A-G?). It would be fantastic if it could be specified in the game options as a global preference - that is, choose to have every mission as hot start/cold start, with mission designers having the ability to override that global preference should it make sense to do so.

You have to use the Saitek profile utility to do that. But it works fine.

I just modded the "HB_F14_RadioNoise.wav" - took it down to about 10% of its original gain - and now have no problems with Jester at all. It sounds very natural, believable, and non-ear-drum-destroying.

It's good they had them ready to go then. Their timing on these was both impeccable and desperately needed. Glad it's moving forwards. (Incidentally, and I know this isn't the correct forum for this, but whenever I hit preview post, the editor seems to add extra carriage returns. Does this happen to anyone else? And if anyone has a link to a solution could you send it my way? Cheers)

I'm not suggesting that all these were coded in the last week, no. However I take anything Ron says with Dead Sea quantities of NaCl. The entire year of Harrier patch notes looks like this: Combined with almost total radio silence on the AV-8B forum on the part of the developers. Yesterday's patch looks like: And we have a new community manager who is actively posting and engaging the community in the last week. Also, a similar thread for Mig-19 managed to get the ADF radio bug fixed in couple of weeks, after a year and half of it being neglected. So while I don't think the community unhappiness caused yesterday's bug fixes to be magically coded in the past week, I do think it spurred on active development for the module and probably got many of them put into the update queue. ... Or perhaps it's just a timely coincidence. :no: However, whatever the reason, it's great to see yesterday's patch for the Harrier, and I welcome such progress enthusiastically.

Ya, it's amazing what some torches and pitchforks can accomplish, which years of waiting patiently seemingly cannot.

Good question. I think I paid $9.95 for the A-10C years ago on Steam. That combined with a price of $9.99 for this upgrade definitely feels like stealing from ED.

I can't seem to reassign the Clickable Mouse Cockpit Mode switch to anything other than ALT-C for the RIO. It won't work with other keyboard bindings nor with controller buttons. That is, I am able to assign other keys/buttons in the controls page, but they don't do anything. The Pilot has no such problem. Sorry if this is a known bug, a search didn't reveal any previous mention to me. I like to assign it to a mouse button so it's easy to switch back and forth while mousing around the cockpit. My mouse button emulates a keyboard press. Cheers

Yep, that's what I'm using too - version 7.0.53.

I'll have to check tomorrow. Sorry, it's late this side of the pond.

My X-65F mouse stick works without issue. It's not accurate enough for hitting buttons, but works well for panning view. I don't recall having to do anything special to have it work. Windows is picky about the driver and I have to manually select which driver to use every time it switches USB ports.

I'll add that the community has already 'bent' a great deal by being patient for so long. We've paid for the module, waited years for it to develop, and put up with being practically ignored by the developer of late. The ball is firmly in the other court. This will set an important precedent for EA status of modules - not really a trivial thing.

Strongly agree! I bought two RAZBAM modules solely because they have Baltic Dragon campaigns. However, even that will no longer be enough for me with regard to future modules, if the Harrier's development and bug squashing, communication with us, and outward attitude towards the customers doesn't improve sufficiently. Not trying to be petty, I'm simply saying these are the areas where RAZBAM hasn't met my expectations as a paying customer.