kingpinda

What i've read is that you can only hook symbols on the tad and then set to spi. So when tad is soi you can make a markpoint on the map with Tms right short then set the dial from steerpoints to markpoints or something like that so the markpoints show up on the tad. Hook/spi that.

Hehe lol been there done that.... After a hour of fiddling to get it back in... I start up the game... and they were upside down!!! NOOOOOOO lol I think I've been a whole day busy with the pedals :p Too bad though that with the spring out I found out that there is a slight hardware deadzone :/ For taxxing and takeoff I had to use curves.. Bah I hate curves...

Yeah I noticed in that mission in the mission editor that group was set to 2. I editted the mission to 1... But then in game the group id was set to 0 and I was identifying myself to atc as 9-1.... ? The wheels up bug does seem to happen. But maybe not 1:1 also some users have experienced the group id reset/reversal not when own wheels are up but when WINGMEN wheels go up... One thing though. Why do you mention the freq? I mean on the one hand its obvious with these frequencies that you will need to switch the vhf am radio to be able to talk to either to atc or jtac and on the other hand... If you don't get the nine line you most definately know you are not getting the triangle either. :p edit: btw.. I haven't been able to find anything that would give me the idea what ID JTAC is looking for *yet*. I just noticed my group id being 2. But for some strange reason edditing this to 1 has unexpected results, see above. I must say though that the editor is something i'm not quite familair with.

Yes switch point 3 and 4 around. Remember.. set ID AFTER gear up.. because of the bug.. buggy bug bug... and then check check before contacting JTAC check.

Aah sorry Sticky i'm blind :)

@sticky: one more thing. Sometimes the triangle is further away than you anticipate. Are you sure the tad is zoomed out far enough to see the triangle? I've missed a couple of targets because of this :p

Off Topic: Sorry Lone crow but i have been staring so long at your signature by now... Shouldnt your sig be the other way around? since landings are more difficult? edit: Bugger I just got it... its not the manner in which you land just THAT you land lol. disregard. ps on topic I have no difficulty finding enemies in campaign missions. problem is they ussually see me first.... :/ and yeah use JTAC that helps heaps.

lol now thats even weirderder :p I do know that i'll be flying with easy radios from now on... just to have one buggy thing less to think about.

I haven't found it yet. But the problem is that there apparently is a bug that when your gear leaves the pavement your netid can be reset. So always check your ID when wheels up.

I don't know actually but in the campaign missions i have flown it seems to be ID 1. I did try to make some sense out of the mission editor information. I even tried to set my flight to group 1 instead of the 2 it was programmed to. Afterwards in flight I was over the comm identifying myself as 9-1??? Then after takeoff I looked at my net id and it was at zero. Presumably due to the net reset bug when gear leaves pavement. I manually made it id 1 and I got the data. Be sure to check your id before contacting JTAC :p I was doing the first campaign I think received the nineline, got standby for data. No triangle. Checked my net id. It was set to zero, changed it to 1. Contacted JTAC tried to get the data again. Had to decline the mission. Again contacted JTAC: No further tasking.... lol.

You could do that I think but what works better is simply remove the bit after the = and putting the {25.0, 86.0} there instead. Also make sure if you don't know already not to make these adjustments with notepad. but use notepad++ instead. Google it to download.

yes if data isnt'received via triangle then (group) ID is wrong. So press the NET osb in lower right corner from your TAD. and then press 1 in the scratchpad beneath your hud and then push on the top ID. then press 1 again in scratchpad and push the lower ID. when both are set to 1 it SHOULD work. regarding mavericks yeah I don't know if the different types matter much but they will lock in my experience anywhere between 7 and 5 nautical miles.

If (not when) Jtac answers and your id is correct (check the tad for the NET osb) it should work. There are numerous reasons Jtac may not answer. most are beyond me. maybe something with the campaign missions. also there is apparantely a bug whenever your gear leaves the ground that net id is reset to 0. so you need to set both back to 1 again in the NET option on the TAD screen. But in the regular missions and quick action missions JTAC works fine and i receive the red triangles.

Exactly that's why I posted how to delete the old driver... But I don't know lonecrowe has tried what I posted. Think not though. We having been giving quite a few tips. Have you tried all of them or not? REALLY REALLY try the correct install method: Unplug camera, deinstall trackir, delete driver from device manager (you might have to reinsert the trackir because it might not show up in device manager when unplugged) have it deleted from HDD and then reinstall trackir beta and then plug in camera. Have you done this?

I see no reason why that shouldnt be possible if your software allows for mouse click binding on joystick buttons.

I havent tried this myself yet but I imagine if you can use your hotas software to map "left mouse click" to a joystick button that it would be as easy as that. edit: although... A-10c cockpit uses three things... left mouse click, right mouse click and scroll for dials for instance.

Weird. I havent been able to make Trackir work in a-10 64 without the beta software.

ah well if it works for you. I take it you don't use a-10 64 bit then.

yes when starting a mission and you see the briefing you will notice below a button mission planner. click that and then to the right there is a grey bar with buttons 1 of those buttons is weapons layout. highlight a loadout you want and exit mission planner then start mission.

and it sees the 3 little green lights in center of software box also? Did you go from 32bit to 64bit trackir software? try unplugging camera, deinstall trackir, delete driver from device manager when it asks delete driver from hdd click yes, reinstall beta track ir and then plug back in the camera. that way you are sure that the driver shipped with the latest beta is being used. I had some problems with that when going from 32bit to 64bit. edit: maybe try and play with the light filter threshold. in the camera tab. But most importantly make sure the 3 lights are in the center of the box in the software. If your camera isnt precisely in front of you you can also input a camera angle. and if that all fails maybe make the profile a bit more sensitive so you don't have to turn your head all the way to the left. I at most have to turn my head 40 degrees to the left to be able to simulate that i'm looking over my shoulder in game. I also tweaked my profile more sensitive in the pitch down area. This is because I otherwise strain to look down. its much easier to look up than down so i tweaked that in.

also make sure trackclippro is highlighted and not trackclip which is just above that one. It acts funky using trackclip function with trackclippro.

Also I believe the time of day has something to do with it. one or both types have problems locking on in dusk. Actually i'm not sure anymore I might be confused with black sharks skval.

Also concerning track ir updating from 32 bit to 64 bit: In my case unplugging and plugging back in usb did not help me to get camera detected. After uninstalling track ir 32 bit i had to unplug usb, delete driver from device manager and install 64 bit software and then plug in usb. That did the trick

Actually you might be able to do that yourself. i know you can export the mfcd's to a different monitor by changing the appropriate lua files and editting in the coordinates but you may even have them overlap on your mainscreen maybe.

THAT'S THE SPIRIT!!! yay :cheer3nc: