xaoslaad

Look for the citations. If in doubt and there is no citation add a note that a citation is needed.

Connecting the pins on a dpdt to make an on-on-on spdt really really does work. If you need witness the cruddy wiring in my controller and output in mmjoy2 i'll record it to prove it...

If it makes you feel better the MiG-15Bis and F-86F are leaving beta. I think I counted around 7 beta modules the other day. That will leave 5. And I honestly thought they were of better than beta quality anyway. Same with the MiG-21Bis. It's not like removal of the beta tag means ipdates stop either.

Ya, sorry, i wasnt specific on the direction with the resistors, but your understanding is correct.... To see if the switch is up/down you just look for 0/1 ON and to see if we're in the middle look for 2 OFF

I'd love a Zulu. More power, more missiles. I'm betting 16 hellfires never happens in real life, but the way we 'all' play... but I can't even imagine how they're going to pull off a Whiskey. I'd take either or both in a heart beat though. Whiskey would be fun to carry mixed TOW and Hellfire armamaents though.

With an on-off-on i'd normally look in this case for pin 0 or 1 to be on. With this case I'd look for 0 or 1 to be on and 2 to be off. I demonstrated with resistors because I dont have diodes handy. Of course this would work in a full blown button matrix as well.

It's murky territory lawyers seem to like to play in. I'd have been interested to see this case settled in court. I've more or less heard that you can portray an AH-1Z, but can't call it a Bell AH-1Z, for instance. They may be taking this kind of approach, using only the government designation. I've no idea the specifics or whether that's the actual logic, or what, mind you... http://www.engadget.com/2013/08/16/ea-settles-battlefield-3-and-textron-helicopter-lawsuit/

This is how I did it with mmjoy2. Turned a dpdt into an on-on-on spdt, which works great for a mode switch. I flip 6 encoders/push buttons between 3 states, so I can do nice things like flip between controlling FM, UHF, and AM radios with the same encoders, etc. In a pinch you can use a on-off-on spdt and a couple diodes to look for reverse voltage for the center pin to determine it's 'on' (no voltage would be the on position for center). This is what I did for a few days while waiting for my dpdt to come in the mail. Both on pins are wired to a third pin (think like a y cable). The diodes prevent each of the on positions from turning on the other. When either position is selected the third wire is lit up as well. When the third pin is off you know you're un center just by looking at the state of a single pin. It worked fine, albeit the wiring was a bit icky. The dpdt was a much nicer option once it arrived.

Maybe try moving the TIR camera more leftward if you can. This helped with the Trackhat Pro clip which I felt had a similar issue. Not necessarily because it caused movement problems, except that it didn't take much at all to send the bottom led out of view. Fiddling with the camera position made the led grouping much tighter and gave a lot more leeway to move

If you buy Falcon 4.0 on gog.com you get that book!

I don't recognize the OP's name. He hasn't posted his opinion ad nauseum. Maybe HE hasn't had his voice heard yet. You on the other hand have been heard over and over and over again. And the last line of your post makes it pretty blatantly clear that you didn't read mine. I flat out said I don't agree with the complaints about progress, so I think it was just put there to egg me on. Regardless of sharing your position on the topic I would like you to give it a rest too. But I know you won't so I'm done responding to this thread.

Look I don't agree with all the complaints about betas and lack of progress either but, all your obnoxious wall of text posts are probably worse. People are entitled to their opinions and to converse. Saying effectively that because you disagree you're going to drone on like a high school essay for each one is basically admitting to trolling. You admit there is no conversation with you and you're intention is to annoy people until they get in line with your thinking.... If anyone there was ever a mod should warn and ban...

Edit: Think I misunderstood the question.

Should work fine in 1.5.3. I can try later and confirm. I did my testing in 2.0, but that was only because the LGB tracking wasn't working yet for the Mirage in 1.5 at the time or something. https://github.com/ciribob/DCS-CTLD/ https://raw.githubusercontent.com/ciribob/DCS-CTLD/master/CTLD.lua It's pretty easy to use. If you look at the test mission I posted you just set them to autolase and they will do anything in range they have LOS on and you go from there. script has the example how to tell them to stop, how to target just troops, _unit_ names set with hpriority and priority labels, etc.

It's a script that has JTAC functionality. You can look at the triggers in the mission above to see how to load it (it requires MIST as well) and set units as JTAC's. In the mission above I was testing the functionality I was adding to allow telling a unit to stop lasing and labeling units as priorities. Anyway as I have it set up use the F10 menu to tell them to start lasing. After that you can flip them on or off at will. I think in its last state they're targeting just 'troop', but you can change it to 'all' or 'vehicle'. I ptefer it because after tearing my hair out with the built in system that seems not to work I found CTLD does actually work... I think Ciribob merged both pieces of functionality in this weekend, so it should all be there

That looks like is _should_ work from what I remember... There's always CTLD... Hoover test.miz

For ground JTAC: http://forums.eagle.ru/showthread.php?p=2668836 I have never been able to get an AFAC to lase; for that and even ground JTAC's I have been using CTLD of late. Far more reliable.

Nice! Thanks!

Maybe MiG-21Bis if not A-10C....

I'm 99.999% certain I've seen heaters track flares prior to launch.

On second thought, do it like this: ctld.JTACAutoLaseStop('AFAC') ctld.JTACAutoLaseStop('AFAC1')

Here EasyEB, try this out: https://github.com/jmontleon/DCS-CTLD/commit/ba850b7cf6cae686dbdcb953f55f5a178d478fcc is all it took to implement a way to stop JTACS. This branch has all both the priority system and means to stop the jtac: https://github.com/jmontleon/DCS-CTLD/tree/all-improvements https://raw.githubusercontent.com/jmontleon/DCS-CTLD/all-improvements/CTLD.lua The attached mission gives an example of how to turn JTACS on and off on the fly via the radio message. Basically just do this to stop them ctld.jtacStop['AFAC'] = true ctld.jtacStop['AFAC1'] = true where AFAC and AFAC1 are the groupnames of my JTAC's. Hoover test.miz

EasyEB think I have something that will work. Want to play with it some more. Basically you have the JTACAutolase function forever looping around until the unit dies/deactivates at which time the function returns. What's needed is a way to make it return without the unit going away. My thought it to do something like this at the top of the JTACautolase function: if JTAC_Sleep == _jtacGroupName then ctld.cleanupJTAC(_jtacGroupName) return end Then you can just use the DO script function to make JTAC_Sleep = "JTACGROUPname", maybe sleep for some seconds and JTAC_Sleep = nil return it to nil so you can call him back up; I can like put that all that in a function so you just say ctld.jtac_sleep('JTACNAME') and the rest is handled behind the scenes... more or less already works but its too late and I'm too tired to finish today. nevertheless, probably before the weekend is over I'll have something for you to try.

How do you fire the Gsh-23? I can fire the wing mounted weapons, but something is eluding me for the gun.

Think it's a bug. I can't get _any_ AFAC to lase. I started using CTLD instead. Made some enhancements recently, to add prioritizing targets, though that's not in Ciribob's repo at present. You can either get his or look back on the thread for the changes I've made. http://forums.eagle.ru/showthread.php?t=141297