Jump to content

Recommended Posts

Posted

A few thoughts and current frustrations - not so much with the sim but with the hardware interfaces I'm using.

 

 

1) TrackIR - I've got version 4 with the clip that attaches to the front of a baseball cap. I've had this for a few years but rarely have used it since I've never been able to get it to fucntion properly. So many people seem to be able to use the TrackIR without issues - its frustrating. To have any hope of efficiency in the A10 cockpit a TrackIR is needed and I just can't get the f'ing thing to work right. The cockpit display goes crazy - spinning around or being otherwise jittery when I try to 'look down' with the TrackIR. I need to be able to see the left and right side panels head on - that is not looking at them fron the side - (I want to see the text on the panels properly, not from the side). Other times if I move too close the screen freezes until I move back.

 

I've got the camera angled down a bit approx. 6" and I'm about 24" from the screen. I'm using the DCS TrackIR profile I found referenced in the DCS forum.

 

2) I'm using the Saitek X65F without any Saitek driver or programming done. Just straight into the USB. I've been able to set it up to approximate the WartHog's HOTAS. Trimming the Warthog with this stick is very difficult - constant pressure must be applied and if I need to press the weapon release button I have to release pressure to move my thumb - and then I've moved the reticle off target. There isn't much pitch movement in the controller A10's setup screen to create enough of a deadzone. If I need to trim I usually reach over with my left hand to adjust the trim hat. The trimming in the sim also seems very coarse - I need to be able to fine trim the elevator.

 

I am also using a FlightSim seat from Playseat which has side trays for the HOTAS. My stick is currently on the right tray - similar to an F16 side stick. I've got to get it center mounted so that I can - steer left handed when I need to use the mouse...

 

Q: Is anyone using the Saitek X65F with its 64-bit driver and programming software? Are you able to adjust the deadzones so trimming is easier?

 

Q: Is anyone else having issues with trimming this aircraft?

 

3) ThrustMaster MFD screens - I think these would be very helpful (as long as they're easy to setup) - pressing the MFD buttons would be more efficient than using the mouse.

 

Ultimately - I plan on getting a TM A10 HOTAS, but before I spend $500 I want to make sure I'm truly addicted to this sim. The learning curve is very steep and I've a ways to go...

Posted

About TrackIR, I've had frustrations with it too. If you open the "camera view" of the TrackIR software, and experiment with it, you'll find the cause of most of your issues. I've found that the camera needs to be quite a bit higher than the bill of your cap in order to prevent it from "freezing". It's usually because the bill of your cap either begins blocking the reflectors, or the upper reflector actually falls below the two lower reflectors due to the camera's perspective when you tilt your head back.

 

I'm not using the X-65, but I would suggest using Saitek's drivers rather than the generic USB plug and play ones from Windows. That might help out your trim. Not sure though.

[sIGPIC][/sIGPIC]

How To Fix Your X-52's Rudder!

Posted

and make sure you dont have the trak-clip pro selected if your using the one that goes on your cap visor. I switch between the two , depending on if headphones are needed or not, and if i dont tell the software which i'm using i get strange movements in game.

I've been using TiR for a couple of years now and still find myself tweaking it periodically, it seems that for me it is a continual WIP, don't give up on it, once you get it down, you'll wonder how you ever did without it.

The MFD's simply plug in and away you go, no programing required for the A-10, and add to the immersion greatly.

Posted (edited)

To point 1: As per others plus...

 

I also have TIR 4 with the cap clip and it works great. If you are not already aware you can use version 5 software with TIR4. They have 64 bit drivers out now at naturalpoint.com

I've never fully got rid of the jitters when looking down, but careful profiling can make it good enough.

 

You will not be able to get the panel views that you want with TIR (maybe someone has done it, but not me). I use snap views from editing the views files. I can snap to CDU, Tacan, Radios, Engines, warning panel, HUD and of course MFCDs. I'll show you how if you want to try it.

 

Enjoy the journey,

BiPod.

Edited by BiPod
Posted

As there has been a request, I have added an image below.

I will get back to you within 24 hours with clear instructions, but you may find info elsewhere with a search. (Not my particular tweaks though.)

Anyone else is welcome to help here if they have something to add.

NB. ED does not want you posting bug reports if you have edited any files.

 

picture.php?albumid=469&pictureid=3187

Posted (edited)

Sandman appears to have done something similar here http://forums.eagle.ru/showthread.php?t=66617 but he has no pics.

Click on the link in his thread to find the original instructions. It's probably best that I don't start a new thread. It is already covered.

The snapviews are mapped to the numpad, but I have them also linked to my Saitek x52 HOTAS.

My tweaks are provided in the spoiler below if you want to use them instead. Sorry I haven't labelled the views.

 

 

 

Snap[11] = {}

Snap[11][1] = {}

Snap[11][1]["y_trans"] = 0

Snap[11][1]["x_trans"] = 0

Snap[11][1]["z_trans"] = 0

Snap[11][1]["vAngle"] = -26

Snap[11][1]["rollAngle"] = 0

Snap[11][1]["viewAngle"] = 65

Snap[11][1]["hAngle"] = 0

Snap[11][2] = {}

Snap[11][2]["y_trans"] = 0.15

Snap[11][2]["x_trans"] = 0.15

Snap[11][2]["z_trans"] = -0.5

Snap[11][2]["vAngle"] = -90

Snap[11][2]["rollAngle"] = 0

Snap[11][2]["viewAngle"] = 45

Snap[11][2]["hAngle"] = 0

Snap[11][3] = {}

Snap[11][3]["y_trans"] = 0.15

Snap[11][3]["x_trans"] = 0.32

Snap[11][3]["z_trans"] = 0.75

Snap[11][3]["vAngle"] = -90

Snap[11][3]["rollAngle"] = 0

Snap[11][3]["viewAngle"] = 30

Snap[11][3]["hAngle"] = 0

Snap[11][4] = {}

Snap[11][4]["y_trans"] = 0.15

Snap[11][4]["x_trans"] = 0.15

Snap[11][4]["z_trans"] = 0.5

Snap[11][4]["vAngle"] = -90

Snap[11][4]["rollAngle"] = 0

Snap[11][4]["viewAngle"] = 45

Snap[11][4]["hAngle"] = 0

Snap[11][5] = {}

Snap[11][5]["y_trans"] = -0.27820714509734

Snap[11][5]["x_trans"] = 0.32762247014528

Snap[11][5]["z_trans"] = -0.24479886800933

Snap[11][5]["vAngle"] = -10.651849345676

Snap[11][5]["rollAngle"] = 0

Snap[11][5]["viewAngle"] = 35

Snap[11][5]["hAngle"] = 0

Snap[11][6] = {}

Snap[11][6]["viewAngle"] = 34.340549468994

Snap[11][6]["x_trans"] = 0

Snap[11][6]["hAngle"] = 0

Snap[11][6]["y_trans"] = 0

Snap[11][6]["rollAngle"] = 0

Snap[11][6]["vAngle"] = -9.5

Snap[11][6]["z_trans"] = 0

Snap[11][7] = {}

Snap[11][7]["y_trans"] = -0.27820714509734

Snap[11][7]["x_trans"] = 0.32762247014528

Snap[11][7]["z_trans"] = 0.24479886800933

Snap[11][7]["vAngle"] = -10.651849345676

Snap[11][7]["rollAngle"] = 0

Snap[11][7]["viewAngle"] = 35

Snap[11][7]["hAngle"] = 0

Snap[11][8] = {}

Snap[11][8]["y_trans"] = 0.15

Snap[11][8]["x_trans"] = 0.58

Snap[11][8]["z_trans"] = 0.75

Snap[11][8]["vAngle"] = -90

Snap[11][8]["rollAngle"] = 0

Snap[11][8]["viewAngle"] = 30

Snap[11][8]["hAngle"] = 0

Snap[11][9] = {}

Snap[11][9]["y_trans"] = -0.4

Snap[11][9]["x_trans"] = 0.30

Snap[11][9]["z_trans"] = 0.1

Snap[11][9]["vAngle"] = -26

Snap[11][9]["rollAngle"] = 0

Snap[11][9]["viewAngle"] = 35

Snap[11][9]["hAngle"] = -18

Snap[11][10] = {}

Snap[11][10]["y_trans"] = -0.4

Snap[11][10]["x_trans"] = 0.30

Snap[11][10]["z_trans"] = 0.1

Snap[11][10]["vAngle"] = -26

Snap[11][10]["rollAngle"] = 0

Snap[11][10]["viewAngle"] = 40

Snap[11][10]["hAngle"] = -18

Snap[11][11] = {}

Snap[11][11]["y_trans"] = 0

Snap[11][11]["x_trans"] = 0

Snap[11][11]["z_trans"] = 0

Snap[11][11]["vAngle"] = 5.1931438446045

Snap[11][11]["rollAngle"] = 0

Snap[11][11]["viewAngle"] = 45.299549102783

Snap[11][11]["hAngle"] = 10.910388946533

Snap[11][12] = {}

Snap[11][12]["y_trans"] = 0

Snap[11][12]["x_trans"] = 0

Snap[11][12]["z_trans"] = 0

Snap[11][12]["vAngle"] = 5.1931438446045

Snap[11][12]["rollAngle"] = 0

Snap[11][12]["viewAngle"] = 45.299549102783

Snap[11][12]["hAngle"] = -10.534552574158

Snap[11][13] = {}

Snap[11][13]["y_trans"] = -0.041336805555555564

Snap[11][13]["x_trans"] = 0.36

Snap[11][13]["hAngle"] = 0

Snap[11][13]["viewAngle"] = 95.0

Snap[11][13]["vAngle"] = -23

Snap[11][13]["rollAngle"] = 0

Snap[11][13]["z_trans"] = 0

 

Thanks to BoredTechie. I have used/altered some of his original work with some of these views.

 

 

 

Edited by BiPod
  • Like 1
Posted
To point 1: As per others plus...

 

****

 

You will not be able to get the panel views that you want with TIR (maybe someone has done it, but not me). *****

 

Enjoy the journey,

BiPod.

 

I have Trak ir 4pro and cap + clip, i don't have any problems to look panels, it's quite easy. Use zoom, i have mapped it to my g940 r2 axis,now i have Binoculars in cockpit :smartass:

 

I can send my tir profile if someone need's it :thumbup:

Oculus CV1, Odyssey, Pimax 5k+ (i5 8400, 24gb ddr4 3000mhz, 1080Ti OC )

 

 

[sIGPIC][/sIGPIC]

Posted
A few thoughts and current frustrations - not so much with the sim but with the hardware interfaces I'm using.

 

 

1) TrackIR - I've got version 4 with the clip that attaches to the front of a baseball cap. I've had this for a few years but rarely have used it since I've never been able to get it to fucntion properly. So many people seem to be able to use the TrackIR without issues - its frustrating. To have any hope of efficiency in the A10 cockpit a TrackIR is needed and I just can't get the f'ing thing to work right. The cockpit display goes crazy - spinning around or being otherwise jittery when I try to 'look down' with the TrackIR. I need to be able to see the left and right side panels head on - that is not looking at them fron the side - (I want to see the text on the panels properly, not from the side). Other times if I move too close the screen freezes until I move back.

 

I've got the camera angled down a bit approx. 6" and I'm about 24" from the screen. I'm using the DCS TrackIR profile I found referenced in the DCS forum.

 

 

Thats the reason why i have bought the trackclip pro. Since using trackcclip pro, i never had this problem in all my games. :)

 

Regards Intruder

Monitor: ASUS TUF Gaming VG27AQL1A| Case: Thermaltake Overseer RX-I | PSU: EVGA SuperNOVA 1300 G2 80+ GOLD, 1300W| Mobo: Gigabyte Z390 Aorus Master | CPU: Intel Core i9 9900KS @5 GHz | CPU-Cooler: Noctua NH-D15 Tower Cooler | RAM: 32GB G.Skill F4-4133C17-8GTZR | GPU:NVIDIA GeForce RTX4090 OC 24GB |SSD: Samsung SSD 860 M.2 1TB | Keyboard: Logitech G110 | Mouse: Logitech G502 | Gaming Devices: Hotas WW Orion 2 Stick&Throttle, Thrustmaster MFD, Pimax Crystal, Stream Deck XL

 

[sIGPIC][/sIGPIC]

Posted

The going crazy happens when :

-one of your reflective dots is no longer picked up by the TIR-unit when you move your head.

-another IR-source (light, reflection, lamp, sun...) behind you periodically pops into vieuw of the TIR-unit.

 

You can check the position of the dots in the tracking-window. Make sure the TIR-unit picks up the dots, even if you move your head to extreme positions.

i7 6700k/GTX1070-8G/MSI-Z170A Gaming Pro Carbon/32GB DDR4 Kingston HyperX PREDATOR DDR4 3000MHZ Vengeance 1600/TM Warthog #6106/Samsung SB350_S27B350H/OCZ Agility3 SSD 128GB / Win10-64/TIR5



 

 

Posted
A few thoughts and current frustrations - not so much with the sim but with the hardware interfaces I'm using.

1) TrackIR

2) Saitek X65F

3) ThrustMaster MFD screens

 

1) As has been mentioned, use the TIR software to see what the camera is doing. I have the TIR4 camera with the TIR 5 software. Works well for me. If you have multiple monitors, you can even bring TIR up on the second while you have the game on the first and see how it behaves. I use the ballcap/trackclip method and have the camera right at eye level. Be sure you have the cap angled down enough so that the brim doesn't block a reflector. The camera must be able to see all three to be able to calculate position and orientation.

 

Something to note, is, in the actual aircraft you really can't read the switch labels clearly from a normal seated position. After a while you don't read them. You just know where everything is and the labels are just a guide. It takes a bit of practice, but it comes. Ok, a lot of practice... :)

 

2) I don't use Saitek gear, but as was suggested, the Saitek drivers would be a good start.

 

3) I was considering buying the MFD screens but have found that you really don't do much fiddling around in the MFDs, at least during "dynamic" phases. If I have to spend any time in there I'm usually able to engage the autopilot and use an MFD snap view. And to me, the content of the MFD is more important than the buttons. If you get the live display behind the buttons then it might be worth it. (yes, I know some folks here have that working)

Posted

I have the tri4 and the track clip pro. In my opinion it is a much better set up then the vector clip. I also have the X-65f, but I do not use the software, programing, but I have the 64 bit drivers. I found that the options menu and axis controller is great in game.

I have no issues looking at the panels while using trackir, it seems natural to me, Hell I can even see the eac switch behind throttle. I know a few have already said make your own profile. It wil make all the difference in the world.

I would bring up a new profile and have the following up, heads and camera, and start adjusting the sliders to make it do what you want it too. Have also true view clicked. It may take some time but well worth the effort.

 

 

 

 

Bullet

I7 4790K running at 4390 with a gigabyte board with 16 gigs of ram with an Asus gtx 660-ti and 2 tb of hard drive space on 2 wd hard drives. A X-65F Hotas with trackir4 and pro combat peddles. A kick butt home built machine unfortunately running a windows 7 OS.

Posted (edited)

Hello JCook,

 

For me TIR 5 works fine with this sim.

I also use the X65F. It was hard at the begening :joystick:, but now, is a very great pleasure flying this bird with this stick :pilotfly:.

Saitek's control panel is very usefull for calibrating force's settings.

Basic defaults are unusable with the A-10C. I also use the programming utility, only for set the wheel bake on the pinky button.

All the other settings are made in DCS's configuration tool.

I think using dead zone parameters is a bad thing with this stick (and may be with others...).

Try curve settings with X/Y axes. Sorry, but I'm at work and I don't remember the value I'm using (pehaps around 11, but I'm not sure :unsure:).

 

Hope this help you,

best regards

Jean-Louis

 

ps: sorry for my poor english :cry:

Edited by HotelPapa
  • 2 weeks later...
Posted

BiPod - I've edited my lua files (what does lua stand for anyway?) and now I have the snap views - however there doesn't seem to be a view for fwd-left panel (fuel switch area). Also pressing the Left-Win key with a keypad key is going to require having an extra hand - but I guess the solution is to map those snap views to the keypad keys only. The views only appear when I hold down the key - which isn't going to allow me to use them to press buttons - like programming the CDU from the view (again not enough hands).

 

How can I make the view an on/off view instead on a momentary view?

 

Thanks

  • Recently Browsing   0 members

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