Taz1004

Not based on the last mission I flew. I had to press TMS twice on red solid datalink targets to lock and launch.

I didn't mean set it as both rudder and rudder trim function. Having a rotary as rudder works like a trim is what I meant. If you have to keep constant 10% pressure to the right rudder to keep your plane or helicopter straight, then with rotary, you just rotate 10% to the right and leave it to go straight.

Reading the manual again, I think there is mistake in the manual and I think I understand what the OP is confused about. Information on page 142, 143 versus information on page 161. Regarding white solid and hallow squre being track target vs system target. It was my understanding that the information on page 142, 143 should be reversed? That hallow is track targets and solid is system target? As indicated on page 161?

The question itself is somewhat confusing but I think you misunderstood the difference between Datalink and your own radar contacts. Hallow datalink targets are reference only. You can't lock them unless you point your own radar towards it and make it solid. Hallow datalink target is datalink target your radar isn't seeing. Solid datalink target is datalink target your radar also sees. White hallow target is unknown trackfile from your own radar. White solid target is unknown correlated target from your own radar. Bottom line is that the targets must be correlated by your own radar in order to lock.

This is more of how to than a mod because what everyone wants to hear and disable would be different. If you're like me, then you're tired of your wingman calling out every ground unit on the battlefield. Below is how you turn it off. /Scripts/Speech/common_events.lua Starting from Line 205 is all the Wingman radio messages. Just commenting each line with -- will disable that specific messages. For example, changing line 218 from this [Message.wMsgWingmenContact] = { _('contact'), 'contact' }, To this --[Message.wMsgWingmenContact] = { _('contact'), 'contact' }, Will disable enemy ground unit contact callouts. What you want to disable and keep is up to you. I personally disabled all the "bandit", "SAM launch", and "engaged defensive" messages too. But kept "Mud spike" Also further down from line 451 is AWACS messages. I disabled "BRA" callouts as they get too repetitive. But kept "pop-up-group" messages. I just need him to tell me once. Doesn't seem to affect IC Check.

You'll need to increase number to compensate. But that's more complicated as it's setup to transition between smoke types. You can try increasing lifetime multiplier.

smokeLifeC is multiplier. Values in velocity are in (X, Y, Z)

smokeLifeC will make them last longer so give more time to move up higher. Or Y velocity will make it move up faster reaching higher. But once again, transparency is the most performance hungry feature in any game engine. Bigger, higher, more, and longer means more draw calls. And worse if you have transparency on top of transparency. If the smoke covers small 100x100 pixel area in the distance, multiple draw call for that small area isn't a big deal. But if it covers half of your screen, it will hurt fps. You can see the impact if you try flying through the smoke.

Looking at the barrels and especially that hole that looks like nostril changes to hexagon so it is LOD shift. Judging by the anti-aliasing, I'm assuming these shots are zoomed in? What does it look like fullscreen?

Thanks for that. I am interested but the website still says it's for A10C. Is there separate version? Or do I just buy that version and same campaign works for A10C-II?

Yea, I've tried every combination in that setting and so far, there's no way to make it work like mouse wheel. It is just button emulation and doesn't account for speed of the wheel's rotation. Just speed of the "clicks". And if you make it "click" too fast, then DCS doesn't recognize it. You can only assign them to non-time critical functions that doesn't require a lot of spinning such as NVG gains. Even for MFD brightness, I have to spin them for long time and using buttons or keyboard is faster.

Encoders another cons of this device. I tried assigning them to knobs like heading bug knob but it doesn't work like mouse scroll wheel. Spinning it fast doesn't make the knobs turn faster. Just make them turn slowly for longer. Like it's delayed. I have one set to night vision gains but haven't found any other uses for them.

So, since you already have throttle like me, what do you use the throttle on the NXT for? I'm having hard time coming up with good use for it.

My primary sim is racing so I've been using my racing pedals as rudders. Then I switched to using rotary on the Saitek throttle. I first started using it as rudder trim, then realized you can't assign two axis to rudder in DCS. So I tried using the rotary as primary rudder. And because rotary can double as rudder and the trim, it's so much easier. I don't have to keep constant pressure on the pedal. It was revelations for me for modules that required constant rudder input like Ka-50. Altho not realistic. Twist rudder is garbage. I suggest giving rotary on your throttle a try.

I have GTX 1080. Smooth 45fps in VR even at low level. Drops to 30fps only over heavy city like Beirut. Your issue might be something else.

You're right. Didn't know there was the other mode.

Hmm... Pressing the dogfight mode again works for me. Same with A2A and A2G mode. Pressing them again takes me back.

Incorrect IPD wont make you cross eyed or wall eyed. You will always look straight and with incorrect IPD, you may look into wrong part of the lens/screen. Eye strain can be related to many other things than just IPD. Comfort, refresh rate, frame rate, smoothness, color, screen type, lens type... And a lot of times depends on the person.

This thread is 5 year old. And there are YouTube videos dating back to 2013 showing same issue.

Well, that'd be absurd even if that was the cause. How am I supposed to match my altitude to my wingman everytime? But it's not related to my altitude or the wingman's altitude. Offset is always constant based on the map. Are you saying this is working for you?

I'm not planning to buy anything for awhile and I have some miles left over from last spending spree because I misunderstood. Guess I'll burn it on campaigns but... none of the A10C campaigns seems to be updated for A10C-II.

It's affected by fog and overcast as well. Even if it's very thin fog.

I know you can't get miles for buying campaigns but can you buy campaigns with miles? I guess I can look it up.

Saitek/Logitech profiler is basically a macro program. With the profiler, buttons on your joystick will emulate keystroke. Keystrokes that match keyboard commands of DCS. And you save the profile as Saitek profile and switch for different plane. It does not export lua file. And X56 section in DCS should be unassigned. You keep everything as default in DCS. Except the axis of course. Reason for using Saitek profiler is the advanced commands. You can have it do one command when you press a button, do another command while you hold it down, then another command when you release the button. For example, press launch button to launch a missile, hold it down to switch camera to weapon view, then release the button returns the view to cockpit. Or speed brake, most module in DCS have one key for extend and one key for retract. With the profiler, you can have the speed brake extend while you hold the button down, and retract when you release the button.