vparez

Hi guys, been experimenting with JTAC lasing in past few days and I got a problem... I do the same mission over and over and in one case I hit all 4 targets, while in the next try I can't hit anything as if JTAC is not lasing. The same targets, the same mission, same comms from my side and JTAC. The targets are not moving. What am I doing wrong? What are the constraints on the weapon launch? I see here people doing it from extreme attitudes and altitudes. I can't pinpoint the reason when the weapon doesn't guide. EDIT: Ok, I found what was I doing wrong: when I send SPOT and then IN to the JTAC, he doesn't lase anymore (although he says cleared HOT). I thought that these two commands should be given before the attack. Is this correct?

Thanks Zeus! I only think that the EW mode switch is STANDBY-HOTAS CONTROLLED-JAM (priority CM). And I doubt that the ECM button on HOTAS would be locked to JAM. Jamming is not something you want on all the time, except when you temporarily push a button to switch it off. I think that Chuck did it right in his guide. But this is all just my logical thinking, I certainly don't have any definite info. Keep up the good work, M2000C is really a wonderful module. Ironically, it reveals the age and the lackings of the DCS engine! :)

Yes, that seems logical. So there should be another command available for Jammer STANDBY which would push the EW mode button into VEI position.

Don't forget that the radar EMITS, but it also RECEIVES. So if the emission from a source behind the radar is of correct properties, it may be received by the radar even if its dish is pointing in the opposite direction. Just like for example when a radar works, there is also radiation (harmful) behind it in the cockpit. I read somewhere that in the MiG31 pilots had to wear protective clothing, that's how intense was the radiation in the rear of the radar.

As long as we are discussing CM... The Jammer key assignments are really strange; jammer ON, OFF and TEST are working ok, but Jammer ACTIVATE is messing both with jammer power switch and jammer mode switch. And you can't put the mode switch back into VEILLE unless you click on it. So if you want to switch jamming on and off IRL, would you really be doing that using the power switch? Or is it a bad button mechanic in the sim?

I have a feeling you already know the answer to this. Sorry, I tried to help, but I misunderstood that the original request was for an FC3-type command, used in SSM.

I can't speak for the devs, but I guess that every feature possible with the current DCS engine will be implemented. The CM launching is working manually so an essential feature is there. As you see from the updates they are currently improving the INS, RWR and ground targeting modes. I am sure the CM profiles will come in due time.

But these commands are not requiring a 3-way switch. They are not in 3-way switch abstraction category but in the HOTAS category. You can assign these commands to 3 regular push buttons.

You can also you the HOTAS "AA gun select" command for a quicker selection.

I got my F22Pro up and running today with the Arduino Micro and MMJoy2! Phenomenal stuff! Now only TQS left to attach! :) Thanks Sokol for your help! +1 rep for you!

Thx, my mistake, I missed it. I guess the manual as it is right now is not an easy read from cover to cover... I guess I like pictures too much ;) Just on p118 there is the picture of the gun arming switch operation... I would have been totally lost without it!

Aaaaa, thx. Would be nice to have this info in the manual.

Hi all, I noticed quite often that I get a large X in the HUD (brake off que?) when approaching an aerial target with Magic missile selected. This happens at ranges longer than the optimal range, ie. I am not too close (I think about 3nm off). A moment after, I get the TIR que, I shoot and everything is ok. So, does anyone know why is this happening?

Hi Sokol, Thanks for the file link, I looked at it but it doesn't clarify anything for me. It seems however that the common wire of the eraserhead is on the side, where the red wire is in the TQS. So I tried to connect this to +5V, and then I connected 2 of the other grey ones to an analog input (as signal and ground)... So, yeah, it gives a response as an analog device, but It is not clear exactly how. What it does it gives positive voltage for two of the four directions, one direction gives negative voltage and one direction doesn't react at all. If I change the connected wires, this response doesn't change! I even connected two pairs of wires to two different analog inputs but the voltage from both is exactly the same and changes in the same way. I'll try to look into it some more but I am sure it can work as an analog device. Just need to figure out the links between different zones. Oh, btw, is the 10-bit resolution of Arduino's ADC enough for the stick axes? What's your personal experience? EDIT: So, just to mention, the output voltage from the stick is about 2.3V if the stick is in neutral. This changes by about +-0.1 to 0.2V depending on which zone you touch (except one zone which doesn't change at all). Looking at your photo, it really looks that the middle wire is common to all 4 zones, and that afterwards you have a line output from each zone. However, If I bring +5V to this line, every other input is saturated at 5V. In the microstick integration file, they put the common line to a -Vref pin. Maybe I am supposed to put a negative voltage to the common line, or something like 3.3V since it seems the transducers are saturated at 5V.

Hi Sokol, So, I got my arduino micro and will use it with MMjoy2 to connect both F22PRO and TQS (on the same controller which will be inside TQS). But I have a very basic question for you: how do I connect TQS buttons? All buttons on the TQS have 1 common wire and 1 wire per button. Can I connect them in a 10x1 matrix then? And what is this common wire originally? Is it +5V or is it GND? Thx!

Can you connect the TQS eraserhead as a multiaxis analog input then?

Hi Sokol, thanks for the repost. My setup is F22Pro + TQS which I forgot, since I was flying IL2 for a long time and my Saitek Aviator was quite good for this. Now that I am back into DCS and jets I would like to give a new life to these old but great controllers, especially since new ones cost 300+EUR :) I was going to use Leo Bodnar's board, but now I see I need to deal with the shift registers in the F22PRO and I don't think it would be very elegant to pass all those wires through the stick into the base... I see your post about MMjoy2 and it looks really interesting. If I understood correctly, you can directly solder the 5 wires from F pro to the board? What should I do with the TQS? How would you recommend I connect it?

Sokol, can you re-upload your chematics please? The links are dead :(

Great guide Chuck, really helped me a lot! One observation though, in preflight on page 41 action 5: V/UHFradio–MARCHE(ON) is not really correct; as you show earlier this M stands for MANUAL, not MARCHE. So, one could use P - PRESET to select a correct channel in preflight, not necessarily M. It certainly isn't powering up the radio.

Thanks for the welcome! Of course thats true, but this leaves the rest without info... I cant see the picture so i dont know exactly where friendlies are. Just leaves me useless and late to help. Anyway, i am glad to see people doing the gci job, it really increases immersion! Nice campaign you guys have here, really well done. Hope you all dont go too much into the balance and whowon debates... its not worth it when we have such a good multiplayer experience!

Hi all, i am new to BF and i flew a few sorties and it wascgreat fun... i can just say that blue GCI was not working very well and the reds seemed much better organized while mostly outnumbered. So i dont think its the weapons, nor is it the individual skill, but teamwork which is the deciding factor. I personally was a bit disappointed how blue gci payed no attention to new players and worked only with pilots they knew from before. In spite of my best efforts to sign in to a proper gci channel, announce my flight and ask for tasking, i was mostly forgotten by the operator. One thing i would like to know (and pardon my ignorance) why does the gci always give directions with respect to a certain player? isnt it more useful to refer to a preset bullseye so that everyone has an idea where is stuff without needing to clutter the channel with questions? of course when the friendly is close to engagement its easier, but when a gci gives a picture it would be much more informative to do it with a common reference?

1. ARH is continuously working to acquire a contact. a chaff that caught the attention of the seeker might at some point reflect less energy and the seeker looses it. then the seeker might have a chance to reacquire the real target. 2. SARH tracks a reflection of the main radar beam but chaff near the main target also cast reflection, the misile isnt specifically told which reflection to track. if the chaff cloud near the locked target casts off a powerful enough reflection the missile might go for it.

Ok gents, I give up on this campaign. Haven't been playing DCS for some time now, so I am a bit surprised how effective are chaff all of a sudden. I sent my wingman to engage while we are still in BVR. He fires... misses... I fire 3x r27er, 1x r27et and finally 1x r73... and they all obediently go for a chaff or a flare. I mean, really?

Hi all, I noticed a lot of problems with the ACS (autopilot). It seems to fight a lot with either the natural stability of the airplane or with the fly-by-wire system (FCS). Most notably it it over-controls initially and then oscillates until much later it finally stabilizes the axis. This seems to me indicative of a very aggressive gain setting of the controller (a PID controller?). I observed this problem not only with the pitching but also when stabilizing the roll. For example, if you engage altitude hold, it definitely oscillates a lot around the pitch axis, but also around the roll axis. I believe that there are also issues with the FBW system since in free flight it tends to over-stabilize the plane in the roll axis. If you bank the airplane a bit suddenly but not a lot, the plane goes back to horizontal, instead of stabilizing at the bank angle you input (after you let go of the stick). Not to mention that the general trim characteristics of the airplane are very much reminiscent of an I-16... If SU27 performs like this in reality... wow, what a failed controller design...

Mirage III would be the best opponent. F4 vs MiG21 is a very dissimilar setup. and would better be suited for a full era sim. I would buy a Mirage in an instant.