Bahnzo

I don't use any sort of TrackIR, but I use the "panel view" as a zoom toggle. You need to know how to use custom static views (google it) and then you can set the panel view (Num 0) as a custom view zoomed way in on the hud. This allows you to then use the panel view toggle (rctrl-Num0) as a way to toggle a zoom view for guns.

I don't see that at all. Works perfectly normal AFAIK. I'm just using the normal 1.5, no beta or anything.

The way I use VA for comms is using the various radios, but I can't imagine the "<backslash>" key would cause a problem. Edit: here's a pic of a very simple "rearm" command. Works perfectly. No need to press the backslash key first, etc. So see if this is how you are using it and go from there. Edit2: Opps I meant this for pocketedition above, but it works for both I guess.

pocket....export your VA profile and upload so we can see it. Sounds like you are missing something not obvious.

One thing that's been bugging me over the last couple weeks with the A10C, is the cockpit view when the game starts. It does that thing where it pulls back slowly? A: Is there any way to stop that? and B: Can I at least get it so that it pulls out to where I like it? I've set the "default" view using the custom snap views thinking that would be it, but it seems to start at my preferred view and then pulls out.

I use the ATC static mod on a stand alone install and it's working fine. (no probs multiplayer)

Try making sure it's set to Digital Combat Simulator and see if that's any different. Are you using VA to send radio/comm messages or for something like flaps, gear? You know what would work best? Export your profile and post it so we can use it and see if there's something broken.

It's hard to say without more info, but first thing that came to my mind is making sure the commands are being sent to the correct location. IE: on the VA page there's the drop down box named "Send commands to:". You want to make sure this says either "Active Window" or "Digital Combat Simulator".

First, I'd recommend just buying the latest FaceTracknoir, it's like $4(us) or something...very affordable. Here's a link that really helped me get mine working much more smoothly. The Accela Filter settings listed make a BIG difference. https://sourceforge.net/p/facetracknoir/discussion/accela/thread/1f231eb1/

It fires at 35km. According to the encyclopedia in the game, the effective range of the missile is 32km.

Surely this has been brought up, but a search shows nothing.... I did a test with the SU-25T against a SAM site(Hawk), and with and without ECM, the site still fires at the same distance. ie: it seems like ECM has zero effect on the tracking of the sam radar. Bug? Known issue? Or a reason behind it?

Ok, that's good to know. I was grouping them, just needed the other search radars eh? Thanks!

I'm just trying to make a simple mission with a single SAM site so I can practice evasion and learn how to attack different ones. But I can't get any of them to even fire on me. Simply, I put down a Hawk SR AN/MPQ-50 radar and numerous Hawk LN M192 launchers, they are set to USA. I set myself up in an SU-25T set to Russia and while they track me, they never fire. WTF am I doing wrong here?

I have to agree. I'm surprised this thread remains actually. It's pretty obvious this is never going to see the light of day, if that was even possible to begin with. That said, I don't think tracking needs to be that expensive. I've got a PS3 Eye and even with the facetacking stuff it works pretty well. The real problem I think seems to be a good source for a point tracking set, at least here in the US. I know EU has a couple people who seem to make quality ones that don't seem overly pricey.

So, after some work and a little back and forth with Hollywood, I was able to make VAICOM work with the use of a pinky switch to toggle radios between only two buttons instead of 4. The problem is since I also use the pinky switch as a modifier in the game, it causes problems when VAICOM tries to issue the radio command. The way to fix it is to add another command to each of the radios (in DCS) including the pinky switch (or whatever other modifier you use). Ex: VHF1 radio is Lalt + Num+, so you would simply keep that and add another command for that radio of Lalt + Num+ + Pinky. And do that for all the radios and the "/" and the "Pause" key as well. Seems to work fine and can save you a couple buttons if you need them.

I'm just venturing into multiplayer also, so I'll give you my tips from that perspective. I'm sure others with more hours will have more details. Get a program called Simple Radio Standalone. It's here in the forums under Mods I think. Most servers use it. Many also use Teamspeak. I've yet to figure out which is used more....seems every time I connect nobody is on either. Because of the radio mod, make sure you understand how to use the radios, as most servers are set to not use easy radios. You'll need to know how to tune and key them to talk. Before you join a server, after you click on it, make sure you read the details on the right side about what is enabled and disabled. Makes things easier later when you can't understand why such-and-such isn't working.

As is it, when your wing calls "rolling" or "wheels up" or other situations in the game (not just your wing, I noticed it does this when the "pull up!" call is made), the radio menu pops up automatically. This is annoying as it can get in the way of changing a view or a radio script or whatever. Can we at least have this set as an option somewhere to turn it off if we don't like it?

The radio pop up thing is just annoying. I'm noticing it's showing for simple stuff like my wing calling "rolling" which is not necessary. Guess it's one for the suggestion box. The two radio tips are certainly ones I didn't think to check. Not sure they are mentioned in either of the startup guides I've been using. Thanks!

Sometimes my radio menu comes up on it's own. One I can think of is on final after asking landing clearance it either comes up during the tower clearance or maybe the low alt warning. But it also comes up on it's own in other situations (another is when my wingman calls). Is this normal? Any way to stop it? Also: I flew the Smerch Hunt mission again tonight and couldn't contact my wingman. I had it set to UHF 251 as the briefing states, and made sure I was using the UHF radio, but he never responded. I am teaching myself to do the manual startup so maybe I missed something? I followed the startup checklist, so....scratching my head here. What would you check in that situation?

I enjoy seeing some wind. Seems like many of the servers I've tried don't bother and it's pure calm. Is there not way to have the map generate a random wind/weather?

Had this happen again tonight. I ran the mission "Smerch Hunt" and after maybe 1.5 hours landed and pulled up the menu to change a few keys....and again what I described above happened. So I pulled up the task manager, and it listed 34% memory used. Not a lot. And when I exited back to the menu, that value didn't change, and trying to bring up the options from the main menu resulted in the same performance issue. I didn't try to reload a mission/map, but I did exit the sim and restarted and all was fine. 14% memory use reported then, BTW. So...not sure what's going on here, but at least the task manager doesn't report high memory usage. I'll try to load up CPUID HW monitor and look at stuff from there. It should report my GTX 750ti's memory usage and other vitals. PS: did I really post this to "Installation Problems" or was this moved? I surely should've posted this to a more apt forum like "Performance Issues".

AMD Phenom II X4 955 GTX 750ti 16 megs DDR3

I've noticed after playing for some time (no exact amount, like an hour or two), while the game itself doesn't seem to slow down, pressing ESC to access the menus (like to quit) results in a HUGE slowdown. So much to so that I've had to just use the task manager to exit sometimes. I've also noticed that alt-tabbing out to another program will cause DCS to "move on" to the selected option (ie: Quit, or the Assign Controls). But, if I Resume, the game returns and it perfectly fine it seems. It's only the ESC menus that are affected. If I exit the program and restart, it's fine.

AutoHotKey script example for use of pinky switch Edit2: Actually this *can* work. I explain in the post below. Also cleaned up code a bit. Edit: oh well...doesn't work. I mean, it works, but having the extra pinkie button causes issues with VAICOM somehow. For people who use AutoHotKey, I thought I'd give my example on how to use two buttons with the pinkie switch to turn them into the four buttons you need for the radios. 2Joy4:: if GetKeyState("2Joy7") ;pinkie/switch button down { Send {Numpad0 down} KeyWait 2Joy4 Send {Numpad0 up} return } else { Send {Numpad1 down} KeyWait 2Joy4 Send {Numpad1 up} return } 2Joy8:: if GetKeyState("2Joy7") ;pinkie/switch button down { Send {Numpad3 down} KeyWait 2Joy8 Send {Numpad3 up} return } else { Send {Numpad2 down} KeyWait 2Joy8 Send {Numpad2 up} return }

Ahh, thank you. I've only flown the SU-25T and I've either yet to read/learn about this yet, or it's something not relative to that plane. Thanks. Edit: and this video I found also helps explain a lot: . This along with the fact MGRS needs to be turned on in the Misc/Options screen pretty much explains why I haven't seen this yet.