FeistyLemur

That's such a good sale it's even cheaper than buying it on newegg.ca for Canada. Assuming newegg will do that, they do ship some things from the .com site here, or used to. I wonder why such a big sale.

This might be why I struggle to find targets so often. Not taking into account that I'm flying below 2000 meters. And in multiplayer I'm usually flying at about 10 meters. Ok maybe a bit more than that.

I spent a lot of time with it last night and may have it figured out. I just assumed it was automatic but the profile switching appears to require set up. The profile switch commands are kind of a strange mixture spread over the profiles and don't have the actual command in place which has to be added. So I got that fixed and it works well now. I find that calling the profiles as 'aircraft select f15c' for example is really fiddly and problematic. Even when I specifically add "f15c" to the windows speech recognition dictionary and record an example, it doesn't work well. Even when it looks like the unrecognized command should have worked in the monitoring window. Plane designations are just hard to pick up for it when I speak them. I changed them to full simple words and set the appropriate command for the profile to enact. EG instead of MIG21 and KA 50 ( the two profiles I use) I set the suffix to bison and shark respectively. This is much more reliable. All of the profile switch commands had the commands broken. If I had to guess it would be maybe because they were looking for profiles that aren't imported yet as you import the profile itself so perhaps it replaces the command for the profile with an error message and never fixes it unless you do it manually. As for the radio issue. I'm still finding some fiddly behavior with them in certain situations. After reading the manual several times and experimenting I think I fully understand how it works and it does work most of the time. The key mistake I was making was not understanding that the radio has to be tuned to the appropriate airfield, as well as requiring you to call 'airfield ATC select' to change it. I seem to have problems getting nalchik to work. It recognizes the command 'nalchik' ATC select options' but under no circumstances can I ever get it to tune to nalchik yet other than flying close to it and catching it with 'nearest / proxy' For example, in testing last night I was flying the KA-50 towards nalchik in the "cold start in mozdok" mission. As I was flying toward it I set my radio to 136 for nalchik, called nalchik set atc options 20 times, and it would not pick up under any circumstance. However, I set the radio for Minivody, called minivody set atc options, it picked up no problem. Then I swapped back and forth between minivody and mozdok(assistent in ka50) several times, it worked 100% reliably going back and forth between those two. But nalchik, nothing, when I got close enough nalchik became "nearest" then it tuned in and worked. Haven't figured out an explanation for that yet. Other than that remaining quirk I've yet to figure out, everything's working great and I'm really enjoying the program a lot, thanks for creating it.

Just adding this guys response because I'm seeing exactly the same behavior he describes, except for the get data part. I've spent a lot more time with it tonight, and I cannot reliably get selection of atc working. Airfield usually goes to nearest and I've found it nearly impossible to get it to select another airfield. Once or twice it's worked but it seems really sticky and unresponsive when using the 'select' commands. This is in addition to my issues with profile selection. I also see the exact same thing he describes when saying "start mission" The thing I'm starting to question is the version of Voice attack. The install guide says you need the beta, but the version listed is actually lower than the current release version. I'm using 1.5.8, the beta listed on their site is 1.5.8.14 I tried both and the 1.5.8.14 beta doesn't work well at all. It hangs importing profiles and gives errors. I'm wondering if there are any problems running this with the current version. There seems to be no way to download previous versions of voice attack.

I seem to be having a lot of problems with selecting things now that I look at it more. I can't select different airfields or farps. It locks to the nearest 80% of the time, sometimes I can fluke it off and get it to go to another airfield but most of the time it stays locked to nearest. I think I must be doing something really wrong somewhere.

If I do it all in one go like that the best I seem to be able to get is command recognized, profile not available. But the profile is installed. I didn't change the name of any of them. 90% of the time it still says command unrecognized. I tried blacklisting some words and recording pronunciations in the windows speech dictionary to get it consistent but I'm trying right now and i consistently get either "command unrecognized' or 'profile not found' if it does register at all.

Stuff like this I find is almost never cheap. A good solution is to find a local machinist to make things for you. There's a local guy with a CNC plasma cutter and a full machine shop who I get to make things. The prices are very reasonable, and anything you can dream up can be made by a machinist, for a price. Retail mounting solutions if they even exist are crazy expensive. Like monitor arms which I currently would like to get, they pretty much start at 200 bucks a monitor for anything decent here. I got the face plate for my panel project plasma cut and it cost me 40 bucks and that was with the cost of material. Honestly 80 euros a piece for those clamps isn't unreasonable given the amount of work that guy is putting into them and the quality level of what he's producing. But at the same time you might not really need something that elaborate.

TM warthog. The slew nipple works great in the A10-c module out of the box, and I was able to tune the axis to make it work with with the FC3 aircraft by adjusting the saturation of the axis. Despite this I was never able to get it to work all that well with the shkval. I got a speed that works quite good for panning around but small adjustments are where I can't get it to work. I'm looking at adding rotary encoders on my next upgrade to my sim panel project, but now I'm thinking tiny analog joysticks would be a good addition to for things like the shkval.

I have my stick trim hat set to slew shkval, I tried to get the mini stick on the throttle to work well but I could never manage to get just the right axis setting to make it work well. As a result of this I use the airbrake button on the throttle as lock target. This allows me to be able to operate it and the skew shkval at the same time. For example to unlock a target or adjust the lock on the current target.

I started a new thread for the same question which was probably a bad idea, so I'll post the question here instead. Everything is working pretty well for me. The one thing I can't seem to figure out is voice called profile switching. The manual states 'Aircraft select F15c' should make the program switch to that profile. But I can't get it to work. Typically "Aircraft select" shows recognized for the word select, but everything after that gets rejected. Even when the command looks right. Example it says 'Unrecognized command f15c' Not having much luck figuring out this part. Also worth mentioning, I did notice in some other module manuals it says to call 'load profile', this also fails for me with call structure errors. I don't have it in front of me at the moment to describe the exact error, but I'll have to check it this evening again.

It works 100% for me. Use the kneeboard as mentioned for the correct numbers. I know there's no RSBN as high as 22 in the mig21. Nalchick for example is 8, Mozdok is probably 9 just of the top of my head, being it's right next door to it.

Someone should make and upload a -40 mission then, with strong wind and AA everywhere and name it Jorge Quiere Ser Hardcore.

Yeah that's pretty much exactly what I was asking about in the original question. It's rock stable in flight director mode or with the trimmer held through the turn. I didn't know if it was a bug or if it's really supposed to behave that way.

So you're saying Russian choppa gets to you...? I'll just show myself out now.

Am I misunderstanding how it's supposed to work? The antenna is fixed is it not? Should that not mean if for example I see another plane outside the coverage area which is just a bit too far above me, should pitching up and aiming the nose in the appropriate place not detect that plane? I know the SU 27 in the FC3 pack seems to have the antenna try to stay glued to the horizon as you maneuver but I was under the impression you just point the nose at what you want to lock up with the 21.

So I have some issues getting the voice profile switching to work. The manual says to say "aircraft select profilename" eg "aircraft select f15c". I've tried everything I can think of I can't get it to switch profiles with voice. The closest I can get is "aircraft select" recognized, but nothing will get recognized after that. Even when it clearly got it, it returns "f15c" not recognized for example. Does anyone know what to do here?

I don't know if it's a bug, or what but a couple times now in multiplayer I've spotted the enlarged models of other planes on the horizon and been completely unable to detect them despite pointing the nose in what looks like a direction that should be able to detect them. Do the enlarged models actually have more visibility than the mig21 radar?

I recommend Vaicom if you like communicating with AI for realism. It's pretty immersive to use. And really convenient and fast for handing targets to AI wingmen. Even playing online I prefer to use ATC and land before leaving where possible. This works well there too.

I presume designate is only referring to when you're using the helmet mounted designator, which if you hold the button slaves the shkval to your hmd. Which I might add is really fun when you use the cannon that way on troops with HE rounds. The only unlocking I know of besides either centering shkval or resetting targeting completely, is to hold down target lock and slew the shkval again, or to hold down designate and move it with the HMD. You can make micro adjustments to your TA target that way by holding lock, nudging it and releasing and it picks it up again. I find it's best to make sure you put target lock and the slew shikval commands on buttons you can use at the same time. If you move it far enough while holding lock it will also break lock I believe.

I played tonight flying frequently with flight director off or holding the trimmer while maneuvering like it was suggested and I had way more fun. It's 200% easier to fly in that way. Had a lot of fun in multiplayer and even flew in formation with 2 other KA-50s for a while.

I thought I understood how the trimmer worked but I didn't realize it was standard practice to hold it down while maneuvering, I thought you just pressed it to trim once you were oriented. I guess I need to practice more. And pick a new trimmer button assignment, I have it set to the big red thumb button on the warthog to make it mirror the in game stick as much as possible, and that thing is hard to hold down. The tutorials made me think flight director mode was only for use when in route following mode.

No I hadn't been, I didn't know you were supposed to.

I would still call myself a novice with the Black Shark but am getting more confident with it. What I wonder about and I haven't been able to find mention of is something to do with turn behavior. I notice when I'm turning I can be doing a nice slow coordinated turn, but when I reach the 180 degree mark in the turn the aircraft tends to suddenly lurch hard in the direction I'm turning, requiring opposite stick and rudder to correct. I notice this a lot because one of my practice routines is to do the cold start Mozdok mission, fly a circle or two around the airfield, and then land. So it's common to do a complete 180 to come in to the airfield. Is this something to do with the trimmer and the way it functions as I'm reaching the complete opposite heading I'm trimmed on?

Hmm, well the way I have it right now in my autohotkey script I find works really well so I might just keep using that. I have to run the AHK script regardless because I need the push to talk for vaicom assigned to a stick button, so I just might as well bind the WH in the same script while I'm at it. The only possible failure conditions for the AHK method are if you A: start the mission with the throttle out of lock. But this is a fact of life for toggle keys that's impossible to avoid to my knowledge. Or B: move the throttle down really fast and drop it into lock before the in game throttle has actually reached the bottom, triggering the lock key-press before it can actually be locked. In those situations, as with all other toggle keys that don't have proper on / off functionality and get out of sync I'm forced to just click the in game cockpit or press the keyboard key manually to resync the de-synced toggle. I can't really think of any workaround for moving the throttle too fast and slapping it into lock before the slider has actually reached the bottom in game. You would have to somehow be able to detect that the games throttle axis is not yet at zero and wait to send the key-press, and I have no idea if that's even possible. The only real downside to AHK is say you want to switch planes you have to alt tab and kill the script and start another one.

I have no idea, maybe one of the lua knowledgeable people will know. I was reading the bug tracker today having discovered it and I noticed that there are still open control related features listed as "assigned" IE maybe more toggle controls and joystick assignable functions are still in the works. At least I hope so. My dream would be for every single switch to have proper up / down / toggle commands, all clicky dials to have + - keys, and analog knobs to have up down axis functionality. And all of it to be able to be bound to any and every device that's appropriate for it to be bound to. They removed a lot of that separate toggle functionality from 1.2 and then put the critical stuff back thankfully, which I participated in campaigning and nagging for pretty relentlessly. I do hope there's even more coming though in regards to controls.