xaoslaad

We got 'im boys!

I like taking control of a SAM around a bridge and using it to get the A-10's and SU-25's playing whack-a-mole while you weave in and out and side to side and pop off a few rounds at them. Sure, if they're half decent they should be able to take care of you in short order, but some guys will waste a truck load of ammunition on you and that alone can be satisfying.

Learn things that will keep you on target and alive. Learn to use the TAD properly. That is one area I am weakest and it is profoundly useful and I still haven't sat down and given it proper attention. Mind the CDU as well. I'm more confident with that, but you'll want to learn it well. Understand the countermeasure systems as well. I was sorely lacking here and didn't even realize it until recently. It has suddenly become much more effective. Don't jump to guns/rockets/bombs/missiles, even though they're naturally the most fun.

Ya, I didn't mean to say it would be a 5 minute change, but there is obviously a lot of energy around pointing out imperfections and some of that could probably be a little more effectively directed.

FWIW, What might cut down on 'complaints' is a public bug tracker. It would allow people to see what bugs are confirmed, needinfo, being worked on, etc. non-constructive complaining would turn into constructive bug reporting, log uploads, etc. At this point people can complain, and maybe a tester or someone at ed will ask for a track or log to look at the issue... Set up redmine or bugzilla. Considering you're moving to public betas it might be a great time to do so. Just a thought.

Another one who will echo the sentiment that some of the stutters seem to go away with an SSD. Again nothing concerete to back it up, but if nothing else load times are way way better.

They said it will have separate configuration.You may expect something like Saved Games\DCS Beta or something...

First thing I thought when I saw that is it looks similar to the design of Fort Independence in Boston (it is definitely not the same though), looking quick I'm guessing Fort Monroe in Virginia http://en.wikipedia.org/wiki/Fort_Monroe edit: and nevermind, I see someone already told you. /me goes back to his hole.

If you set the X and Y axis to saturation y to 15 (leave saturation x at 100) with a deadzone of 2 and no curve the ministick behaves fine in the Ka-50 and probably in the Su-25T (just got the stick this weekend so spent time messing with it in yhe shark first. But yes it flies VERY fast by default in anything but the A-10C. Other than that I haven't had problems setting inputs in game and nothing has made me want to use TARGET yet.

It looks like th A-10C gets ALQ-184 now too? From quick reading aircraft never carry both, but then which for what occassion. Being so top secret is there even an in game difference?

I have not been able to get it run on KVM. I don't think the emulated graphics are powerful enough. It just crashes on startup for me...

Cool. Thanks for the explanation. It makes a lot of sense as to where all the confusion comes from.

Interesting if it's not true. I ran across the page while researching in anticipation of a warthog christmas so I can't speak from experience, but it seemed reasonable. Again, it didn't say you couldn't use them, just that they wouldn't have DX assignments. If not true, it's not true, but then it seems to be a very common misconception. "Before going any further, it is important to understand the limitations of using a controller in pure DirectX mode. When DirectX sees a controller that you've plugged in, it will recognize a maximum of 32 buttons and 8 axes on that controller. These can be 'directly' used in-game and are often automatically set to perform certain default functions, e.g. Button1 = DX1 = fire guns. You can also manually assign them in-game in the controller properties page, e.g. click on "Fire guns" and then press Button1 on your controller. But what happens if you have more than 32 buttons or 8 axes on a single controller? In that case, those 'extra' buttons/axes are not assigned DirectX names, and so from DirectX's perspective, they're not even there. However, you CAN pass keyboard assignments through those buttons/axes, provided you have some programming utility outside of the game (TARGET, Foxy, etc.) that can handle that. So, let's say you have a 33rd button on your joystick. By default, pressing this button in-game will do nothing, because DirectX doesn't see anything beyond 32 buttons. But if you've programmed that button from outside the game to represent, for example, 'G' for landing gear, now when you press that button in-game, the game simply sees 'G' and doesn't care where it came from." See also: http://simhq.com/forum/ubbthreads.php/topics/3593984/TARGET_vs_DirectX.html

It's not HID that is limiting, but rather DirectX. You can still use additional keys on a controller, but it won't have a DX button assignment. I think this explains it better than I ever could: http://forums.eagle.ru/showthread.php?t=81222 I also read a rant about TARGET merging all controllers it is used on into one giant virtual controller with potentially many more than 32 buttons/8 axis essentially 'breaking' the DX 'plug and play' style buttons. But that has little to do with what people are looking to do here, except to illustrate the point that you can have a lot more than 32 buttons on a controller.

My only two cents on top of what everyone else said: If you've got labels on try it with them off. They are a performance killer. I also think being on the ground at the runway is notoriously slow, at least among my group. More so with labels on (all the more reason to learn to play without them).

I'm hoping they release a Track No IR ala something like the Microsoft Kinect that can do face tracking one day so we need no clips, etc. That's just a pipe dream of mine though. I'd settle for a wireless pro clip as an upgrade.

Do you have Office XP by any chance? You may have (and need to disable) the Microsoft Debug Manager running the in the background. If not XP could be something similar. If you provide the process list from the task manager people can probably help you better to identify what might be running that is causing the issue. Could possibly be something from a Visual Studio Suite or something similar if you have such a thing installed. OR running a command prompt as administrator and run "bcdedit /debug OFF" to disable the windows debugger and reboot. The great and might $tarforce is trying to protect itself.

Read 5 or so posts back. Data Execution Prevention...

The application should still be fixed. It running better without DEP enabled is indicative of a problem. Disabling it is an OK temporary solution, but not a good permanent answer.

Why are you having to turn off DEP? DEP only prevents areas of memory not marked as executable from being executed. It's a security feature meant to prevent stuff like buffer overflow attacks. That wreaks of a bug in serious need of fixing if true. And while not hard to turn off people should not have to expose their system to more risk to play and I bet most wouldn't. Even know where to find the setting...

I could cause/fix the issue at will by opening and closing teamspeak once I figured out the pattern. I dont see what running them inadmin mode is going to get me. I am using windows 8 though so maybe its the 3 way combo... Cant say.

Not sure where to put this, but was hoping for somewhere with high visibility to hopefully save someone elses sanity. What little I had is now completely gone. I deleted my configs and reconfigured everything twice, reinstalled drivers, repaired DCS, and in general went flippin' nuts. I would think it was working and then it would go hay wire. Back and forth and round and round. Looks like The X52 (Pro definitely, possible non-Pro, but don't know) and TeamSpeak are conflicting. For me this was manifesting as literally dozens of button presses by holding a button for a couple seconds. http://forum.teamspeak.com/showthread.php/89956-Saitek-x52-Pro-Profiler-Conflict Anyway, I was able to fix this by going to: Settings, Options, Hot Keys, and changing the drop down over the Apply button to Keyboard and Mouse only. Ironically it still works just fine with the stick profiling pressing the hot key to talk...

There are also a lot more virtualization technologies (and versions of them) than there were X number of years ago. Heck, just VMWare has Fusion, Workstation, Player, Server, ESX, yadda yadda yadda. Now add Parallels, HyperV, KVM, Xen, VirtualBox, etc. It could be that it's just like playing whack-a-mole trying to keep up with all the different implementations.

I read it differently, but without word from them or ED to clarify it's impossible to say for sure. My take is that if they are making an effort to detect virtualization, and preventing the game from running when they do, it is intentional and they're just not doing a very comprehensive/complete job of detecting virtualization. I'd guess their opinion is, what's to stop someone from installing a registered game in a VM and then distributing the VM. Afterall, if it's not the case, why stop if you do detect virtualization. StarForce/ProActive isn't doing you a favor by telling you that your VM is or isn't sufficient to run the game. It's not their job or their purpose. All guesses and interpretation on my part...

This probably explains some of the confusion over what exactly the DRM is. ProActive is product name (I did not know that) made by StarForce, the company. http://proactive.star-force.com/2.0/activate.php http://www.star-force.com/