NWGJulian

exactly! i personally do it the same way as@JSpidey does, and it works good. but is that the right way? i have no idea. i will try the suggested method with just looking into the BS device (ignoring yellow circles) today and see if its any different

the problem is not that he hadnt meantened it. he obviously did meanten it and showed it. but its not clear what he is exactly doing -> how does he adjust the camera position? by just moving his head down („squeezing“ himself down), or by lowering his virtual position with the numblock keys? i think after some testing I now know how to do it -> squeezing down to align the circles and the IHADSS center is enough. but is this correct, do i even need to try to make the circles concentric? i dont know, it wasnt really clear from the video. all i can say is that it works for me. the manual also says that i have to get into a „natural posture“, which is imho the exact opposite of „squeezing myself into position“ just a few posts about mine, someone said that all he does is looking into the boresight, and his alignment is good. he basically ignores everything related to those yellow circles. is this correct? i dont know, because it is not clear. others say they align their camera first with num-keys.

just wanted to note that the fix „set a deadzone of 2 and 3 and a small curve to the axis“ did the trick for me! works reliable now! but the initial problem is obviously still there

okay, thanks! it just wonderes me that - at least in the youtube videos - people seem to try to make the yellow circles concentric. there is also a picture of that in the manual.

this is actually exactly the opposite what others say … i dont know who id right. you say just look straight into boresight, others say place your head so that everything is aligned. others say you need to adjust the seat so that everything is aligned without moving the head at all! the official quick start manual says pretty much what you say -> head position natural posture, look into boresight, click, finished. nothing about concentric at all i think we need @Wags to clear this up, i think there is a lot of confusion about boresighting

will try that, thanks!

i will try and get a track-file, but yesterday it didnt happen once. i shot 8 hellfires without a problem.

what do you mean with small null? i have the same problem

i did exactly that and i like it! -> 8bitdo pro 2 pad

i have the same thing. but sometimes i cannot slew the cursor at all after that.

i think i could create a perfect track-file. it is the quickstart AH64 HOT START mission. i am in pilot seat first, cursor works. then i go to CPG seat, and the cursor still works. suddenly it doesnt work anymore, but suddenly it works again. in the end it doesnt work. all i do is, slewing around with the TADS, press slave/unslave, SIGHT select HMD and TADS, etc. it changes everytime i restart the mission EDIT: it might have to do something with slewing the cursor the the border of the screen cursor_not_slewable_as_cpg.trk

hi all noticed this issue a few times today. laser is ON (util-page), codes are set correctly and tads says i am in correct parameters for the hellfire shot (small solid box). but the small solid box doesnt get big, means the hellfires is not tracking anything. laser is 100% ON, and i also can shoot the hellfire. but obviously its not hitting. if i re-assign the same laser codes after deactivate and activate again the LASER and MSL under wpn->utiliz, suddenly it works. but only for like a few shots, suddenly i have to reassign laser codes again, and i get the message „REMOTE“ on the tads. anybody else with this problem?

hey guys i have flown for hours today with my friend, and this problem occured basically everytime. it should be easy to reproduce: 1. after hot start, i can simply place some waypoints and target points on the TSD. works with mission grip cursor and also with LHG cursor on the tedac handle 2. get into combat, engage bandits, sight to tads, fire laser, launch hellfires, blow stuff up etc 3. go back to TSD and try to place some new waypoints 4. notice that you cannot slew your cursor anymore anybody else with this problem?

+1 just like the throttle levers in the F14. 100% supporting this.

making an AI intuitiv and autonomous is a challenge. on one side you want him to do things without u needing to say what to do, and i think he does that pretty good, turn on weapons etc. but on the other hand he cannot magically just know what YOU want HIM to do. in the end it is an AI and cannot do anything without your input, which means you need to have some sort of buttons etc. to tell him. tbh i like the jester menu much more, but thats how ED designed george, more a10/f16 style with a 4way switch. it is a design choice and you will NEVER find a way that everybody will like it. but i think most people will at least be ok with george. i heard a lot of people dont like the jester menu and prefer the petrovic style, but i LOVE how jester works this is a problem with every AI. if you want to use him hands-free, just use voice commands if you could decide how george should work, how would you design it? i am just curious imho the solution to this problem is a gamepad. i am using the 8bitdo pro 2. i binded basically all important TEDAC controls on it, so i can use my HOTAS as CPG with almost the exact same bindings as i would be the pilot

what do you expect? george is basically like petrovic in the mi24. you give him orders, „look over there“, „target that guy and shoot“. or when he is the pilot „fly there“, „fly with xx knots and in yy ft height“, „hover now“. it is very basic but it works. but if you want the full great ah64 experience, u NEED to go multiplayer! i mean, yes you can have fun with bots in mario kart. but it is a whole other game when played with your friends!

i think this thread pretty much nails it. this is how it should be implemented. the button that transmits the radio1/2, intercom, ptt, etc. (dependend of the module), should transmit to the AI menu when short pressed, and to the voicecomm when held down. no need for extra keybinds, just place the voicecomm buttons to these buttons. this works for modules like the f16/f18, where you have different buttons for the radios without a PTT button. and also for modules like the apache, where you have a button to cycle through the radios, and a PTT button (again, short press = ai menu, hold down = voicecomm)

+1 this. exactly this! in addition, i want my voice ptt buttons on the module keybindings, not on "general". because on the f16 i use a 4way hat UP and DOWN, on the f18 its LEFT and RIGHT, and on the hind i actually use the trigger first and second detent.

i think the „problem“ is, that these videos are really theoretical, and that everything will be a lot easier and self explaining as soon as people can try it out themselve.

i tried something similar with a modifier switch for tedac controls on the warthog stick too, but after all, it seems just too complicated, so i decided to go for a 8bitdo gamepad and bind them there (like suggested from bradmick) this whole topic is going to be interesting when the apache released

i sent the jetpad back to andre. 5 out of 8 motors are broken, its probably a problem with the control unit. very very unlikely to have 5 broken motors on the same time.

yep sorry, i already did

sooo i just found out, that on the working motors, there is a 12V AC signal with about 120-150 Hz. on the 3 broken motors, there is only a somewhere between 10-50 mV signal with 10-90 Hz. all connections seems to be good. sadly i cannot test the motors because i dont have a function generator at home. otherwise there is nothing i can test anymore, the electronic board is out of my skills.

they are in the SSA app, and they will be created automatically when you get into the specific aircraft. that means, at first you have to fly a mission with SSA on, and then you get the profile automatically.

grazie mille! very useful information glad i am an electrical guy, i will take my fluke off from work today and measure to see if there is power on the electric vibration motors, i will also check the electric connections between the connector and the board. i am pretty sure that i can identify where the problem is.