Jump to content

Recommended Posts

Posted

I'm using the Warthog Mic Switch (Not an axis so Axis edit doesn't work) for my TDC slew and it is way too sensitive. One quick flick and it moves 3 crosshair widths.

Posted

Which screen mode are you using, PPI or B-Scope (F-15 like mode)?

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted

Hello,

I have the same kind of issue, I'm using the PPI (default settings), the piper is not that difficult to move actually, as long as you can tap the keyboard quickly (I get a half cross arm length accuracy).

However using a joystick makes tapping much more difficult and lead to wider piper movement.

I don't know what is the real one's sensitivity though, so I can't really tell it's a bug or not, maybe it's not meant to be used that way and the user should zoom more to be able to accurately select a target (?).

Posted

I agree it is a problem, but it is hard to get a speed that will allow you to quickly position the TDC over your target and at the same time not to be fast enough to send it to one side of the screen with a single push.

 

I'll try to find a way to test this, or to set a TDC speed option. I'll see what can be done.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted
Can you add Axis commands for TDC? would be preferable I think.

 

I'll check but very likely the answer is yes. I'll just have to make sure it works.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

Posted
Can you add Axis commands for TDC? would be preferable I think.

 

I don't think the real aircraft has an axis for that.

Hardware: VPForce Rhino, FSSB R3 Ultra, Virpil WarBRD, Hotas Warthog, Winwing F15EX, Slaw Rudder, GVL224 Trio Throttle, Thrustmaster MFDs, Saitek Trim wheel, Trackir 5, Quest Pro

Posted
I'll check but very likely the answer is yes. I'll just have to make sure it works.

 

Great - was about to post a request to add that to the axis controls configuration (as well as the radar tilt axis)

  • ED Team
Posted
I'll check but very likely the answer is yes. I'll just have to make sure it works.

 

Thanks. TDC as axis option would be great.

AMD Ryzen 9 3900X, GeForce RTX 2080Ti, 32 GB DRAM, HOTAS TM Warthog, FSSB R3 Lighting, MFG Crosswind, Win 10 Pro

Posted
I'll check but very likely the answer is yes. I'll just have to make sure it works.

 

Is it me or is locking up targets with the TDC difficult, i can't count the amount of times my cursor is basically on the aircraft but it won't like, and since it's so sensitive it is extremely accurate to pinpoint onto the target.

[sIGPIC][/sIGPIC]

Director | Team Coordinator

PC Specs:

 

 

  • Intel I7 8700k 4.7Ghz
  • Gigabyte Aorus Ultra Gaming Z370 Motherboard
  • 16GB Corsair Vengeance DDR4 3000MHz Ram
  • 500GB Samsung Evo 850 SSD

 

 

Posted
Is it me or is locking up targets with the TDC difficult, i can't count the amount of times my cursor is basically on the aircraft but it won't like, and since...

 

Turn Facebook Datalink on? :)

Posted
Is it me or is locking up targets with the TDC difficult, i can't count the amount of times my cursor is basically on the aircraft but it won't like, and since it's so sensitive it is extremely accurate to pinpoint onto the target.

 

This is the only issue I have, I think the TDC movement speed is fine

Posted (edited)

I faced the same thing here and I was going to ask about it before I saw this topic.

 

I have assigned the TDC of my F-15C on Warthog Mic Switch as axis but it is still too sensitive. I am still not able well to look on my targets specially on TWS mode.

 

I have tried to increase little the deadzone and make some curve but still too sensitive. is there any way to make it more slow in movement?

Edited by Rabso

i7-6700K | MSI Z170A Gaming M7 | Dominator 32GB 3000MHz | MSI GTX 1070 GAMING Z | 2TB SSD & 1TB HDD | Acer H277HU 27" WQHD | Audeze Mobius | TM Warthog | MFG Crosswind | TrackIR 5 | Windows 10 Pro

Posted

Just one observation on TDC movement.

 

In PPI it uses polar movement. If you keep moving to one side you will see that it actually curves downwards.

 

So in PPI when you have to engage a target you have to move sideways and slightly UP.

 

If you feel that is too much work, change to B-Scope mode, and the screen uses the familiar F-16/F-15 format, and TDC moves in X/Y axis normally.

"Programming today is a race between software engineers striving to build bigger and better idiot-proof programs, and the Universe trying to produce bigger and better idiots. So far, the Universe is winning."

"The three most dangerous things in the world are a programmer with a soldering iron, a hardware type with a program patch and a user with an idea."

  • 3 weeks later...
  • ED Team
Posted

Is it going to be the TDC as an axis option in upcoming update or later?

AMD Ryzen 9 3900X, GeForce RTX 2080Ti, 32 GB DRAM, HOTAS TM Warthog, FSSB R3 Lighting, MFG Crosswind, Win 10 Pro

Posted
Is it me or is locking up targets with the TDC difficult, i can't count the amount of times my cursor is basically on the aircraft but it won't like, and since it's so sensitive it is extremely accurate to pinpoint onto the target.

I had this too but if this happens the button on the weapon control panel to lock the nearest target doesnt't work either. So i think the "problem" is not (only) related to TDC sensitivity. I have locked targets with the TDC only near the symbol on my display.

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

Posted

I had an interesting observation with the "can't lock target" problem. I did an intercept mission and shot my first 530D missile, the enemy bandid went defensive and the lock broke as soon as he was 90° aspect to me as expected. After he reappeared on my radar screen i tried to lock him again with the TDC or the "lock nearest target" button but both doesn't work. I reduced the radar range scale of the screen far enough that the bandid wasn't showing anymore and increased the range again, and i could lock the bandid instantly. I unlocked the target and tryed to lock him again but it wasn't working, decreasing/increasing the range and locking him again worked flawlessly.

 

Can someone confirm this behaviour?

 

Maybe there is a bug in the "lock-algorithm" or it was just a accident that it worked like described?

 

Zeus wrote once that decreasing the radar screen range so that a target isn't shown anymore will work like a filter for any target that is not locked in STT.

 

The range selection acts as a filter. If not in STT, when you reduce it, all contacts above that range, even locked ones, will be dropped.

 

If you want to refuce range for better visualization, wait until your locked contact is past the half way mark

Modules: KA-50, A-10C, FC3, UH-1H, MI-8MTV2, CA, MIG-21bis, FW-190D9, Bf-109K4, F-86F, MIG-15bis, M-2000C, SA342 Gazelle, AJS-37 Viggen, F/A-18C, F-14, C-101, FW-190A8, F-16C, F-5E, JF-17, SC, Mi-24P Hind, AH-64D Apache, Mirage F1, F-4E Phantom II

System: Win 11 Pro 64bit, Ryzen 3800X, 32gb RAM DDR4-3200, PowerColor Radeon RX 6900XT Red Devil ,1 x Samsung SSD 970 EVO Plus 2TB NVMe, 2 x Samsung SSD 2TB + 1TB SATA, MFG Crosswind Rudder Pedals - VIRPIL T-50CM and VIRPIL MongoosT-50 Throttle - HP Reverg G2, using only the latest Open Beta, DCS settings

 

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...