Sacarino111

HI. Inr¡teresting one, never thought about that design feature, IF real , what a good one! Thanks for your thoughts, always interesting and instructives. Saca111

Hi. I've seen the F16.acmi one, and I think I know what the issue is; Don't get me wrong, please, it is just my opinion. For the AIM120 to track and hit a non locked target, it is not "PitBull" what is in game, but "VISUAL": PitBull means that you already had a target lock ( STT or TWS, cant tell if that matters), you fired against it and at some point in the fly, the missile is close enough to find/track and hit it autonomously (is that a word?), so the shooter can break lock and the missile should do his thing. Visual means no lock, the shouter keeps the target in the circle shown in the HUD and keeps it there until hit/miss. From your TacView file I can't tell if you had a lock or not, so if no lock, you turned away from the target too soon so the missile could not "ride the beam", hence no track and no hit. Try to fire the missile and keep the bogey inside the HUD circle, it should home on it. Saludos. Saca11. Again, I can't tell if you had a valid lock before launch.

Hi. I can't tel if that is the cause, but most of the time I try to set the Range finder to AUTO for the gun, most the times something goes wrong and I have to re do the thing a few times; I have a "home made cockpit" (ufff) and I like to press the MPD button and the "A" key without taking the eyes off the screen. AS I said, most of the times I find I wrote something strange with multiple A s. Again, can't tell this is the reason ut I will check out! Cheers. Saca111

Hola. Pues a mi me sigue pareciendo un truño como se maneja cuando vas lento y quieres mantener un azimut y una altura, sobre todo el pedal del antitorque... Lo del compenador.... la verdad es que a mí, en esto módulo, se me ha atragantado un poco/mucho. En otros no, los manejo bien y entiendo el trim sin dificultad, pero en este..., siempre me sobre compensa, o se me queda corto, o salta al otro lado del rango como si tuviera inercia (si el cambio es grande, se va al otro extremo, un infierno, vamos). A ver si terminan de afinarlo... Saludos. Saca111

Hi. According to your picture, the CPG should not be opening fire!: A) Left hand Menu: there is no target selected. You have to press CPG Right ("D") to tell Geprge to select the marked target and designate it. A small box should appear, and expand if/when ready to fire. B) Right hand menu: George is in "FREE FIRE", so he will fire as soon as he has the target in weapons constrain. He will not follow your comand. Press "W" long to set weapons hold. C) Left hand MPCD: the HellFire is not ready to shoot from your position. First , tell George to be "weapons hold", ( "W" long ), the menu should turn Amber. Now, tell him to designate a taget ( Right on target's menu), manouver to have the target well in front/constraints and then, press the trigger (if the cover is up, if not, first press the trigger. When the CPG considers the target is OK and the Hello is stable, he will shoot. Saludos. Saca111

Hi. Yesterday I couldn't get the ACLS to engage; Link to the carier ON; Autothrottle on (close to IDLE, BTW), all ACLS anunciator lights ON, DLC out, Gear down, Flaps fully down Pressing NWS did nothing. It was a long MP mission, so I couldn't get a track. Will try it on SP and get a track. Saludos. Saca111

Hi. Same here Saludos. Saca111

Hi. I assume you are on a stable (more or less) hover, pointing in the general direction of the target and that the HellFire box is Big, yes? Assure the Trigger guardis open. Also check your assignements, just to pe om the safe side... Also, if in the pilot seat, don't forget to select the HellFire with the stick control (can't recall the exact name, I think it is WAS) before every shot, as if the previouse missile did it's job, , the CPG undesignates and then no missile is selected. Saludos. Saca111

Hi. I think it was "Left Throttle button" or "Throttle button". Something similar. A soon as I download the Update I check it out!. Saca111

HI. The ALT autoplot is working ok. You have to understand that it will do "some of the work", not all. You have first to be at a reasonable level flight/hover, with little to no oscilation in altitude, and then you enable it, and don't touch the collective, or it will self disconnect the moment you add some little variation to the collective. The trick is to enable the controlers view (CTRl+ENTR) and check its channel. If the line is over the center, it means it is "trying hard" to keep the altitude. You should add a lilltle bit of collective and re enable it again. If below, then you had too much collective at the moment when you enabled it, so it is trying to "take some work out" from the engine /collective. Reduce collective and re enble autopilot. IF you wnat to hover, first reduce horizontal speed to almost zero, then enable the auto hover and then the altitude hold (the one for hover not for flying, with the small square in the picture you uploaded.)It will do an outstandong job keeping the thing stable in place. About the SPUU (¿?), I can't tell; I activate it at start up and forget about all flight... Saca111

HI. Once the target is found, make an SPI in his location by TMS UP Long. Now that point/target is the Aircraft target, and all sensors should try to lock on it. The MAV should need an extra step, by slaving the sensor on that SPI (can't recall at this moment the name for it and I am away of DCS). ONce the MAV is pointing that target, you need to make the MAV screen SOI and once in range, TMS up Short to lock the MAv on the target. If done correctly, the MAV symbols will collapde on the target picture and then you are ready to shoot. More or less... Saca111

HI. Congratulations! Nice pannel! Looks amazing. Keep the pictures comming... Saca111

Hi. In a future update. Wait for an update and check the ChangeLog or try it ingame. Saludos. Saca111

Sure. Get an arduino MEGA 256 Rev3, original or not but be sure that it has those pins. Connect the Mega to the PC, get it working ok (try the "blink" sketch), then upload the Sketch from the link I posted. Bridge the two pins closest to the USB (the leftmost two in the picture) and them flash the new firmware. Unplug, plug back and enjoy heaven! If need be, try to PM and we should meet in discord and I guide you. Saludos. Saca111null

Yes, you need a MEGA with the pins so you can enter DFU mode. Besides that, there is no programming needed at all! it is as simple as conneting to the IDE, loading the already written code, flash the new firmware, unplug, plug it back and done. If I could make it (no knowledge on the matter at all before this) anybody can! Once flashed, the PC will recognise the MEGA as two Joysticks, each of them with 128 buttons. Depending on the code loaded, you can have 8 axis for the first joystick. The first 64 first buttons of the first JOY are dedicated to rotary encoders, so you could conncet up to 32 encoders or ON-OFF/ON-OFF-ON levers(not bad). After that, there comes the wiring and there are some tricks to know, but not difficult if some one helps you! Saludos. Saca111

Hi. Maybe I'm late, but did you knew about this? https://forum.dcs.world/topic/97434-an-arduino-usb-hid-controller-composite-usb-controller I did a few of them and can help, if need be... Saludos. Saca111

HI. Acording to your description, you haven't permission to join, as @feefifofumsaid. Set correct radio freq. Use this radio/freq, not othe other ones. Fly to a left formation and do a first call, telling your intentions to join. Wait for the tanker to allow you to "pre-contact position". You should see the tanker lights up the nav lights. Once cleared, place your AC behind the tanker (about 100 meters), declare "ready precontact". If in the correct position, the tanker should "clear to join", and the boom should descend. Fly to the correct position and stay there until the boom operator made his mouvement. Don¡t forget to press the NWS button in your JOY to get the ready light an be able to receive fuel. Stay there... Hope this helps. Saludos. Saca111

Hi. First, save all your bindings. Then; IF it is a slight right bank; Then, clear them all and check ingame . If the AC still banks, check that you don't have the TGP on right hand cheek, wich is known to cause a slight bank to the right, difficult to cancel by trimming. If so, unload it and try again. The plane should fly straight and level Once you are sure it is not the TGP, start plugging one by one the controllers (Joy, Pads etc) and check after each introduction. If you find the culprit, try to fix/clear the binding and once fixed/cleared, load the saved profiles and clear the known culprit. IF it is a violent mouvement, Check for double assignements and/or check HOTAS synchronization before starting the mission, to be sure the joy is recognized before starting. Also , mouve the joy all ways around before pressing the "fly" buton. Saludos. Saca111

HI. 1 "Is the F-16 module really incomplete in DCS; say in comparison to the A-10C II module? " YES, quite incomplete if you compare them. The A10 is a more than 10 years completed module, and F-16 is EA still, so lot of incompleteness, even though the F-16 is a real pleasure to fly and fight with. You wont be wrong if you purchase it. 2 "And is it really that much more bugged than any of the other modules and/or DCS in general?" NO. To my knowledge, some "little" bugs". It is more an incomplete than bugged one Again, you won't regret buying it... 3 " I don't fly the Viper, but was honestly of the opinion that it is of the most complete offered by DCS and functions as well, if not better, than any of the other jets." NO. It is incomplete, but very much functional. The F/A-18 is far more complete (it is out of Early Acces, by the way). The A10 is feature complete, Cold war era AC are complete, the P51 also is complete etc. Get the free trial, take a taste of it, then pay the fee and you will be happy... Saludos. Saca111

Hi. A10C II, no doubt! The F-16 would also be a thing, but it is incomplete and bit bugged (?) in some features. And for the very very man, the F-14 Tomcat... Saludos. Saca111

HI. Nice video. Thanks for the effort. Saludos. Saca11

HI. Can't tell, as I don't use to play campaigns, but the GBU-31 should be plenty enough. (if time period or constrains accept it) Saludos. Saca111

HI. I only have a X52Pro, but I like fiddling with my toys and made some mistakes soo... 1 Isthe stick showing properly in Windows ? If YES: Then it is inside DCS. Erase all axis bindings and redo. Consider a DCS repair... If NO: Then it is inside the Joy. By the image you posted, it looks like the pot/Hall Effect Sensor is locked in max position or shorted to ground (depends on the wiring position). Try disconecting the POT/H.E.S. and using an external one and see if ot goes normal. If Yes, order new POT/HES and replace. If no; Check the wires and/or traces and look for continuity issues. Other than that, it could be inside the Joy PCB, so probably you will need a new one (PCB, not JOY). In any case, I hope the warranty cover your device. I hope I could be more helpfull. Saludos. Saca111

YUCK! Heretick! Just kidding...

HI. Thanks for the answer... To me , the most limiting thing of the link I posted is the "name gate" I did try every single trick I know (wich indeed is to aks for help to any one who kows about programming, as myself I am absolute ignorant on it), so if you mange to find the way to change the windows name it would be great, I even found the "descriptor.h" file where you can change the name, and I know how change it, but couldn't compile it, always the same errors. But, besides that, al working great. I neither use any external software for it, just the DCS setup, that recognises up to 128 buttons per joy and as every arduino is set up as two joysticks, you have up to 256 buttons and 8 axis. Saludos. Saca111 And recently started fiddeling with DCS-BIOS; Master Caution light (F/A-18 and A10C), Landing Gear lever light and AoA indexer.... drooling!