ZaltysZ

Completely linear, no deadzones.

Go to T.A.R.G.E.T, click "Control Center Deadzone" under WT Joystick picture and make sure that check box is unchecked. Please note, that your stick won't be centered perfectly anymore, however this will give smoother response when you have to fly in out of trim situations and have to move past center a lot. Next, bind elevator and aileron trim controls, push your P51 out of trim: nose up, right wing dip, so that you have to hold stick slightly forward and left to fly level. Do some strafing and rocket runs. Do that for 30-60 min or so. If you can achieve plausible accuracy, you don't need any curves. The problem while dogfighting is somewhere else. The most likely suspects are: elevator reversal, uncoordinated "ball to the side" turning, unintentional crossing of controls (i.e. too much aileron while pulling Gs). I personally had elevator reversal as the main reason for my departs until I learned to ease up a bit once desired Gs were reached.

But what if I have a "curve" in my head and it auto-magically fixes my input? :) Let's drop a sim context for a while and take a Real Time Strategy game as an example. The main control device is mouse there. Brains command the hand movement and feedback is given by eyes tracking the pointer. Basically: move hand, check current pointer position vs target position, adjust hand, repeat... This "pointer tracking" works extremely well for various mouse sensitivity settings until either control device becomes a limiting factor (the smallest input registrable by it is too large for intended input) or hand can't give precise enough input. The first problem can be solved by changing the device to more precise one, and the second can be alleviated by improving motor skills. However, there is still one more issue, which becomes noticeable only when mouse sensitivity is changed suddenly. Brains get used to certain mouse sensitivity (pointer movement vs hand movement) and habituation happens: brains decreases the frequency of checking the pointer position and begin to send commands to hand while depending on prediction most of the time. This allows quickly moving pointer from corner to corner even while not looking at the screen and so on. Once habituation happens, usage of different mouse sensitivity settings becomes extremely difficult and requires great focus. This is solvable only through practice as brains need time to "unlearn" old sensitivity and readjust. I think Der Fred is saying that stick throw is not important if your motor skills are good enough, because brains can adjust. I have tried flying P51 with WT while using linear response with 80% outside deadzones, i.e. making the stick x5 sensitive. It looked a bit twitchy at first, but began to feel like old P51 after 30min. My brains readjusted because I (as sim) pilot almost exclusively use visual information for determining what input I should give. This is an analogy to tracking the mouse pointer. However, Der Fred might a bit underestimate the importance of habituation, especially for older people. This is where stick throw becomes important. If person got used to large stick throw, large resistance, feedback through stick forces and so on, switching to desktop stick can easily break control prediction used in real life and show lack of fine motor skills, which are not needed in real world flying. Some thing must be learned and some unlearned before erratic flying stops. It is not hard, and you can even get away with single curve adjustment. The one titled "expectation of instant gratification". :D

Does the same happen offline? If not, some of you may have too slow network link. Lots of bullets -> lots of network packets -> network congestion.

Rubber doll would never make you feel guilty for spending your hard earned money on new sim instead of buying her a pair of new shoes. Just saying... :D

It sounds a bit like a control issue, like spiking input or control conflict. DCS P51 can be twitchy at the edges of envelope, but if you are smooth with it, even large corrections should not be a problem. Remove all deadzones and curvatures, give your dad to fly it and then upload a track here. Alternatively, press LCTRL+ENTER and observe control positions in red square while your dad flies. Look for violent jumps or jitter. P.S: #1: "controls are responding, well, not the way he's giving input" - this can be a result of deadzones/curves. #2: there is "rudder assist" setting. I don't know how to ride the pony with it turned on. Maybe your dad would be better with that setting off too. :)

Keep in mind that disabling TRIM will gradually degrade write performance of Your SSD. Once slow down becomes unbearable, reenable TRIM and fill up the disk fully with some arbitrary files, and then delete those files - this will get your SSD TRIMed. Alternatively, search for ForceTRIM app on internet - it will help with filling the disk up. Do this when it gets unbearable, don't make it a daily routine or your SSD will wear off. Also, the more free space you have, the later You will notice the degradation.

Then the fault was in old SSD or mobo (if you have changed it too). Do you still have that SSD? If you do and want to experiment a bit try hooking it up and disabling a TRIM. Commands: To disable: fsutil behavior set disabledeletenotify 1 To enable: fsutil behavior set disabledeletenotify 0 TRIM is supposed to lessen the performance decrease of future writes once drive fills up a bit, however TRIM has its own performance penalty. If your drive is pre-SATA 3.1, it does not support queued TRIM, and that means it stalls all other drive commands until it is finished. That penalty is rarely noticeable in desktop environments, but usually shows up in servers or other systems with high disk workload: lots of parallel small writes and reads, or too much unbuffered IO. I think it is worth to test without TRIM if you have some sort of SSD related IO "stalls", especially if SSD is old.

I would wait until beta is over :smartass: I started with A10C while it was still in beta, and quite a bit changed since then. Some stuff was relearned a few times.

No FPS gain, but very apparent improvement in loading times (it took way too much with HDD). Maybe less stutters here and there, but not too noticeable change for me in this area. I suppose, if you have =<8GB of RAM and around 1GB of VRAM, SSD could be more important as there would be more frequent reads from disk.

Game GUI still shows external IP, but it seems that game listens on interface to which IP from network.cfg belongs. So, it will probably work.

I will try to explain what he probably means. He has multihomed network (computer connected to multiple networks) and wants to use specific network interface for hosting DCS game. The problem is that DCS picks only the interface which is used to connect to DCS main server and listens for connections only on it. This basically prevents hosting DCS games via Hamachi or similarly working VPN solutions, which use virtual network interfaces. It is legit to ask for an option to specify network interface. Imagine a situation in which a person lives in university campus and wants to host a game for friends from outside. No one will forward ports and no one will allow UPnP. VPN working behind a NAT is usually the only solution in such cases.

Small unguided rockets are not very useful as area weapon in DCS. If you are calling God because of surviving trucks, I wonder what you would you call seeing what rockets do to infantry. :lol: I don't know that mission, but maybe you could try spraying AA at first and then attack the trucks? Use MGs when out of rockets.

The problem is not the low speed after execution of cobra. The problem is before that - the low entry speed for cobra. If you are not too fast for cobra, you are probably already having problems in general.

Multiple things can be blamed. Upload a track.

You can try converting Ministick to DX axis, if you can afford loosing some other axis (i.e. twist is good candidate for sacrifice, if you use rudder pedals): http://forums.eagle.ru/showthread.php?t=63794&highlight=x52

In addition, press Ctrl+Enter and check brake response in the red square. If you have assigned brakes to the axis, it might need to be inverted.

If you put normal stick for right hand and twist control for left, then maybe twist will be ok. However, if twist control is on the single normal stick, you will have control 'noise': operating twist will affect elevator/aileron, and operating elevator/aileron will affect rudder. This will be especially true at some stick positions due to anatomy of human hand and wrist. Rudder pedals make some things much easier and precise.

You need to be in position and call for "Contact". Boom operator will do his stuff, only if he replies with "Contact clear". If you wander away by too much, you will need to get back and ask for contact again, or else boom will just hang there.

It is either monitor settings or some sort of deviation from standard human vision, which typically shows highest perception for green shades (that is why HUDs are green or yellow-green). Standard HUD is more readable for me too. In fact the difference is so high, that standard color could be described as glowing, burning when compared to that screenshot with changed color. P.S.: if someone finds standard HUD looking dimmed, they should try checking HDR setting. Colder settings make that green look somewhat dimmed.

If you want to dogfight well in this P-51, you should take care learning about so called elevator reversal. Manual speaks about it, but in short: it is tendency of plane to tighten the turn by itself, and the need for the pilot to loosen the stick once desired Gs are reached. It is supposed to be a problem only with filled aft tank, but I feel this feature even in lightly loaded plane. It certainly can contribute to lots of stalls for an unaware pilot.

Why the Stormtrooper? Why not the normal TIE pilot?

Tracks (.trk) go to C:\Users\your_user_name\Saved Games\DCS\Tracks. If you want acmi files, you will need tacview (http://lomac.strasoftware.com/tacview-en.php). Install it, enable lua export and your played missions and tracks will produce acmi files.

Extending wont work while having such small initial separation and energy difference. Basically, all tracks except the first were a "no no". You do a right thing when you go for a loop like in the first track, however you should level out and begin climbing the moment enemy passes you instead of continuing a dive. Remember, enemy is turning while you are entering a loop - you are converting speed to altitude, when he is simply wasting the speed. You can easily exploit this small energy difference while you are at the top of the loop. Enemy will have to go defensive, because you will stay longer in the climb.

Fly again, abuse it, then exit the mission after you have decided it should have died long ago, save a track, attach it here.