Steggles

isTargetDetected doesn't work with friendly units either :-( Is there any other way I can check this? I've looked thru the wiki but couldn't find anything. If all else fails I'll just check distance between the friendly unit and radar.

Thanks mate! Just tested out the getDetectedTargets and it does only detect enemies. I'll have a fiddle with isTargetDetected tomorrow. If it can detect a friendly that I know the name / ID of, it'll still do what it need it to. Thanks heaps for your help! Solved my problems.

Thank you sir!! Its a step in the direction I was after. The getDetectedTargets is what I think I'm after (every aircraft currently detected by the radar) Is there any particular reason isTargetDetected would be used apart from a trigger being set for when a particular unit is detected?

I believe the main hold up for the F/A 18 is the A-G radar, and judging by the advancements they have made in 2015, in 2016 it could very well happen.

Is there a simple way to check if an EWR / AWACS unit has detection on any units and retrieve information (coalition, air-frame, position, heading and speed) on all detected aircraft? I would prefer it be done using a information directly from the EWR unit if possible, rather then just checking if its within a certain range of the EWR unit. I've looked at a few of the EWR / AWACS scripts out there, and they are far beyond the complexity I'm after. If I can just get the above mentioned information I can do what I need with it. Thanks Steggles EDIT: Or if someone could point me towards documentation on the API on EWR / AWACS units would be great too.

Slightly off topic, but cause it concerns views.lua and Zeus is active here, I believe this trackIR fix will help too, if it was added as standard. http://forums.eagle.ru/showpost.php?p=2616849&postcount=1

I won't bother with my screenshot. He may as well copied that one from my computer :-)

I can confirm I have the same problem using trackIR 5. EDIT: Didn't read the last bit of your post. Thanks for the fix.

I believe it was said somewhere that the IFF would not be functioning when the beta was released. I can't remember where I seen it written.

I'm in the wrong time zone. 1600 ATM on Christmas Day. My F5 key is going to break soon.

ATM, Nevada is still in Alpha. So the mission availability is limited. Most of the ED modules have instant action missions available, but most of the 3rd party ones do not (You can always look in the user files for missions people have done, and some people have gotten creative with the multiplayer missions). It's my belief that the map was created primarily as a training map, however, the ability of the human mind to create things can easily change this. Considering you have a budget, if you are mainly wanting combat missions, it's my opinion you shouldn't purchase Nevada yet, and wait until after the Alpha is complete and missions are more widely available. It is a great map thou, and ED have done a great job. No complaints so far apart from the lack of airfield lights at night (It is alpha, so I can live with it). The FC3 missions will keep you going for a while, if you're interested in trying all the FC3 aircraft outside of the Nevada alpha (1.5 and 1.2). I haven't tried the FC3 campaigns in 1.5 thou, so maybe someone else can comment if they are working correctly. Anyways, that's my 2 cents, good luck in your hunt for answers and hope you enjoy whatever you decide to buy.

The 'L' is not radar, it is laser illumination. Meaning a laser is painting your aircraft, very different from a radar threat. Also, I think the red missile launch light turns off 10 seconds after the detected missile's rocket motor stops burning. Don't have the manual in front of me so can't check the exact timeframe. The A10's MWS is different system to the f15 etc. All it detects is the infra-red of a missiles rocket motor, and when this is detected, it sounds the warning. This is why you get warnings regardless if the missile was launched at you or not. It has no way of distinguishing. Edit: I believe the red light starts flashing as soon as a launch is detected.

Nope. Try setting system time 1 day ahead and start DCS. The updater should start. Failing that, use the updater in the install directory.

Cheers Bignewy

Is the updater being throttled or is it just a heavy server load? I'm flat out getting 90 KB's on the update download :-(

I believe that the fc downloadable files are for the stable release (currently 1.2.x) and for the 1.5 beta it has to be done thru the module manager. Someone feel free to correct me if I'm wrong Cheers

My 3 screen setup works good. I've got 2x 4K monitors and a 3rd smaller one, with the main view port in the centre. I'm at work ATM, should be finished in around 8 hours. I'll check back here when I'm finished and if you haven't resolved the problem by then, I'll pass on my lua file setup for your dimensions to try.

Judging on the application and web app that they have for the buddy spike 24/7 campaign, I'm guessing you can. As for how, I'm in the dark as much as you.

Maddog Simulations are worth a look for you Crunchy. They are more of a club then a squadron, and are happy for the casual players to join too. They also have internal squadrons for all DCS modules should someone want to take things more seriously. Check them out here: http://www.maddog-simulations.com/index.php

I read the newsletter as it's nearing final release, but as they state they are releasing new versions next week. In my eyes I see that as a new version of the beta. And I kinda hope that is the case, because there's a lot of work to do before I see it suitable for a public 'stable' build.

Oh good. Thought it was just my client being retarded. The entire MP interface is being retarded for me.

Ground effect as in with choppers? Yeah it is. Wake turbulence I'm not too sure about.

There is a sticky thread in this very forum about that. It's a known problem with the protection system.

+1 for this. Editing lua files for each module gets a bit tedious after a while.

It makes the pointer invisible. Not stops you from looking around the cockpit if mouse look is enabled.