Stingray66

That could really be the difference -> CIV traffic (i.e. moving trees :D ) or real objects placed in the mission editor... is it really that hard to implement the CIV traffic as real objects that do affect path finding - my tanks also dont go through buildings or trees, at least thats what I hope :) though I have to admit that moving trees might be more difficult ;)

Dunno whether this really belongs here - but have a look at this: the rescue convoi just drove through that bus...

Good so... :) just one thing: What if you hit that band accidently AFTER you have already started the engines...so "restart" ??? ?)

To bring it to a point: I think you have to decide whether you want a force sensor or not. If yes, the choice is obvious, and yes the X65F can handle all A10 functions. If no - well then I would go for the TM Warthog because it has similar functionalities that could also be used in other sims.

Without writing like 5 pages...I have it now for more than one year, and I am completely satisfied. I never had quality issues or problems with installation, software, and so on. First to mention though: As far as I know, there is only one additional axis available and that is the POV coolie. If you want another ministick to be recognized as axis you have to reassign a different axis (e.g. the z-movement of the stick, which you usually dont worry about when you have pedals) to that one. And this reassignment is not done via the Saitek software, but you'll find some manuals in the net. -> ergo: This is a little bit annoying BUT the software is great and and diminishes this annoyance to a minimum as you can configure nearly everything there. Concerning the feeling...It took me like 2 days to become comfortable with the stick. You can do very, very, very exact flyings and maneuvers, and since you can adjust the force-meter at any time, you can immediately go for a more or less sensitive stick according to the situation. E.g. in AAR I choose a "harder" profile as in normal flying. And in Falcon, I go for a more sensitive force-readout during dogfights. The amount of buttons and coolies on the stick are just fine, and indeed similar to TM whatever stick. But the ones on the throttle are overwhelming. And this renders this HOTAS system a very versatile tool for any sim you are flying. Quick&dirty: Dont worry about the force-sensing stuff - it is awesome. If you plan to fly A10 forever and no other sim, the you should go for the TM Warthog, obviously. The thing is, that I dont want to miss the precision of my force sensor anymore. BTW: IRL, pilots that do have a force sensing stick (F14,F16) love it, maybe you go through some literature or internet posts or maybe someone else can comment this - but in high-G situations you are simply better because of your stick. Admittedly, this doesnt count in the A10 ;) :D EDIT: No problems yet at all. Saitek guys in Europe are very friendly, dunno about overseas. BUT: Hehe, you shouldnt place your mobile next to the stick: Once you get a call while you are flying you will definitely crash :D took me a few crashes after I realized that, but hey, it makes perfect sense.

Although the TM Warthog might be the best, I have a Saitek X65F and I dont miss anything. All HOTAS controls are on the stick thanks to the many rotaries and coolies...

Hargh - Let me guess.... It will be released when it's ready :smartass: :D

if I lase a target for my buddy, I usually broadcast my SPI which is at or close to the target such that he can pick it up abd knows roughly where I am lasing. He then has already a SPI for the roll- in. dunno whether this is THE correct procedure - it works fine though.

That explains a lot...:thumbup:

Yeah...I know what and how that Markpoint works...it was just the symbology...I obviously never paid much attention but the last time in JTAC training where you handle a lot of little triangles it really popped out ... but now that I do pay attention to this small white triangle, it really is always a small white triangle and not displayed as every other markpoint... And yes indeed, JTAC would not make much sense without friendlies nearby :D

Thanks for all the information - really appreciated!

:D so always a white triangle ... have to pay more attention to my TAD next time...it never jumped into my eye before...just when messing aroung with JTAC triangles, then it is annoying having another triangle there... :P hmm...what can I do with these?

Didnt mean the lines -> meant the crosses.... concerning the Z markpoint, I thought it is a normal markpoint and should be displayed as such (green box) - and not as white triangle... could be - but in this mission -> Dragon's JTAC training, there were just enemies... Could the crosses be related some issue with the EGI???

Two maybe simple question about the TAD and its symbology: 1) under which circumstances are all waypoints of a flight plan displayed with a cross in the box - and if I deselect the flight plan the crosses stay...(see screen below) 2) Which condition has to be met that markpoint "z" displayed as white triangle? (screenshot below) Thanks

Well stated!

Not quite... 1) It should be disclaimed somewhere that there shouldnt be a MAV page on -> maybe I post this in the other thread about the manual improvement... 2) Far more important...although it's nice to have a shortcut for both, SOI and PAGE, it doesnt give you any benefit in quicklier selecting the MAV as SOI as compared to a Coolie Hat long... So what is the purpose of this shortcut IRL, what situation can one think of where this attribute of the CHF is needed? Maybe if you set a SPI via HUD if you unexpectedly observe a new threat and want to eliminate it -> then you can quickly go to the Mavs. On the other hand, NOT really handy, because usually the EO timer would be OFF at that time...unless you are lucky. If you had to wait then for 3 min to cool down, you have all the time you need for selecting mavs as PAGE and SOI.... :smilewink:

And you are way quicker -> multi Mav attack on several markpoints. Cycle through the markpoints with HUD as SOI - switch to the Mav with the CHF that you would in the same moment use to expand the FOV (2xCHF short instead one Coolie Hat long and then CHF short) - I suppose you save more than 2 seconds...

That sounds odd now :D Why would it make a difference in RL whether the MAV page is selected or not -> IMO it should work in all cases....

So again - it didnt work for me. What I did (track attached) Flew a training mission - just Mavs on board, tried to become better with the Mav seeker only; doesnt matter for this thread. After setting a SPI close to the targets, I slew my Mav seeker on them, forgot to select a profile, did load a profile, shot 5x RIFLE - then thought about trying this switching from the HUD as SOI, so I selected the HUD as SOI and my maverick (i.e. the last one) was active...as active as it could be and selected - pressed China fwd short -> NOTHING... Maybe I am just forgetting something... the interesting part is at the end of the track... noswitch.trk

I'll give it a try!

Indeed, page 91, china hat fw short... see screen (BTW It is also in the 1.0.0.8 manual!) ...maybe I DID understand where "odd" related to in the wrong way ;)

:music_whistling:

how is this related to the option 'Random system failures' which CAN be turned off. With it turned off I have never ever had any failures other than induced by gunshots or MY flying ;)

I stepped across this as well - not working...

Thats Kind of strange - we have the same GPU and I didn't even OC anything at the moment. Everything is running smoothly. You have the newest drivers? Edit: I use a 600W power supply which should be enough...